QUERY USER command

Use the QUERY USER command to display information about VTAM® users across the IMSplex. A user is either a dynamic (ETO) user, or a static or dynamic (ETO) ISC subpool user. In this context, a user ID that is used for user or terminal security is not considered as a user, but rather as a user ID. 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 USER command and keywords
Command / Keywords DB/DC DBCTL DCCTL
QUERY USER X   X
NAME X   X
SHOW X   X
STATUS X   X

Syntax

Read syntax diagramSkip visual syntax diagramQUERYQRYUSERNAME(*)NAME(,usernameusername*)SHOW(GLOBAL,LOCAL)SHOW(GLOBAL,LOCAL,A)SHOW(,GLOBALLOCAL,A)STATUS(,ALLOCCONVDEADQEXCLMFSTPRSTRESPRESPINPRESPINPFPRMRMACTIVERMOWNEDSTATICSTOSGNTEST)
A
Read syntax diagramSkip visual syntax diagram,ALLAUTOLOGONCONVEMHQIDLTERMNODEOWNERPRESETQCNTRECOVERYSTATUSUSERIDVERSION

Keywords

The following keywords are valid for the QUERY USER command:

NAME()
Specifies the names of one or more users (dynamic user or ISC subpool user) that are to be displayed. Valid names are 1-8 characters, and wildcards can be specified. To display all users, specify NAME(*). NAME(*) is the default.
SHOW()
Specifies the user output fields to be returned. The user 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 user 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 user 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).
AUTOLOGON
Displays the current autologon information for the specified user. This includes the name of the node with which to establish a session, the VTAM mode table name, the name of the node descriptor to be used to build the node, and (if ISC) the identifier of the other system half-session qualifier.
CONV
The conversation ID, transaction, and conversation status associated with the user. 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).
EMHQ
Displays the user message queue count in the Expedited Message Handler (EMH) queues. The queue count is the sum of the queue counts for each lterm associated with the specified user.

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 user resource exists in the resource structure, then the lterms associated with the global user resource are used to obtain the queue counts from the EMH queues. Otherwise, the lterms associated with the local user resource are used, but if the user does not exist locally on the command master, then the queue count is 0.

GLOBAL
When GLOBAL is specified, the command master displays global information, depending on the other SHOW parameters specified. This includes information from shared queues and 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 or sysplex terminal management (or both). GLOBAL is not applicable when the command master is not using shared queues 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 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.
LOCAL
When 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).

LTERM
Displays the logical terminal (lterm) names, if any, associated with the user. A user might have zero or more logical terminals associated with it. Each lterm associated with the user is returned on a separate command response line.

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

NODE
Displays the dynamic or ISC node that the user is associated with.
OWNER
Displays the owner of the user resource in the resource structure. This applies only when sysplex terminal management is enabled, and is processed by the command master only. All other IMS systems ignore this parameter.

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

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

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.

When 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 shared message queues are enabled.

When 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 user resource exists in the resource structure, then the lterms associated with the global user resource are used to obtain the queue counts from shared queues. Otherwise, the lterms associated with the local user resource are used, but if the user 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 user. 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 user signoff, or session or IMS termination. The output displays the SRM for the user 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 user. See QUERY USER status for a list and meaning of possible status that might be returned.
USERID
The RACF® user ID that was used to sign the user on to a node.
VERSION
Displays the RM version number of the user resource. This is the version number assigned to the user, which is assigned by MVS, and maintained by RM, when the resource is created or updated in the resource structure. VERSION applies only when sysplex terminal management is enabled. VERSION is ignored when sysplex terminal management is not enabled.
STATUS()
Selects users for display that possess at least one of the specified user 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 users 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 users 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 users 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 user, even if SHOW(STATUS) is not specified.

To determine which filters can be used to select users with corresponding status, see QUERY USER status.

Usage notes

The QUERY USER command can be specified only through the OM API.

The QUERY USER command 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 USER 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, 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 user 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.

Similar IMS type-1 commands

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

