QUERY NODE command

Use the QUERY NODE command to display information about ISC TCP/IP or VTAM® nodes (terminals) and non-VTAM devices (SPOOL and SYSOUT devices) in an IMSplex.

For ISC TCP/IP nodes, the command also displays the IMS Connect instance that provides the TCP/IP support.

This command can be specified only through the OM API and is valid on an XRF alternate.

Subsections:

Environment

The following table lists the environments (DB/DC, DBCTL, and DCCTL) in which you can use the commands and keywords.

Table 1. Valid environments for the QUERY NODE command and keywords
Command / Keywords DB/DC DBCTL DCCTL
QUERY NODE X   X
NAME X   X
USER X   X
SHOW X   X
STATUS X   X

Syntax

Read syntax diagramSkip visual syntax diagramQUERYQRYNODENAME(*)NAME(,nodenamenodename*)NAME( nodename)USER(,usernameusername*)SHOW(GLOBAL,LOCAL)SHOW(GLOBAL,LOCAL,A)SHOW(,GLOBALLOCAL,A)STATUS(,ACTIVEASRBACKUPCINOPCLSDSTCOLDCONCONVDEACTEXCLFORCSESSIDLEINOPLOCKLOSTMFSTOPNDSTPAGEPRIPRSTQUIRELREQRESPRESPINPRESPINPFPRESYNCRMRMACTIVERMOWNEDSECSHUTSIGNSIMLOGONSTATICSTOLGNTESTTKOTRATRACE)
A
Read syntax diagramSkip visual syntax diagram,ALLAFFINCICSAPPLCICSNETIDCIDCONVCOUNTEMHQIDIMSCONLOGONDLTERMMODETBLOWNERPRESETQCNTRECOVERYSTATUSTYPEUSERUSERIDVERSION

Keywords

The following keywords are valid for the QUERY NODE command:

NAME()
Specifies the names of one or more VTAM nodes (terminals) or non-VTAM devices that are to be displayed. Valid names are 1-8 characters, and wildcards can be specified. To display all nodes and devices, specify NAME(*). NAME(*) is the default.

Any static or dynamic VTAM terminal name can be specified. Supported terminal types are LU0, LU1, LU2, and LU6.1 (ISC only).

Any non-VTAM device can be specified. Non-VTAM devices are assigned a LINE and PTERM number during the system definition process. Supported device types are CONSOLE, SYSOUT (DISK, PUNCH, PRINTER, READER, TAPE), SPOOL, and TCO:
CONSOLE
This is the system console. IMS automatically assigns LINE 1 PTERM 1 to this device.
DISK
Defined by the LINEGRP macro, UNITYPE=DISK.
PUNCH
Defined by the LINEGRP macro, UNITYPE=PUNCH.
PRINTER
Defined by the LINEGRP macro, UNITYPE=PRINTER.
READER
Defined by the LINEGRP macro, UNITYPE=READER.
SPOOL
Defined by the LINEGRP macro, UNITYPE=SPOOL.
TAPE
Defined by the LINEGRP macro, UNITYPE=TAPE.
TCO
This is the device assigned as the Time Control Option. The system definition process automatically assigns the last LINE number to this device.

To specify a non-VTAM device, specify a name of DFSLNxxx, where xxx is the LINE number of the device. For example, to display the system console (LINE 1), specify NAME(DFSLN001).

SHOW()
Specifies the node output fields to be returned.

The node name is always returned along with the name of the IMS that created the output and the completion code. If SHOW is not specified, only the node names are returned, provided that the STATUS filter is not specified. This provides a method for a system management application to obtain a list of all node names that are currently known in the IMSplex.

Two parameters, GLOBAL and LOCAL, are used to specify the location (global resources or local resources) where IMS should obtain the information that is to be displayed. The default is both GLOBAL and LOCAL.

The rest of the parameters are used to specify what information is displayed.

The parameters supported with the SHOW keyword, which can be specified in any order, are:

ALL
Returns all of the output fields, except for those fields displayed when the LTERM and CONV parameters are specified. To display LTERM and conversation information with all other output, specify SHOW(ALL,LTERM,CONV).
AFFIN
IMS APPLID to which the node has VTAM generic resource affinity, if applicable. VTAM generic resource affinity is valid only when the GLOBAL parameter is specified on the SHOW keyword. If GLOBAL is not specified, then the AFFIN parameter is ignored.
CICSAPPL
For ISC TCP/IP nodes, displays the APPLID of the remote CICS® subsystem.
CICSNETID
For ISC TCP/IP nodes, displays the NETWORK ID of the remote CICS.
CID
VTAM connection identifier.
CONV
The conversation ID, transaction, and conversation status associated with the node. Each conversation is returned on a separate command response display line. Conversation status is not included when SHOW(ALL) is specified. To display conversation information with all other output, specify SHOW(ALL,CONV).
COUNT
Displays the number of messages sent to and received from the specified node.
EMHQ
Displays the node message queue count in the Expedited Message Handler (EMH) queues. The queue count is the sum of the queue counts for each logical terminal associated with the specified node.

EMHQ is valid only when the GLOBAL parameter is specified on the SHOW keyword. If GLOBAL is not specified, then the EMHQ parameter is ignored.

EMHQ is processed by the command master only. It is ignored by all other IMS systems.

EMHQ is valid only if shared EMH is used in a shared queues environment. Otherwise, this parameter is ignored.

If the node resource exists in the resource structure, then the logical terminals associated with the global node resource are used to obtain the queue counts from the EMH queues. Otherwise, the logical terminals associated with the local node resource are used, but if the node does not exist locally on the command master, then the queue count is 0.

GLOBAL
If GLOBAL is specified, the command master displays global information, depending on the other SHOW parameters specified. This includes information from the resource structure.

The GLOBAL parameter is processed by the command master only. All other IMS systems ignore this parameter. If LOCAL is not also specified, then all IMS systems other than the command master ignore the command.

