SHWCLHELP.HLB  —  Fields
  You can specify valid field names with the ADD, REMOVE, and SET commands.

1  –  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.

3  –  BDT_WAITS

  Number of times this connection had to wait for a buffer descriptor.

4  –  BLKS_REQ

  Number of block-request data commands initiated to
  block transfer data from the remote system to the local system.

5  –  BLKS_SENT

  Number of block-send data commands initiated to
  block transfer data from the local system to the remote system.

6  –  BUFF_DESCR

  Number of buffer descriptors in use.

7  –  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.

8  –  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.

9  –  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.

10  –  CL_MEMBERS

  Number of processors participating in the cluster.

11  –  CL_QDVOTES

  Number of votes contributed by the quorum disk.

12  –  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.

13  –  CL_VOTES

  Total number of votes contributed by all members of the
  cluster at any point in time.

14  –  CMDS_QUEUED

  Total number of messages, datagrams, and port commands queued
  by the port for transmission at all priorities.

15  –  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.

16  –  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.

17  –  COUNTER_OWNER

  Name of the process currently using the port traffic counters.

18  –  CR_WAITS

  Number of times this connection had to wait for send credit.

19  –  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.

20  –  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.

21  –  DGS_DSCRD

  Number of application datagrams discarded by the port driver.

22  –  DGS_FREE

  Number of free datagram buffers currently queued for receive
  commands.

23  –  DGS_RCVD

  Number of application datagrams received by the local system over
  the connection from the remote system and given to SYSAP.

24  –  DGS_SENT

  Number of application datagrams sent over the connection.

25  –  DG_OVRHD_SIZE

  Number of bytes of port header, SCS header, and DECnet header in a
  datagram.

26  –  DG_SIZE

  Maximum number of bytes of application data in datagrams
  sent over the circuit.

27  –  DIR_WT

  Lock Manager-distributed directory weight.

28  –  ERT_COUNT

  Number of port reinitialization attempts remaining.

29  –  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.

30  –  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.

31  –  FORMED

  Time at which the cluster was formed, expressed as dd-mmm-yy hh:mm.

32  –  FORM_CIRCS

  Number of formative circuits (circuits in the process of opening)
  from the port.

33  –  FREE_BUFF

  Number of CI buffer descriptors free for use.

34  –  HW_TYPE

  System hardware type (for example, VAXstation 3100 or HS70).
  Use double quotation marks before and after the system type.

35  –  HW_VERS

  Hardware configuration and revision levels of the remote system.

36  –  INCARNATION

  Unique 16-digit hexadecimal number established when the system
  is booted.

37  –  INCN_TIME

  Incarnation number expressed as a time (dd-mmm-yy hh:mm).

38  –  INIT_REC

  Initial receive credit extended to the remote system when the
  connection was made.

39  –  KB_MAPPED

  Number of kilobytes of data mapped for block transfer.

40  –  KB_RCVD

  Number of kilobytes of data received by the local system from
  the remote system through request-data commands.

41  –  KB_SENT

  Number of kilobytes of data sent from the local system to the remote
  system through send-data commands.

42  –  LAST_TRANSITION

  Last time at which a system left or joined the cluster, expressed
  as dd-mmm-yy hh:mm.

43  –  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.

44  –  LD_CLASS

  The circuit's current capacity rating.

45  –  LOC_CONID

  Identification number of the local side of the connection.

46  –  LOC_PROC_NAME

  Name of the local process associated with the connection.

47  –  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.

48  –  LPORT_NAME

  Device name of the local port associated with the circuit
  (PAA0, PAB0, PEA0).

49  –  LP_LD_CLASS

  Hard-coded capacity value of the port, based on the megabits-
  per-second rate of the interconnect of the port.

50  –  LP_PRIORITY

  Management priority assigned to the port.

51  –  LP_STATUS

  Status of the local port. The port is either on-line or off-line.

52  –  LP_TYPE

  Device type of the port (CI780, CI750).

53  –  MAX_PORT

  Largest port number to which a virtual circuit open is attempted.

54  –  MEMSEQ

  Membership state sequence number, which changes whenever a node
  joins or leaves the cluster.

55  –  MGT_PRIORITY

  Priority value assigned to the circuit by management action.

56  –  MIN_REC

  Minimum receive credit (minimum send credit required by
  the remote system).