Table 2. Type-1 equivalents for the QUERY USER command
QUERY USER command Similar IMS type-1 command
QUERY USER SHOW(AUTOLOGON) /DISPLAY USER user AUTOLOGON
QUERY USER SHOW(CONV) /DISPLAY CONV USER user
QUERY USER SHOW(EMHQ) /DISPLAY USER user QCNT EMHQ
QUERY USER SHOW(ID) /DISPLAY ASMT USER user
QUERY USER SHOW(LTERM) /DISPLAY ASMT USER user
QUERY USER SHOW(NODE)

/DISPLAY ASMT USER user
/DISPLAY USER user

QUERY USER SHOW(OWNER) /DISPLAY USER user RECOVERY
QUERY USER SHOW(PRESET) /DISPLAY USER user
QUERY USER SHOW(QCNT)

/DISPLAY USER user
/DISPLAY USER user QCNT

QUERY USER SHOW(RECOVERY) /DISPLAY USER user RECOVERY
QUERY USER SHOW(STATUS) /DISPLAY USER user
QUERY USER SHOW(USERID)

/DISPLAY ASMT USER user
/DISPLAY USER user

QUERY USER STATUS(CONV) /DISPLAY CONV
QUERY USER STATUS(status) /DISPLAY STATUS USER

Output fields