GLOBAL is applicable only when the command master is using shared queues, VTAM generic resources, sysplex terminal management, or any combination of these. GLOBAL is not applicable when the command master is not using shared queues, VTAM generic resources, or sysplex terminal management. In this environment, if LOCAL is also specified, then GLOBAL is ignored. Otherwise, the command master rejects the command.

If shared queues are enabled, and global queue counts are requested, then the command master will make requests to CQS to determine the appropriate queue counts. This includes both MSGQ and EMHQ.

If VTAM generic resources (VGR) is enabled, and VGR affinity information is requested, then the command master will make requests to VTAM to determine any VGR affinity.

If sysplex terminal management is enabled, then the command master will make requests to RM to determine the appropriate global status.

If both GLOBAL and LOCAL are specified (which is the default), then the command master builds global and local information separately. Global information is displayed as one output line (or set of output lines), and local information is displayed as another output line (or set of output lines).

ID
Displays the other half-session qualifier name of the ISC node.
IMSCON
For ISC TCP/IP nodes, shows the IMSplex member name of the IMS Connect instance that provides TCP/IP support for the node.
LOCAL
If LOCAL is specified, then all IMS systems including the command master display local information, depending on the other SHOW parameters specified. This includes information local to the IMS processing the command.

The LOCAL parameter is processed by all IMS systems, including the command master. LOCAL is applicable in any environment, regardless of whether shared queues or sysplex terminal management are used.

If both GLOBAL and LOCAL are specified (which is the default), then the command master builds global and local information separately. Global information is displayed as one output line (or set of output lines), and local information is displayed as another output line (or set of output lines).

LOGOND
For ISC TCP/IP nodes, displays the name of the ETO logon descriptor that was used to establish the session in use by the node.
LTERM
Displays the logical terminal (LTERM) names, if any, associated with the node. A node may have zero or more logical terminals associated with it.

Each logical terminal associated with the node is returned on a separate command response line.

The LTERM status is not included when SHOW(ALL) is specified. To display logical terminal information with all other output, specify SHOW(ALL,LTERM).

MODETBL
Displays the mode table names that are associated with the specified nodes. The output includes both the default mode table name and the actual mode table name. The default mode table name is the default name that is set by system definition. This name can be modified by the LOGON exit. The actual mode table name is the actual name used to initiate the session. This name is displayed only while the session is active, and is blank at all other times.
OWNER
Displays the owner of the node resource in the resource structure. This applies only when sysplex terminal management is enabled, and is only processed by the command master. All other IMS systems ignore this parameter.

The owner is the IMSID (or RSENAME for XRF systems) of the IMS system that owns the node. An IMS system owns a node resource if the resource is active (the node is logged on), or an IMS system is maintaining significant status for that resource.

PRESET
Displays the preset destination name for a node. A node is in preset destination mode set by the /SET command. The preset destination name is either a transaction name, or a logical terminal (LTERM) name. All messages entered from this node are sent to the preset destination transaction or LTERM.
QCNT
Displays the node message queue count. The queue count is the sum of the queue counts for each logical terminal associated with the specified node.

The local queue counts value returned on this command represents the messages being processed by the IMS system where this command is issued. In a shared-queues environment, do not use the local queue counts for queue evaluation purposes. The global queue counts, which are returned on this command, represent the current message queue counts on the shared queues structure.

If the LOCAL parameter is also specified on the SHOW keyword, then all IMS systems that process the command, including the command master, display the local queue count. This is valid whether or not shared message queues are enabled.

If the GLOBAL parameter is also specified on the SHOW keyword, and shared message queues are enabled, then the command master displays the global queue count on the shared message queues (MSGQ). If the node resource exists in the resource structure, then the logical terminals associated with the global node resource are used to obtain the queue counts from shared queues. Otherwise, the logical terminals associated with the local node resource are used, but if the node does not exist locally on the command master, then the queue count is 0.

The local and global queue counts are displayed as separate output fields.

RECOVERY
Displays the status recovery mode (SRM) and level of recovery for the node. End-user significant status can be conversation, Fast Path, full-function response mode, or STSN (set-and-test-sequence-number) status.

SRM determines where end-user significant status, if any exists, is recovered following a session or IMS termination. The output displays the SRM for the node as either GLOBAL (sysplex terminal management recovers it in the resource structure), LOCAL (IMS recovers it locally, which indicates an affinity to a particular IMS), or NONE (status is discarded).

Level of recovery determines what end-user significant status, if any exists, is recovered (if SRM is GLOBAL or LOCAL). The output displays whether conversation status is recovered (RCVYCONV), Fast Path status is recovered (RCVYFP), full-function response mode is recovered (RCVYRESP), and STSN status is recovered (RCVYSTSN).

STATUS
Returns local or global status of the node. See QUERY NODE status for a list and meaning of possible status that might be returned.
TYPE
VTAM node type. The possible node types are AVM, FIN, LUT6, NTO, SLUP, SLU1, SLU2, 3277, 3286, 3790, CONSOLE, RDR/PTR (for SYSOUT and SPOOL), and TCO.
USER
Displays the dynamic or ISC user associated with the node. For ISC parallel-session nodes, this is the user structure representing the half-session qualifier. For static ISC, this is defined with the SUBPOOL macro. For non-ISC dynamic nodes, this is the user structure allocated to the node during signon of a user ID to the node. The user name might or might not be the same as the user ID, depending on installation-specific user exits or descriptors used. Static non-ISC nodes (and single-session ISC nodes) do not have users (even if a user ID is signed on).
USERID
Displays the user ID (for security, usually RACF®), signed on to the node. This is applicable to any device type, static or dynamic, and is distinct from the user name.
VERSION
Displays the version number assigned to RM resources, which is assigned by MVS™, and maintained by RM, when the resources are created or updated in the resource structure.

