IST961I  [NONDISRUPTIVE] LOAD OF ncpname [WITH loadmodname] FAILED
IST523I  REASON = reason

PERMANENT I/O ERROR [–REQ: runame SENSE: sense]

Explanation: During an attempt to load the communication controller, VTAM detected a permanent I/O error. This may have been caused by one of the following:

• Hardware error
• VTAM detected channel contention in a multiple-channel attached communication controller that was being loaded from another domain.
• If a MODIFY LOAD command was issued for a local or remote NCP, the size of MAXDATA on the PCCU macro must be at least 2,048 plus the size of the TH and RH.

runame is the name of the request unit that failed. See Command and RU types in VTAM messages for a description of runame.

sense is the SNA sense code for the failed request unit. See the z/OS Communications Server: IP and SNA Codes for a description of sense. If sense is set by NCP, see NCP, SSP, and EP Messages and Codes for a complete description.

The values of runame and sense are issued only for remote NCP loads.

System Action: VTAM rejects the command. The communication controller remains inactive and unavailable to VTAM.

Operator Response: Save the system log and obtain an NCP dump with the NCP dump utilities for problem determination.

Run your operating system service aid program to determine whether MDR/OBR information has been recorded. See the EREP User's Guide and Reference for more information on using EREP.

If you use a network management application such as NetView®, check to determine whether an alert was recorded for this problem.

Programmer Response: Verify that the CUA operand (on the PCCU definition statement of the NCP source statements) matches the actual channel address that is connected to the controller. If the controller is multiple-channel attached and the failure was caused by a load from another domain, wait for the completion of that load operation.

Make the necessary changes to the NCP generation. If problems persist, take the following actions:

• If you have access to IBMLink, search for known problems with similar symptoms. If no applicable matches are found, report the problem to IBM® by using the Electronic Technical Report (ETR) option on IBMLink.
• If you do not have access to IBMLink, report the problem to the IBM software support center. If available, provide the MDR/OBR information from your operating system service aid program or the alert information recorded by your network management application.

INITIAL TEST HARDSTOP

Explanation: VTAM detected an error condition that caused the initial test program of the load utility for the NCP to hardstop the communication controller.

System Action: VTAM rejects the command. The communication controller remains inactive.

Operator Response: Save the system log for problem determination.

Programmer Response: If you cannot determine the cause of the problem from the output provided or need additional assistance, contact the IBM software support center.

LOADER FAILURE

Explanation: An error occurred during an attempt to load an NCP into a communication controller.

System Action: VTAM deactivates the communication controller.

Operator Response: Save the system log for problem determination. Message IST155I or other system messages may provide additional information about the cause of the loader failure.

Programmer Response: If you cannot determine the cause of the problem from the output provided or need additional assistance, contact the IBM software support center.

ddname BLDL ERROR

Explanation: VTAM tried to load a communication controller.

The operation failed because a BLDL (the load of a core resident table with track addresses of frequently used modules on a link library) issued for that library defined by DD statement ddname failed.

System Action: The communication controller is not activated. Other VTAM processing continues.

Operator Response: VTAM operations can be continued with other nodes in the network. Save the system log for problem determination.

Programmer Response: Inspect the directory of the partitioned data set defined by the DD statement ddname.

• If it is the NCP module library, ensure that the NCP being loaded into the communication controller is a member of that library (the NCP name is defined by the NEWNAME operand on the NCP BUILD definition statement).
• If ddname defines the initial test library, make sure modules IFL3705D and IFL3705B are members of the library.

INVALID DEVICE TYPE DEFINITION

Explanation: VTAM tried to load a communication controller, but failed after checking the communication controller unit control block (UCB) and determining that the operating system generation did not specify a valid channel adapter type for this NCP.

System Action: The communication controller is deactivated.

Operator Response: Save the system log for problem determination.

Programmer Response: Check the channel unit address of the specified communication controller to make sure that it is the correct address. If it is, the communication controller might have been incorrectly specified during the operating system generation.

UNEXPECTED END OF FILE ON DATA SET

Explanation: While trying to load an NCP into a communication controller, the load program encountered an unexpected end-of-file condition either on the NCP load module data set or on the initial test data set.

System Action: The communication controller is deactivated. Other processing continues.

Operator Response: Save the system log for problem determination.

Programmer Response: Ensure that the DD statements for the NCP load module and initial test data sets specify the correct data sets. Make sure these data sets contain the correct NCP load module and test routines for the communication controller hardware.

UNEXPECTED CODE code FROM loadmod

Explanation: VTAM tried to load an NCP into a communication controller. The load failed when VTAM received an unrecognizable return code code, in decimal, from the NCP load utility program loadmod.

loadmod is IFLOADRN.

System Action: The communication controller is deactivated.

Operator Response: Attempt to load the communication controller offline to VTAM using the NCP utility program. See the NCP, SSP, and EP Generation and Loading Guide for information on using the utility program.

Save the system log and obtain an NCP dump with the NCP dump utilities for problem determination.

Programmer Response: Make the necessary changes to the NCP generation. See the z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for more information on NCP problems.

LOAD MODULE TOO LARGE

Explanation: An attempt to load an NCP into a communication controller failed because the NCP load module was too large for the particular communication controller.

System Action: VTAM deactivates the communication controller. Other VTAM processing continues.

Operator Response: Save the system log for problem determination.

Programmer Response: Check the NCP generation for errors or unnecessary use of storage. The NCP needs to be regenerated.

PERMANENT I/O ERROR ON libname

Explanation: VTAM tried to load a communication controller with an NCP. It failed because a permanent I/O error occurred on the data set defined by the DD statement libname (the NCP library).

System Action: VTAM deactivates the communication controller.

Operator Response: If the error persists, save the system log for problem determination.

Message IOS000I or other related messages may be issued and can provide additional information.

This is probably a hardware error. Run your operating system service aid program to determine whether MDR/OBR information has been recorded. See the EREP User's Guide and Reference for more information on using EREP.

If you use a network management application such as NetView, check to determine whether an alert was recorded for this problem.

Programmer Response: Create the NCP library on a different disk pack if possible.

If you cannot determine the cause of the problem from the output provided or need additional assistance, contact the IBM hardware support center.

If available, provide the MDR/OBR information from your operating system service aid program or the alert information recorded by your network management application.

ddname COULD NOT BE OPENED

Explanation: VTAM tried to load a communication controller. It failed because the data set defined by the DD statement ddname (the NCP load library) could not be opened.

System Action: VTAM deactivates the communication controller.

Operator Response: Save the system log for problem determination.

Programmer Response: Make sure the specified DD statement in the VTAM procedure is included and correctly specified.

Check the definition library to ensure that all requirements for VTAM are correct for your system.