LOCAL DEVICE REMOTE  PATHIN  REMOTE               LAST      MXFER
PATHIN       SYSTEM  STATUS  PATHOUT RETRY MAXMSG RECVD     TIME
ldev         sysname status  rdev    retry maxmsg lastrcvd  xfertime

LOCAL  REMOTE  REMOTE  PATHIN DELIVRY BUFFER MSGBUF SIGNL
PATHIN PATHOUT SYSTEM  STATUS PENDING LENGTH IN USE NUMBR   NOBUF
ldev   rdev    sysname status pndmsg  bflen  in-use sgnl#   nobuf

LOCAL DEVICE REMOTE  PATHOUT REMOTE               TRANSPORT
PATHOUT      SYSTEM  STATUS  PATHIN  RETRY MAXMSG CLASS
ldev         sysname status  rdev    retry maxmsg classname

LOCAL   REMOTE  REMOTE  PATHOUT TRANSFER BUFFER MSGBUF SIGNL  MXFER
PATHOUT PATHIN  SYSTEM  STATUS  PENDING  LENGTH IN USE NUMBR  TIME
ldev    rdev    sysname status  pndmsg   bflen  in-use sgnl#  ioxfr

STRNAME      REMOTE  PATHIN  UNUSED               LAST      MXFER
PATHIN       SYSTEM  STATUS  PATHS   RETRY MAXMSG RECVD     TIME
strname      sysname status  numopen retry maxmsg lastrcvd  xfertime

STRNAME        REMOTE  PATHIN DELIVRY BUFFER MSGBUF SIGNL
PATHIN  LIST   SYSTEM  STATUS PENDING LENGTH IN USE NUMBR   NOBUF
strnm  listnbr sysname status pndmsg  bflen  in-use sgnl#   nobuf

STRNAME      REMOTE  PATHOUT UNUSED               TRANSPORT
PATHOUT      SYSTEM  STATUS  PATHS   RETRY MAXMSG CLASS
strname      sysname status  numopen retry maxmsg classname

STRNAME        REMOTE  PATHOUT TRANSFER BUFFER MSGBUF SIGNL  MXFER
PATHOUT LIST   SYSTEM  STATUS  PENDING  LENGTH IN USE NUMBR  TIME
strnm  listnbr sysname status  pndmsg   bflen  in-use sgnl#  ioxfr


[NO SIGNALLING PATHS MATCH THE SPECIFIED CRITERIA]

[THERE ARE NO bound PATHS DEFINED TO THIS SYSTEM]

[pathtype REQUESTED BUT NOT SHOWN
ARE NOT DEFINED TO XCF AS bound
optionaltrailer]

[TRANSPORT CLASSES REQUESTED BUT NOT SHOWN
DO NOT HAVE DEVICES OR STRUCTURES ASSIGNED TO
THEM, OR ARE NOT DEFINED]

hh.mm.ss

The time in hours (00-23), minutes (00-59), and seconds (00-59) for the DISPLAY XCF command.

ldev

The device number for the inbound or outbound signalling path on the local system.

sysname

The name of the system connected to the signalling path. If the system is not known, ???????? is displayed for the system name.

status

One of the following:

STARTING

The system is verifying that the signalling path is suitable for XCF.

RESTARTING

XCF is restarting a failed signalling path.

WORKING

The signalling path is capable of message transfer.

STOPPING

XCF is removing the signalling path from the signalling service.

LINKING

XCF is establishing communication links between systems for this signalling path.

INOPERATIVE

The signalling path is defined to XCF but not usable until hardware and/or definition problems are resolved.

STOPFAILED

XCF was removing the signalling path from the signalling service, but there was a failure during removal.

REBUILDING

Rebuild has been initiated for the associated list structure.

QUIESCING

The signalling path is operational but no new I/O operations are being initiated. I/O operations may or may not have completed.

QUIESCED

The signalling path is operational but all I/O operations have completed and no new I/O operations are being initiated.