Static single-session nodes (not parallel-session ISC) are represented in RM by two resources: the node resource, and the static-node-user resource. The VERSION parameter displays the version number for each of these resources. Static parallel-session ISC nodes and all dynamic nodes are represented in RM by one resource: the node resource. The VERSION parameter displays the version number of the node resource.

VERSION applies only when sysplex terminal management is enabled. VERSION is ignored when sysplex terminal management is not enabled.

STATUS()
Selects nodes for display that possess at least one of the specified node statuses. The status might exist locally or globally if sysplex terminal management (STM) is enabled.

The STATUS filter is valid in both a sysplex terminal management environment and in a non-sysplex terminal management environment. In a sysplex terminal management environment, the status selected might exist locally, globally, or both. If sysplex terminal management is not enabled, then the status only exists locally.

If SHOW(LOCAL) is specified, then IMS will select only those nodes with the appropriate status in the local system. The command is processed by all IMS systems, including the command master.

If SHOW(GLOBAL) is specified, and sysplex terminal management is enabled, then IMS will select only those nodes with the appropriate status in the resource structure. The command is processed only by the command master.

If SHOW(GLOBAL) is specified, but sysplex terminal management is not enabled, then the command is rejected.

If SHOW(GLOBAL,LOCAL) is specified (the default), then IMS will select those nodes with the appropriate status either locally or in the resource structure (if sysplex terminal management is enabled). The command is processed by all IMS systems. The command master processes both global and local information.

The output returned when the status filter is specified includes the status of the node, even if SHOW(STATUS) is not specified.

See QUERY NODE status to determine which filters can be used to select nodes with corresponding status.

USER()
For a specific ISC node, specifies the names of one or more ISC user names allocated to the node. Valid names are 1-8 characters, and wildcards can be specified. To display all users allocated to the node, specify USER(*), or omit the USER keyword.

The output returned includes the user name even if SHOW(USER) is not specified.

Usage notes

QUERY NODE can be specified only through the OM API.

QUERY NODE can be issued on an XRF alternate system, but SHOW(GLOBAL) is not supported. Only local information can be displayed.

The processing of the QUERY NODE command is different depending on whether IMS sysplex terminal management is enabled.

  • If IMS sysplex terminal management is not enabled, processing is local for each system. The results of type-1 and type-2 commands are similar.
  • If IMS sysplex terminal management is enabled, type-1 and type-2 command processing is similar when displaying local information. However, they differ in how global information is displayed.
  • For type-1 /DISPLAY commands with IMS sysplex terminal management enabled, the command master displays information from either the resource structure or the local system, but not both. If the resource being displayed is not owned by any system or is owned by the command master, the command master displays the global resource. However, if the resource is owned by a system other than the command master, the command master displays only the local resource, and the owning system is responsible for displaying the global resource.
  • For type-2 QUERY commands with IMS sysplex terminal management enabled, the command master is the only system that displays global resource information, regardless of whether the resource is owned. In addition, the command master displays local resource information. All other IMS systems that process the command display local resource information only. This approach allows more flexibility in displaying all information in an IMSplex.

The SHOW keyword determines which IMS systems process the command and what information is displayed.

  • If SHOW(GLOBAL) is specified, then the command master displays global information, which includes the global queue count if shared queues are enabled, generic resource affinity information if VTAM generic resource (VGR) is enabled, and status from the resource structure if sysplex terminal management is enabled (STM=YES defined in DFSDCxxx PROCLIB member). This is true whether or not the node is active on any particular IMS system. All other IMS systems to which OM routes the command ignore the GLOBAL parameter with return code X'00000004' and reason code X'00001000'.
  • If SHOW(LOCAL) is specified, then each IMS system to which OM routes the command (including the command master) processes the command, and displays information that is local to each system.
  • If both GLOBAL and LOCAL are specified (which is the default), then the command master displays both global and local information, and all other IMS systems to which OM routes the command displays local information.

Equivalent IMS type-1 commands

The following table shows variations of the QUERY NODE command and the type-1 IMS commands that perform similar functions.

Table 2. Type-1 equivalents for the QUERY NODE command
QUERY NODE command Similar IMS type-1 command
QUERY NODE SHOW(AFFIN) /DISPLAY AFFIN NODE node
QUERY NODE SHOW(CID) /DISPLAY NODE node
QUERY NODE SHOW(CONV) /DISPLAY CONV NODE node
QUERY NODE SHOW(COUNT) /DISPLAY NODE node
QUERY NODE SHOW(EMHQ) /DISPLAY NODE node QCNT EMHQ
QUERY NODE SHOW(LTERM) /DISPLAY ASMT NODE node
QUERY NODE SHOW(MODETBL) /DISPLAY NODE node MODE
QUERY NODE SHOW(OWNER) /DISPLAY NODE node RECOVERY
QUERY NODE SHOW(PRESET) /DISPLAY NODE node
QUERY NODE SHOW(QCNT)

/DISPLAY NODE node
/DISPLAY NODE node QCNT

QUERY NODE SHOW(RECOVERY) /DISPLAY NODE node RECOVERY
QUERY NODE SHOW(STATUS) /DISPLAY NODE node
QUERY NODE SHOW(TYPE) /DISPLAY NODE node
QUERY NODE SHOW(USERID) /DISPLAY NODE node
QUERY NODE SHOW(USER)

/DISPLAY NODE node
/DISPLAY ASMT NODE node

QUERY NODE STATUS(CONV) /DISPLAY CONV
QUERY NODE STATUS(TRACE) /DISPLAY TRACE NODE
QUERY NODE STATUS(status) /DISPLAY STATUS NODE

Output fields

