Server startup problems
When the Server encounters a problem during startup, it produces a C2RW message. These messages are described in the IBM® Security zSecure: Messages Guide. The following startup problems do not produce C2RW error messages.
- Attempts to start the server before z/OS®
UNIX System Services initialization
is complete (that is, too soon after IPL) result in message ICH408I.
ICH408I USER(C2RSERVE) GROUP(C2R) NAME(ZSECURE VISUAL SERVR) CL(FSOBJ ) INSUFFICIENT AUTHORITY TO DUBThe task runs, but not as an z/OS UNIX System Services process, which makes it useless. If you receive this message:
- Cancel the task.
- Wait for the BPX1004I message as described in Starting the Visual Server.
- Start the task again.
- Attempts to run the server when you are not allowed to use the
port number result in the following error message:
TCPIP Conn: can't bind to socket (errno 111)In this case, you might have reserved the TCP/IP port numbers used by the server using parameters in the PROFILE.TCPIP dataset. The commands can look similar to:PORT xxxx TCP C2RSERVE NOAUTOLOGorPORTRANGE xxxx yy TCP C2RSERVE NOAUTOLOGIn this case, the C2RSERVE jobname is the only ID allowed to open the port. Therefore, if the installation step runs with a different jobname, it receives a bind() errno=111 message.
To avoid this problem, base your protection of TCP/IP ports on userid, rather than jobname. See TCP/IP Security.
- Attempts to run the server while TCP/IP has not been started result
in the following error message:
S8E220:TCPIP Conn: Socket error 112In this case there might be problems with TCP/IP, or TCP/IP might not be active at all.
ICH420I PROGRAM CKGRACF FROM LIBRARY CKR.SCKRLOAD
CAUSED THE ENVIRONMENT TO BECOME UNCONTROLLED.
BPXP014I ENVIRONMENT MUST BE CONTROLLED FOR
SERVER (BPX.SERVER) PROCESSING.
This message might be accompanied by a dump file (CEEDUMP.timestamp) in the run directory. A dump that is written for this reason can be discarded.