Reason:
This message is issued in response to the TCPIP START command if an attempt to use the HPNS interface is made in an environment that does not support it.
System Action:
The TCPIP START command fails.
User Action:
Determine the correct interface type for the current operating system and environment. Issue another TCPIP START command using the TYPE=tttt operand with the correct type specified.
Reason:
This message is issued in response to a TCPIP START command when the HPNS interface to TCP/IP is unable to initialize because of one of the following reasons:
The interface was unable to obtain required storage.
The interface was unable to obtain required storage.
The interface was unable to load a required module. If the module name is EZASOH03, it probably indicates that IBM TCP/IP V3.2 is not installed on this system. Other names generally indicate that the required IBM C runtime libraries are not installed.
The interface was unable to locate the control blocks to obtain the required information.
The OPTIONS operand of the TCPIP START command specified keywords that are not recognized by the IUCV interface.
The named OPTIONS operand of the TCPIP START command was duplicated.
The PREFIX option of the TCPIP START command is not valid.
The NODE option of the TCPIP START command is not valid.
The PATH option of the TCPIP START command is not valid.
The interface was unable to load a required module.
The JOB option of the TCPIP START command is not valid.
The HOST option of the TCPIP START command is not valid.
The DOMAIN option of the TCPIP START command is not valid.
The DATADD option of the TCPIP START command is not valid.
The DATADSN option of the TCPIP START command is not valid.
An attempt to establish a connection to TCP/IP failed. The return code is displayed. The most likely reason is that the target TCP/IP address space is not active.
An attempt to create a socket failed. The return code is displayed.
An attempt to create a socket failed. The return code is displayed.
An attempt to create an AF_INET6 socket failed. The system has not been configured for AF_INET6 sockets to be created.
An attempt to destroy a socket failed. The return code is displayed.
An attempt to destroy a socket failed. The return code is displayed.
An attempt to obtain the local host IP address failed. The return code is displayed.
An attempt to obtain the local host IP address failed. The return code is displayed.
An attempt to obtain the local host domain name failed. The return code is displayed.
An attempt to obtain the local host domain name failed. The return code is displayed.
An attempt to obtain the local host domain name failed. The returned name is blank.
The SYSTCPD ddname is allocated as DD DUMMY, preventing the interface from obtaining necessary information from the TCPIP.DATA data set.
The indicated TCPIP.DATA data set could not be allocated DISP=SHR because it is in exclusive use by another user or job.
The indicated TCPIP.DATA data set could not be allocated DISP=SHR because a DYNALLOC failure occurred. The DYNALLOC error and information reason codes are displayed.
The indicated TCPIP.DATA data set could not be allocated DISP=SHR because the name is invalid or the data set could not be located.
A RDJFCB macro failed for the indicated TCPIP.DATA ddname.
The indicated TCPIP.DATA data set could not be opened.
The indicated TCPIP.DATA data set could not be opened because an ABEND occurred.
The indicated TCPIP.DATA data set could not be used because it had an invalid record format (not F, FB, V, or VB) or record length (F up to 255 and V from 4 to 259).
The indicated TCPIP.DATA data set had an I/O error during processing. The MVS SYNAD error message text is displayed.
The indicated source line in the TCPIP.DATA file had an error related to the TCPIPUSERID or TCPIPJOBNAME statement.
The indicated source line in the TCPIP.DATA file had an error related to the DOMAINORIGIN statement.
The indicated source line in the TCPIP.DATA file had an error related to the DATASETPREFIX statement.
The indicated source line in the TCPIP.DATA file had an error related to the HOSTNAME statement.
The indicated TCPIP.DATA file could not be allocated because the path name is invalid or the file could not be located.
The indicated TCPIP.DATA file could not be allocated because a DYNALLOC failure occurred. The DYNALLOC error and information reason codes are displayed.
The path name of an allocated TCPIP.DATA file could not be obtained because a DYNALLOC failure occurred. The DYNALLOC error and information reason codes are displayed.
System Action:
Initialization of TCP/IP fails. Depending on the error, it may be automatically retried in 30 seconds.
User Action:
If the error is permanent (no retry), then correct the problem and issue another TCPIP START command.
If the error is temporary (retry will occur), then correct the problem so that the retry will succeed.
Reason:
This message is issued in response to a SHOW TCPIP command when the HPNS interface is in use. It shows the TCP/IP region jobname, TCP/IP node name, and TCPIP.DATA dataset name.
The TCP/IP version is shown in vvvv (For example, 3.2). If the version cannot be determined, 'UNKNOWN' is displayed.
System Action:
None.
User Action:
None.
Reason:
This message is issued when the HPNS interface subtask has an initialization failure. The reasons are listed below and description are provided.
The interface was unable to obtain required storage.
An attempt to initialize the macro interface failed. The target TCP/IP job is shown, with the return code and error number.
System Action:
If this error occurs during TCPIP START processing, initialization fails. If it occurs later, an individual SOCKET verb will fail.
User Action:
Examine the error information and determine whether the correct jobname is being used.
You may need to contact your software support office.
Reason:
This message is issued to the SOLVE log when the TCP/IP HPNS interface receives a TCP/IP termination notification, The reason is displayed.
Termination reasons are:
1: The TCP/IP address space has terminated
2: TCP/IP has terminated the connection to SOLVE
4: Other reason (Manual says CALL IBM).
System Action:
The TCP/IP interface will automatically stop.
User Action:
Determine the reason that the termination has occurred and take appropriate corrective action.
|
Copyright © 2014 CA.
All rights reserved.
|
|