The following table shows the QUERY NODE output fields. The columns in the table are:
Short label
Contains the short label generated in the XML output.
Long label
Contains the column heading for the output field in the formatted output.
SHOW parameter
Identifies the parameter on the SHOW keyword that caused the field to be generated. Error appears for output fields that are returned for a non-zero completion code. N/A (not applicable) appears for output fields that are always returned.
Scope
Identifies the scope of the output field. GBL indicates that the field can be generated only by the command master when displaying global information for SHOW(GLOBAL). LCL indicates that the field can be generated by any IMS displaying local information for SHOW(LOCAL). N/A (not applicable) appears for output fields that are always returned.
Meaning
Provides a brief description of the output field.
Table 3. Output fields for the QUERY NODE command
Short label Long label SHOW parameter Scope Meaning
AFFIN Affin AFFIN GBL IMS APPLID to which the node has VTAM generic resource affinity, if applicable.
AMTB ActMdtbl MODETBL LCL Active mode table. This name is only displayed when the session is active.
CC CC N/A N/A Completion code. The completion code indicates whether or not IMS was able to process the command for the specified resource. See Return, reason, and completion codes for more information. The completion code is always returned.
CCTXT CCText Error N/A Completion code text that briefly explains the meaning of the non-zero completion code. This field is returned only for an error completion code.
CICAP CICSApplid CICSAPPL LCL The APPLID of the remote CICS subsystem.
CICNT CICSNetid CICSNETID LCL The NETWORK ID of the remote CICS.
CID CID CID LCL VTAM connection identifier.
CNTR RecdCnt COUNT LCL Number of messages received from the specified node.
CNTS SentCnt COUNT LCL Number of messages sent to the specified node.
CONVID ConvID CONV GBL The conversation ID for a conversation associated with the node, as it exists in the resource structure. A node might have zero, one, or more conversations. Each conversation will have its own line of output.
CONVSTT ConvStat CONV GBL The status of a conversation associated with the node, as it exists in the resource structure. A node might have zero, one, or more conversations. The status can be:
  • CONVHELD - conversation is held
  • CONVACTV - conversation is active
  • CONVSCHD - conversation is scheduled
CONVTRN ConvTran CONV GBL The transaction for a conversation associated with the node, as it exists in the resource structure. A node might have zero, one, or more conversations.
DMTB DefMdtbl MODETBL LCL Default mode table.
EMHQ EMHQCnt EMHQ GBL Global logical terminal queue count in the EMH (Expedited Message Handler) queues. EMHQ is displayed only if shared EMH is used.
GBL Gbl GLOBAL GBL If 'Y', then the output reflects the status found globally in RM. If blank, then the output reflects the status found locally.
ID ID ID GBL For ISC parallel-session terminals, displays the global half-session qualifier of the other system.
ISCUSER ISCUser N/A N/A When the node is parallel-session ISC, the user subpool name is returned to differentiate parallel sessions for the same node. This field will appear when an ISC node has been selected for display.

When the user name is also displayed, both the ISCUSER and USER fields will contain the same user name.

For LOCAL scope, N/A is displayed for a parallel session that is not yet allocated.

For GLOBAL scope, N/A is displayed once for each node, which represents global status for the node.

LCONVID LConvID CONV LCL The conversation ID for a conversation associated with the node, as it exists in the local system. A node might have zero, one, or more conversations. Each conversation will have its own line of output.
LCONVSTT LConvStat CONV LCL The status of a conversation associated with the node, as it exists in the local system. A node might have zero, one, or more conversations. The status can be:
  • CONVHELD: Conversation is held
  • CONVACTV: Conversation is active
  • CONVSCHD: Conversation is scheduled
LCONVTRN LConvTran CONV LCL The transaction for a conversation associated with the node, as it exists in the local system. A node might have zero, one, or more conversations.
LGND LclLogonD LOGOND LCL The dynamic logon descriptor name that was used to establish the current session for the ISC TCP/IP terminal.
LIC LclImsCon IMSCON LCL For ISC TCP/IP nodes, the IMSplex member name of the local IMS Connect that provides TCP/IP support for the specified node, as defined by the LCLICON= keyword on the logon descriptor or, for statically defined terminals, on the ISCTCPIP keyword in the DFSDCxxx PROCLIB member.
LID LID ID LCL For ISC VTAM parallel-session terminals, displays the local half-session qualifier of the other system.

For ISC TCP/IP parallel-session terminals, displays the dynamic or ISC user that is allocated to the node.

LINE Line N/A LCL Identifies the line number for system console, SPOOL, SYSOUT, or TCO device. This is only displayed if the node is non-VTAM.
LLTERM LLterm LTERM LCL Local logical terminal names. The logical terminal names associated with the node.
LPRST LPreset PRESET LCL Identifies the preset destination transaction or LTERM name when the node is in preset destination mode, which is established by the /SET command. All messages entered at this terminal are sent to the preset destination trancode or LTERM.
LQ LQCnt QCNT LCL Local queue count.
LRCVY LRcvy RECOVERY LCL The level of recovery for end-user significant status in the local system, which indicates what type of status is recoverable.

Any value presented here implies that the corresponding status is recoverable. If SRM is LOCAL, the status will be recovered locally. If SRM is GLOBAL, the status will be recovered globally. These values are not applicable if SRM is NONE or there is no SRM.

The status values that can be returned (more than one are possible) are:

  • CONV: IMS conversations are recoverable (RCVYCONV=YES).
  • FP: Fast Path status is recoverable (RCVYFP=YES).
  • RESP: Full-function response mode status is recoverable (RCVYRESP=YES).
  • STSN: STSN status is recoverable (RCVYSTSN=YES).
LSRM LSRM RECOVERY LCL The status recovery mode in the local system, which determines where the end-user significant status is maintained and recovered from. The output will be one of the following:
  • GBL: Status is saved globally in the IMS resource structure.
  • LCL: Status is saved in local control blocks and log records.
  • NONE: Status is not saved in the IMS resource structure or log records.
  • Blank: SRM is not yet established, the node is not logged on and there is no end-user significant status, or there is no user signed on.