STALL-IOPND

The signalling path appears to be capable of message transfer in that it has established connectivity with the remote system. However, the path has pending I/O that does not appear to be completing in a timely manner. If the condition persists, the path will be restarted for a stalled I/O condition.

Stalled I/O is often caused by no buffer conditions on the inbound side of the path, which in turn are often caused by XCF group members failing to process signals in a timely fashion (refer the explanation of message IXC431I for possible reasons why). Stalled I/O can also be caused by system delays on the inbound side as well as problems, issues, or errors with the underlying hardware for the signalling path.

STALL-INOP

The signalling path appears to be capable of message transfer in that it has established connectivity with the remote system. However, the path is not considered viable. For example, the inbound side may be experiencing no buffer conditions and signals therefore cannot be transferred. If the conditions that make the path not viable are resolved, the path will once again be used for transferring signals. If not, the path may be restarted for a stalled I/O condition.

STALL-SS?

The signalling path appears to be capable of message transfer in that it has established connectivity with the remote system. However, the path is not considered viable and is being monitored for potential sympathy sickness impact. In particular, the inbound side is experiencing no buffer conditions that appear to be caused, at least in part, by one or more stalled XCF group members that have failed to process signals in a timely manner. If these delays persist, the outbound side may be impacted as well. If the conditions that make the path not viable are resolved, the path will once again be used for transferring signals. If not, the path may be restarted for a stalled I/O condition.

STALL-SS

The signalling path appears to be capable of message transfer in that it has established connectivity with the remote system. However, the path is not considered viable. The outbound side is suffering from sympathy sickness since there are signals that cannot be transferred to the inbound side. Signals for the target system are being delayed and/or rejected because the inbound side is experiencing no buffer conditions that appear to be caused by one or more stalled XCF group members that have failed to process signals in a timely manner. The actual impact is difficult to predict since it will depend on the set of applications and subsystems whose signals are being delayed or rejected. In general, processing of work is likely to hang. The impact may be isolated to signals in a particular transport class. In some cases the impact can spread to other transport classes. In the worst case, all signals from the outbound side to the inbound side could be impacted.

XCF issues messages IXC440E and IXC640E when such sympathy sickness is detected. XCF may be able to alleviate the sympathy sickness condition if the current Sysplex Failure Management (SFM) policy MEMSTALLTIME specification for the target system permits such action. Message IXC615I is issued to indicate such action, or to request operator intervention if automatic action is not permitted.

rdev

The device number for the associated inbound or outbound signalling path on the remote system. If the device number is not known, question marks are listed.

retry

The retry limit for the path. The retry limit is used to determine whether a signalling path should be removed.

maxmsg

The amount of space, in kilobytes, of message buffer space defined to the signalling service for the path.

lastrcvd

Signal number of the last signal received over the signalling path. As each signal is queued for transfer over a signalling path, it is assigned an over increasing number (subject to wrap). That signal number, modulo 100,000 is displayed for the latest signal to be received. Signal numbers may be reset to lower values when the signalling path is restarted.

xfertime

The average transfer time, in microseconds, for signals recently received over the signalling path. Up to 64 of the latest signals received over the path are considered when computing the average transfer time. Signals received more than a minute ago are excluded from the average. For a seldom used path, excluding old signals can make it appear that its transfer time is changing even though it is not receiving any new signals. A dash is displayed if no data is available (no signals recently received or the sending system does not provide the necessary data). Average transfer times in excess of a tenth of a second are displayed as 99999. The transfer time shown is recomputed using the data that is current at the time the display command is processed.

pndmsg

For an outbound path, indicates the number of signals queued to the path for which I/O transfer appears to be pending. Since notification of I/O completion is asynchronous to the actual I/O transfer, the signals may in fact have been transferred to the target system even though the count is not zero.

