|
|
This section describes messages issued by the Link Layer routine. These messages include T01LL000 through T01LL999.
In the following series of messages, device generally refers to the physical channel interface used to connect a network interface to an MVS host. The term interface generally refers to the logical endpoint within a particular network interface.
For instance, a 3172 type device has a single channel interlace and form 1 to 4 LAN cards. The device in this case represents the channel interface, and each LAN card represents an interface. Deactivation of the channel path renders all interfaces useless, whereas, deactivating of a single interface does not affect the device or the other interfaces that share the same device.
For devices such as 3745 running the CDLC protocol or a 3762 running CETI, the distinction between the device and the interface is less clear.
From an operational viewpoint, the LNI STOP NAME(if_name) command attempts to halt communications with an interface by sending to it the proper shutdown command(s). If the device is experiencing problems, the shutdown command(s) may not be sent and the LNI STOP command will fail to complete. The DEVSTOP NAME(dev_name), however, deals at the subchannel level, and results in a Halt Subchannel being issued to the targeted device, ensuring that all communications with the device will be stopped.
Explanation The virtual driver has completed its initialization sequence successfully. IP packets may now be sent from one application on the host to another application on the same host.
Explanation The virtual driver has completed its termination sequence. IP packets may no longer be sent between an application on the host to another application on the same host.
Explanation Program prog_name attempted to perform an ILATCH operation for latch name latch_name, but the call failed with reason code rsn_code. As a result, interface if_name may no longer operate correctly.
| if_name | Name of the interface. |
| prog_name | Name of the program to be interfaced to. |
| call_type | Type of latch call, which will be one of the following:
· GET · GETSHR · FREE · FREESHR |
| latch_name | Name of latch calling. |
| rsn_code | Reason code. |
Recommended Action If an SVCDUMP was produced, save the dump and contact Customer Support.
It may be necessary to stop, LNI STOP NAME(if_name), and restart the interface, LNI START NAME(if_name) to make the it fully operational again. If the LNI STOP command does not stop the interface, use the device stop command instead, DEV STOP NAME(if_name).
Explanation Program prog_name attempted to perform an ILATCH operation, for latch latch_name. The ILATCH call failed with reason code rsn_code. As a result, one or more interfaces associated with media med_name may no longer operate correctly.
| med_name | Media name. |
| prog_name | Program name. |
| call_type | Type of latch call, which will be one of the following:
· GET · GETSHR · FREE · FREESHR |
| latch_name | Latch name. |
| rsn_code | Reason code. |
Recommended Action If an SVCDUJP was produced, save the dump and contact Customer Support.
It may be necessary to stop, LNI STOP NAME(if_name), and restart each interface, LNI START NAME(if_name), associated with the media to make the media fully operational. If the LNI STOP command does not stop an interface, use the device stop command instead, DEV STOP NAME(if_name).
Explanation Program prog_name attempted to perform an ILATCH operation for latch name latch_name, but the call failed with reason code rsn_code. As a result, interface if_name may no longer operate correctly.
| dev_name | Device name. |
| prog_name | Name of the program to be interfaced to. |
| call_type | Type of latch call, which will be one of the following:
· GET · GETSHR · FREE · FREESHR |
| latch_name | Name of latch calling. |
| rsn_code | Reason code. |
Recommended Action If an SVCDUMP was produced, save the dump and contact Customer Support.
It may be necessary to stop, DEV STOP NAME(if_name), and restart the device, DEV START NAME(dev_name) to make the it fully operational again. If the device in question is a 3172 or its equivalent, the DEV STOP command may affect more than one interface.
Explanation During the initialization sequence of an interface, an Address Request Protocol (ARP) message is sent on the local network to see if any other host is using the same IP address as the MVS host. If another host responds to this message, indicating the MVS host's IP address is its IP address, this message is issued.
The implication of this message is that two hosts are using the same IP address. Depending on timing and the routing of IP datagrams, all sessions may be lost or experience severe degradation of service while both hosts are active.
Recommended Action An IP address can only be assigned to a single active host at any point in time. Locate the remote host and change the IP address on either the remote host or the local MVS host.
Explanation The named device is being restarted because the restart timer associated with the device has expired. The restart time is controlled by the RESTART(time) keyword on the configuration statement for the device in configuration member TCPCFGxx.
Recommended Action If the automatic restart is desired, no action is necessary. If the restart interval is too long or too short, change the related device statement in TCPCFGxx. To prevent the device from automatically restarting, issue command LNI STOP NAME(if_name) for each interface associated with this device (3172s may have up to 4 interfaces associated with a device).
Explanation An attempt was made to automatically restart a device, but insufficient virtual storage was available, preventing the auto restart.
Recommended Action Reduce the virtual storage utilization in the region and issue the DEV START NAME(dev_name) command manually to restart the device.
Explanation The named device failed to complete its initialization sequence ina timely manner. In other words, 30 seconds passed and the device ailed to complete the full exchange of startup messages.
Recommended Action A problem may exist with the device in question. Resetting the device may clear the problem. If the problem continues after resetting the device, use the TCPEEP utility to trace the exchange of startup messages.
Explanation An attempt was made to automatically shut down a device, but insufficient virtual storage was available, preventing the auto shutdown. The lack of virtual storage may explain why the device was being shut down.
Recommended Action Reduce the virtual storage utilization in the region and issue the DEV STOP NAME(dev_name) command manually to shut down the device.
Explanation An I/O operation was started to the named device on subchannel address unit_addr. The I/O operation was expected to complete but did not. Shutdown processing is being initiated for the device for this reason.
Recommended Action Check the device to determine the reason it failed to complete the I/O operation in a timely manner. Restart the device with the DEV START NAME(dev_name) command when the problem has been corrected.
Explanation An attempt was made to automatically shut down a device, but insufficient virtual storage was available, preventing the auto shutdown. The lack of virtual storage in the region may explain why the device was experiencing problems and is now being shut down.
Recommended Action Reduce the virtual storage utilization in the region and issue the DEV STOP NAME(dev_name) command manually to shut down the device.
Explanation Certain types of devices, including the named device, support commands that are sent periodically from the host to the device, to determine if the device is still functioning properly. The device usually sends a response to these commands, and as a result the host still knows that at least the channel interface of the device is still fully functional. In this particular instance, the device failed to respond to the command sent by the host.
Recommended Action Check the device to determine why it failed to respond to the command sent to it by the host. If there is a possibility that the device is responding but the host is failing to recognize the response, use a TCPEEP interface trace or a GTF trace to diagnose the error on the host.
Explanation An attempt was made to automatically shut down a device, but insufficient virtual storage was available, preventing the auto shutdown. The lack of virtual storage in the region may explain why the device was experiencing problems and is now being shut down.
Recommended Action Reduce the virtual storage utilization in the region and issue the DEV STOP NAME(dev_name) command manually to shut down the device.
Explanation The named interface is being restarted because the restart timer associated with the interface has expired. The restart time is controlled by the RESTART(time) keyword on the configuration statement for the interface in configuration member TCPCFGxx.
Recommended Action If automatic restart is desired, no action is necessary. If the restart interval is too long or too short, change the related interface statement in TCPCFGxx. To prevent the interface from automatically restarting, issue the command LNI STOP NAME(if_name) for the interface.
Explanation An attempt was made to automatically restart an interface, but insufficient virtual storage was available, preventing the auto restart.
Recommended Action Reduce the virtual storage utilization in the region and issue the LNI START NAME(if_name) command manually to restart the device.
Explanation The named interface failed to complete its initialization sequence in a timely manner. In other words, 60 seconds passed and the interface failed to complete the full exchange of startup messages.
Recommended Action There may exist a problem with the interface in question. Resetting the interface may clear this problem. If the problem continues after resetting the interface, the TCPEEP utility may be used to trace the exchange of startup messages.
Explanation An attempt was made to automatically shut down an interface, but insufficient virtual storage was available, preventing the auto shutdown. The lack of virtual storage may explain why the interface was being shut down.
Recommended Action Reduce the virtual storage utilization in the region and issue the LNI STOP NAME(dev_name) command manually to shut down the device.
Explanation Too much time has passed since the last packet was received on the named interface. At this point, the interface does not know if this is due to an idle network, or whether the interface is experiencing technical problems. To determine why no packets have been received, the interface tries to actively solicit responses from other devices on the local network.
If no response can be solicited from any device on the local network, message T01LL117W will be issued and the interface will be shut down.
Recommended Action The IDLENET keyword of the Media statement within configuration member TCPCFGxx controls the period an interface will wait while idle before polling. Adjust this value to meet the traffic conditions of the local network.
If this message is issued when a network is not idle, check for interface problems and correct if necessary.
Explanation After message T01LL116W has been issued, the named interface tried to solicit a response from a device on the local network. After reaching the query limit set by the IDLENET keyword of the Media statement, the interface is now shutting down to see if resetting the interface corrects the lack of input messages. The interface will automatically be restarted.
Recommended Action Determine if the lack of input messages to the interface is caused by a network with no other active devices or whether the lack of messages is caused by a malfunctioning controller. If the network is truly idle, the IDLENET keyword of the Media statement in TCPCFGxx can be set to an idle time of 0 to disable this feature. If the network is active but the controller is malfunctioning, fix the controller.
Explanation See Message T01LL117W.
Recommended Action See Message T01LL117W.
Explanation An attempt was made to automatically shut down an interface, but insufficient virtual storage was available, preventing the auto shutdown. The lack of virtual storage may explain why the interface was being shut down.
Recommended Action Reduce the virtual storage utilization in the region and issue the LNI STOP NAME(dev_name) command manually to shut down the device.
Explanation The termination sequence for the named device has been initiated, but the Purge I/O SVC call failed with the specified reason code. The reason codes from Purge are documented in IBM manual SC26-4921, DFSMS/MVS V1R4 DFSMS Advanced Services.
If I/O was still active after the Purge SVC failed, an ABEND may occur when the I/O completes due to freed control blocks being accessed.
Recommended Action Using the Purge SVC reason code, determine why the Purge SVC failed. If the problem is caused by site specific conditions, correct the problem. If the problem is due to a TCP/IP software defect, contact Customer Support.
Explanation During initialization of the named device, the Itime service failed to allocate a new timer element (ITIM) to be used by the device and its associated interfaces. Device initialization cannot continue.
Recommended Action Use the reason code supplied by the Itime service to determine why the ITIM allocation request failed.
Explanation During initialization of the named device, a Storage Obtain request for a save area pool failed. The reason code from Storage Obtain is documented in IBM manual GC28-1478, Authorized Assembler Services Reference SET-WTO. The save area pool is allocated from subpool 91 for a length of 4608 bytes.
Recommended Action Use the reason code from Storage Obtain to determine why the request for private storage failed. If there is insufficient storage in the region, change the region size for the current step in the TCP/IP JCL and restart TCP/IP.
Explanation During initialization of the named device, a Storage Obtain request for the LNIO pool failed. The reason code from Storage Obtain is documented in IBM manual GC28-1478, Authorized Assembler Services Reference SET-WTO. The LNIO pool is allocated from subpool 230. The requested length in bytes is equal to the count of input and output buffers for the device times 256.
Recommended Action Use the reason code from Storage Obtain to determine why the request for private storage failed. If there is insufficient storage in the region, change the region size for the current step in the TCP/IP JCL and restart TCP/IP.
Explanation During initialization of the named device, a Storage Obtain request for the I/O buffer pool failed. The reason code from Storage Obtain is documented in IBM manual GC28-1478, Authorized Assembler Services Reference SET-WTO. The I/O buffer pool is allocated from subpool 79. The requested length in bytes is equal to the count of input buffers times the input buffer size, plus the count of output buffers times the output buffer size. For CETI devices, add an additional 112 bytes to this total.
I/O Buffer sizes in bytes are:
| CDLC | MTU size specified on related Media + 4. |
| CETI | 1518. |
| Claw | Size defined by the BUFSIZE keyword on the CLAW statement. |
| Hyperchannel | MTU size specified on related Media + 64. |
| LCS | 20480. |
Recommended Action Use the reason code from Storage Obtain to determine why the request for private storage failed. If there is insufficient storage in the region, change the region size for the current step in the TCP/IP JCL and restart TCP/IP. If the error occurred due to too many I/O buffers being requested, change the IBUF and OBUF values in TCPCFGxx to reflect more appropriate values.
Explanation During initialization of the named device, a Storage Obtain request for the LNSI pool failed. The reason code from Storage Obtain is documented in IBM manual GC28-1478, Authorized Assembler Services Reference SET-WTO. The LNSI pool is allocated from subpool 245, above the 16 megabyte line, for a length of 256 bytes times the sum of the input and output buffers.
Recommended Action Use the reason code from Storage Obtain to determine why the request for global system storage failed. If there is insufficient storage in Extended SQA, change your system configuration to allocate more extended global storage or fix the application or system service which is exhausting extended global storage.
Explanation An internal logic error occurred while trying to build the channel program for the read subchannel for the named device.
Recommended Action Contact Customer Support.
Explanation The named device requires use of an unsolicited attention handler to operate correctly. The attention handler manager, T01SUIHR, was unable to register the named device. Initialization of the device cannot continue.
Use the reason code returned from T01SUIHR to diagnose and correct the problem. These reason codes are:
| 0 | Successful. |
| 4 | Error accessing IEANTRT (possible link edit error). |
| 8 | Non-zero return code from IEANTRT was returned. See IBM manual GC28-1476, Authorized Assembler Services Reference ENF-ITT for the return codes returned from IEANTRT. |
| 12 | No empty slots in unsolicited interrupt handler table (UIHT). |
| 16 | Load of T01PATTN failed. See the text of message T01LL154E for the reason code returned from the ILOAD (not LOAD) service. |
| 20 | Storage Obtain for UIHT failed (subpool 245, length 784 bytes). See the text of message T01LL153E and IBM manual, GC28-1478, Authorized Assembler Services Reference SET-WTO, for the reason code returned from Storage Obtain. |
| 24 | Non-zero return code from NUCLKUP for module IOSVATTN. See the text of message T01LL152E and IBM manual GC28-1477, Authorized Assembler Services Reference LLA-SDU for the reason codes returned from NUCLKUP. |
| 28 | MVS system attention table is full. |
| 32 | Non-zero return code from IEANTCR was returned. See the text of message T01LL150E and IBM manual GC28-1476, Authorized Assembler Services Reference ENF-ITT for the reason codes returned from IEANTCR. |
Explanation The initialization of the named device failed because the system service UCBLOOK returned a non-zero return code, ret_code.
Recommended Action Use the return code and reason code to diagnose why the dynamic allocation failed. The return code and reason codes from UCBLOOK are documented in IBM manual, GC28-1478, Authorized Assembler Services Reference SET-WTO.
Explanation The initialization of the named device failed because the dynamic allocation system service, SVC 99, failed. At the time of the error, SVC 99 was invoked to de-allocate the specified unit. SVC 99 return values are documented in IBM manual GC28-1467, Authorized Assembler Services Guide.
Recommended Action Use the return code, ret_code, and the reason code, rsn_code, to diagnose why the dynamic allocation failed.
Explanation The initialization of the named device failed because the dynamic allocation system service, SVC 99, failed. At the time of the error, SVC 99 was invoked to allocate the specified unit. SVC 99 return values are documented in IBM manual GC28-1467, Authorized Assembler Services Guide.
Recommended Action Use the return code, ret_code, and the reason code, rsn_code, to diagnose why the dynamic allocation failed.
Explanation The initialization of the named device failed because the specified unit is not online to the MVS I/O subsystem.
Recommended Action Vary the device online if possible and issue the DEV START NAME(dev_name) to restart the affected device.
Explanation An IP datagram of length msg_len was given to the named device for transmission. The length of the datagram exceeded the maximum length supported by the device and the IP datagram was discarded.
Recommended Action Validate that the Media statement in configuration member TCPCFGxx has an MTU value that is valid for the named device.
Explanation An internal logic error occurred on the call from T01SLCWR to T01SARSR, resulting in the discard of an IP datagram.
Recommended Action Contact Customer Support.
Explanation An internal logic error occurred while trying to build the channel program for the control subchannel for the named device.
Recommended Action Contact Customer Support.
Explanation The named device has received the first initialization message from the network controller indicating that the device is operational. The initialization sequence for the device continues.
Explanation Initialization for the named CDLC device failed because the configured buffer size (Media statement MTU size) does not match the value defined in the CDLC device.
Recommended Action Correct either the MTU size on the Media statement in configuration member TCPCFGxx or correct the value defined in the CDLC device.
Explanation The named device has completed its device level initialization sequence. Although the device has completed initialization, no IP datagrams may be sent or received via the device until one or more associated interfaces completes its initialization sequence.
Explanation The initialization sequence for the named CDLC device failed, because the CDLC device is in an invalid state. The sense data returned by the device indicates the current CDLC state. The sense data is documented in IBM manual LY43-0029, NCP VxRx and EP Rx Reference.
Recommended Action Use the sense data to determine which state the CDLC device is currently in. Once the state has been determined, perform the necessary actions on the CDLC device to place it in the proper state required for TCP/IP initialization.
Explanation The CDLC device driver for the named device was unable to recognize the channel command code used in the last I/O operation. This is most likely the result of an internal logic error.
Recommended Action Contact Customer Support.
Explanation An I/O error occurred on subchannel unit_addr for the named device. Sense data was supplied by the device. IOSCOD is the MVS/ESA IOS post code recorded in the IOSB and documented in IBM manual LY28-1858, MVS/ESA Data Areas, Vol 2 (DCCB-ITTCTE). The channel status word is the value presented by the MVS subchannel at the time of I/O completion and is also recorded in the IOSB. The channel status word is documented in IBM manual SA22-7201, ESA/390 Principles of Operation. The sense data returned is specific to the device and can usually be located with documentation supplied by the hardware vendor.
Recommended Action Use the channel status word, post code and sense data to determine why the I/O error occurred. If the problem is due to a hardware error, correct the error and restart the device with a DEV START NAME(dev_name) command.
If the problem is due to a software problem, issue command F TCPIP,LOGGING PRINT((LL,ALL)), run GTF, recreate the problem and then Customer Support.
Use the following options when starting GTF:
TRACE=IOP,SSCHP,HSCH,CSCH,MSCH,CCWP,PCIExplanation An I/O error occurred on subchannel unit_addr for the named device. Sense data was not supplied by the device. IOSCOD is the MVS/ESA IOS post code recorded in the IOSB and documented in IBM manual LY28-1858, MVS/ESA Data Areas, Vol 2 (DCCB-ITTCTE). The channel status word is the value presented by the MVS subchannel at the time of I/O completion and is also recorded in the IOSB. The channel status word is documented in IBM manual SA22-7201, ESA/390 Principles of Operation.
Recommended Action Use the channel status word and post code to determine why the I/O error occurred. If the problem is due to a hardware error, correct the error and restart the device with a DEV START NAME(dev_name) command.
If the problem is due to a software problem, issue command F TCPIP,LOGGING PRINT((LL,ALL)), run GTF, recreate the problem and then contact Customer Support.
Use the following options when starting GTF:
TRACE=IOP,SSCHP,HSCH,CSCH,MSCH,CCWP,PCIExplanation An I/O error occurred on the named device and as a result, the affected device is being shutdown.
Recommended Action Locate previous error messages for an explanation of the I/O error. Perform the recommended action for the previous messages and issue command DEV START NAME(dev_name) when the condition causing the error has been eliminated.
Explanation An attempt was made to automatically shutdown a device, but insufficient virtual storage was available, preventing the auto shutdown. The lack of virtual storage in the region may explain why the device was experiencing problems and is now being shut down.
Recommended Action Reduce the virtual storage utilization in the region and issue the DEV STOP NAME(dev_name) command manually to shutdown the device.
Explanation An I/O error occurred on subchannel unit_addr for the named device. Sense data was supplied by the device. IOSCOD is the MVS/ESA IOS post code recorded in the IOSB and documented in IBM manual LY28-1858, MVS/ESA Data Areas, Vol 2 (DCCB-ITTCTE). The channel status word is the value presented by the MVS subchannel at the time of I/O completion and is also recorded in the IOSB. The channel status word is documented in IBM manual SA22-7201, ESA/390 Principles of Operation. The sense data returned is specific to the device and can usually be located with documentation supplied by the hardware vendor.
The disable interrupt exit reason code (die_rsn_code) identifies the exact error test that detected the error condition. The DIE reason codes are:
| 2 | No CCW address in CSW (device possibly reset) |
| 3 | CCW address less than lowest LNIO address |
| 4 | CCW address higher than highest LNIO address |
| 5 | LNIO ID validation failed |
| 6 | LCS input - Unrecognized / invalid ending status |
| 7 | LCS input - LNIO with ending status not first active LNIO |
| 8 | LCS output - Unrecognized / invalid ending status |
| 9 | CLAW input - Unrecognized / invalid ending status |
| 10 | Claw output - Unrecognized / invalid ending status |
| 11 | CDLC input - Unrecognized / invalid ending status |
| 12 | CDLC input - Unknown operation code |
| 13 | CDLC input - Missing DE on read |
| 14 | CDLC input - Busy on read |
| 15 | CDLC input - DE on Read Start 0 or 1 |
| 16 | CDLC input - Unrecognized status on Read Start 0 or 1 |
| 17 | CDLC output - Unrecognized / invalid ending status |
| 18 | CDLC output - Unknown operation code |
| 19 | CDLC output - Chaining error (DE on write) |
| 20 | CDLC output - Unrecognized status on Write |
| 21 | CDLC output - Unrecognized status on Write Break |
| 23 | CDLC output - Chaining error (DE on Write Start 0 or 1) |
| 24 | CDLC output - Unrecognized status on Write Start 0 or 1 |
| 40 | Hyperchannel input - Unrecognized / invalid ending status |
| 41 | Hyperchannel input - LNIO with ending status not first active LNIO |
| 42 | Hyperchannel output - Unrecognized / invalid ending status |
| 50 | CETI control - Any ending status |
| 54 | CETI attention - Status other than ATTN or UC |
| 58 | CETI input - Any ending status |
| 62 | CETI output - Any ending status |
Recommended Action Use the channel status word, post code, sense data, and DIE reason code to determine why the I/O error occurred. If the problem is due to a hardware error, correct the error and restart the device with a DEV START NAME(dev_name) command.
If the problem is due to a software problem, issue command F TCPIP,LOGGING PRINT((LL,ALL)), run GTF, recreate the problem and then contact Customer Support. Use the following options when starting GTF:
TRACE=IOP,SSCHP,HSCH,CSCH,MSCH,CCWP,PCIExplanation An I/O error occurred on subchannel unit_addr for the named device. Sense data was not supplied. IOSCOD is the MVS/ESA IOS post code recorded in the IOSB and documented in IBM manual LY28-1858, MVS/ESA Data Areas, Vol 2 (DCCB-ITTCTE). The channel status word is the value presented by the MVS subchannel at the time of I/O completion and is also recorded in the IOSB. The channel status word is documented in IBM manual SA22-7201, ESA/390 Principles of Operation. The disable interrupt exit reason code (die_rsn_code) identifies the exact error test that detected the error condition. These codes are documented in message T01LL144E.
Recommended Action Use the channel status word, post code and DIE reason code to determine why the I/O error occurred. If the problem is due to a hardware error, correct the error and restart the device with a DEV START NAME(dev_name) command.
If the problem is due to a software problem, issue command F TCPIP,LOGGING PRINT((LL,ALL)), run GTF, recreate the problem and then contact Customer Support. Use the following options when starting GTF:
TRACE=IOP,SSCHP,HSCH,CSCH,MSCH,CCWP,PCIExplanation Device initialization is in progress for dev_name.
Explanation Interface initialization is in progress for the if_name.
Explanation Device termination is in progress.
Explanation The termination of the named device failed because the dynamic allocation system service, SVC 99, failed. At the time of the error, SVC 99 was invoked to de-allocate the specified unit. SVC 99 return values are documented in IBM manual GC28-1467, Authorized Assembler Services Guide.
Recommended Action Use the return code, ret_code, and the reason code, rsn_code, to diagnose why the dynamic de-allocation failed.
Explanation The named device requires use of an unsolicited attention handler to operate correctly. The attention handler manager, T01SUIHR, was unable to register the named device due to an error returned by the MVS system service IEANTCR service. Initialization of the device cannot continue. The reason codes returned by IEANTCR are documented in IBM manual GC28-1476, Authorized Assembler Services Reference ENF-ITT.
Recommended Action Use the reason code returned from IEANTCR to diagnose and correct the problem.
Explanation The named device requires use of an unsolicited attention handler to operate correctly. The attention handler manager, T01SUIHR, was unable to register the named device because all system wide attention table slots are in use. Initialization of the device cannot continue.
Recommended Action If the attention table can be expanded via a user mod or PTF from IBM, expand the attention table. Otherwise, obtain a network device that does not require the use of the attention table.
Explanation The named device requires use of an unsolicited attention handler to operate correctly. The attention handler manager, T01SUIHR, was unable to register the named device because a call to MVS system service NUCLKUP failed. Initialization of the device cannot continue. The reason codes returned by the NUCLKUP service are document in IBM manual GC28-1477, Authorized Assembler Services Reference LLA-SDU.
Recommended Action Use the reason code returned from NUCLKUP to diagnose and correct the problem.
Explanation The named device requires use of an unsolicited attention handler to operate correctly. The attention handler manager, T01SUIHR, was unable to register the named device because a call to MVS system service NUCLKUP failed. Initialization of the device cannot continue. The reason codes returned by the NUCLKUP service are document in IBM manual GC28-1477, Authorized Assembler Services Reference LLA-SDU.
Recommended Action Use the reason code returned from NUCLKUP to diagnose and correct the problem.
Explanation The named device requires use of an unsolicited attention handler to operate correctly. The attention handler manager, T01SUIHR, was unable to register the named device due to a non-zero return code being returned by the ILOAD service. Initialization of the device cannot continue. The ILOAD service was attempting to load module T01PATTN into system subpool 245 storage.
Recommended Action Use the reason code returned from the ILOAD service to diagnose and correct the problem. This error may be caused by insufficient extended global storage and may require modifications to system parameters to increase the amount of global virtual storage available for application usage. This error may also be caused by module T01PATTN not existing in a data set that is part of the TCP/IP Steplib concatenation.
Explanation The named device requires use of an unsolicited attention handler to operate correctly. The attention handler manager, T01SUIHR, was unable to register the named device because its private attention table is full. Initialization of the device cannot continue. The private attention table is capable of holding information for 32 separate devices.
Recommended Action Contact Customer Support and ask them to provide a new version of module T01SUIHR that allocates a private attention table with a larger capacity.
Explanation The named device requires use of an unsolicited attention handler to operate correctly. The attention handler manager, T01SUIHR, was unable to register the named device due to a non-zero reason code being returned by the MVS system service IEANTRT. Initialization of the device cannot continue. The reason codes returned by IEANTCR are documented in IBM manual GC28-1476, Authorized Assembler Services Reference ENF-ITT.
Recommended Action Use the reason code returned from IEANTRT to diagnose and correct the problem.
Explanation The named device requires use of an unsolicited attention handler to operate correctly. The attention handler manager, T01SUIHR, was unable to register the named device because module T01SUIHR was not properly link edited with module IEANTRT at TCP/IP installation time. Initialization of the device cannot continue.
Recommended Action Correct the SMP/E error condition that caused the original link edit to fail and then link edit T01SUIHR with module IEANTRT, which can typically be located in library SYS1.CSSLIB.
Explanation The termination sequence for the name device has successfully completed. All resources used by the device have been freed.
Explanation The termination sequence for the name device has successfully completed. All resources used by the interface have been freed. If multiple interfaces share the same device, the device may still be holding resources for the other interfaces. Use the DEV STOP NAME(dev_name) command to stop the device in this case.
Explanation An LNI STOP command was issued, but the named device associated with the targeted interface was still in its termination phase. The command was ignored.
Recommended Action Wait for the device to complete termination or investigate why the device is failing to terminate in a timely manner.
Explanation An LNI START command was issued, but the named device associated with the targeted interface was still in its initialization phase. The command was ignored.
Recommended Action Wait for the device to complete initialization or investigate why the device is failing to initialize in a timely manner.
Explanation A request to initialize the named interface required the initialization of the associated device. The device initialization failed.
Recommended Action Look for other error messages for the named device that explain why the initialization of that device failed.
Explanation A request to initialize the named interface was ignored because the interface has not completely finished a previous shutdown sequence.
Recommended Action The interface can be forced down by issuing the DEV STOP NAME(dev_name) command. Then the interface can be restarted by issuing the LNI START NAME(if_name) command. Be aware that some physical intervention with the network controller may be necessary if the controller is malfunctioning.
Explanation A request to initialize the named interface was ignored because the interface was already in the process of initializing.
Recommended Action Wait for interface initialization to complete. If interface initialization fails to complete, issue the DEV STOP NAME(dev_name) command to shutdown the interface and device, correct any error with the network controller, and then issue the LNI START NAME(if_name) command to restart the interface.
Explanation A request to initialize the named interface was ignored because the interface was fully operational.
Explanation An internal logic error occurred while trying to build a channel program for the named interface.
Recommended Action Contact Customer Support.
Explanation All network controllers with the exception of CDLC and Hyperchannel network controllers must be defined to the MVS I/O subsystem as a Channel-To-Channel Adapter (CTCA). The named device is not defined to MVS as a CTCA.
Recommended Action If this message is issued because the unit address specified on the device statement in configuration member TCPCFGxx is incorrect, change the unit address on the statement and restart TCP. If the unit address is correct, change the unit definition within MVS, defining the network controller as a CTCA.
Explanation During the initialization sequence of the named device, the dynamic allocation of unit_addr failed with SVC 99 error code x'0214' or x'0244', indicating that the device was either offline or allocated to another application.
Recommended Action Validate that the correct unit address was specified on the device statement in configuration member TCPCFGxx. If the unit address is correct, use the MVS command D U,,ALLOC,unit_addr to determine the other application which is currently using the named device. Once this is determined, reconfigure either this TCP/IP stack or the other application, such that only one application uses the device at a time.
Explanation A request to shutdown the named interface was ignored because the associated device was already shut down.
Explanation A request to shutdown the named interface was ignored because the associated device was already in the process of shutting down.
Explanation A request to shutdown the named interface was ignored because the associated device has not completed its initialization sequence.
Recommended Action If the device appears to be hung, issue the DEV STOP NAME(dev_name) command to shut down the device immediately.
Explanation A request to shutdown the named interface was ignored because the interface is not currently active.
Explanation A request to shutdown the named interface was ignored because the interface already started shutdown processing.
Recommended Action If shutdown processing of the interface appears to have stalled, issue the DEV STOP NAME(dev_name) command to immediately shutdown the device and all of its associated interfaces.
Explanation A request to shutdown a CLAW interface has found no active CLAW links. As a result, the underlying CLAW device is being shutdown also.
Explanation A request to shutdown the named interface has been accepted and shutdown processing for the interface is now active.
Explanation This diagnostic message is produced following an I/O error. The storage being dumped is the Local Network Device Control (LNDC) block. The LNDC is used to keep track of the state of a particular device, and all its resources.
Recommended Action This information is being supplied as part of diagnostic data when an I/O error occurs. The intended audience for this data is TCP/IP support personnel. Customers should make this data available to support personnel when reporting I/O error problems.
Explanation This diagnostic message is produced following an I/O error. The storage being dumped is the LNI SRB / IOSB (LNSI) block. The IOSB is the control blocked used to communicate information about I/O requests between TCP/IP and the MVS I/O Subsystem. The IOSB is located at offset x'48' in the LNSI and its layout is documented in IBM manual LY28-1858, MVS/ESA Data Areas, Vol 2 (DCCB-ITTCTE).
Recommended Action This information is being supplied as part of diagnostic data when an I/O error occurs. The intended audience for this data is TCP/IP support personnel. Customers should make this data available to support personnel when reporting I/O error problems.
Explanation This diagnostic message is produced following an I/O error. The storage being dumped is the LNI Input / Output (LNIO) block. The LNIO contains the Channel Command Words (CCW's) and Indirect Addressing Word (IDAW) lists.
Recommended Action This information is being supplied as part of diagnostic data when an I/O error occurs. The intended audience for this data is TCP/IP support personnel. Customers should make this data available to support personnel when reporting I/O error problems.
Explanation The named interface has completed its initial hand shaking sequence. Depending on the device type, the initialization sequence may require more data exchanges to make the interface fully operational. At that point, IP datagrams can be sent and received.
Explanation All processing required to activate the named interface has completed successfully. The interface is now capable of sending and receiving IP datagrams.
Explanation All processing required to activate the named device has completed successfully. No IP datagrams may be sent or received, however, until one or more associated interfaces complete its initialization sequence and becomes fully operational.
Explanation The initialization process has begun for the named interface.
Explanation A 3172 type device received a shutdown notification from the network controller. The device and all of its interfaces are immediately shutdown. Automatic restart of the device will occur when the time interval specified by the RESTART keyword of the LCS statement in configuration member TCPCFGxx expires.
Recommended Action f the shutdown message was received unexpectedly, check the network controller to determine why the shutdown message was sent to the host.
Explanation This message is issued following message T01LL184W or T01LL186E, to identify each interface which is being shutdown automatically.
Recommended Action Perform the recommended action for the previously issued error or warning message.
Explanation A 3172 type interface or device was sent the command code 3172_cmnd. The command, however, was returned by the network controller in error.
Recommended Action Try to determine why the network controller rejected the command. Customers may need to contact support personnel for assistance in identifying the meaning of the 3172_cand code and the expected response from the device.
Explanation All processing required to activate the named device has completed successfully. No IP datagrams may be sent or received, however, until one or more associated interfaces complete its initialization sequence and becomes fully operational.
Explanation During the initialization of a CLAW device, the primary CLAW link used to transmit IP datagrams has been established. The link ID is for use in identifying the link when running network traces.
Explanation During the initialization of a CLAW device, the secondary CLAW link used to transmit TCP/IP datagrams which will have offloaded check summing processing performed on them has been established. The link ID is for use in identifying the link when running network traces.
Explanation During the initialization of a CLAW device, the packed CLAW link used to transmit multiple IP datagrams has been established. The packed link cannot actually transmit or receive IP datagrams until the TCP/IP and checksum sub-links have been established.
Explanation The named device has stopped processing for the specified CLAW link. The type of link can be identified by locating the previous T01LL188I, T01LL189I or T01LL190I message.
Recommended Action If the stopping of the link was unexpected, determine why the network control stopped the link.
Explanation All processing required to activate the named interface has completed successfully. The interface is now capable of sending and receiving IP datagrams.
Explanation The Media statement in the configuration member TCPCFGxx, was coded with keyword Assist, NoCheckSum, or OffLoadCkSum. The named device, however, is not capable of performing offloaded checksum processing.
Recommended Action If the network controller is incapable of performing offloaded checksum processing, change the Media statement in TCPCFGxx to include option NoAssist, CheckSum or HostCkSum. If the network controller does support offloaded checksum processing, verify that the network controller is properly configured to perform this service on the subchannel addresses being used by the device.
Explanation The CLAW statement in the configuration member TCPCFGxx, was coded with keyword Packed. The named device, however, is not capable of packing multiple datagrams into a single channel I/O buffer.
Recommended Action If the network controller is incapable of performing packed I/O buffering, change the CLAW statement in TCPCFGxx, removing the Packed keyword. If the network controller does support packed I/O buffering, verify that the network controller is properly configured to perform this service on the subchannel addresses being used by the device.
Explanation The named CLAW device received a CLAW protocol error for the specified CLAW command code. CLAW command codes and CLAW error codes are documented in IBM manual SC23-2427, Block Multiplexer Channel Adapter: User's Guide and Service Information or manual SC23-2474, Enterprise Systems Connection Adapter: User's Guide and Service Information.
Recommended Action Use the supplied information to determine why the CLAW command was rejected by the network controller. If the problem appears to be TCP/IP software related, contact Customer Support.
Explanation An attempt was made to automatically shutdown a device, but insufficient virtual storage was available, preventing the auto shutdown. The lack of virtual storage in the region may explain why the device was experiencing problems and is now being shutdown.
Recommended Action Reduce the virtual storage utilization in the region and issue the DEV STOP NAME(dev_name) command manually to shutdown the device.
Explanation The controller is configured for the PACKED option, but the CLAW statement in the TCPCFGxx member does not contain the PACKED option keyword. Both configuration options must match. The controller shuts down.
Recommended Action Correct either the startup configuration member, or reconfigure the controller to match.
Explanation The named Media was defined with one or more interfaces. At least one of these interfaces is now fully functional. As a result, the IP addresses associated with this Media can not be accessed from remote hosts.
Explanation The named Media was defined with one or more interfaces. All of these interfaces are now shutdown or in the process of being shutdown. As a result, the IP addresses associated with this Media most likely can not be accessed from remote hosts unless some other form of IP routing via a different Media is occurring.
Recommended Action If the desired state of the interfaces owned by this Media is not down, then issue the LNI START NAME(if_name) command to start one or more of the interfaces owned by this Media.
Explanation The named CETI device reported a level 2 error. The error code is printed in hexadecimal, along with its English translation. IBM manual SA33-1590, IEEE 802.3 Local Area Network Reference Manual documents the CETI protocol. The error message is received and documented, but no further action is performed by the device driver.
Recommended Action If the CETI interface is malfunctioning, this error message may help explain the cause of the malfunction. Otherwise, no action is required.
Explanation The named CETI device has detected excessive collisions on the attached Ethernet. This may be the cause of TCP/IP network performance problems.
Recommended Action If excessive collisions are affecting network performance, then reconfiguration of the local area network may be necessary to reduce the collision rate.
Explanation The named CETI device has detected excessive out of window collisions on the attached Ethernet. This may be the cause of TCP/IP network performance problems.
Recommended Action If excessive out of window collisions are affecting network performance, then reconfiguration of the local area network may be necessary to reduce the collision rate.
Explanation The named CETI device has detected excessive alignment errors on the attached Ethernet. This may be the cause of TCP/IP network performance problems.
Recommended Action If excessive alignment errors are affecting network performance, then locate and correct the device on the Ethernet causing the alignment errors.
Explanation The named CETI device has detected that the Ethernet carrier has been lost. This is most likely caused by a loose cable or a cut cable.
Recommended Action Locate and fix the break in the physical medium.
|
|