LSTT LclStat STATUS LCL Local node status. See QUERY NODE status for a list and explanation of the possible node status.
LTERM Lterm LTERM GBL Global logical terminal names. The logical terminal names associated with the node.
LTYPE LType TYPE LCL VTAM node type. The possible node types are: AVM, FIN, LUT6, NTO, SLUP, SLU1, SLU2, 3277, 3286, 3790, CONSOLE, RDR/PTR (for SYSOUT and SPOOL), and TCO.
LUID LUserid USERID LCL Identifies the local user ID signed on to the node.
LUSER LUser USER LCL Identifies the local dynamic or ISC user allocated to the node.
LVER LVersion# VERSION LCL Version number for the node resource being maintained in the local system. This field applies only when STM is enabled.
LVERSNU LVersion#SNU VERSION LCL Version number for the static-node-user resource being maintained in the local system. This field applies only to static single-session nodes when STM is enabled.
MBR MbrName N/A N/A IMSplex member (modular unit) that built the output line. IMS identifier of the IMS that built the output. The IMS identifier is always returned.
NODE Node N/A N/A The node name. The node name is always returned.
OWNER Owner OWNER GBL Resource owner. IMS identifier or RSENAME of IMS where the node is active. If no owning IMS system exists and RM contains an entry for the resource, the owner field will be blank.
QCNT QCnt QCNT GBL Global queue count on the shared queues. Global queue count can be displayed only if shared queues are used.
PTERM PTerm N/A LCL Identifies the PTERM number for system console, SPOOL, SYSOUT, or TCO device. This is only displayed if the node is non-VTAM.
RCVY Rcvy RECOVERY GBL The level of recovery for end-user significant status in the resource structure, which indicates what type of status is recoverable.

Any value presented here implies that the corresponding status is recoverable. If SRM is LOCAL, the status will be recovered locally. If SRM is GLOBAL, the status will be recovered globally. These values are not applicable if SRM is NONE or there is no SRM.

The status values that can be returned (more than one are possible) are:

  • CONV: IMS conversations are recoverable (RCVYCONV=YES).
  • STSN: STSN status is recoverable (RCVYSTSN=YES).
  • FP: Fast Path status is recoverable (RCVYFP=YES).
SRM SRM RECOVERY GBL The status recovery mode in the resource structure, which determines where the end-user significant status is maintained and recovered from. The output will be one of the following:
  • GBL: Status is saved globally in the IMS resource structure.
  • LCL: Status is saved in local control blocks and log records.
  • NONE: Status is not saved in the IMS resource structure or log records.
  • Blank: SRM is not yet established, the node is not logged on and there is no end-user significant status, or there is no user signed on.
STT Status STATUS GBL Global node status. See QUERY NODE status for a list and explanation of the possible node status.
TYPE Type TYPE GBL VTAM node type. The possible node types are AVM, FIN, LUT6, NTO, SLUP, SLU1, SLU2, 3277, 3286, 3790.
UID Userid USERID GBL Identifies the RACF user ID signed on to the node.
USER User USER GBL Identifies the dynamic or ISC user signed on to or associated with the node.
VER Version# VERSION GBL Version number for the node resource being maintained in the resource structure. This field applies only when STM is enabled.
VERSNU Version#SNU VERSION GBL Version number for the static-node-user resource being maintained in the resource structure. This field applies only to static single-session nodes when STM is enabled.

QUERY NODE status

The following table shows the possible node status that can be displayed. The columns in the table are:

Status
The node status that is displayed.
STATUS parameter
The STATUS() filter that will select nodes with the specified status.
Scope
The scope of the status. GBL indicates that the status can be global (it exists in the resource structure when STM is enabled), and is returned with the STT short label. LCL indicates that the status can be local, and is returned with the LSTT short label.
Meaning
Provides a brief description of the status.
Table 4. QUERY NODE status
Status STATUS parameter Scope Meaning
ACTIVE ACTIVE LCL Node is in an XRF session on the active system.
ASR ASR LCL Node has session initiation option ASR.
BACKUP BACKUP LCL Node is in an XRF session on the alternate system.
CLSDST CLSDST LCL Session is being disconnected.
COLD COLD GBL and LCL For a SLUP or FINANCE terminal, indicates that the next session initiation is cold (message sequence numbers are initialized to 0).
CON CON LCL Node is connected or in session with IMS.
CONVACT CONV GBL and LCL An active conversation exists.
CONVHELD CONV GBL and LCL One or more held conversations exist.
C1INOP
C2INOP
C3INOP
C4INOP
CINOP LCL Indicates the inoperable node or terminal component, where C1, C2, C3 and C4 refer to the component as defined by system definition. (See the /COMPT command and the /RCOMPT command for details on how to ready inoperable components).
DEACT DEACT LCL Node has been permanently deactivated. Restart of node requires /STOP DC and /START DC commands. Message DFS2473 in the system console log might contain information regarding the reason this status was set. DFS2473 can occur more than once in the system console log.
EXCL EXCL GBL and LCL The node is in exclusive mode set by the /EXCLUSIVE command. Exclusive mode restricts the output received by the terminal affected.
FORCSESS FORCSESS LCL Node has session initiation option of FORCE.
IDLE IDLE LCL No activity of any kind is in progress for the node.
INOP INOP LCL NODE is inoperable.
LOCK LOCK LCL Node is locked, set by the /LOCK command. The sending and receiving of messages for the VTAM node is stopped.
LOST LOST LCL The VTAM LOSTERM EXIT has been scheduled for this node but has not yet been recognized by IMS. At the next interrupt for this node, IMS interrogates the LOSTERM value.

All values, with one exception, result in an immediate CLSDST, or disconnection from IMS. For the LOSTERM exception, IMS must wait for VTAM to notify IMS (via another LOSTERM) of completion of recovery operation. This indicates an IMS logger's connection to the Transport Manager Subsystem is gone because of TMS or VTAM failure.

