NETC* - CTC Option Messages

The Entire Net-Work CTCA or FCTC driver is only supported on z/OS operating systems.

Run Entire Net-Work CTCA or FCTC on an appropriate operating system.

The Entire Net-Work CTCA or FCTC line driver requires the use of certain supervisor functions. As a result, ADARUN must be link edited with option AC(1) and all libraries in the STEPLIB DD concatenation must be specified in the IEAAPFxx member of SYS1.PARMLIB.

Make sure that ADARUN is correctly link edited and all libraries in the Steplib DD concatenation are APF authorized.

The Entire Net-Work CTCA or FCTC driver uses extended real and extended virtual storage. ADARUN must be link edited with attribute AMODE(31) in order for CTCA or FCTC to execute correctly.

Relink ADARUN with the AMODE(31) option.

The CTCA or FCTC attention routine NCHXAR is dynamically loaded into extended CSA during CTCA or FCTC driver initialization. The load has failed and execution of the CTCA or FCTC driver is not possible.

Look for a related z/OS system message explaining the reason that the load failed. Also make sure that NCHXAR is in the same library as NETCTCA or NETFCTC. Note that NCHXAR does not have to be installed in the fixed LPA as did previous Entire Net-Work CTCA or FCTC drivers.

During link open processing of the link named in the message (linkname), the dynamic allocation of CTC unit Cuu failed.

The SVC 99 error code ECCC and information code ICCC are printed to help resolve the problem.

Look up the SVC 99 error and information codes and take appropriate action to make the unit usable. Then issue the CTCA linkname OPENor FCTC linkname OPEN command to access the device.

During link open processing of the link named in the message (linkname), a check of the Unit Control Block (UCB) for CTC device Cuu showed that the device was not marked online to MVS.

Vary the device online to MVS. Then issue the CTCA linkname OPEN or FCTC linkname OPEN command to access the device.

During link open processing of the link named in the message (linkname), a check of the Unit Control Block (UCB) for device Cuu showed that the device was not defined to z/OS as a CTCA or FCTC device.

Verify that the unit specified in the LINK statement is correct. If the unit address is correct, then the MVS/IOCP may need to be correctly genned.

During link open processing of the link named in the message (linkname), an attempt to GETMAIN storage for I/O buffers failed with GETMAIN return code xxxxxxxx. The amount of storage required for I/O buffers is computed as follows:

