1 Fields You can specify valid field names with the ADD, REMOVE, and SET commands. 2 ACKR_SQ Sequence number of the last acknowledgment received over the cluster connection. 2 ACK_LM Maximum number of OpenVMS Cluster messages the remote system can receive before sending an acknowledgment. 2 BDT_WAITS Number of times this connection had to wait for a buffer descriptor. 2 BLKS_REQ Number of block-request data commands initiated to block transfer data from the remote system to the local system. 2 BLKS_SENT Number of block-send data commands initiated to block transfer data from the local system to the remote system. 2 BUFF_DESCR Number of buffer descriptors in use. 2 CABLE_STATUS Status of the CI circuit paths A and B. Crossed cables are also noted. The field applies only to the CI. Possible displays are as follows: #-# - Paths A and B are bad. A-# - Path A is good. #-B - Path B is good. A-B - Paths A and B are good. CROSSED - Cables are crossed. 2 CIR_STATE State of the virtual circuit. Possible displays are as follows: CLOSED - Circuit is closed. OPEN - Circuit is open. ST_REC - Circuit has a start received. ST_SENT - Circuit has a start sent. VC_FAIL - Virtual circuit failure is in progress. 2 CL_EXPECTED_VOTES The number of votes the cluster has ever seen (or could see), as determined by the connection manager. The value is based on the maximum value of CL_EXPECTED_VOTES, the value for EXPECTED_VOTES that is specified by each node, and the sum of the cluster votes (CL_VOTES). CL_QUORUM is derived from CL_EXPECTED_VOTES. 2 CL_MEMBERS Number of processors participating in the cluster. 2 CL_QDVOTES Number of votes contributed by the quorum disk. 2 CL_QUORUM The number of votes that must be present for the cluster to function and permit user activity. CL_QUORUM is equal to (CL_EXPECTED_VOTES + 2) divided by 2. 2 CL_VOTES Total number of votes contributed by all members of the cluster at any point in time. 2 CMDS_QUEUED Total number of messages, datagrams, and port commands queued by the port for transmission at all priorities. 2 CNX_STATE State of the cluster connection. Possible displays are as follows: ACCEPT - Initial connection is accepted. CLOSED - Connection is closed. CONNECT - Initial connection is being accepted. DEAD - No connection is possible. DISCONNECT - Disconnection is in progress. NEW - No attempt to make a connection has yet been made. OPEN - Connection is open. REACCEPT - Connection is accepting the reconnect request. RECONNECT - Connection is attempting to reconnect. WAIT - Timeout is in progress. 2 CON_STATE The state of the connection. Possible displays are as follows: ACCP_SENT - Accept request has been sent. CLOSED - Connection is closed. CON_ACK - Connect request has been sent and acknowledged. CON_REC - Connect request has been received. CON_SENT - Connect request has been sent. DISC_ACK - Disconnect request is acknowledged. DISC_MTCH - Disconnect request is matched. DISC_REC - Disconnect request has been received. DISC_SENT - Disconnect request has been sent. LISTEN - Connection is in the listen state. OPEN - Connection is open. REJ_SENT - Reject has been sent. VC_FAIL - Virtual circuit has failed. 2 COUNTER_OWNER Name of the process currently using the port traffic counters. 2 CR_WAITS Number of times this connection had to wait for send credit. 2 CSID Cluster system identification number. This number is unique over the life of the cluster. Unlike SYS_ID, this identification number might change when the system reboots. 2 DGI_MAP A 16-bit bit map displayed as four hexadecimal digits. Each bit in the map represents a port in the cluster from which datagram reception has been disabled. 2 DGS_DSCRD Number of application datagrams discarded by the port driver. 2 DGS_FREE Number of free datagram buffers currently queued for receive commands. 2 DGS_RCVD Number of application datagrams received by the local system over the connection from the remote system and given to SYSAP. 2 DGS_SENT Number of application datagrams sent over the connection. 2 DG_OVRHD_SIZE Number of bytes of port header, SCS header, and DECnet header in a datagram. 2 DG_SIZE Maximum number of bytes of application data in datagrams sent over the circuit. 2 DIR_WT Lock Manager-distributed directory weight. 2 ERT_COUNT Number of port reinitialization attempts remaining. 2 ERT_MAX Total number of times a recovery from fatal port errors can be attempted by shutting down all virtual circuits and connections and reinitializing the port. 2 EXPECTED_VOTES Maximum number of votes that an individual node can encounter. Used as an initial estimate for computing CL_EXPECTED_VOTES. The cluster manager sets this number using the EXPECTED_VOTES system parameter. It is possible for this field to display a number smaller than the EXPECTED_VOTES parameter setting if the REMOVE_NODE option was used to shut down a cluster member or the SET CLUSTER/EXPECTED_VOTES DCL command was used since this node was last rebooted. The dynamic value for EXPECTED_VOTES used clusterwide is the CL_EXPECTED_VOTES field, which is described in the CLUSTER class category. 2 FORMED Time at which the cluster was formed, expressed as dd-mmm-yy hh:mm. 2 FORM_CIRCS Number of formative circuits (circuits in the process of opening) from the port. 2 FREE_BUFF Number of CI buffer descriptors free for use. 2 HW_TYPE System hardware type (for example, VAXstation 3100 or HS70). Use double quotation marks before and after the system type. 2 HW_VERS Hardware configuration and revision levels of the remote system. 2 INCARNATION Unique 16-digit hexadecimal number established when the system is booted. 2 INCN_TIME Incarnation number expressed as a time (dd-mmm-yy hh:mm). 2 INIT_REC Initial receive credit extended to the remote system when the connection was made. 2 KB_MAPPED Number of kilobytes of data mapped for block transfer. 2 KB_RCVD Number of kilobytes of data received by the local system from the remote system through request-data commands. 2 KB_SENT Number of kilobytes of data sent from the local system to the remote system through send-data commands. 2 LAST_TRANSITION Last time at which a system left or joined the cluster, expressed as dd-mmm-yy hh:mm. 2 LB_STATUS Loopback status of each cable from the port to the star coupler. The field applies only to CI. Possible displays are as follows: A-B - Loopback tests pass on paths A and B. A-# - Loopback tests pass on path A. #-B - Loopback tests pass on path B. #-# - Loopback tests failed on paths A and B. N/A - Loopback tests are not being done. 2 LD_CLASS The circuit's current capacity rating. 2 LOC_CONID Identification number of the local side of the connection. 2 LOC_PROC_NAME Name of the local process associated with the connection. 2 LOG_MAP A 16-bit bit map displayed as four hexadecimal digits. Each bit in the map represents a port in the cluster for which an error was logged. Errors are logged when data provided by the configuration database on the local system conflicts with data provided by the remote system. When a conflict is discovered and an error is logged, virtual circuits to the remote system can no longer be established. 2 LPORT_NAME Device name of the local port associated with the circuit (PAA0, PAB0, PEA0). 2 LP_LD_CLASS Hard-coded capacity value of the port, based on the megabits- per-second rate of the interconnect of the port. 2 LP_PRIORITY Management priority assigned to the port. 2 LP_STATUS Status of the local port. The port is either on-line or off-line. 2 LP_TYPE Device type of the port (CI780, CI750). 2 MAX_PORT Largest port number to which a virtual circuit open is attempted. 2 MEMSEQ Membership state sequence number, which changes whenever a node joins or leaves the cluster. 2 MGT_PRIORITY Priority value assigned to the circuit by management action. 2 MIN_REC Minimum receive credit (minimum send credit required by the remote system). 2 MIN_SEND Minimum send credit. 2 MSGS_FREE Number of free message buffers currently queued for receive commands. 2 MSGS_RCVD Number of application datagram messages received over the connection. 2 MSGS_SENT Number of application datagram messages sent over the connection. 2 MSG_HDR_SIZE Number of bytes of port header and SCS header in a message. 2 MSG_SIZE Maximum number of bytes of application data in messages sent over the circuit. 2 NAME Device name of the local port. 2 NODE Node name of the remote system. Normally, the cluster manager sets the node name using the system parameter SCSNODE. The node name should be the same as the DECnet node name. (Note that SCSNODE cannot be more than six characters.) 2 NUM_CIRCUITS Number of virtual circuits between the local system and remote systems. 2 NUM_CONNECTIONS Number of connections on the circuit between the local and remote systems. 2 NUM_ERRORS Number of errors that have been logged on the port since the system was booted. This number includes errors encountered in reinitialization attempts as well as recoverable errors, such as virtual circuit failure. This is the same error count as that displayed by the DCL command SHOW DEVICE. 2 OPEN_CIRCS Number of virtual circuits open from the port. 2 PEND_REC Receive credit not yet extended to the remote system. 2 POOL_WAITERS Number of processes waiting for nonpaged pool resources for message buffers. 2 PORT_NUM Port number assigned to the port. 2 PRIORITY Circuit's current priority, which is the sum of the management priorities assigned to the circuit and the associated local port. 2 PROTOCOL Protocol version number and ECO level of the connection management software. 2 PRT_MAP A 16-bit bit map displayed as three hexadecimal digits. Each bit in the map represents a port in the cluster that has been recognized by the host system. 2 QDVOTES Number of votes the remote system recommends be contributed by the quorum disk. Normally, the cluster manager sets this number using the system parameter QDSKVOTES. 2 QD_NAME Full device name of the quorum disk. 2 QF_ACTIVE Indicates whether the remote system's quorum file is accessible. 2 QF_SAME Indicates whether the local and remote systems agree about which disk is the quorum disk. 2 QF_VOTE Indicates whether or not the quorum disk is contributing any votes toward the cluster quorum. 2 QF_WATCHER Remote system has an active connection to the quorum disk and can verify its connection for members unable to access the disk directly. 2 QUORUM Derived from EXPECTED_VOTES and calculated by the connection manager. It represents an initial value for the minimum number of votes that must be present for this node to function. The dynamic QUORUM value is the CL_QUORUM field, which is described in the CLUSTER class. 2 RCVD_SQ Sequence number of the last message received over the OpenVMS Cluster connection. 2 RECEIVE Receive credit (send credit held by the remote system). 2 RECNXINTERVAL Displays the time (in seconds) that the connection manager will wait before timing out the corresponding connection. It is the maximum of the value contained in the system parameter RECNXINTERVAL on the local node and the amount of time it would take for the connection manager on the remote node to discover that the connection is broken. 2 REM_CONID Identification number of the remote side of the connection. This information does not apply for connections in the listen state. 2 REM_PROC_NAME Name of the remote process associated with the connection. This information does not apply for connections in the listen state. 2 REM_STATE State of the remote port. Possible displays are as follows: DISAB - Remote port is disabled. ENAB - Remote port is enabled. M_DISAB - Remote port is in maintenance mode and is disabled. M_ENAB - Remote port is in maintenance mode and is enabled. M_UNINIT - Remote port is in maintenance mode and has not been initialized. UNINIT - Remote port has not been initialized. 2 RPORT_NUM Port number of the remote port associated with the circuit. The field applies only to CI. 2 RP_FUNCTIONS Function mask of the remote port. 2 RP_OWNER Port number of the remote port owner. 2 RP_REVISION Hardware or microcode revision number of the remote port. 2 RP_TYPE Type of remote port associated with the circuit. Examples of some possible types might include: CIMNA, KFMSA, SHAC, SII, BVPSSP (a BVP storage systems port), CI780, CI750, CIBCA-A and CIBCA-B, RF and TF devices (for example RF73 or TF85), HSC devices (for example, HSC65 or HSC90), Ethernet, PASSTH (port is in passthrough mode), and so on. 2 RSPS_QUEUED Total number of responses of all kinds received from the port but not yet processed. 2 SCS_STATE SCS send blocked state. If the connection is waiting to send an SCS control block message, the SCS send blocked state indicates what kind of message it is waiting to send. Possible displays are as follows: ACCP_PEND - Waiting to send an accept request. CLEAR - Not blocked. CON_PEND - Waiting to send a connection request. CR_PEND - Waiting to send credit. DCR_PEND - Waiting to send credit in preparation for a disconnect. DISC_PEND - Waiting to send a disconnect request. REJ_PEND - Waiting to send a reject request. 2 SCS_WAITERS Number of connections waiting to send SCS control messages on the virtual circuit. 2 SEND Current send credit. 2 SEND_SQ Sequence number of the next message to be sent over the OpenVMS Cluster connection. 2 SOFTWARE Name and version of the operating system currently running on the remote system. 2 STATUS Status of the node in the cluster. Possible displays are: 3 blank System is not being considered as a cluster member. 3 BRK_MEM System is a member of the cluster, but the connection manager has lost communication with it. 3 BRK_NEW System has just booted but has not yet joined the cluster, and the connection manager has lost communication with it. 3 BRK_NON Connection manager has lost communication with the system, and the system is no longer a member of the cluster. 3 BRK_REM Connection manager has lost communication with the system, and the system has been removed from the cluster. 3 MEMBER System is participating in the cluster. 3 NEW System has just booted, but has not yet joined the cluster. If this system would normally be a member of the cluster and is displaying NEW in this field, you can expect that the display will eventually change to MEMBER. 3 NON System is not a member of the cluster. 3 REMOVED System has been removed from the cluster. 2 SW_VERS Indicator of the software version running on the node. 2 SYS_ID Identification number of the remote system. Normally, the cluster manager sets this number using the system parameters SCSSYSTEMID and SCSSYSTEMIDH. This number should be the same as the DECnet node number. 2 TRANSITION_TIME Time of the system's last change in membership status. (See the STATUS field.) 2 UNACKED Number of unacknowledged OpenVMS Cluster messages received by the remote system. 2 VOTES Number of votes the remote node contributes toward quorum. 2 WARMCDRPS Number of CDRPs on the CDRP free queue.