MFST MFST GBL and LCL Node is in MFSTEST mode, set by the /TEST MFS command. Terminals supported by Message Format Service use format blocks from a special test library if the requested format block is in the test library; otherwise the blocks are obtained from the production library.
OPNDST OPNDST LCL OPNDST is in progress for this node.
PAGE PAGE LCL Indicates an MFS paged message.
PRI PRI GBL and LCL This node is the primary partner of an ISC session.
PRST PRST LCL The node is in preset destination mode. PRST mode is established by the /SET command. All messages entered at this terminal are sent to the preset destination transaction code or logical terminal.
QUI QUI LCL A VTAM node has sent a VTAM Quiesce-End-of-Chain indicator to suspend IMS output.
RELREQ RELREQ LCL VTAM RELREQ exit routine has been driven but IMS is waiting for an operation in progress to complete before releasing the node.
RESP RESP GBL and LCL The node is in response mode and the response reply message is available for output or in the process of being sent.
RESPINP RESPINP GBL and LCL The node is in response mode and the response mode input is still in-doubt; for example, the response reply message is not available for output.
RESPINPFP RESPINPFP GBL and LCL The node is in Fast Path response mode and the response mode input is still in-doubt; for example, the response reply message is not available for output.
RESYNC RESYNC LCL The positive acknowledgment of an IMS recoverable output message was not received when the connection with the VTAM node was terminated. This message is subject to resynchronization when the next connection for this node is attempted.
RM RM GBL The node exists in the resource structure managed by RM.
RMACTIVE RMACTIVE GBL The node is active (logged-on) in the IMSplex, as indicated in the RM structure (RM active).
RMOWNED RMOWNED GBL The node is owned by an IMS system in the IMSplex, as indicated in the RM structure (RM owned).
SEC SEC GBL and LCL This node is the secondary partner of an ISC session.
SHUT SHUT LCL Normal processing has completed for the node and a VTAM shutdown-complete indicator was returned to IMS. The node can receive IMS output but cannot enter data while in this state.
SIGN SIGN GBL and LCL The user is signed on to a node under enhanced security.
SIMLOGON SIMLOGON LCL A logon to IMS has been simulated.
STATIC STATIC GBL and LCL The node was defined during system definition.
STOLGN STOLGN GBL and LCL Node was stopped from logging on by the /STOP NODE command.
TEST TEST LCL The node is in test mode.
TKOTRA TKOTRA LCL Node in an XRF session is to be traced only during takeover, to help diagnose XRF terminal switch problems.
TRACE TRACE GBL and LCL Node is being traced.

Return, reason, and completion codes

An IMS return and reason code is returned to OM by the QUERY NODE command. The OM return and reason codes that may be returned as a result of the QUERY NODE command are standard for all commands entered through the OM API.

The following table includes the return and reason codes and a brief explanation of the codes. The return or reason code returned for the command might also indicate an error from a CSL request.

Table 5. Return and reason codes for the QUERY NODE command
Return code Reason code Meaning
X'00000000' X'00000000' The command completed successfully.
X'00000004' X'00001000' The command was not processed on the IMS system as the IMS system is not the command master. No resource information is returned.
X'00000008' X'00002014' An invalid character was specified in the resource name.
X'00000008' X'00002040' An invalid parameter value was specified. An invalid SHOW or STATUS value might have been specified.
X'00000008' X'00002133' The NAME() keyword specified is either a generic name or multiple specific names, but the USER() keyword was also specified. When USER() is specified, only one NAME parameter is allowed.
X'0000000C' X'00003000' The command was successful for some resources but failed for others. The command output contains a line for each resource, accompanied by its completion code. See Table 6 for details.
X'0000000C' X'00003004' The command was not successful for any resource. The command output contains a line for each resource, accompanied by its completion code. See Table 6 for details.
X'00000010' X'00004004' Command processing terminated because CQS was not active.
X'00000010' X'00004005' Command processing terminated because CQS was not connected to the queue structure.
X'00000010' X'0000400C' Command is not valid on the XRF alternate.
X'00000010' X'00004014' Command is not valid on the RSR tracker.
X'00000010' X'00004018' Command processing terminated because the resource structure is not available.
X'00000010' X'0000401C' Command is not valid on the FDBR region.
X'00000010' X'00004028' Global queue counts were requested, but shared message queues are not enabled.
X'00000010' X'0000403C' VTAM generic resource affinity information was requested, but VGR is not enabled.
X'00000010' X'00004104' Command processing terminated because RM is not available.
X'00000010' X'00004108' Command processing terminated because SCI is not available.
X'00000014' X'00005004' A DFSOCMD response buffer could not be obtained.
X'00000014' X'00005008' DFSPOOL storage could not be obtained.
X'00000014' X'00005100' Command processing terminated because of an RM error.
X'00000014' X'00005104' Command processing terminated because of a CQS error.
X'00000014' X'00005108' Command processing terminated because of an SCI error.
X'00000014' X'00005FFF' Command processing terminated because of an internal IMS error.

The following table includes an explanation of the completion codes. Errors unique to the processing of this command are returned as completion codes. A completion code is returned for each action against an individual resource.

Table 6. Completion codes for the QUERY NODE command
Completion code Completion code text Meaning
0   The QUERY NODE command completed successfully for the resource.
10 NO RESOURCES FOUND The resource name is unknown to the client that is processing the request. The resource name might have been typed in error or the resource might not be active at this time. If this is a wildcard request there were no matches for the name. Confirm that the correct spelling of the resource name is specified on the command.
98 CQS REQUEST ERROR Global queue counts could not be obtained because of a CQS error.
1A1 Node resource is in error The node resource was found in the resource structure and an associated resource was needed, but it was either not found or appeared to be in error. This is normally an error condition. However, it could be a temporary condition caused by terminal or command activity. The command should be retried.

