/TEST command

Subsections:

• Environment
• Syntax
• Keywords
• Usage notes
• Examples

Environment

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

Syntax

>>-+-/TEST-+--+---------------------------------------------+--><
   '-/TES--'  '-MFS--+------------------------------------+-'   
                     +-LINE--line#--PTERM--pterm#---------+     
                     +-NODE--nodename--+----------------+-+     
                     |                 '-USER--username-' |     
                     '-USER--username---------------------'     

Keywords

The following keywords are valid for the /TEST command:

MFS

Specifies MFS test mode for the terminal or user. The MFS parameter is valid only for terminals supported by Message Format Service (MFS). When the /TEST MFS USER command is issued for a dynamic user, it is not possible to determine if the MFSTEST mode is valid until the user signs on to a terminal. Once the user signs on to a terminal, a check is made to determine whether that terminal supports MFSTEST mode. If the terminal does not support MFSTEST mode, the mode is not propagated to the terminal and is removed from the USER unless another /TEST MFS USER command is issued.

LINE, PTERM

Specifies the non-VTAM line and pterm to place into MFSTEST mode.

NODE

Specifies the VTAM® node to place into MFSTEST mode.

The /TEST MFS NODE form of the command is valid only for statically defined nodes.

Restrictions for using NODE and USER parameters together:

• Commands with the NODE USER keyword pair are valid only if:
  • The USER is signed on to the NODE
  • In an ISC environment, the USER is allocated to the NODE
  • The nodes and users already exist
• /TEST MFS NODE USER commands are valid for ISC, LUP, and 3600 nodes only. For ISC, the /TEST MFS NODE nodename USER username form of the command is supported for ISC nodes and applies to the half-session allocated to the USER username.

USER

When specified without the NODE keyword, USER specifies the dynamic user to place into MFSTEST mode. MFSTEST mode status is kept from one signon to another. For example, if a user issues a /TEST MFS command, signs off, and then signs on again at another terminal, the MFSTEST mode is still in effect. If the user does not exist, it is created and MFSTEST mode is set.

Usage notes

This command can be issued to an IMSplex using the Batch SPOC utility.

In test or echo mode, any input from the terminal is sent back. Input and output errors are not checked, and IMS™ error notification procedures are bypassed. Echo mode continues until reset with an /END, /STOP LINE, /STOP LINE PTERM, or a /STOP NODE command. The /DISPLAY command identifies a terminal or user in test mode or MFSTEST mode. If no keywords are supplied, the terminal entering the command is placed into test mode or MFSTEST mode.

Test mode is not a command significant status, so the commands to set test mode are not recoverable nor are they kept after signons and can only be set by the end user or terminal, not remotely by an operator. The /TEST LINE, /TEST NODE, and /TEST USER commands, which set test mode remotely, are no longer supported.

In MFSTEST mode, terminals supported by the 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. MFSTEST mode continues until reset with an /END command. Certain error conditions can occur that cause MFSTEST mode to terminate. If an error condition occurs, the terminal operator receives an error message.

MFSTEST mode is a command significant status, is recoverable and is remembered across logons and signons. For example, if a /TEST MFS NODE command is entered at a node, the node logs off and logs back on at another terminal, MFSTEST mode is still in effect. If a dynamic user issues a /TEST MFS USER command, signs off, and then signs on again at another terminal, MFSTEST mode is still in effect.

/TEST MFS NODE applies to dynamic nodes in addition to static nodes because MFSTEST mode is associated with dynamic nodes as well as dynamic users. /TEST MFS NODE and /TEST MFS NODE USER set MFSTEST mode at the node level. /TEST MFS USER sets MFSTEST at the user level. /TEST MFS with no keywords sets MFSTEST at the node level for static terminals (they have no user level) and at the user level for dynamic terminals.

The /TEST NODE USER command is supported for static and dynamic ISC sessions. For ISC, /TEST MFS NODE USER is required. You cannot use /TEST MFS NODE (without USER) for ISC and have it apply to all of the half-sessions.

If global resource information is kept in Resource Manager, MFSTEST mode is set globally. If global resource information is not kept in Resource Manager, the resource does not exist, and ETO is enabled, the resource (node or user) is created and MFSTEST mode is set. If a temporary node is dynamically created to hold command status, and the temporary node has MFSTEST status, then, when a logon occurs for the node, the MFSTEST status is set for the logged-on node. If the node logging on is an ISC parallel session, MFSTEST is set only for the first half-session that is logged on. Subsequent ISC half-sessions will not be put into MFSTEST mode.