IXL150I

number1

Explanation
In the message, text is: COUPLING FACILITY   type.mfg.plant.sequence
                    PARTITION:       partition side  CPCID: cpcid
                    LP NAME:         lparname        CPC NAME: cpcname
                    CONTROL UNIT ID: cuid
NAMED cfname
COUPLING FACILITY SPACE UTILIZATION
  ALLOCATED SPACE                     DUMP SPACE UTILIZATION
    STRUCTURES:  strspace u    STRUCTURES DUMP TABLES:    strdumpspace u
    DUMP SPACE:  dumpspace u   TABLE COUNT:               tablecount
    FREE SPACE:  freespace  u  FREE DUMP SPACE:           freedumpspace u
    TOTAL SPACE: totalspace u  TOTAL DUMP SPACE:          totaldumpspace u
                               MAX REQUESTED DUMP SPACE:  maxreqdumpspace u
        VOLATILE:  {YES|NO}
        CFLEVEL:   cflevel
        CFCC RELEASE  release1.release2, SERVICE LEVEL service1.service2

        BUILT ON      mm/dd/yyyy AT hh:mm:ss
        STORAGE INCREMENT SIZE:               stgincrement u
        STORAGE-CLASS MEMORY INCREMENT SIZE:  scmincrement u
COUPLING FACILITY HAS ONLY ONE ONLINE SENDER PATH 