Examples

The following are examples of the QUERY NODE command:

Example 1 for QUERY NODE command

TSO SPOC input:
QRY NODE NAME(NODE2*,XYZ) SHOW(LOCAL)
TSO SPOC output:
Node     ISCUser  MbrName CC CCText
NODE21            IMS1     0
NODE22            IMS1     0
NODE22            IMS2     0
NODE23            IMS2     0
NODE24   USER24A  IMS2     0
NODE24   USER24B  IMS2     0
NODE24   N/A      IMS2     0
XYZ               IMS1    10 NO RESOURCES FOUND
XYZ               IMS2    10 NO RESOURCES FOUND

Explanation: There are two IMS systems in the IMSplex: IMS1 and IMS2. STM and shared queues are irrelevant because only local information is requested. IMS1, the command master, displays only local information because no global information is requested. IMS2 displays local information only.

  • NODE21 exists on IMS1 only.
  • NODE22 exists on IMS1 and IMS2.
  • NODE23 exists on IMS2 only.
  • NODE24 is an ISC node with 3 parallel sessions available on IMS2, two of which are allocated.
  • XYZ does not exist on any system.

Example 2 for QUERY NODE command

TSO SPOC input:
QRY NODE NAME(NODE2*)
TSO SPOC output:
Node     ISCUser  MbrName CC  Gbl
NODE21            IMS1     0  Y
NODE21            IMS1     0
NODE22            IMS1     0
NODE22            IMS2     0
NODE23            IMS1     0  Y
NODE23            IMS2     0
NODE24   USER24A  IMS1     0  Y
NODE24   USER24B  IMS1     0  Y
NODE24   N/A      IMS1     0  Y
NODE24   USER24A  IMS2     0
NODE24   USER24B  IMS2     0
NODE24   N/A      IMS2     0

Explanation: There are two IMS systems in the IMSplex: IMS1 and IMS2. RM is maintaining status (STM=YES). Shared queues are irrelevant because queue counts are not requested. IMS1, the command master, displays global and local information. IMS2 displays local information only.

  • NODE21 exists on IMS1 and in the resource structure.
  • NODE22 exists on IMS1 and IMS2 only.
  • NODE23 exists on IMS2 and in the resource structure.
  • NODE24 is an ISC node with 3 parallel sessions available on IMS2, two of which are allocated on IMS2 and in the resource structure. IMS1 also displays an output line for NODE24 with N/A as the ISC user, which represents any global status that the node might have (that is not tied to any particular parallel session).

Example 3 for QUERY NODE command

TSO SPOC input:
QRY NODE NAME(NODE2*) STATUS(STATIC) SHOW(LOCAL)
TSO SPOC output:
Node     ISCUser  MbrName CC  LclStat
NODE21            IMS1     0  IDLE,CONVACT,CON,STATIC
NODE22            IMS1     0  IDLE,STATIC
NODE22            IMS2     0  IDLE,STATIC
NODE24   USER24A  IMS2     0  IDLE,CON,PRI,STATIC
NODE24   USER24B  IMS2     0  IDLE,CON,PRI,STATIC
NODE24   N/A      IMS2     0  IDLE,STATIC

Explanation: There are two IMS systems in the IMSplex: IMS1 and IMS2. RM is maintaining status (STM=YES). Shared queues are irrelevant because queue counts are not requested. IMS1, the command master, displays local information only because SHOW(LOCAL) is specified. IMS2 displays local information only. All static nodes are displayed, and status is displayed, because the STATUS filter was specified.

  • NODE21 exists on IMS1, is logged on, and has an active conversation.
  • NODE22 exists on IMS1 and IMS2.
  • NODE24 is an ISC node with 3 parallel sessions available on IMS2, two of which are allocated and are the primary partners.

Example 4 for QUERY NODE command

TSO SPOC input:
QRY NODE NAME(NODE21) SHOW(GLOBAL,CONV,LTERM,STATUS)
TSO SPOC output:
(screen 1)
Node     MbrName CC  Gbl  Lterm    ConvID ConvTran ConvStat
NODE21   IMS1     0  Y
NODE21   IMS1     0  Y    LTERM21A
NODE21   IMS1     0  Y    LTERM21B
NODE21   IMS1     0  Y                  1 TRAN1A   CONVHELD
NODE21   IMS1     0  Y                  2 TRAN1A   CONVHELD
NODE21   IMS1     0  Y                  3 TRAN1A   CONVACTV

(scrolled right to screen 2)
Node     MbrName Gbl  Status
NODE21   IMS1    Y    CONVACT,STATIC,RM,RMACTIVE,RMOWNED
NODE21   IMS1    Y
NODE21   IMS1    Y
NODE21   IMS1    Y
NODE21   IMS1    Y
NODE21   IMS1    Y

Explanation: There are two IMS systems in the IMSplex: IMS1 and IMS2. RM is maintaining status (STM=YES). Shared queues are irrelevant because queue counts are not requested. IMS1, the command master, displays global information only. IMS2 ignores the command (RC=4, RSN=x1000) because only global information is requested.

NODE21 exists in the resource structure. IMS1 displays a global line which shows that the node is active in the IMSplex, and has a conversation active. There are two logical terminals assigned to the node, and are displayed on separate output lines. There are three conversations associated with the node, and are displayed on separate output lines.

Example 5 for QUERY NODE command

TSO SPOC input:
QRY NODE NAME(NODE23) SHOW(CONV,STATUS,OWNER,RECOVERY)
TSO SPOC output:
(screen 1)
Node     MbrName CC CCText             Gbl  Owner  SRM  Rcvy
NODE23   IMS1     0                    Y    IMS2   LCL  CONV,FP 
NODE23   IMS1    10 NO RESOURCES FOUND
NODE23   IMS2     0
NODE23   IMS2     0
NODE23   IMS2     0