57  –  MIN_SEND

  Minimum send credit.

58  –  MSGS_FREE

  Number of free message buffers currently queued for receive
  commands.

59  –  MSGS_RCVD

  Number of application datagram messages received over the
  connection.

60  –  MSGS_SENT

  Number of application datagram messages sent over the connection.

61  –  MSG_HDR_SIZE

  Number of bytes of port header and SCS header in a message.

62  –  MSG_SIZE

  Maximum number of bytes of application data in messages sent
  over the circuit.

63  –  NAME

  Device name of the local port.

64  –  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.)

65  –  NUM_CIRCUITS

  Number of virtual circuits between the local system and remote
  systems.

66  –  NUM_CONNECTIONS

  Number of connections on the circuit between the local and
  remote systems.

67  –  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.

68  –  OPEN_CIRCS

  Number of virtual circuits open from the port.

69  –  PEND_REC

  Receive credit not yet extended to the remote system.

70  –  POOL_WAITERS

  Number of processes waiting for nonpaged pool resources for
  message buffers.

71  –  PORT_NUM

  Port number assigned to the port.

72  –  PRIORITY

  Circuit's current priority, which is the sum of the management
  priorities assigned to the circuit and the associated local port.

73  –  PROTOCOL

  Protocol version number and ECO level of the connection
  management software.

74  –  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.

75  –  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.

76  –  QD_NAME

  Full device name of the quorum disk.

77  –  QF_ACTIVE

  Indicates whether the remote system's quorum file is accessible.

78  –  QF_SAME

  Indicates whether the local and remote systems agree about
  which disk is the quorum disk.

79  –  QF_VOTE

  Indicates whether or not the quorum disk is contributing any
  votes toward the cluster quorum.

80  –  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.

81  –  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.

82  –  RCVD_SQ

  Sequence number of the last message received over the OpenVMS
  Cluster connection.

83  –  RECEIVE

  Receive credit (send credit held by the remote system).

84  –  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.

85  –  REM_CONID

  Identification number of the remote side of the connection.
  This information does not apply for connections in the
  listen state.

86  –  REM_PROC_NAME

  Name of the remote process associated with the connection.
  This information does not apply for connections in the listen
  state.

87  –  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.

88  –  RPORT_NUM

  Port number of the remote port associated with the circuit. The
  field applies only to CI.

89  –  RP_FUNCTIONS

  Function mask of the remote port.

90  –  RP_OWNER

  Port number of the remote port owner.

91  –  RP_REVISION

  Hardware or microcode revision number of the remote port.

92  –  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.

93  –  RSPS_QUEUED

  Total number of responses of all kinds received from the
  port but not yet processed.

94  –  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.

95  –  SCS_WAITERS

  Number of connections waiting to send SCS control messages on
  the virtual circuit.

96  –  SEND

  Current send credit.

97  –  SEND_SQ

  Sequence number of the next message to be sent over the
  OpenVMS Cluster connection.

98  –  SOFTWARE

  Name and version of the operating system currently running on
  the remote system.

99  –  STATUS

  Status of the node in the cluster. Possible displays are:

99.1  –  blank

  System is not being considered as a cluster member.

99.2  –  BRK_MEM

  System is a member of the cluster, but the connection manager
  has lost communication with it.

99.3  –  BRK_NEW

  System has just booted but has not yet joined the cluster,
  and the connection manager has lost communication with it.

99.4  –  BRK_NON

  Connection manager has lost communication with the system,
  and the system is no longer a member of the cluster.

99.5  –  BRK_REM

  Connection manager has lost communication with the system,
  and the system has been removed from the cluster.

99.6  –  MEMBER

  System is participating in the cluster.

99.7  –  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.

99.8  –  NON

  System is not a member of the cluster.

99.9  –  REMOVED

  System has been removed from the cluster.

100  –  SW_VERS

  Indicator of the software version running on the node.

101  –  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.

102  –  TRANSITION_TIME

  Time of the system's last change in membership status. (See
  the STATUS field.)

103  –  UNACKED

  Number of unacknowledged OpenVMS Cluster messages received by
  the remote system.

104  –  VOTES

  Number of votes the remote node contributes toward quorum.

105  –  WARMCDRPS

  Number of CDRPs on the CDRP free queue.
Close Help