DFHSOxxxx messages

Start of changeDFHSO0001End of change
Start of changeapplid An abend (code aaa/bbbb) has occurred at offset X'offset' in module modname.End of change
Start of change
Explanation:

An abnormal end (abend) or program check has occurred in module modname. This implies that there may be an error in the CICS code. Alternatively, unexpected data has been input, or storage has been overwritten.

The code aaa/bbbb is a 3-digit hexadecimal MVS code (if applicable), followed by a 4-digit alphanumeric CICS code. The MVS code is a system completion code (for example, 0C1 or D37). If an MVS code is not applicable, this field is filled with three hyphens. The CICS code is an abend code or a number referring to a CICS message (for example, AKEA is a CICS abend code; 1310 refers to message DFHTS1310).

End of change
Start of change
System action:

An exception entry is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case CICS could be terminated by the caller ( for example, the domain manager, DFHDMDM). A message is issued to this effect.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

Notify the system programmer. If CICS is still running, it is necessary to decide whether to terminate CICS.

Look up the MVS code, if there is one, in the relevant MVS codes manual.

Next, look up the CICS alphanumeric code. This tells you, for example, whether the error was a program check, an abend, or a runaway, and may give you some guidance concerning user response.

If module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.
If you cannot run without the full use of module modname you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS® Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSOCKEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeaaa/bbbb,End of changeStart of changeX'End of changeStart of changeoffset', End of changeStart of changemodnameEnd of change

Start of changeDFHSO0002End of change
Start of changeapplid A severe error (code X'code') has occurred in module modname.End of change
Start of change
Explanation:

An error has been detected in module modname. The code X'code' is the exception trace point ID which uniquely identifies what the error is and where the error was detected.

End of change
Start of change
System action:

An exception entry (code X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.

Start of changeIf the exception entry made in the trace table has a trace ID with a value of X'0425', message DFHKE0501 was issued by the CICS Kernel earlier during CICS initialization.End of change

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

This indicates a possible error in CICS code. The severity of its impact depends on the importance of the function being executed at the time of the error.

Start of changeIf the exception entry made in the trace table has a trace ID with a value of X'0425', further information can be found in message DFHKE0501 issued by the CICS Kernel earlier during CICS initialization.End of change

CICS may not have been terminated. If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot run without the full use of module modname, you should bring CICS down in a controlled shutdown.

You need further assistance from IBM to resolve this problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSODM, DFHSOL, DFHSOCK, DFHSORD, DFHSOIS.End of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changecode',End of changeStart of changemodnameEnd of change

Start of changeDFHSO0004End of change
Start of changeapplid A possible loop has been detected at offset X'offset' in module modname.End of change
Start of change
Explanation:

A CICS function is taking more time to process than CICS expects. A possible loop has been detected in module modname at offset X'offset'. This is the offset of the instruction which happened to be executing at the time when the error was detected.

End of change
Start of change
System action:

An exception entry is made in the trace table.

A system dump is taken unless you have specifically suppressed the dump (by a user exit program at the XDUREQ exit, in the dump table or by global system dump suppression). CICS processing continues unless you have specified in the dump table that CICS should terminate.

Message DFHME0116 is normally produced containing the symptom string for this problem.

End of change
Start of change
User response:

If CICS has not been terminated, it is necessary to decide whether the problem is serious enough to bring CICS down.

Since some CICS functions can use a lot of CPU time, this message may have been caused by a long-running function, and there may not be an error. Usually, CICS purges a CICS function which exceeds the runaway task time interval that you have specified in the ICVR system initialization parameter. This means that execution of module modname is terminated and CICS continues.

If you have specified system initialization parameter ICVR=0 and you consider that module modname is looping, you must terminate CICS in order to terminate the runaway function.

If CICS has terminated module modname, and you consider that it was not a runaway, you should increase the value of the ICVR system initialization parameter. You have to close down CICS at a suitable time to do this permanently. You can change the ICVR time interval temporarily online using the CEMT transaction.

If raising the ICVR time does not solve the problem, you may need further assistance from IBM to resolve the problem. See CICS Problem Determination Guide for guidance on how to proceed.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSOCK, DFHSOSEEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'offset', End of changeStart of changemodnameEnd of change

Start of changeDFHSO0100IEnd of change
Start of changeapplid Sockets domain initialization has started.End of change
Start of change
Explanation:

This is an informational message indicating that sockets domain initialization has started.

End of change
Start of change
System action:

System initialization continues.

End of change
Start of change
User response:

None. The message can be suppressed with the system initialization parameter MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSODMEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHSO0101IEnd of change
Start of changeapplid Sockets domain initialization has ended.End of change
Start of change
Explanation:

This is an informational message indicating that sockets domain initialization has completed successfully.

End of change
Start of change
System action:

System initialization continues.

End of change
Start of change
User response:

None. The message can be suppressed with the system initialization parameter MSGLVL=0.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSODMEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHSO0102End of change
Start of changedate time applid An OpenEdition Assembler Callable Service error (code X'code') has occurred on receipt of a severe TCP/IP return code; the TCPIPSERVICE tcpipservice on port portnumber at IP address ipaddress will be closed.End of change
Start of change
Explanation:

An error has been detected in DFHSOLS. The error has been caused by a severe return code received from TCP/IP.

End of change
Start of change
System action:

An exception entry X'code' is made in the trace table. No system dump is taken, unless you have specifically requested a dump in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate.

The TCPIPSERVICE tcpipservice on port portnumber at the specified IP address will be shutdown. When this is complete then message DFHSO0108 will be issued.

End of change
Start of change
User response:

This error could have been returned if TCP/IP had been shutdown, for example. The exception trace entry will tell you which service routine was called and the return values that were returned. Refer to the OS/390 OpenEdition Messages and Codes book to determine the cause of the error.

The TCPIPSERVICE tcpipservice will be closed, and after the TCP/IP region has been restarted the closed TCPIPSERVICE should be reopened. At this point normal work can resume on the TCPIPSERVICE.

End of change
Start of change
Destination:

Console and Transient Data Queue CSOO

End of change
Modules:

Start of changeDFHSOLSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changecode', End of changeStart of changetcpipservice,End of changeStart of changeportnumber, End of changeStart of changeipaddressEnd of change

Start of changeDFHSO0103End of change
Start of changeapplid ENCRYPTION=level is not available on this system.End of change
Start of change
Explanation:

The ENCRYPTION=level system initialization parameter was specified, where level may be STRONG or NORMAL, but the necessary feature to implement it was not installed on your system.

End of change
Start of change
System action:

Sockets Domain initialization fails, and CICS terminates.

End of change
Start of change
User response:

If you wish to use STRONG encryption with the secure sockets layer, you must order and install the North American Secure Encryption feature. This OS/390 feature is only available in the United States of America and Canada.

If the feature is unavailable, you must specify ENCRYPTION=NORMAL, which is the default.

In France, you must specify ENCRYPTION=WEAK unless you have ordered and installed the standard encryption feature for OS/390, when you may specify ENCRYPTION=NORMAL.

End of change
Start of change
Destination:

Console Routecodes 2, 9, 10 and 11

End of change
Modules:

Start of changeDFHSODMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changelevelEnd of change

Start of changeDFHSO0104End of change
Start of changeapplid Secure sockets program pgmname could not be loaded. Secure Sockets Layer is not available.End of change
Start of change
Explanation:

The program module pgmname, which is required to implement the secure sockets layer, could not be loaded.

If pgmname is GSKCMS, GSKSSL, or GSKX509, the System SSL component of OS/390 is not available in your release of OS/390, or it has not been installed properly. (This component is only available in OS/390 Version 2 Release 7 and later releases.)

End of change
Start of change
System action:

System initialization continues, but support for the secure sockets layer is not enabled.

End of change
Start of change
User response:

If this message is preceded by message DFHSO0103, try restarting CICS with ENCRYPTION=NORMAL.

If pgmname is GSKCMS, GSKSSL, or GSKX509, ensure that the System SSL library is available to CICS. For z/OS releases prior to Version 1 Release 6, this library is prefix.SGSKLOAD, where prefix is defined by the installation. For z/OS Version 1 Release 6 and later, this library is prefix.SIEALNKE, where prefix is defined by the installation. You should ensure that it is installed in the system linklist or referenced in the STEPLIB concatenation in the CICS JCL. If it is included in the CICS STEPLIB the library must be APF-authorized.

End of change
Start of change
Destination:

Console Routecodes 2, 9, 10 and 11

End of change
Modules:

Start of changeDFHSODMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changepgmnameEnd of change

Start of changeDFHSO0105End of change
Start of changeapplid ENCRYPTION=level is not available on this system. ENCRYPTION=WEAK is used instead.End of change
Start of change
Explanation:

The ENCRYPTION=NORMAL system initialization parameter was specified, but the necessary feature to implement it was not installed on your system, and is not available to be ordered at your level of operating system.

End of change
Start of change
System action:

The lower level of encryption corresponding to ENCRYPTION=WEAK is used instead.

End of change
Start of change
User response:

None. The encryption support required for ENCRYPTION=NORMAL will be available in OS/390 Version 2 Release 8. With that level of operating system, the system initialization parameter will be honored and this message will not appear.

End of change
Start of change
Destination:

Console Routecodes 2, 9, 10 and 11

End of change
Modules:

Start of changeDFHSODMEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changelevelEnd of change

Start of changeDFHSO0106End of change
Start of changedate time applid An OpenEdition Assembler Callable Service error (code X'code') has occurred in module modname.End of change
Start of change
Explanation:

An error has been detected in module modname. The code X'code' is the exception trace point ID which uniquely identifies what the error is and where the error was detected.

End of change
Start of change
System action:

An exception entry (code X'code' in the message) is made in the trace table. A system dump is taken, unless you have specifically suppressed dumps in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate. If appropriate, an error return code is sent to the caller of this domain. In this case, CICS could be terminated by the caller (for example, the domain manager, DFHDMDM). A message is issued to this effect.

Start of changeMessage DFHME0116 is normally produced containing the symptom string for this problem.End of change

End of change
Start of change
User response:

This indicates a possible error in CICS code or the called Assembler Callable Service routine. The exception trace entry will tell you which service routine was called and the return values that were returned. Refer to the OS/390 OpenEdition Messages and Codes book to determine the cause of the error. The severity of its impact depends on the importance of the function being executed at the time of the error.

CICS may not have been terminated. If the message occurs once and module modname is not crucial to the running of your CICS system, you may decide to continue to run and bring CICS down at a convenient time to resolve the problem.

If the message recurs or if you cannot run without the full use of module modname, you should bring CICS down in a controlled shutdown.

End of change
Start of change
Destination:

Console and Transient Data Queue CSOO

End of change
Modules:

Start of changeDFHSOCKEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeX'End of changeStart of changecode', End of changeStart of changemodnameEnd of change

Start of changeDFHSO0107End of change
Start of changedate time applid TCPIPSERVICE tcpipservice has been opened on port portnumber at IP address ipaddress.End of change
Start of change
Explanation:

The TCPIPSERVICE tcpipservice has been opened on port portnumber at the IP address specified.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSOCKEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetcpipservice, End of changeStart of changeportnumber,End of changeStart of changeipaddressEnd of change

Start of changeDFHSO0108End of change
Start of changedate time applid TCPIPSERVICE tcpipservice on port portnumber at IP address ipaddress has been closed.End of change
Start of change
Explanation:

The TCPIPSERVICE tcpipservice on port portnumber on the specified IP address has been closed.

End of change
Start of change
System action:

CICS continues.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSOCKEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetcpipservice, End of changeStart of changeportnumber,End of changeStart of changeipaddressEnd of change

Start of changeDFHSO0109End of change
Start of changedate time applid The TCPIPSERVICE tcpipservice could not be opened because the port portnumber is already in use on the IP address ipaddress .End of change
Start of change
Explanation:

This message is issued when the open of a TCPIPSERVICE cannot be completed. The port number specified is already in use in combination with the IP address. By default, TCP/IP only allows one server to be listening on a port at any one time.

Specifically, this message is issued when the TCP/IP bind call fails with a return code of EADDRINUSE.

End of change
Start of change
System action:

The TCPIPSERVICE does not open, but remains closed. An exception trace entry is written detailing the return values from the TCP/IP bind call. An application using the EXEC API to set the TCPIPSERVICE open receives an RESP(INVREQ) RESP2(9).

End of change
Start of change
User response:

Check that there are no other TCPIPSERVICES open using the same port number and IP address as the failing one. If there is another TCPIPSERVICE open using the port, it must be closed before the new one can be opened.

If no TCPIPSERVICES are using the requested port, there may be another OS/390 application acting as a TCP/IP server already listening on the port. For example, the Lotus Go for OS/390 web server may be installed and running on port 80 on the same TCP/IP stack as CICS. Attempting to open a TCPIPSERVICE on port 80 will fail. Use the TSO command NETSTAT to display TCP/IP servers on the system. Choose an unused port for the TCPIPSERVICE.

If your OS/390 system has more than one TCP/IP stack you may specify another stack's IP address on the TCPIPSERVICE definition. This will allow you to install multiple TCPIPSERVICES each using the same port number. You may also configure support in TCP/IP for virtual IP addresses on a single system. This will also allow more than one TCPIPSERVICE to share the same port.

Finally, TCP/IP for OS/390 can be configured with port sharing. This allows multiple servers (TCPIPSERVICES) to use the same port with TCP/IP using load balancing to direct incoming connections to the set of servers on the port. With this enabled, multiple TCPIPSERVICES can each be opened on the same IP address with the same port.

End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSOCKEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetcpipservice, End of changeStart of changeportnumber,End of changeStart of changeipaddressEnd of change

Start of changeDFHSO0110End of change
Start of changedate time applid The TCPIPSERVICE tcpipservice cannot be opened on the IP address ipaddress because the address is unknown to TCP/IP.End of change
Start of change
Explanation:

Opening the TCPIPSERVICE has failed because the IP address specified on the definition is not known to TCP/IP.

This message is issued when the TCP/IP bind call fails with the return value of EADDRNOTAVAIL.

End of change
Start of change
System action:

The IP address must be a valid address known to TCP/IP. It is possible to configure multiple TCP/IP stacks for a single OS/390 system, or to have virtual IP addresses on a single stack. If the system only has one IP address then the IP address field of the TCPIPSERVICE definition can be Start of changeleft blank, or specified as ANY. This causes the bind to use the default IP address for the system.End of change To use an alternative, a valid address must be specified.

End of change
Start of change
User response:

Check that the address specified on the TCPIPSERVICE definition is known to TCPIP on the system. If it is not, then consult the OS/390 TCP/IP OpenEdition: Configuration Guide for information on defining IP address.

End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSOCKEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetcpipservice, End of changeStart of changeipaddressEnd of change

Start of changeDFHSO0111End of change
Start of changedate time applid Opening the TCPIPSERVICE tcpipservice has failed because the region jobname is not authorized to bind to port portnumber.End of change
Start of change
Explanation:

Opening the TCPIPSERVICE has failed because the jobname of the region is not authorized to use the port number specified.

Binding to port numbers below 1024 requires TCP/IP configuration directives specifying the CICS jobname to TCP/IP and associating it with the specified port. This may also be done for ports greater than 1024, thus a CICS region may also fail to open a port greater than 1024 if the port has been associated with another job.

This message is issued when the TCP/IP bind call fails with a return value of EPERM.

End of change
Start of change
System action:

The TCPIPSERVICE is not opened. If an application has used the EXEC API to open the TCPIPSERVICE, it receives RESP(INVREQ) RESP2(3) values.

End of change
Start of change
User response:

The CICS region's jobname must be authorized to open the specified port. Consult the OS/390 TCP/IP OpenEdition: Configuration Guide for details on how to do this.

End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSOCKEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetcpipservice, End of changeStart of changeportnumberEnd of change

Start of changeDFHSO0112End of change
Start of changedate time applid TCPIPSERVICE tcpipservice cannot be opened because TCPIP status is not OPEN.End of change
Start of change
Explanation:

Opening the TCPIPSERVICE has failed because TCPIP is currently not open. Either TCPIP=NO has been specified in the SIT or TCPIP has been dynamically closed using CEMT or an SPI command.

End of change
Start of change
System action:

The TCPIPSERVICE is not opened. If an application has used the EXEC API to open the TCPIPSERVICE, it receives RESP(INVREQ) RESP2(4) values.

End of change
Start of change
User response:

Open TCPIP and re-open the TCPIPSERVICE.

End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSORDEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHSO0113End of change
Start of changeapplid The IP address ip_address cannot be resolved to a host name by the gethostbyaddr function.End of change
Start of change
Explanation:

CICS has issued the TCP/IP function gethostbyaddr to resolve the IP address ip_address to a host name, but the call failed.

End of change
Start of change
System action:

An exception trace entry is made. CICS will continue to attempt to access the name server for subsequent requests.

End of change
Start of change
User response:

The gethostbyaddr function will usually perform a name server reverse lookup to resolve the IP address into a host name. This can fail if CICS is unable to contact a name server, or the name server does not know the correct host name to IP address mapping.

Check that the name server defined to TCP/IP in the /etc/resolv.conf file is valid and responding correctly. You can issue the TSO NSLOOKUP command to query the name server. If a SYSTCPD DD name has been defined in the CICS job, check that the file it references correctly defines the name server. If the name server is defined correctly to CICS then contact the administrator to determine why the IP address lookup has failed.

End of change
Start of change
Destination:

Console

End of change
Start of change
Modules:

DFHSOIS

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeip_addressEnd of change

Start of changeDFHSO0114End of change
Start of changedate time applid The socket listener cannot attach the transaction transaction, the TCPIPSERVICE tcpipservice will be closed.End of change
Start of change
Explanation:

The TCP/IP listener task has received a connection from a client but the attach for the transaction associated with the TCPIPSERVICE definition has failed. The associated transaction may not have been installed or the TCPIPSERVICE definition could have specified the wrong transaction.

End of change
Start of change
System action:

The TCPIPSERVICE that is defined on the port that the connection arrived on is closed. The socket accepted for the client is closed.

End of change
Start of change
User response:

Determine why the attach for the transaction has failed. Correct the error and re-open the TCPIPSERVICE.

End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSOCKEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changetransaction, End of changeStart of changetcpipserviceEnd of change

Start of changeDFHSO0115End of change
Start of changedate time applid CICS has registered the group name groupname with Work Load Manager. The TCP/IP host name genericname will become available for DNS connection optimization.End of change
Start of change
Explanation:

The group name has been registered with Work Load Manager for Domain Name Service (DNS) connection optimization. This occurs when a TCPIPSERVICE is opened where its name begins with the character 'D'. The new generic TCP/IP host name becomes available for clients to use to access the CICS system, and any others that have registered with the named group name.

End of change
Start of change
System action:

CICS has issued the Work Load Manager macro IWMSRSRG to register the specified group name for DNS connection optimization. This only occurs when the name of the TCPIPSERVICE begins with a 'D'. Work Load manager registration only occurs once for a given group name. If multiple TCPIPSERVICES define the same group name, then registration will only occur once.

The group name registered is taken from a combination of part of the name of the TCPIPSERVICE and the transaction defined for the TCPIPSERVICE. Any characters of the name following a dot '.' are concatenated with the transaction identifier to form the group name. For example, a TCPIPSERVICE has the name D1.CICS and is defined with the transaction IIOP (the IIOP transaction being an alias of the CICS-supplied CIRR transaction). The group name generated is 'CICSIIOP'. If the TCPIPSERVICE name does not contain a dot, then only the transaction identifier is used. For example, a TCPIPSERVICE with a name of 'DYNWEB' and a transaction of WWW will generate a registration for the group 'WWW'.

The group name registered effectively becomes a new name in the sysplex TCP/IP domain. When multiple CICS systems in a sysplex each register with the same group name, the DNS server uses Work Load Manager to resolve the group name into one of the IP addresses of the associated systems. The IP address returned is that of the system that is most eligible according to Work Load Manager's load balancing rules. For example, two OS/390 systems in a sysplex are mvs1.plex.hursley.ibm.com and mvs2.plex.hursley.ibm.com; and on each system, CICS registers with the group name cicsiiop. The new name cicsiiop.plex.hursley.ibm.com is dynamically added to the DNS name server's tables. Client TCP/IP applications can use this name instead of the name of one of the specific OS/390 images. When a client resolves the name to an IP address using the DNS, it will get the IP address of the most eligible system. Since the DNS dynamically knows when systems register and deregister, additional CICS systems can be registered as required to expand the list of available IP addresses returned for a group name. If a system fails, its IP address will be removed from the DNS server's list of associated addresses for any groups with which it was registered.

End of change
Start of change
User response:

No user action is necessary.

End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSOCKEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changegroupname, End of changeStart of changegenericnameEnd of change

Start of changeDFHSO0116End of change
Start of changedate time applid CICS has deregistered the group name groupname with Work Load Manager.End of change
Start of change
Explanation:

The group name has been deregistered from Work Load Manager. This CICS system will no longer participate in connection optimization in the group specified. This occurs when a TCPIPSERVICE is closed where its name begins with a 'D'.

End of change
Start of change
System action:

The Work Load Manager IWMSRDRS call is made to deregister the group name. This will remove the IP address of the system from the DNS server's table associated with the group name.

If more than one open TCPIPSERVICE share the same group name, then the WLM deregistration only occurs when the last one is closed.

End of change
Start of change
User response:

Check the availability of the name server.

End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSOCKEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changegroupnameEnd of change

Start of changeDFHSO0117End of change
Start of changeapplid Unable to determine the TCP/IP host name. OpenEdition return code X'retcode', reason code X'rc'.End of change
Start of change
Explanation:

OpenEdition has returned a non-zero return code/reason code to a gethostname call during Listener initialization or has returned a blank hostname.

End of change
Start of change
System action:

Listener initialization continues.

End of change
Start of change
User response:

Determine the reason for the gethostname failure. The return code and reason code included in the message text are described in the z/OS UNIX System Services Messages and Codes manual.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSOLSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeX'retcode', End of changeStart of changeX'End of changeStart of changercEnd of changeStart of change'End of change

DFHSO0118
applid The GETHOSTBYADDR call to resolve IP address IP_ADDRESS to a host name took over 3 seconds to complete.
Explanation:

CICS has issued the TCP/IP function gethostbyaddr to resolve the IP address ip_address to a host name. This call took greater than three seconds during which time the sockets TCB was blocked. During this time no socket IO was possible.

System action:

CICS continues.

User response:

The gethostbyaddr function will usually perform a name server reverse lookup to resolve the IP address into a host name. This call took over three seconds to complete. The gethostbyaddr function is most commonly driven by EXEC CICS EXTRACT TCPIP CLIENTNAME.

Check that the name server defined to TCP/IP in the /etc/resolv.conf file is valid and responding correctly. You can issue the TSO NSLOOKUP command to query the name server. If a SYSTCPD DD name has been defined in the CICS job, check that the file it references correctly defines the name server. If the name server is defined correctly to CICS then contact the administrator to determine why the IP address lookup failed to respond in a timely fashion. The TCP/IP RESOLVERTIMEOUT parameter can be used to control the duration of a gethostbyaddr call.

Destination:

Console

Modules:

DFHSOIS

XMEOUT Parameters:applid, ip_address

Start of changeDFHSO0119End of change
Start of changeapplid Unable to register service servicename for WLM DDNS on host hostname.End of change
Start of change
Explanation:

During activation of a TCPIPSERVICE, the Sockets Domain was unable to locate a TCP/IP hostname. Without a hostname, CICS cannot obtain the information necessary for registration with WLM DDNS.

End of change
Start of change
System action:

TCPIPSERVICE activation continues, but this service is not registered with WLM DDNS.

End of change
Start of change
User response:

Determine why no hostname was returned. Message DFHSO0113 may have preceded this message. Once the problem has been rectified, re-install the TCPIPSERVICE.

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSOLSEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changeservicename, End of changeStart of changehostnameEnd of change

Start of changeDFHSO0120End of change
Start of changeapplid numtcbs TCBs are initialized for SSL processing.End of change
Start of change
Explanation:

The specified number (numtcbs) of TCBs have been attached and initialized to perform Secure Sockets Layer processing for CICS.

End of change
Start of change
System action:

CICS can handle numtcbs simultaneous SSL sessions.

End of change
Start of change
User response:

None.

End of change
Start of change
Destination:

Console Routecodes 2 and 10

End of change
Modules:

Start of changeDFHSOSEEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changenumtcbsEnd of change

Start of changeDFHSO0121End of change
Start of changeapplid No TCBs have been initialized for SSL processing. Secure Sockets Layer has been deactivated.End of change
Start of change
Explanation:

CICS requires at least one TCB to be successfully initialized to handle the TCP/IP Secure Sockets Layer, but it has been unable to initialize any.

End of change
Start of change
System action:

CICS cannot handle any SSL sessions, so attempts to open TCPIPSERVICEs which specify SSL(YES) or SSL(CLIENTAUTH) will fail.

End of change
Start of change
User response:

The REGION size of the CICS address-space is probably too small to allow CICS Secure Sockets Layer to be initialized. Restart CICS with a larger REGION size. None.

End of change
Start of change
Destination:

Console Routecodes 2 and 10

End of change
Modules:

Start of changeDFHSOSEEnd of change

Start of changeXMEOUT Parameter:End of changeStart of change End of changeStart of changeapplidEnd of change

Start of changeDFHSO0122End of change
Start of changedate time applid SSL request from ipaddr on TCPIPSERVICE(service) rejected because of insufficient TCBs.End of change
Start of change
Explanation:

An Secure Sockets Layer connection from a client with address ipaddr was received on TCPIPSERVICE(service), but there were no available TCBs to process the request.

End of change
Start of change
System action:

The socket for the connection is closed. No message is sent to the client because the client expects the response to be encrypted by SSL, but SSL services cannot be provided.

End of change
Start of change
User response:

If this message occurs frequently, consider raising the value of the MAXSSLTCBS system initialization parameter.

End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSOSEEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changeipaddr, End of changeStart of changeserviceEnd of change

Start of changeDFHSO0123End of change
Start of changedate time applid Return code rc received from function '{unknown | gsk_environment_init |gsk_environment_open | gsk_environment_close | gsk_secure_socket_init | gsk_secure_socket_open |gsk_secure_socket_close | gsk_secure_socket_read | gsk_secure_socket_write |gsk_attribute_set_buffer | gsk_attribute_set_callback | gsk_attribute_set_enum |gsk_attribute_set_numeric_value}' of System SSL. Reason: {Unrecognized return code | Key database not found | Key database access not authorized | Invalid password for key database | Expired password for key database | Stashed password file not found | Session timeout value is invalid | An I/O error occurred | An unknown error occurred |Invalid distinguished name | No common ciphers negotiated | No certificate available | Server certificate rejected by client | Root certificate authority not supported | Unsupported operation | Invalid certificate signature | SSL protocol violation | Not authorized | Self-signed certificate | Invalid session state |Handle creation failed | No private key |Untrusted Certificate Authority | Certificate date invalid | Invalid cipher suite |Handshake abandoned by client | Cannot open key database | Host certificate not yet valid | Certificate parsing error | Certificate is revoked |LDAP server is inactive | Unknown certificate authority | Internal error on partner | Unknown alert received | Client authentication alert | Incorrect key usage | Server name not recognized}. Client: clientaddr, TCPIPSERVICE: tcpipservice.End of change
Start of change
Explanation:

A non-zero return code rc was received from the specified function of the Start of changez/OSEnd of change System SSL service. A brief interpretation of the return code is shown. The service was processing a connection Start of changewith a partnerEnd of change at IP address clientaddr to TCPIPSERVICE tcpipservice.

End of change
Start of change
System action:

The secure sockets operation is abandoned. A sockets domain severe error message, DFHSO0002, may be produced with error code X'080C'.

End of change
Start of change
User response:

If this message is not accompanied by message DFHSO0002, the error is probably due to some unexpected action by the connected Start of changepartnerEnd of change, and this message is for information only. If this message is accompanied by message DFHSO0002, the error is probably due to some sort of configuration error. Use the description in the message to determine what is wrong. For descriptions of the return code rc, see the z/OS System SSL Programming Guide, Start of changeSC24-5901-03End of change. For further guidance see the CICS Internet Guide.

Note:
Start of change
If the brief interpretation of the return code is Certificate date invalid the certificate may either have expired or be not yet valid, and may refer to either the local certificate or the remote partner's certificate.
End of change
End of change
Start of change
Destination:

CSOO

End of change
Modules:

Start of changeDFHSOSEEnd of change

Start of changeStart of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changedate, End of changeStart of changetime,End of changeStart of changeapplid, End of changeStart of changerc, End of changeStart of change{1=gsk_initialize,End of changeStart of change2=gsk_get_cipher_info, End of changeStart of change3=gsk_get_dn_by_label,End of change Start of change4=gsk_secure_soc_init, End of changeStart of change5=gsk_secure_soc_read,End of changeStart of change6=gsk_secure_soc_write, End of changeStart of change7=gsk_secure_soc_close}, End of changeStart of change{0=Unrecognized return code, End of changeStart of change1=Key database not found, End of changeStart of change2=Key database access not authorized, End of change Start of change3=Invalid password for key database, End of changeStart of change4=Expired password for key database, End of changeStart of change5=Stashed password file not found, End of changeStart of change6=Session timeout value is invalid, End of change Start of change7=An I/O error occurred, End of changeStart of change8=An unknown error occurred,End of changeStart of change16=Invalid distinguished name, End of changeStart of change17=No common ciphers negotiated, End of changeStart of change18=No certificate available, End of changeStart of change19=Server certificate rejected by client, End of change Start of change20=Root certificate authority not supported, End of changeStart of change21=Unsupported operation, End of changeStart of change22=Invalid certificate signature,End of change Start of change23=Peer system not recognized, End of changeStart of change24=Not authorized,End of changeStart of change25=Self-signed certificate, End of changeStart of change26=Invalid session state, End of changeStart of change27=Handle creation failed,End of changeStart of change28=No private key, End of changeStart of change29=Untrusted Certificate Authority, End of changeStart of change30=Certificate date invalid, End of changeStart of change31=Invalid cipher suite,End of changeStart of change32=Handshake abandoned by client, End of changeStart of change33=Cannot open key database, End of changeStart of change34=Host certificate not yet valid, End of changeStart of change35=Certificate parsing error,End of change36=Certificate is revoked, 37=LDAP server is inactive, 38=Unknown Certificate Authority, 39=Internal error on partner, 40=Unknown alert received, 41=Client authentication alert, 42=Incorrect key usage, 43=Server name not recognized}, Start of changeclientaddr, End of change Start of changetcpipserviceEnd of changeEnd of change

Start of changeDFHSO0124End of change
Start of changeapplid The MAXSOCKETS system initialization parameter has a value of mmmmm which exceeds the MAXFILEPROC value of nnnnn. The MAXSOCKETS value has been set to the lower value.End of change
Start of change
Explanation:

The value specified in the MAXSOCKETS system initialization parameter is greater than the value specified in the z/OS UNIX System Services MAXFILEPROC option.

CICS has attempted to set the MAXSOCKETS value higher than the MAXFILEPROC value, but has been unable to do so because the userid under which CICS is running does not have superuser authority.

End of change
Start of change
System action:

CICS continues execution with the MAXSOCKETS value set equal to the MAXFILEPROC value.

End of change
Start of change
User response:

You may:

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSOISEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changemmmmm,End of changeStart of changennnnnEnd of change

Start of changeDFHSO0125End of change
Start of changeapplid The MAXSOCKETS parameter retrieved from the catalog has a value of mmmmm which exceeds the MAXFILEPROC value of nnnnn. The MAXSOCKETS value has been set to the lower value.End of change
Start of change
Explanation:

The value of the MAXSOCKETS system initialization parameter retrieved from the catalog during a warm or emergency restart is greater than the value specified in the z/OS UNIX System Services MAXFILEPROC option.

CICS has attempted to set the MAXSOCKETS value higher than the MAXFILEPROC value, but has been unable to do so, because the userid under which CICS is running does not have superuser authority.

This situation may arise when:

End of change
Start of change
System action:

CICS continues execution with the MAXSOCKETS value set equal to the MAXFILEPROC value.

End of change
Start of change
User response:

You may:

End of change
Start of change
Destination:

Console

End of change
Modules:

Start of changeDFHSOISEnd of change

Start of changeXMEOUT Parameters:End of changeStart of change End of changeStart of changeapplid, End of changeStart of changemmmmm,End of changeStart of changennnnnEnd of change

DFHSO0126 W
applid An attempt to create a socket has failed because the MAXSOCKETS limit has been reached.
Explanation:

An attempt to create a tcpip socket has failed as the number of open sockets in the system would exceed the current MAXSOCKETS value.

System action:

The socket is not opened and failure is reported.

User response:

Start of changeIf this behaviour is undesireable, use CEMT SET TCPIP to increase the number of sockets in the system.End of change

Destination:

Console

Modules:

DFHSOMG

XMEOUT Parameter: applid

Start of change
DFHSO0128A
applid Information to specify a bind to an LDAP server cannot be obtained from the PROXY segment of CRLPROFILE profile.
Explanation:

The CRLPROFILE system initialization parameter has been specified, but the information required by CICS and System SSL to perform a bind to an LDAP server cannot be obtained from the profile that it identifies.

CICS has attempted to extract the following information from the PROXY segment of the profile profile in the LDAPBIND class of the external security manager's database:

LDAPHOST
The Uniform Resource Locator (URL) of an LDAP server that contains certificate revocation information
BINDDN
The LDAP distinguished name of a user who is authorized to access certificate revocation lists in the specified LDAP server
BINDPW
The password used to authenticate the user specified by BINDDN.

Either the specified profile does not exist, or CICS does not have authority to access the profile, or one or more of the required components are missing from the profile.

System action:

The CICS SSL function cannot retrieve certificate revocation lists to determine whether certificates have been revoked. To prevent further error messages, the CRLPROFILE function has been disabled. Therefore CICS will be unable to check whether SSL certificates are revoked.

User response:

Ensure that the profile profile in the LDAPBIND class of the security manager is defined with a PROXY segment that contains all three required components. Also ensure that the CICS region userid had READ access to the profile, then restart CICS.

Destination:

Console Routecodes 2, 9 and 10

Modules:

DFHSOSE

XMEOUT Parameters: applid, profile

End of change
Start of change
DFHSO0129A
applid The LDAP server whose name was obtained from CRLPROFILE is inactive. Certificate revocation checks have been disabled.
Explanation:

The LDAP server, whose name was obtained from the PROXY segment of the external security manager's profile specified by the CRLPROFILE system initialization parameter, cannot be accessed.

System action:

The CICS SSL function cannot retrieve certificate revocation lists to determine whether certificates have been revoked. To prevent further error messages, the CRLPROFILE function has been disabled. CICS will not make any further attempts to acquire certificate revocation lists from the LDAP server. Therefore CICS will be unable to check whether SSL certificates are revoked.

User response:

To re-enable certificate revocation list checking, the LDAP server specified within the CRLPROFILE must be restarted. All CICS systems, that specify a CRLPROFILE definition that references this server, must then also be restarted.

Destination:

Console Routecodes 2, 9 and 10

Modules:

DFHSOSE

XMEOUT Parameter: applid

End of change
Start of change
DFHSO0130
date time applid A TCPIP ACCEPT call has failed. The TCPIPSERVCE tcpipservce on port portnumber at IP address ipaddress will be closed. The values returned are bpx_return_value(bpx return value), bpx_return_clode(bpx return code), and bpx_reason_code(bpx reason code).
Explanation:

A TCP/IP ACCEPT call has returned an error.

System action:

An exception trace entry is made in the trace table. No system dump is taken, unless you have specifically requested a dump in the dump table.

CICS continues unless you have specified in the dump table that CICS should terminate.

The TCPIPSERVICE tcpipservice on port portnumber at the specified IP address is shut down. When this shutdown is complete, message DFHSO0108 is issued.

The return value, return code, and reason code reported by UNIX System Services are displayed to aid with diagnostics.

User response:

Determine the reason for the ACCEPT failure. The return code and reason code included in the message text are described in the z/OS UNIX System Services Messages and Codes manual. A possible cause of this error is if TCP/IP has reached MAXSOCKETS. Check the system console for any messages issued by TCP/IP and take the recovery action indicated.

The TCPIPSERVICE tcpipservice is closed. After the TCP/IP problem has been resolved, you can reopen the closed TCPIPSERVCE.

Destination:

Console

Modules:

DFHSOLS

XMEOUT Parameter: date, time, applid, tcpipservice, portnumber, ipaddress, bpx return value, bpx return code, bpx reason code.

End of change
Start of change
DFHSO0135W
applid An attempt to switch to an S8 SSL TCB has failed because the request has timed out.
Explanation:

An attempt to switch to an S8 SSL TCB has failed because the request has timed out.

System action:

The SSL request is not performed and the task is purged.

User response:

Increase the number of S8 SSL TCBs available to the CICS sockets domain by changing the MAXSSLTCBS value, either in the SIT or via the CEMT SET DISPATCHER command.

Destination:

Transient Data Queue CSOO

Modules:

DFHSOSE

XMEOUT Parameter: applid.

End of change [[ Contents Previous Page | Next Page Index ]]