XCF Paths attributes

The XCF Paths attribute group monitors the status and activity of XCF signaling paths between z/OS images.

Destination Device Represents the destination of the path. Destination devices may be coupling facility structures as well as CTC devices. In this case, the designation can be either ListStructure (which implies that the System To value is unknown), or CFList. It is also possible that the destination device is unknown at the time the data is collected. Valid format is a simple text string of 1 through 4 characters. To designate a structure in a situation for Destination Device:

Examples: CTC Device - 07F6. Structure - List

Managed System A sysplex in your enterprise that is being monitored by OMEGAMON XE for z/OS agents. Valid value is a character string with a maximum length of 32 bytes, in the format <plexname>:MVS:SYSPLEX.

Message Limit Maximum number of messages allowed to be sent by the signaling path. This is the maximum number of messages concurrently in progress. Valid value is an integer in the range 0 through 2147483647 and includes the use of the *AVG, *MAX, *MIN, or *SUM functions. An example is 750.

Origin Device Device from which the path originates. Origin devices may be Coupling Facility structures as well as CTC devices. In this case, the designation can be either ListStructure (which implies that the System To value is unknown), or CFList. Valid format is a simple text string of 1 through 4 characters. To designate a structure in a situation for Origin Device:

Examples: CTC Device - 07F6. Structure - List

Restart Count Number of times XCF restarted the signaling path. Valid value is an integer in the range 0 through 2147483647 and includes the use of the *AVG, *MAX, *MIN, or *SUM functions. An example is 1.

Retry Limit Retry limit for the signaling path. Valid value is an integer in the range 0 through 2147483647 and includes the use of the *AVG, *MAX, *MIN, or *SUM functions. An example is 60.

Retry Percent Percentage of the retry limit reached by the signaling path. Valid value is an integer in the range 0.0 through 100.0, to one decimal point precision, and includes the use of the *AVG, *MAX, *MIN, or *SUM functions. An example is 25.5.

Signals Pending Transfer Number of messages waiting to be sent through the signaling path. Valid value is an integer in the range 0 through 2147483647 and includes the use of the *AVG, *MAX, *MIN, or *SUM functions. An example is 2.

Signals Received Number of messages received through the signaling path. Valid value is an integer in the range 0 through 2147483647 and includes the use of the *AVG, *MAX, *MIN, or *SUM functions. An example is 1582.

Signals Sent Number of messages sent through the signaling path. Valid value is an integer in the range 0 through 2147483647 and includes the use of the *AVG, *MAX, *MIN, or *SUM functions. An example is 2176.

Status Status of the signaling path. Valid values are:

Starting

Validating and initializing path hardware.

Restarting

Making path ready (again) for use.

Working

Path is capable of being used.

Stopped

Stopping use, in the process of being removed from service.

WaitingForComp

Waiting for completion of initial protocol used to establish communication link.

NotOperational

Not operational. Path defined to XCF but not usable until hardware and/or definition problems are resolved.

Failed

Stop failed, intervention required.

Rebuilding

In the process of being rebuilt.

Quiescing

Quiescing the use of.

Quiesced

Use was quiesced.

Storage In Use Amount of storage that is in use by the path. Valid value is an integer in the range 0 through 2147483647 and includes the use of the *AVG, *MAX, *MIN, or *SUM functions. The value is expressed as a count of 1K buffers. For example, 280 KB is expressed as Storage_In_Use=280.

System From Name of the z/OS image from which the signaling path originates. Valid format is a simple text string from 1 through 8 characters; for example, SYSA.

System Name Path as seen from this system. Each path has a sending and receiving system. This attribute indicates which of these systems is providing the data observation.

System To Name of the z/OS image that is the destination of the signaling path. Valid format is a simple text string from 1 through 8 characters; for example, SYSB.

Times Buffer Unavailable Number of times message receipt was delayed because no buffer was available. Valid value is an integer in the range 0 through 2147483647 and includes the use of the *AVG, *MAX, *MIN, or *SUM functions. An example is 1.

Times Path Busy Number of sends issued when the path was busy. Valid value is an integer in the range 0 through 2147483647 and includes the use of the *AVG, *MAX, *MIN, or *SUM functions. An example is 1.

Transport Class Name of a transport class associated with the signaling path. Valid format is a simple text string from 1 through 8 characters; for example, DEFAULT.