The following table shows the QUERY USER 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 USER command
Short label Long label SHOW parameter Scope Meaning
AUTID AutLID AUTOLOGON GBL Identifier of the other system half-session qualifier for autologon in the resource structure. This is only applicable if the user is associated with a parallel session ISC node.
AUTLD AutLDsc AUTOLOGON GBL The logon descriptor for autologon in the resource structure.
AUTMD AutLMdt AUTOLOGON GBL The VTAM mode table name for autologon in the resource structure.
AUTND AutLNode AUTOLOGON GBL The node name for autologon in the resource structure.
CC CC N/A N/A Completion code for the line of output. The completion code indicates whether 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.
CONVID ConvID CONV GBL The conversation ID for a conversation associated with the user, as it exists in the resource structure. A user 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 user, as it exists in the resource structure. A user 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 user, as it exists in the resource structure. A user might have zero, one, or more conversations.
EMHQ EMHQCnt EMHQ GBL Global lterm 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.
LAUTID LAutLID AUTOLOGON LCL Identifier of the other system half-session qualifier for autologon in the local system. This is applicable only if the user is associated with a parallel session ISC node.
LAUTLD LAutLDsc AUTOLOGON LCL The logon descriptor for autologon in the local system.
LAUTMD LAutLMdt AUTOLOGON LCL The VTAM mode table name for autologon in the local system.
LAUTND LAutLNode AUTOLOGON LCL The node name for autologon in the local system.
LCONVID LConvID CONV LCL The conversation ID for a conversation associated with the user, as it exists in the local system. A user 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 user, as it exists in the local system. A user 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 user, as it exists in the local system. A user might have zero, one, or more conversations.
LID LID ID LCL For ISC parallel-session terminals, displays the local half-session qualifier of the other system.
LLTERM LLterm LTERM LCL Local logical terminal names. The logical terminal names associated with the user.
LNODE LNode NODE LCL Identifies the dynamic or static node associated with the user on the local system.
LPRST LPreset PRESET LCL Identifies the preset destination transaction or LTERM name when the user is in preset destination mode, which is established by the /SET command. All messages entered at this terminal are sent to the preset destination transaction code 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, or the user is not signed on and there is no end-user significant status.
LSTT LclStat STATUS LCL Local user status. See QUERY USER status for a list and explanation of the possible user status.
LTERM Lterm LTERM GBL Global logical terminal names. The logical terminal names associated with the user.
LUID LUserid USERID LCL Identifies the local user ID signed on to the user.
LVER LVersion# VERSION LCL Version number for the user resource being maintained in the local system. This field applies only 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 NODE GBL Identifies the dynamic or static node associated with the user in the resource structure.
OWNER Owner OWNER GBL Resource owner. IMS identifier or RSENAME of IMS where the user 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 only be displayed if shared queues are used.
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).
  • FP: Fast Path status is recoverable (RCVYFP=YES).
  • STSN: STSN status is recoverable (RCVYSTSN=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, or the user is not signed on and there is no end-user significant status.
STT Status STATUS GBL Global user status. See QUERY USER status for a list and explanation of the possible node status.
UID Userid USERID GBL Identifies the RACF user ID signed on to the user.
USER User N/A N/A The user name. The user name is always returned.
VER Version# VERSION GBL Version number for the user resource being maintained in the resource structure. This field applies only when STM is enabled.

QUERY USER status

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

Status
The user status that is displayed.
STATUS parameter
The STATUS() filter that will select users 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 USER status
Status STATUS parameter Scope Meaning
ALLOC ALLOC GBL and LCL A user or ISC subpool is allocated to a node.
CONVACT CONV GBL and LCL An active conversation exists.
CONVHELD CONV GBL and LCL All conversations are held.
DEADQ DEADQ LCL The user has dead letter queues, or whose last access time was outside the limit set by the DLQT JCL parameter. The DEADQ status can be removed by signing on the user or entering the /DEQUEUE or /ASSIGN command.
EXCL EXCL GBL and LCL The user is in exclusive mode set by the /EXCLUSIVE command. The exclusive mode restricts the output received by the terminal affected.
MFST MFST GBL and LCL The user is in MFSTEST mode, set by the UPDATE USER START(MFST) command or 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.
PRST PRST LCL The user 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.
RESP RESP LCL The user 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 user 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 user 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.
RM RM GBL The user exists in the resource structure managed by RM.
RMACTIVE RMACTIVE GBL The user is active (signed on) in the IMSplex, as indicated in the RM structure (RM active).
RMOWNED RMOWNED GBL The user is owned by an IMS system in the IMSplex, as indicated in the RM structure (RM owned).
STATIC STATIC GBL and LCL The user was defined during system definition.
STOSGN STOSGN GBL and LCL The user was stopped from signing on with the UPDATE USER command or the /STOP USER command.
TEST TEST LCL The user is in test mode set by the /TEST command. Test or echo mode sends any input from the terminal back to the terminal.

Return, reason, and completion codes

An IMS return and reason code is returned to OM by the QUERY USER command. The OM return and reason codes that may be returned as a result of the QUERY USER 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 QUERY USER command.

Table 5. Return and reason codes for the QUERY USER 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'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'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'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 USER command
Completion code Completion code text Meaning
0   The QUERY USER 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.
1A2 User Resource is in error The user 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 USER command:

Example 1 for QUERY USER command

TSO SPOC input:
QRY USER NAME(USER2*,XYZ) SHOW(LOCAL)
TSO SPOC output:
User     MbrName CC CCText
USER23   IMS1     0
USER23   IMS2     0
USER24A  IMS2     0
USER24B  IMS2     0
USER24C  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.

  • USER23 exists on IMS1 and IMS2.
  • USER24A exists on IMS2.
  • USER24B exists on IMS2.
  • USER24C exists on IMS2.
  • XYZ does not exist on any system.

Example 2 for QUERY USER command

TSO SPOC input:
QRY USER NAME(USER2*)
TSO SPOC output:
User     MbrName CC  Gbl
USER23   IMS1     0  Y
USER23   IMS1     0
USER23   IMS2     0
USER24A  IMS1     0  Y
USER24A  IMS2     0
USER24B  IMS1     0  Y
USER24B  IMS2     0
USER24C  IMS2     0
USER25   IMS1     0  Y
USER26   IMS1     0  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 and local information. IMS2 displays local information only.

  • USER23 exists on IMS1, IMS2 and in the resource structure.
  • USER24A exists on IMS2 and in the resource structure.
  • USER24B exists on IMS2 and in the resource structure.
  • USER24C exists on IMS2 only.
  • USER25 exists in the resource structure only.
  • USER26 exists in the resource structure only.

Example 3 for QUERY USER command

TSO SPOC input:
QRY USER NAME(USER2*) STATUS(STATIC) SHOW(LOCAL)
TSO SPOC output:
User     MbrName CC CCText              LclStat
USER24A  IMS2     0                     ALLOC,STATIC
USER24B  IMS2     0                     ALLOC,STATIC
USER24C  IMS2     0                     STATIC
USER2*   IMS1    10 NO RESOURCES FOUND

Explanation: There are two IMS systems in the IMSplex: IMS1 and IMS2. RM and shared queues are irrelevant because no global information is requested. IMS1, the command master, displays local information only because SHOW(LOCAL) is specified. IMS2 displays local information only. All static users are displayed, and status is displayed because the STATUS filter was specified. IMS1 did not find any static users that matched the name specified.

  • USER24A exists on IMS2, and is allocated to a node.
  • USER24B exists on IMS2, and is allocated to a node.
  • USER24C exists on IMS2, but is not allocated.

Example 4 for QUERY USER command

TSO SPOC input:
QRY USER NAME(USER25) SHOW(GLOBAL,CONV,LTERM,STATUS)
TSO SPOC output:
(screen 1)
User     MbrName CC  Gbl  Lterm    ConvID ConvTran ConvStat
USER25   IMS1     0  Y
USER25   IMS1     0  Y    LTERM25A
USER25   IMS1     0  Y    LTERM25B
USER25   IMS1     0  Y                  1 TRAN1A   CONVHELD
USER25   IMS1     0  Y                  2 TRAN1A   CONVHELD
USER25   IMS1     0  Y                  3 TRAN1A   CONVACTV

(scrolled right to screen 2)
User     MbrName Gbl  Status
USER25   IMS1    Y    CONVACT,RM
USER25   IMS1    Y
USER25   IMS1    Y
USER25   IMS1    Y
USER25   IMS1    Y
USER25   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.

USER25 exists in the resource structure. IMS1 displays a global line that shows that the user is not active (not signed on) in the IMSplex, and has a conversation active. There are two lterms assigned to the user, and are displayed on separate output lines. There are three conversations associated with the user, and are displayed on separate output lines.

Example 5 for QUERY USER command

TSO SPOC input:
QRY USER NAME(USER23) SHOW(CONV,STATUS,OWNER,RECOVERY)
TSO SPOC output:
(screen 1)
User     MbrName CC Gbl  Owner  SRM  Rcvy
USER23   IMS1     0 Y    IMS2   LCL  CONV,FP 
USER23   IMS1     0 
USER23   IMS2     0
USER23   IMS2     0
USER23   IMS2     0

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

(scrolled right to screen 3)
User     MbrName Gbl  LSRM LRcvy    LConvID LConvTran LConvStat LclStat
USER23   IMS1    Y
USER23   IMS1         LCL  CONV,FP
USER23   IMS2         LCL  CONV,FP                              ALLOC,CONVACT
USER23   IMS2                             1 TRAN1A    CONVHELD
USER23   IMS2                             2 TRAN1B    CONVACTV

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.

USER23 exists on IMS1, IMS2 and in the resource structure. IMS1 displays a global line that shows the user 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 USER23 exists locally, but has no local status. IMS2 displays the local information for the active user, which includes one status line that shows that an active conversation exists, and an additional output line for each conversation active or held locally.

Example 6 for QUERY USER command

TSO SPOC input:
QRY USER NAME(USER23) SHOW(ALL)
TSO SPOC output:
(screen 1)
User     MbrName CC Gbl QCnt EMHQCnt Owner  SRM  Rcvy     Userid   Node   Version#
USER23   IMS1     0 Y      0       0 IMS2   LCL  CONV,FP  UID23    NODE23       38
USER23   IMS1     0
USER23   IMS2     0

(scrolled right to screen 2)
User     MbrName Gbl  AutLNode AutLMdt  AutLDsc  AutLID Status
USER23   IMS1    Y    NODE23   SLU2MOD2 NODE23          ALLOC,RM,RMACTIVE,RMOWNED 
USER23   IMS1
USER23   IMS2

(scrolled right to screen 3)
User     MbrName Gbl  LQCnt LSRM LRcvy    LUserid  LNode   LVersion#  LPreset
USER23   IMS1    Y
USER23   IMS1             0 LCL  CONV,FP                           0
USER23   IMS2             0 LCL  CONV,FP  UID23    NODE23         38

(scrolled right to screen 4)
User     MbrName Gbl  LAutLNode LAutLMdt LAutLDsc LAutLID LclStat
USER23   IMS1    Y
USER23   IMS1
USER23   IMS2         NODE23    SLU2MOD2 NODE23           ALLOC,CONVACT

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.

USER23 exists in IMS1, IMS2, and in the resource structure. IMS1 displays a global line that shows global queue counts and global status from the resource structure. Global status indicates that the user is active 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 USER23 exists locally, but has no local status. IMS2 displays the local information for the active user, which shows that conversation status exists locally.