(# of read buffers * size of read buffers) + (# of write buffers * size of write buffers).

Make sure sufficient extended virtual storage exists in the private portion of the region to satisfy the GETMAIN request or reduce the size and/or number of buffers defined in the LINK statement. Then issue the CTCA linkname OPEN or FCTC linkname OPEN command to restart the open process.

During link open processing of the link named in the message (linkname), an attempt to GETMAIN storage for I/O blocks failed, with GETMAIN return code xxxxxxxx. The amount of storage required for I/O blocks is computed as follows:

(# of read buffers + # of write buffers) * 4096.

Make sure sufficient extended virtual storage exists in the private portion of the region to satisfy the GETMAIN request or reduce the number of buffers defined in the LINK statement. Then issue the CTCA linkname OPEN or FCTC linkname OPEN command to restart the open process.

During link open processing of the link named in the message (linkname), an attempt to GETMAIN storage for SRB/IOSB blocks failed with GETMAIN return code xxxxxxxx. The amount of storage required for I/O blocks is computed as follows:

(# of read buffers + # of write buffers) * 256.

Make sure sufficient extended virtual storage exists in the extended system queue area to satisfy the GETMAIN request or reduce the number of buffers defined in the LINK statement. Then issue the CTCA linkname OPEN or FCTC linkname OPEN command to restart the open process.

During link open processing of the link named in the message (linkname), an attempt to GETMAIN storage for work queue elements failed with GETMAIN return code xxxxxxxx. The amount of storage required for work queue elements is computed as follows:

(128 + number of read and write buffers) * 32.

Make sure sufficient extended virtual storage exists in the private portion of the region to satisfy the GETMAIN request. Then issue the CTCA linkname OPEN or FCTC linkname OPEN command to restart the open process.

During link open processing of the link named in the message (linkname), an attempt to GETMAIN storage for the link trace table failed with GETMAIN return code xxxxxxxx. The amount of storage required for the trace table is defined on the link definition (TRACESIZ).

Make sure sufficient extended virtual storage exists in the private portion of the region to satisfy the GETMAIN request. Then issue the CTCA linkname OPEN or FCTC linkname OPEN command to restart the open process.

An attempt was made during open processing of the link named in the message (linkname) to dequeue a write WQE from the free write WQE queue. The queue was empty, and should not be empty at this point.

Contact your Software AG technical support representative for assistance.

The Disabled Interrupt Exit could not correctly convert the real address of the last CCW to complete in the channel program to a virtual address. This condition should never occur. If this condition does occur, an SVC dump is sent to one of the SYS1.DUMPxx data sets .

With the dump available, contact your Software AG technical support representative for assistance.

During link connect processing for the link named in the message (linkname), there were not sufficient write buffers to send a connect request. As a result, the connect process is terminated and the link remains disconnected.

Make sure sufficient write buffers are allocated for the link.

A disconnect request was received on the link named in the message (linkname). A disconnect response was successfully sent, and the link is now disconnected.

No action is required for this informational message.

The CTCA or FCTC driver dequeues and processes WQE elements in response to events that occur. In this instance, a command such as CONNECT was issued, but the CTCA or FCTC substate was such that the command was rejected. This normally occurs on connect commands if the CTCA or FCTC driver is already in the process of connecting, and on disconnect commands if the CTCA or FCTC driver has not fully completed the connect process with the peer.

No action is required for this informational message.

The CTCA or FCTC driver has received a request from Entire Net-Work on the remote side of the CTCA or FCTC requesting connection.

A connect response is sent; the link is marked connected when the response is sent. In the interim, the CTCA or FCTC substate is marked as 'Connecting-R' .

No action is required for this informational message.

A shortage of write buffers occurred for the link named in the message (linkname), preventing the sending of a connect response. This condition should not occur.

Contact your Software AG technical support representative for assistance.

A connect request was received by the CTCA or FCTC driver on the remote side of the link named in the message (linkname). It has responded by sending a connect response. As a result, the link is now connected.

No action is required for this informational message.

A connect request has been sent to the CTCA or FCTC driver on the remote side of the link named in the message (linkname). It should respond by sending a connect response. Until a connect response is received, the link remains in substate 'Connecting-S(2) .

No action is required for this informational message.

A connect response has been sent to the CTCA or FCTC driver on the remote side of the link named in the message (linkname). As a result, the link is now connected.

No action is required for this informational message.

A disconnect request has been sent to the CTCA or FCTC driver on the remote side of the link named in the message (linkname). It should respond by sending a disconnect response. Until a disconnect response is received, the link remains in substate 'Disconnecting-S(2)'.

No action is required for this informational message.

A disconnect request has been received from the CTCA or FCTC driver on the remote side of the link named in the message (linkname).

A disconnect response will be sent. When that completes, the link will be marked disconnected.

No action is required for this informational message.

A terminate request has been received from the CTCA or FCTC driver on the remote side of the link named in the message (linkname). A terminate request indicates that the node on the remote side of the link is being shut down; a disconnect request indicates only that the remote link is being disconnected.

A disconnect response is sent. When that completes, the link is marked disconnected.

No action is required for this informational message.

A message was received on the link named in the message (linkname), and either the contents of the message were invalid (incorrect block header and trailer) or the message length exceeded the maximum block size.

The control blocks for the link are snapped and the link is disconnected. If the link is connected, an attempt is made to disconnect the link properly. This message is followed by NETC029, which shows the header and trailer of the invalid message.

If this error occurred as a result of hardware problems or a remote disconnect (a write was possibly purged), then no action is required until the link is to be reconnected. Otherwise, this error indicates a possible logic error in the buffer management logic of the CTCA or FCTC driver and the problem should be reported to your Software AG technical support representative.

A CONNECT command was issued to the CTCA or FCTC driver for the link named in the message (linkname) as a result of either an operator CONNECT command or automatic start/restart of the link. A connect request was sent to the remote CTCA or FCTC driver. It should send a connect response to complete the connect sequence. Until that time, the link will be marked "Connecting-S(2)".

No action is required for this informational message.

During the connect sequence for the link named in the message (linkname), the remote CTCA or FCTC driver identified itself as being link linkname2 on node nodename, and using remote device Cuu. The maximum receive buffer size is RCVBLKSZ and is provided as an easy way to verify that the local write buffer size and the remote buffer size are efficiently set. When the send buffer size is not a direct multiple of the receive buffer size or vice versa, the efficiency of I/O operations may be decreased.

No action is required unless tuning of send and receive buffer sizes are desired.

This message is issued immediately after message NETC026 when an invalid message has been received. The eight-byte header and the eight-byte trailer are printed in hexadecimal for debugging purposes. The first four bytes of the trailer are the compliment of the first four bytes of the header. The second four bytes of the trailer are the compliment of the second four bytes of the header.

If this error occurred as a result of hardware problems or a remote disconnect (a write was possibly purged), then no action is required until the link is to be reconnected. Otherwise, this error indicates a possible logic error in the buffer management logic of the CTCA or FCTC driver and the problem should be reported to your Software AG technical support representative.

An I/O operation completed with a unit check status in which the sense data indicated "Intervention Required". This indicates that the remote side of the CTCA or FCTC is not ready as a result of a system reset, a selective reset, or an interface disconnect.

The first two of these conditions normally occur when a remote IPL occurs, or when the subchannel path is varied offline. The last of these conditions normally occurs when an active I/O operation is purged. In any case, this side of the CTCA or FCTC is incapable of successfully sending a request to the other side.

If Entire Net-Work is not active on the remote system, restart Entire Net-Work if possible. Entire Net-Work should automatically attempt to connect to this side during startup. Make sure the remote subchannel path is online by issuing the D M=DEV(Cuu) command on the remote system.

If Entire Net-Work is active on the remote system, the remote Entire Net-Work must issue an I/O request to the device to clear the not ready condition. If the link is disconnected on the remote side, issue the CONN linkname command to connect the links. If the link is connected, issue the DISC linkname command followed by the CONN linkname command. If the link is in the process of connecting but is not yet connected, issue the CTCA linkname CLOSE OPEN or FCTC linkname CLOSE OPEN command to close and reopen the link, followed by the CONN linkname command to initiate the connect.

An I/O operation on the link named in the message (linkname) has completed in error. The error is considered permanent and the link will be disconnected.

This message is followed by message NETC032 which explains the I/O error in more detail.

Analyze the device and unit status bytes of the Channel Status Word to determine the exact I/O condition. If the problem is a hardware problem, contact your hardware support representative and reconnect the link when the problem is corrected.

If the problem appears to be a software problem, issue the CTCA linkname SNAP or FCTC linkname SNAP command, and then contact your Software AG technical support representative.

This message immediately follows message NETC031 when an I/O error has occurred.

The last Channel Command Word (CCW) to complete, the Channel Status Word (CSW), the Sense Data (SNS) and IOS Post Code (PC) are displayed in hexadecimal.

Analyze the device and unit status bytes of the Channel Status Word to determine the exact I/O condition. If the problem is a hardware problem, contact your hardware support representative and reconnect the link when the problem is corrected.

Refer to the IBM documentation on CTCA or FCTC Sense Codes.

The driver dequeues and processes Work Queue Elements for events that occur according to rules defined in a finite state table.

The event name for the event is marked in the state table as "Not Applicable" for the current state. This indicates that either the state table is incorrectly defined or a logic error in the driver is causing the event to occur.

Contact your Software AG technical support representative for assistance.

This condition occurs when a logical message within a block of messages does not start where it is expected to start. This condition is detected by the receiving side of the link. It indicates that a logic error has occurred in either the sender's buffer fill routine or the receiver s buffer process routine.

The control blocks for link linkname are snapped, and the link is disconnected.

Contact your Software AG technical support representative for assistance.

A message was received on the link named in the message (linkname), in which the length of the message exceeds the size of the short term buffer pool. The driver is therefore unable to copy the message from its buffer to a short term buffer and is discarding it.

This error message is followed by error message NETC036.

Either expand the size of the short term buffer pool, or change the application to issue smaller requests to the short term buffer pool. For information about setting the size of the buffer pool, see the section Entire Net-Work Node Statement.

This error message is issued immediately after error message NETC035 or error message NETC037 is issued because of a received message that cannot be copied due to its length.

The received message is discarded. The message length is displayed for informational purposes.

See error message NETC035 or NETC037.

A message was received on the link named in the message (linkname), but there was insufficient storage remaining in the short term buffer pool to copy the message. The CTCA or FCTC driver is therefore unable to copy the message from its buffer to a short term buffer and is discarding it.

This error message is followed by error message NETC036.

Either expand the size of the short term buffer pool, or change the application to issue smaller requests to the short term buffer pool. For information about setting the size of the buffer pool, see the section Entire Net-Work Node Statement .

The link named in the message (linkname) has resumed processing of data and requests.

No action is required for this informational message.

The link named in the message (linkname) has suspended processing of data and requests. This condition occurs either when an operator requests the link to suspend (CTCA linkname SUSPEND or FCTC linkname SUSPEND) or when a buffer shortage condition occurs.

Issue the CTCA linkname RESUME or FCTC linkname RESUME command to restart processing on the link when desired.

A CTCA or FCTC linkname command was passed to the CTCA or FCTC driver but the link linkname is not a CTCA or FCTC type of link.

Reissue the command, specifying either the correct link name or the correct driver name.

A CTCA or FCTC linkname command was accepted for processing.

Depending on the substate of the link, actual processing of the command(s) may be done immediately. Processing is deferred if the link is suspended.

No action is required for this informational message.

The statistics for the link named in the message (linkname) have been reset either as a result of an operator request or automatic reset. The next statistics display will show only activity after this reset.

No action is required for this informational message.

The current state of the link or driver listed in the message (name) is displayed with a count of messages sent and received. The message counts are for the period of time since the driver was opened, the link connected, or the statistics reset for either the driver or the link.

This message is automatically produced as a result of a command being issued to a link or driver while the link or driver was in an incorrect state for the command or as a result of a CTCA name STATUS or FCTC name STATUS command being issued.

No action is required for this informational message.

A CTCA linkname ALTER or FCTC linkname ALTER command was issued for link linkname, but the configuration was not modified because one or more parameters are incorrect.

Determine which parameters are incorrect; then correct the command and reissue it.

An attempt was made to open a link that is already open or has been disabled.

No action is required for this warning message.

An I/O operation was started on link linkname, but proper notification of the sending of the disconnect message was never received.

This problem can be caused by hardware problems or problems with Entire Net-Work on either side of the link. Possible hardware problems include:

• powering off the channel adapter

• disconnecting a cable on the remote side of the adapter

• powering off or IML/IPLing the remote system

• forcing off the device or path

• bad communications lines when using channel extenders.

Possible problems with the remote Entire Net-Work include:

• The remote Entire Net-Work has been canceled or forced, preventing normal disconnect

• The remote Entire Net-Work is not being dispatched by MVS due to another address space consuming the remote CPU

• A message has been send out of order, or a partial message received. (NET0151 may be evident.)

Determine why the device failed to complete the I/O operation. The command CTCA linkname SNAP or FCTC linkname SNAP should be issued on both sides of the adapter to print the internal trace tables and dump link specific control blocks. If Entire Net-Work fails to respond to the command, check to see if Entire Net-Work can be dispatched by MVS due to dispatching priorities and a higher priority address space consuming the CPU. Change Entire Net-Work's performance group if necessary.

If the links fail to reconnect, issue the MVS commands D U, cuu and D M, DEV=(cuu) where cuu is the unit address. Verify the following: the device is online, the path is logically and physically online, the path is operational. Vary the device and path online if necessary.

If the device or a path is not operational, physically check the device, channel cables, ESCON director and any other piece of hardware that comprises the channel-to-channel link. Contact the appropriate hardware vendor if necessary.

A CTCA or FCTC linkname OPEN or CLOSE command was issued for link linkname, and the link was successfully opened or closed.

No action is required for this informational message.

An I/O operation was started on link linkname, but ending status (channel end and device end) was never received. After 60 seconds, the link is automatically disconnected.

This problem can be caused by hardware problems or problems with Entire Net-Work on either side of the link. Possible hardware problems include the following: powering off the channel adapter; disconnecting a cable on the remote side of the adapter; powering off or IML/IPLing the remote system; forcing off the device or path; bad communications lines when using channel extenders.

Possible problems with the remote Entire Net-Work include the following: it has been canceled or forced, preventing normal disconnect; it is not being dispatched by MVS due to another address space consuming the remote CPU; it is looping or is in an abnormal wait.

Determine why the device failed to complete the I/O operation. The command CTCA linkname SNAP or FCTC linkname SNAP should be issued on both sides of the adapter to print the internal trace tables and dump link specific control blocks. If Entire Net-Work fails to respond to the command, check to see if Entire Net-Work can be dispatched by MVS due to dispatching priorities and a higher priority address space consuming the CPU. Change Entire Net-Work s performance group if necessary.

If the links fail to reconnect, issue the MVS commands 'D U, cuu' and 'D M, DEV=(cuu)' where cuu is the unit address. Verify the following: the device is online, the path is logically and physically online, the path is operational. Vary the device and path online if necessary.

If the device or a path is not operational, physically check the device, channel cables, ESCON director and any other piece of hardware that comprises the channel-to-channel link. Contact the appropriate hardware vendor if necessary.

This multi-line display is produced when the CTCA linkname STATS or FCTC linkname STATS command is issued, or when the automatic statistics interval has expired and PSTATS=Y is specified in the link configuration parameters. Values are displayed and updated asynchronously; therefore, the totals displayed may not always be accurate.

The contents of this message are as follows

No action is required for this informational message.

A CTCA/FCTC linkname ALTER or CTCA/FCTC linkname SHOW command was issued. The information displayed shows the current configuration for the link.

If an FCTC command was issued, then the following line is printed:

CHREAD(channel-type)  TOKEN(tokenid)

No action is required. This message is informational only.

An attempt was made to connect an FCTC link to a CTCA link or prior version FCTC link. This is an invalid connection.

Correct the configuration so that both links are using either the FCTC line driver or the CTCA line driver.

An attempt was made to connect two links that have incompatible UNITREAD or UNITWRT settings.

Ensure that channel pairs are defined so that they have UNITREAD on one side and UNITWRT on the other side.

This message is issued in response to link-specific CTCA and FCTC operator commands when no matching links are found.

No action is required. This message is informational only.

A unit has become unavailable and the link has reverted to impaired mode. The link name (linkname) and unit name (unit) are given in the message

The link can continue to function in impaired mode until the problem is resolved. After the unit is repaired, disconnect and reconnect the link to make it fully functional again.

COMPAT=Y cannot be specified if the ADARUN parameter ZIIP is set to YES. zIIP processing is disabled.

Set COMPAT=N or ZIIP=NO.