For an inbound path, indicates the number of signal buffers associated with the path that are engaged in some stage of message dilivery. An idle inbound CTC path will usually have four signals pending. An idle inbound list path will usually have no signals pending. Delivery counts will be greater than the idle values when the signal buffers are in the midst of delivering a message to a user signal exit routine. Delivery counts smaller than the idle value (for a CTC path) may be indicative of a signal buffer shortage, which in turn could cause signalling performance degradation. Note that some combinations of current buffer length and MAXMSG specifications can cause a CTC path to run idle with fewer than four buffers.

For an inbound path, the number of signal buffers that are pending delivery may be less than the number of work items pending delivery to the XCF group members (as shown by the DISPLAY XCF,GROUP,grpname,memname command). The difference arises from the fact that messages are not the only work items that can be queued for a member. Also, XCF does not necessarily use signal I/O buffers to queue messages for delivery.

bflen

The maximum number of bytes of message data that will fit in the size signal buffer that is currently in use by the signalling path. The buffer length used by the signalling path is adjusted dynamically by XCF in response to the message traffic load.

in_use

The amount of message buffer space, in kilobytes, currently associated with the signalling path.

Note that for an outbound path, this value may exceed the MAXMSG value specified for the path since outbound buffer pools are not managed on a path basis but on a transport class basis. The current path value may also include signal buffers from other transport classes that do not have their own signalling paths. Signal buffers for internal XCF signals, which are managed separately from customer defined transport classes may also be included.

sgnl#

Each signal sent over a signalling path is assigned a signal number (subject to wrap). That signal number, modulo 100,000 is displayed.

For an outbound signalling path, this value will be the signal number of the last signal queued for transfer over the path. For an inbound signalling path, this value will be the signal number of the latest signal received over the path. The signal number of the outbound side of a path can be compared to the signal number of the inbound side of the path to gauge activity of the signalling path.

Signal numbers may be reset to lower values when the signalling path is started, restarted, or stopped.

nobuff

For an inbound path, indicates the number of times (modulo 100,000) that lack of a signal buffer prevented a new read operation from being initiated over the path. This count is cumulative for the life of the path so a nonzero value does not imply that the path is currently experiencing a buffer shortage. The value should be compared to the data from a subsequent display command to determine whether the path had buffer shortages recently.

classname

The name of the transport class to which this signalling path is assigned. classname is only displayed for outbound signalling paths, and only if a signalling path is assigned to the class. Transport classes without devices assigned are not displayed.

strname

Name of structure defined for use as a signalling path.

numopen

Number of lists in the list structure that are available for use as signalling paths.

ioxfr

For an outbound path, indicates the transfer time value that is currently being used to determine which outbound signalling paths are most likely to provide the fastest signal delivery. The average transfer time is measured by the inbound side of the path and periodically sent back to the system on the outbound side. The value shown in the display is the average transfer time that was most recently received from the inbound side. In contrast, the transfer time displayed for an inbound path is recomputed each time the display command is issued.

A dash is displayed if no data is available (no signals recently received or the sending system does not provide the necessary data). Average transfer times in excess of a tenth of a second are displayed as 99999.

listnbr

The decimal list number of the list being used for the signalling path.

bound

One of the following:

INBOUND

Inbound paths were specified, but none are defined.

OUTBOUND

Outbound paths were specified, but none are defined.

PATHIN

Inbound paths were specified, but were not displayed.

PATHOUT

Outbound paths were specified, but were not displayed.

pathtype

One of the following:

DEVICES

Devices were specified.

STRUCTURES

Structures were specified.

optionaltrailer

One of the following:

OR ARE NOT IN REQUESTED TRANSPORT CLASS

Specified paths may not have been displayed because they were not in the requested transport class.

OR DO NOT HAVE REQUESTED STATUS

Specified paths may not have been displayed because they did not have the requested status.

ARE NOT IN REQUESTED TRANSPORT CLASS, OR DO NOT HAVE REQUESTED STATUS

Specified paths may not have been displayed either because they were not in the requested transport class or because they did not have the requested status.