[COUPLING FACILITY HAS ONLY SHARED PROCESSORS|COUPLING FACILITY HAS ONE OR MORE DEDICATED PROCESSORS]
[COUPLING FACILITY HAS shr SHARED AND ded DEDICATED PROCESSORS 
  DYNAMIC CF DISPATCHING: {ON | OFF | THIN INTERRUPTS]

COUPLING FACILITY IS standalonestate
COUPLING THIN INTERRUPTS: cti
[COUPLING FACILITY HAS ONLY ONE ONLINE SENDER PATH]

mtofstatus
[REASON: mtofreason]

STORAGE CONFIGURATION
                        ALLOCATED         FREE             TOTAL
CONTROL SPACE:          allocspace u      freespace u      totalspace u
NONCONTROL SPACE:       allocspace u      freespace u      totalspace u
[STORAGE-CLASS MEMORY:  allocspace u      freespace u      totalspace  u      ]
[NO COUPLING FACILITY SPACE DATA AVAILABLE]

PATH             PHYSICAL            LOGICAL        CHANNEL TYPE        AID PORT
chpid[/pchid]    phystatus           logstatus      chtype [pathmode]   aid port

COUPLING FACILITY SUBCHANNEL STATUS                               
 TOTAL: number1		IN USE: number2  NOT USING: number3	 NOT USABLE: number4
 OPERATIONAL DEVICES / SUBCHANNELS:                                      
       device / subchannel    device / subchannel    
       device / subchannel    device / subchannel
 NOT OPERATIONAL DEVICES / SUBCHANNELS:
       device / subchannel    device / subchannel    
       device / subchannel    device / subchannel

REMOTELY CONNECTED COUPLING FACILITIES 
       CFNAME               COUPLING FACILITY	             
       -------              -----------------
       rfcfname             rftype.rfmfg.rfplant.rfsequence
                            PARTITION: partition rfside CPCID: rfcpcid 
                            CHPIDS ON cfname CONNECTED TO REMOTE FACILITY
                            RECEIVER:    CHPID      TYPE
                                         rfchpid    rfchtype [rfpmode]
                            SENDER:      CHPID      TYPE       
                                         rfchpid    rfschtype [rfspmode]
                             [* = PATH OPERATING AT REDUCED CAPACITY]

[NO REMOTELY CONNECTED COUPLING FACILITY DATA AVAILABLE]
[THE SIGNALLING VECTOR WAS NOT CREATED IN THIS CF]
NOT OPERATIONAL CHPIDS ON cfname
 rfinochpid rfinochpid rfinochpid rfinochpid
 rfinochpid rfinochpid rfinochpid rfinochpid

Coupling
Facility space data will not be available if either this system is
not physically connected to the Coupling Facility at the time the
DISPLAY CF command was executed, or this system is physically connected
to the Coupling Facility, but the Coupling Facility is not defined
in the active CFRM policy. In either case, the COUPLING FACILITY
SPACE UTILIZATION and the COUPLING FACILITY SPACE CONFIGURATION sections
will be replaced with NO COUPLING FACILITY SPACE DATA AVAILABLE.
Sender
Path data will not be available if no channel paths are currently
defined to the Coupling Facility control unit. In this case,  the SENDER
PATH section is replaced with NO PATH STATUS AVAILABLE.
Coupling
Facility Subchannel data will not be available if no subchannels/devices
are currently defined for this Coupling Facility control unit. In
this case, the COUPLING FACILITY DEVICE section is replaced
with NO COUPLING FACILITY DEVICE STATUS AVAILABLE.
Information about one or more coupling facilities was
requested by a D CF command. Information displayed will contain space
utilization and configuration data of the requested facility or all
coupling facilities. Sender CHPIDs and coupling facility subchannels
are also displayed with their status for each coupling facility. If
the coupling facility is level 10 or higher, then available information
is also displayed about any remotely connected coupling facilities
and the CHPIDs that may be used to connect them.
The
Display CF command also displays information on the CF request time
ordering function: 
In the message text: hh.mm.ss
The time in hours (00-23), minutes (00-59), and seconds (00-59).
type
Node type (See ndetype in IXLYNDE).
mfg
Node manufacturer ID (See ndemfg in IXLYNDE).
plant
Node manufacturer plant ID (See ndeplant in IXLYNDE).
sequence
Node sequence number (See ndesequence in IXLYNDE).
partition
Node LPAR partition number (See ndepartition in IXLYNDE).
side
The node PP/SI mode indicator and configuration code from the
IXLYNDE are used to determine the value for side.
Value and meaning are: SIDE: 0 means the coupling facility is on SIDE 0 of a partitionable
CPC.
SIDE: 1 means the coupling facility is on SIDE 1 of a partitionable
CPC.
blank means the coupling facility is in a non-partitionable CPC.

cpcid
Node Central Processor Complex (CPC) ID (See ndecpcid in IXLYNDE).
lparname
Name assigned to the logical partition on which the CF is running.
N/A indicates that the name is not available.
cpcname
Name assigned to the CPC on which the CF is running. N/A indicates
that the name is not available.
cuid
Control unit number of the coupling facility.
cfname
Name of the coupling facility from the CFRM active policy.
strspace
Total amount of facility storage in use by allocated
structures.
u
The integer size unit specification. One of the following: K (kilobytes)
M (megabytes)
G (gigabytes) 
T (terabytes)

Note: The size unit displayed will be the highest one which can
be used to show the storage increment  size value.  For  example,
a storage increment size of 1048576K may be converted to a storage
increment size of 1G for the purpose of messages. A storage increment
size  of 120000K will not cause the  displayed size to be converted
 because it is not an even multiple of megabytes, gigabytes, or terabytes.
All the other size units (for example, strspace, strdumpspace, dumpspace, freespace, freedumpspace,
and totalspace) will be displayed with  the same
unit specification chosen for the storage increment size. This will
allow for better readability of the size counts when compared to the
total counts for the specific coupling facility.

strdumpspace
Total amount of facility dump storage assigned to dump tables.
dumpspace
Total amount of storage assigned to dumping storage.
tablecount
Current® number of dump
tables assigned to structures.
freespace
Total amount of storage available for assignment
to structures.
freedumpspace
Total amount of dumping storage available for assignment
in a dump table.
totalspace
Total amount of storage available,for the allocation
of structures.
totaldumpspace
Total amount of storage assigned as dumping storage.
maxreqdumpspace
Maximum amount of dump space requested to be assigned
to dump tables.
YES
The facility space is volatile.
NO
The facility space is non-volatile.
stgincrement
Storage increment size for this facility.
cflevel
Coupling facility level for this facility
release1
Coupling facility release level part 1
release2
Coupling facility release level part 2
service1
Coupling facility service level part 1
service2
Coupling facility service level part 2
mm/dd/yyyy
The date in month, day, and year.
hh:mm:ss
The time in hours, minutes, and seconds.
stgincrement
Storage increment size for this facility.
scmincrement
Storage-class memory increment size for this facility.
standalonestate
One of the following:STANDALONE
The CF resides on a CEC with no general-purpose processors, so
that no z/OS image can run on the CEC.
NOT STANDALONE
The CF resides on a CEC with at least one general-purpose processor,
so it is possible to configure a z/OS image on the same CEC.

cti
One of the following:ENABLED
Coupling thin interrupts is enabled for the coupling facility.
NOT-ENABLED
Coupling thin interrupts is not enabled for the coupling facility.
NOT-AVAILABLE
Coupling thin interrupts is not available in the coupling facility.
A CFLEVEL of 19 or higher has the coupling thin interrupt functionality
available for enablement.

text
text is one of the following:CF REQUEST TIME ORDERING: REQUIRED AND ENABLED
The CF request time ordering function is required for operations
to the CF. The required hardware (CF request time ordering function
installed on both the CECs where the CF and z/OS® systems are running) is available. The CF and z/OS system
are synchronized in the same timing network.
CF REQUEST TIME ORDERING: NOT-REQUIRED AND ENABLED
The CF request time ordering function is not required for operations
to the CF. The required hardware (CF request time ordering function
installed on both the CECs where the CF and z/OS systems are running) is available. The CF and z/OS system
are synchronized in the same timing network.
CF REQUEST TIME ORDERING: NOT-REQUIRED AND NOT-ENABLED
The CF request time ordering function is not required for operations
to the CF. The CF request time ordering function is not enabled: either
the required hardware (CF request time ordering function installed
on both the CECs where the CF and z/OS systems
are running) is not available, or the CF and z/OS system are not synchronized
in the same timing network. 
CF REQUEST TIME ORDERING: REQUIRED AND NOT-ENABLED
The CF request time ordering function is required for operations
to the CF; however, the CF request time ordering function is not enabled:
either the required hardware (CF request time ordering function installed
on both the CECs where the CF and z/OS systems
are running) is not available, or the CF and z/OS system are not synchronized
in the same timing network.. The reason CF request time ordering
is not enabled is described in the REASON message text.
CF REQUEST TIME ORDERING: REQUIRED AND WILL NOT BE ENABLED
The CF request time ordering function is required for operations
to the CF. However, the timing characteristics of the CF are not consistent
with timing characteristics of the of the z/OS system. 
REASON: reason
reason is one of the following:REASON: FUNCTION NOT INSTALLED ON THIS SYSTEM
The CF request time ordering function is required for operations
to the CF; however, the function is not installed on the CEC running
the z/OS system.
REASON: ETR NOT CONNECTED TO COUPLING FACILITY
The CF request time ordering function is required for operations
to the CF; however, there is no ETR connected to the CEC where the
CF is running.
REASON: REQUEST TIME ORDERING FUNCTION FAILURE
The CF request time ordering function is required for operations
to the CF; however, the CF request time ordering function has encountered
a non-recoverable error. The ETR connected to the sender z/OS system and the receiver CF system may not
be functioning properly.
REASON: REQUEST TIME ORDERING NOT INSTALLED ON THIS SYSTEM
The CF request time ordering function is required for operations
to the CF; however, the CF request time ordering function is not available
or not installed on the CEC running the z/OS system.
CF request time ordering function must be installed on both CECs where
the sender z/OS system and
the receiver CF are running in order for CF request time ordering
to be enabled.
REASON: CTNID MISMATCH - CF CTNID: cfstpid
The CF request time ordering function is required for operations
to the CF; however, the CTNID that is defined for the CEC that is
running the CF does not match the CTNID that is defined for the CEC
that is running the z/OS system.
The cfstpid is the eight-byte STP portion of the
CTNID that has been defined for the CEC running the CF. The sysplex
is running in a Coordinated Timing Network that is using STP to steer
the local clock. The ETR portion of the CNTID is not displayed.Issue
D ETR to obtain CTN information for the CEC running the z/OS system.

REASON: ETR NETID MISMATCH - CF ETR NETID: etr netid
The CF request time ordering function is required for operations
to the CF; however, the ETR that is connected to the CEC that is running
the CF does not match the ETR that is connected to the CEC that is
running the z/OS system. Issue
D ETR to obtain the ETR NetID of the ETR connected to the z/OS system.
REASON: CF IS OUT OF SYNCH WITH TIMING NETWORK
The CF request time ordering function is required for operations
to the CF; however, the TOD clock for the CF is not in synchronization
with the timing network in use by the other systems in the sysplex.
The timing network is defined by the CTNID for the CEC the CF is running
on.

COUPLING FACILITY HAS ONLY SHARED PROCESSORS
All central processors in the coupling facility are defined to
be shared. IBM® recommends using
dedicated CPs for production coupling facility LPARs which will allow
the best performance and throughput. See the PR/SM™ Planning Guide for more information
regarding processor considerations for coupling facility LPARs.
COUPLING FACILITY HAS ONE OR MORE DEDICATED PROCESSORS
One or more central processors in the coupling facility is defined
to be dedicated. This is an optimal configuration. See the PR/SM Planning Guide for
more information regarding processor considerations for coupling facility
LPARs.
COUPLING FACILITY HAS num1 SHARED AND num2 DEDICATED
PROCESSORS
The number of shared and dedicated processors in the coupling
facility. This line is displayed only for a CFLEVEL 15 facility from
a z/OS V1R9 system or from
a z/OS system with the software
support installed. See the PR/SM Planning Guide for more information
about processor considerations for coupling facility LPARs.
 DYNAMIC CF DISPATCHING: ON | OFF | THIN INTERRUPTS
The Dynamic CF Dispatching setting for the coupling facility.
This line is displayed only for a CFLEVEL 15 facility from a z/OS V1R9 system or from a z/OS system with the software support
installed. The Dynamic CF Dispatching setting will
be THIN INTERRUPTS when the Dynamic CF Dispatching setting is OFF,
but coupling thin interrupts is enabled for the coupling facility.
The Dynamic CF Dispatching setting will display THIN INTERRUPTS only
for a CFLEVEL 19 facility from a z/OS V2R1 system or from a z/OS system
with the software support installed.See the PR/SM Planning Guide for
more information about the use of the Dynamic CF Dispatching function
for coupling facility LPARs.

allocspace
The total amount of storage of the indicated type currently allocated
for use by structures.
freespace
The total amount of storage of the indicated type currently available
for the allocation of structure objects.
totalspace
The total amount of storage of the indicated type in the facility.
chpid
Coupling facility sender CHPID.
pchid
Coupling facility sender PCHID.
phystatus
One of the following: ONLINE
The path chpid to the coupling facility cfname is
physically available for use. The chpid is configured
online and is operational.
ONLINE - DEGRADED
The path chpid to the coupling facility cfname is
physically available for use. The chpid is configured
online and is operating, but at a reduced capacity.
OFFLINE
The path chpid to the coupling facility cfname is
configured offline.
MISCABLED
The path chpid to the coupling facility cfname is
not connected to the correct facility.
NOT OPERATIONAL
The path chpid to the coupling facility cfname is
not operational.
FACILITY PAUSED
The path chpid to the coupling facility cfname is
not operational. The most recent path validation operation attempted
for this path received a facility paused status condition.
PATH NOT AVAILABLE
The path chpid to the coupling facility cfname is
not operational. The most recent path validation operation attempted
for this path received a path not available status condition. A path
not available status is reported when the CF is not responding. One
reason for this might be low LPAR weight assigned to the CF LPAR.
NOT IN CONFIGURATION
The path chpid to the coupling facility cfname is
defined to a control unit that is accessible by this partition; however
the channel path is not accessible by the partition (the channel path
is not in the access list nor in the candidate list for this partition).
The partition cannot access this channel path.

logstatus
One of the following: ONLINE
The path chpid to the coupling facility cfname is
logically online.
OFFLINE
The path sender chpid to the coupling facility cfname is
logically offline.

channel type
One of the following: CFS
The channel path type description of path chpid is
Coupling Facility Sender.
CBS
The channel path type description of path chpid is
Coupling Facility Integrated Cluster Bus Sender.
ICS
The channel path type description of path chpid is
Internal Coupling Sender.
CBP
The channel path type description of path chpid is
Coupling Facility Integrated Cluster Bus Peer.
CFP
The channel path type description of path chpid is
Coupling Facility Peer.
ICP
The channel path type description of path chpid is
Internal Coupling Peer.
CIB
The channel path type description of path chpid is
Coupling over Infiniband.
CS5
The channel path type description of path chpid is Coupling over PCIe.

pathmode
One of the following:H
The channel path supports a 1.0625 Gb/sec data rate (half rate).
F
The channel path supports a 2.125 Gb/sec data rate (full rate). It may operate at either 1.0625
or 2.125 Gb/sec.
1X-IFB
The channel path is operating at 1X bandwidth using the IFB protocol.
12X-IFB
The channel path is operating at 12X bandwidth using the IFB protocol.
12X-IFB3
The channel path is operating at 12X bandwidth using the IFB3 protocol.
8X-PCIE3
The channel path is operating at 8X bandwidth using the third generation PCIe protocol.

aid
The adapter identifier associated with path chpid,
if applicable and available.
port
The port associated with path chpid, if applicable
and available.
COUPLING FACILITY SUBCHANNEL STATUS
TOTAL:number1
Number of coupling facility subchannels that have been defined
for this system.
IN USE:number2
Number of coupling facility subchannels that are currently being
used by this system to execute requests to the coupling facility.
This is equal to the number of concurrent operations that can be initiated
to this coupling facility minus any subchannels that are not being
used because of subchannel tuning actions.
NOT USING:number3
Number of coupling facility subchannels that are eligible to be
used but are not currently being used by this system to execute requests
to the coupling facility. This is equal to the number of subchannels
that have been taken out of the pool of usable subchannels by subchannel
tuning actions. This count may temporarily include some number of
subchannels when a readjusting of the IN USE subchannel count is in
progress as a result of configuration actions against CF Links for
this facility.
NOT USABLE:number4
Number of coupling facility subchannels that have been defined
for this system that can not be used to execute requests to the coupling
facility. Equal to the number of subchannels defined that are in excess
of the number of concurrent operations that can be initiated to this
coupling facility. This count also includes the number of not-operational
subchannels, if any.
OPERATIONAL DEVICES / SUBCHANNELS:
The list of coupling facility subchannels to the coupling facility
that are operational and available for operations.
NOT OPERATIONAL DEVICES / SUBCHANNELS:
The list of coupling facility subchannels to the coupling facility
that are not operational and not available for operations.

device
Coupling facility device.
subchannel
Coupling facility subchannel.
rfcname
Name of coupling facility from CFRM active policy. If N/A is displayed,
then the  coupling facility which is remotely-connected is not also
connected to the system on which the D CF command was issued.
rftype
Node type (See ndetype in IXLYNDE).
rfmfg
Node manufacturer ID (See ndemfg in IXLYNDE).
rfplant
Node manufacturer plant ID (See ndeplant in IXLYNDE).
rfsequence
Node sequence number (See ndesequence in IXLYNDE).
partition
Node LPAR partition number (See ndepartition in IXLYNDE).
rfside
The node PP/SI mode indicator and configuration code from the
IXLYNDE are used to determine the value for side. Value and meaning
are: SIDE: 0 means the coupling facility is on SIDE 0 of a partitionable
CPC.
SIDE: 1 means the coupling facility is on SIDE 1 of a partitionable
CPC.
blank means the coupling facility is in a non-partitionable CPC.

rfcpcid
Node Central Processor Complex (CPC) ID (See ndecpcid in IXLYNDE).
rfchpid
CHPID installed on cfname that is being used for a peer connection
between coupling facility cfname and coupling facility rfcfname. An
asterisk following the CHPID indicates that the path is operating
at reduced capacity.
rfrchanpathtype
One of the following:CBP
The channel path type description of path chpid is
Coupling Facility Integrated Cluster Bus Peer.
CFP
The channel path type description of path chpid is
Coupling Facility Peer.
ICP
The channel path type description of path chpid is
Internal Coupling Peer.
CFR
The channel path type description of path chpid is
Coupling Facility Receiver.
CBR
The channel path type description of path chpid is
Coupling Facility Integrated Cluster Bus Receiver.
ICR
The channel path type description of path chpid is
Internal Coupling Receiver.
CIB
The channel path type description of path chpid is
Coupling over Infiniband.
CS5
The channel path type description of path chpid is Coupling over PCIe.

rfpmode
One of the following:H
The channel path supports a 1.0625 Gb/sec data rate (half rate).
F
The channel path supports a 2.125 Gb/sec data rate (full rate). It may operate at either 1.0624
or 2.125 Gb/sec.
1X-IFB
The channel path is operating at 1X bandwidth using the IFB protocol.
12X-IFB
The channel path is operating at 12X bandwidth using the IFB protocol.
12X-IFB3
The channel path is operating at 12X bandwidth using the IFB3 protocol.
8X-PCIE3
The channel path is operating at 8X bandwidth using the third generation PCIe protocol.

rfschanpathtype
One of the following:CFS
The channel path type description of path chpid is
Coupling Facility Sender.
CBS
The channel path type description of path chhpid is
Coupling Facility Integrated Cluster Bus Sender.
ICS
The channel path type description of path chpid is
Internal Coupling Sender.
CBP
The channel path type description of path chpid is
Coupling Facility Integrated Cluster Bus Peer Channel.
CFP
The channel path type description of path chpid is
Coupling Facility Peer Channel.
ICP
The channel path type description of path chpid is
Internal Coupling Peer Channel.
CIB
The channel path type description of path chpid is
Coupling over InfiniBand.
CS5
The channel path type description of path chpid is Coupling over PCIe.

rfspmode
One of the following:H
The channel path supports a 1.0625 Gb/sec data rate (half rate).
F
The channel path supports a 2.125 Gb/sec data rate (full rate). It may operate at either 1.0624
or 2.125 Gb/sec.
1X-IFB
The channel path is operating at 1X bandwidth using the IFB protocol.
12X-IFB
The channel path is operating at 12X bandwidth using the IFB protocol.
12X-IFB3
The channel path is operating at 12X bandwidth using the IFB3 protocol.
8X-PCIE3
The channel path is operating at 8X bandwidth using the third generation PCIe protocol.

rfinochpid
CHPID installed on cfname that is currently
not operational. The list of not operational CHPIDs may span multiple
lines, with up to eight CHPIDs per line.
etr netid
The ETR Net ID of the ETR connected to the Coupling Facility.

System action
The system continues processing.

Operator response
Not Applicable.

System programmer response
Not Applicable.

Source
Cross System Extended Services (XES)

Module
IXLR3DSF

Routing code
#

Descriptor code
5,8,9