(scrolled right to screen 2)
Node     MbrName Gbl  ConvID ConvTran ConvStat Status
NODE23   IMS1    Y                             RM,RMACTIVE,RMOWNED
NODE23   IMS1
NODE23   IMS2
NODE23   IMS2
NODE23   IMS2

(scrolled right to screen 3)
Node     MbrName Gbl  LSRM LRcvy    LConvID LConvTran LConvStat
NODE23   IMS1    Y
NODE23   IMS1
NODE23   IMS2         LCL  CONV,FP
NODE23   IMS2                             1 TRAN1A    CONVHELD
NODE23   IMS2                             2 TRAN1B    CONVACTV

(scrolled right to screen 4)
Node     MbrName Gbl  LclStat
NODE23   IMS1    Y
NODE23   IMS1
NODE23   IMS2         IDLE,CONVACT,CON
NODE23   IMS2
NODE23   IMS2

Explanation: There are two IMS systems in the IMSplex: IMS1 and IMS2. RM is maintaining status (STM=YES). Shared queues are irrelevant because queue counts are not requested. IMS1, the command master, displays global and local information. IMS2 displays local information.

NODE23 exists in IMS2 and in the resource structure. IMS1 displays a global line which shows the node is active and owned on IMS2, and its status recovery mode is LOCAL, which means conversation information is not known globally. IMS1 also displays a local line showing that NODE23 does not exist locally. IMS2 displays the local information, which includes one status line, and an additional output line for each conversation active or held locally.

Example 6 for QUERY NODE command

TSO SPOC input:
QRY NODE NAME(NODE23) SHOW(ALL)
TSO SPOC output:
(screen 1)
Node     MbrName CC CCText             Gbl QCnt EMHQCnt Type  Owner  SRM  Rcvy
NODE23   IMS1     0                    Y      0       0 SLU2  IMS2   LCL  CONV,FP 
NODE23   IMS1    10 NO RESOURCES FOUND
NODE23   IMS2     0

(scrolled right to screen 2)
Node     MbrName Gbl  User     Userid   Affin    Version# Version#SNU Status
NODE23   IMS1    Y    USER23   UID23    IMS2            5           0 RM,RMACTIVE,RMOWNED 
NODE23   IMS1
NODE23   IMS2

(scrolled right to screen 3)
Node     MbrName Gbl  LQCnt LType CID      RecdCnt SentCnt DefMdtbl ActMdtbl
NODE23   IMS1    Y
NODE23   IMS1
NODE23   IMS2             0 SLU2  02000003       9      13 SLU2MOD2 SLU2MOD2

(scrolled right to screen 4)
Node     MbrName Gbl  LSRM Lrcvy    LUser    LUserid  LVersion# LVersion#SNU LclStat
NODE23   IMS1    Y
NODE23   IMS1
NODE23   IMS2         LCL  CONV,FP  USER23   UID23            5            0 IDLE,CONVACT,CON

Explanation: There are two IMS systems in the IMSplex: IMS1 and IMS2. RM is maintaining status (STM=YES). Shared queues are active. IMS1, the command master, displays global and local information. IMS2 displays local information.

NODE23 exists in IMS2 and in the resource structure. IMS1 displays a global line which shows global queue counts and global status from the resource structure. Global status indicates that the node is active on IMS2, has a VGR affinity with IMS2, and its status recovery mode is LOCAL, which means conversation information is not known globally. IMS1 also displays a local line showing that NODE23 does not exist locally. IMS2 displays the local information, which shows that conversation status exists locally.

Example 7 for QUERY NODE command

TSO SPOC input:
QRY NODE NAME(DFSLN001,DFSLN002) SHOW(LOCAL,TYPE)
TSO SPOC output:
Node     Line Pterm MbrName CC LType
DFSLN001    1     1 IMS1     0 CONSOLE
DFSLN001    1     1 IMS2     0 CONSOLE
DFSLN002    2     1 IMS1     0 RDR/PTR
DFSLN002    2     1 IMS2     0 RDR/PTR

Explanation: There are two IMS systems in the IMSplex: IMS1 and IMS2. STM and shared queues are irrelevant because only local information is requested. IMS1, the command master, displays only local information because no global information is requested. IMS2 displays local information only.

DFSLN001 represents the system console, LINE 1 PTERM 1, on each system. DFSLN002 represents a SYSOUT or SPOOL device, LINE 2 PTERM 1, on each system.

Example 8 for QUERY NODE command: ISC TCP/IP parallel session

Explanation: In the following example, TCP is shown in the LType column to indicate that node CICS is an ISC TCP/IP terminal. In the LclLogonD column, the ETO logon descriptor that was used to establish the current session is LU6TCP1. The local IMS Connect instance that is providing TCP/IP support is identified as HWS1 in the LclImsCon column. Under the CICSApplid column, CICS1 is the APPLID of the remote CICS subsystem with which the ISC TCP/IP terminal is connected. The network ID, IMSNET, of the CICS subsystem that the ISC TCP/IP terminal is connected to is displayed under the CICSNetid column.

TSO SPOC input:
QUERY NODE NAME(CICS) SHOW(ALL)
TSO SPOC output:
(Screen 1)                                                       
Node      ISCUser  MbrName    CC     LQCnt LType  LclImsCon   CICSApplid 
CICS      IMSUS01  IMS1        0         0 TCP    HWS1        CICS1
(Screen 2)                               
Node      ISCUser  MbrName    CICSNetid  LclLogonD  RecdCnt  SentCnt  LSRM 
CICS      IMSUS01  IMS1       IMSNET     LU6TCP1          0        0  LCL 
(Screen 3)                             
Node      ISCUser  MbrName    LRcvy    LUser    LID       LclStat
CICS      IMSUS01  IMS1       STSN     IMSUS01  IMSUS01   SIGN,IDLE,CON