Error scenarios and tracing
If the installed library has not been added to program control, this message appears in the JESMSGLG for the server task:
ICH420I PROGRAM IPVSRV FROM LIBRARY IPV.V1R10.SIPVMODA CAUSED
THE ENVIRONMENT TO BECOME UNCONTROLLED. BPXP014I ENVIRONMENT MUST
BE CONTROLLED FOR SERVER (BPX.SERVER) PROCESSING.Messages similar to the following might be generated if the user connecting to the server does not have read access to the SIPVMODA library:
ICH408I USER(BILLMAN ) GROUP(USERCOD ) NAME(MANDELLA, BILL ) 218
IPV.V1R10.SIPVMODA CL(DATASET ) VOL(COD035)
INSUFFICIENT ACCESS AUTHORITY
FROM IPV.V1R10.* (G)
ACCESS INTENT(READ ) ACCESS ALLOWED(NONE )
IEC150I 913-38,IFG0194E,BILLMAN,OS390,ISP19502,8E10,COD035,IPV.V1R10.SIPVMODAMessages on SYSLOG at the time of attempted connection, like the ones that are shown here, are generated when the relevant CONFIG contains an invalid library, or is missing a library from the SPAWN_STEPLIB statement:
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=EC6 REASON CODE=0B26C032
TIME=11.37.04 SEQ=38113 CPU=0000 ASID=00ED
PSW AT TIME OF ERROR 070C3000 82C44CE8 ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
DATA AT PSW 02C44CE2 - C06C18F2 0A0D41B0 D4D0180B
AR/GR 0: 00000000/00000026_00000648 1: 00000000/00000000_04EC6000
2: 01FF000C/00000000_0B26C032 3: 00000000/00000000_8286F5B8
4: 00000000/00000000_00000000 5: 00000000/00000000_00000000
6: 01FF000C/00000000_00000700 7: 01FF000C/00000000_09BFC3F8
8: 00000000/00000000_11F4B610 9: 00000000/00000000_163031FF
A: 00000000/00000000_11F4B610 B: 01FF000C/00000000_7FFC3A00
C: 00000000/00000000_02C47AC0 D: 00000000/00000000_16302200
E: 00000000/00000000_82C44CB0 F: 00000000/00000000_0B26C032
END OF SYMPTOM DUMP
If the above are not occurring, but connections are still not successful, shut down the server and start it again with tracing active. If using the supplied sample, this can be done on the start command. For example, S IPVSRV1,TRACE=D. This produces trace entries in the server task on the IPVTRACE DD.
A typical trace, with SSL active, before connections are made, looks similar to the one shown here. The main entries of interest confirming startup was successful are highlighted:
2018-11-29-10:54:39.442 [IPVSRV:266] Server built at: Nov 29 2018 10:54:03
2018-11-29-10:54:39.601 [IPVSRV:952] Record in length:1903
2018-11-29-10:54:39.601 [IPVSRV:969] Token: CONFIG Value: DEFAULT
2018-11-29-10:54:39.601 [IPVSRV:989] Config DEFAULT allocated.
2018-11-29-10:54:39.601 [IPVSRV:969] Token: SSL_REQUIRED Value: YES
2018-11-29-10:54:39.601 [IPVSRV:969] Token: WORKDIR Value: /etc/ipv/v110/ipvsrv1
2018-11-29-10:54:39.602 [IPVSRV:1070] Confirmed temporary write access ok dir=/etc/ipv/v110/ipvsrv1.
2018-11-29-10:54:39.602 [IPVSRV:969] Token: SPAWN_STEPLIB Value: IPV110SVC.BUILD.LOAD ...
2018-11-29-10:54:39.602 [IPVSRV:969] Token: CONFIG Value: FM
2018-11-29-10:54:39.602 [IPVSRV:989] Config FM allocated.
2018-11-29-10:54:39.602 [IPVSRV:969] Token: SPAWN_PROGRAM Value: FMNCSEP
2018-11-29-10:54:39.602 [IPVSRV:1089] Creating temp filename.
2018-11-29-10:54:39.602 [IPVSRV:1106] Created temporary spawn image file ok.
2018-11-29-10:54:39.602 [IPVSRV:1116] spawn_program /etc/ipv/v110/ipvsrv1/FMNCSEP
2018-11-29-10:54:39.602 [IPVSRV:1117] spawn_fn FMNCSEP
2018-11-29-10:54:39.602 [IPVSRV:969] Token: SPAWN_JOBNAME Value: FMCLIENT
2018-11-29-10:54:39.602 [IPVSRV:969] Token: SPAWN_STEPLIB Value: FMN.V16R1M0.OPTIONS...
2018-11-29-10:54:39.602 [IPVSRV:969] Token: SPAWN_PARMS_SECTION Value:
2018-11-29-10:54:40.495 [IPVSRV:1956] Environment open rc=0 Handle=16AB09A8 Ha=16AA6490
2018-11-29-10:54:40.495 [IPVSRV:1965] Set SSLV2 off rc=0
2018-11-29-10:54:40.495 [IPVSRV:1973] Set SSLV3 off rc=0
2018-11-29-10:54:40.495 [IPVSRV:1982] Set TLSV1 off rc=0
2018-11-29-10:54:40.495 [IPVSRV:1997] Certfile=/etc/ipv/v110/ipvsrv1/IPVSRVC3-IPVCERT.kdb
2018-11-29-10:54:40.495 [IPVSRV:1998] Set keyring rc=0
2018-11-29-10:54:40.495 [IPVSRV:2006] Set pw rc=0
2018-11-29-10:54:40.511 [IPVSRV:2014] Environment init rc=0 Handle=16AB09A8
2018-11-29-10:54:40.511 [IPVSRV:281] Mixed case password support is off
2018-11-29-10:54:40.512 [IPVSRV:1902] Set socket linger rc=0
2018-11-29-10:54:40.512 [IPVSRV:1906] Set socket reuseaddr rc=0
2018-11-29-10:54:40.512 [IPVSRV:1910] Set socket keepalive rc=0
2018-11-29-10:54:40.512 [IPVSRV:301] Launching accept thread socket 0, listen code 0
2018-11-29-10:54:40.512 [IPVSRV:513] Acceptor thread running.
2018-11-29-10:54:40.512 [IPVSRV:527] About to accept.If the highlighted statements are similar to the example that is shown here, all rc=0, then try to connect.
Several trace entries that are created by the server are similar to the ones that are shown here. Again, those that are of interest are highlighted.
2018-11-29-10:55:02.943 [IPVSRV:543] Connect received.
2018-11-29-10:55:02.943 [IPVSRV:549] Set client socket linger rc=0
2018-11-29-10:55:02.944 [IPVSRV:570] Thread launch
2018-11-29-10:55:02.944 [IPVSRV:527] About to accept.
2018-11-29-10:55:02.944 [IPVSRV:428] Conversation thread started.
2018-11-29-10:55:02.944 [IPVSRV:451] Server and peer on different hosts.
2018-11-29-10:55:02.944 [IPVSRV:1461] Outgoing message length=111, message=SSL=Y,
SERVERVERSION=01.01,SERVERNAME=IPVSRVC3,SYSNAME=z/OS,NODENAME=FMD2,
RELEASE=11.00,VERSION=01,MACHINE=2094
2018-11-29-10:55:02.944 [IPVSRV:1524] Sent 115 bytes
2018-11-29-10:55:02.945 [IPVSRV:2028] gsk_secure_socket_open rc=0
2018-11-29-10:55:02.945 [IPVSRV:2040] Set native socket rc=0
2018-11-29-10:55:02.945 [IPVSRV:2049] Set keyring label ADFzCC Server
Certificate rc=0
2018-11-29-10:55:02.945 [IPVSRV:2058] Set session type rc=0
2018-11-29-10:55:03.980 [IPVSRV:2081] Secure socket init rc=0
2018-11-29-10:55:03.980 [IPVSRV:1328] RecvSSL
2018-11-29-10:55:04.191 [IPVSRV:1360] Header indicates length 50
2018-11-29-10:55:04.722 [IPVSRV:1423] Incoming message: >>user=PROWSE3 pass=AXXXXXXX
config=UTCAPI DEBUG=YES<<
2018-11-29-10:55:04.723 [IPVSRV:1640] Uppercasing password 8 chars
2018-11-29-10:55:04.723 [IPVSRV:588] process_launch trying to match config UTCAPI.
2018-11-29-10:55:04.723 [IPVSRV:657] Parms: SOCKETH=00000001 ....
2018-11-29-10:55:04.723 [IPVSRV:658] Steplib: STEPLIB=IPV16SVC ...
2018-11-29-10:55:04.723 [IPVSRV:1828] Authenticated ok for user PROWSE3.
2018-11-29-10:55:04.724 [IPVSRV:1461] Outgoing message length=7, message=AUTH=Y
2018-11-29-10:55:04.724 [IPVSRV:1524] Sent 11 bytes
2018-11-29-10:55:05.282 [IPVSRV:702] gsk_secure_socket_close okay
2018-11-29-10:55:05.285 [IPVSRV:739] Spawned /etc/ipv/v110/ipvsrv1/IDIGMAIN Process 83886421
2018-11-29-10:55:05.285 [IPVSRV:745] Close client sock rc=0If the Spawned trace line is present, check the SYSLOG at the time of the spawn for any messages that are issued by a started task. If there are no log messages, then look for output that is produced by the spawned user. For instance, in the example that is shown here, the user PROWSE3 has generated some output. Once you have this information, and the server's IPV TRACE output, contact IBM® support.