/OPNDST command

For VTAM terminals, if the USER keyword is specified, the user is signed on automatically to the terminal after successful session initiation.

For ISC TCP/IP terminals, the user is signed on automatically after successful session initiation.

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

The /OPNDST command without the USER keyword: Use this form of the command for all static and ETO terminals except ETO SLU P and Finance terminals, ETO output-only devices, and all ISC parallel sessions.

The /OPNDST command with the USER keyword for non-ISC: Use this form of the command for:

• ETO SLU P and Finance terminals
• ETO output-only devices, for example, 3284, 3286, and SLU P1 with a single component of PRINTER1

The /OPNDST command with the USER keyword for ISC TCP/IP: Use this form of the command for all ISC parallel sessions, both static and ETO.

The /OPNDST command with the USER keyword for ISC VTAM: Use this form of the command for all ISC parallel sessions, both static and ETO.

Keywords

The following keywords are valid for the /OPNDST command:

ID

Is applicable only if the USER keyword is specified and the node is a parallel session ISC VTAM node. ID must not be specified for a single session ISC node.

For ISC VTAM parallel sessions, ID identifies the other system half-session qualifier. ID idname must be specified to open ISC nodes defined with users. The ID idname is passed to the other half-session with the session initiation request. If the other system is another IMS system, idname is the name of an ISC user in that system.

For ISC TCP/IP parallel sessions, the ID keyword does not apply. If the ID keyword is specified, it is ignored.

LOGOND

Indicates the logon descriptor used for session establishment. LOGOND is supported for both dynamic ISC TCP/IP nodes and dynamic non-ISC nodes.

If a logon descriptor name is provided by the Logon exit routine (DFSLGNX0), the name provided by the exit routine overrides the name specified on the LOGOND keyword.

For ISC TCP/IP nodes, the name specified on the LOGOND keyword must match a logon descriptor that specifies the LCLICON keyword for TCP/IP support. If the logon descriptor does not specify TCP/IP support, IMS attempts to open the session as a VTAM node.

MODE

Identifies the LOGON MODE table entry that VTAM must use and can determine operating characteristics for certain VTAM terminals. If a list of node names is given, the MODE keyword is applied to each of them. The command checks whether each node has been defined to accept IMS initiated connections. If the node was defined as NOPNDST, the /OPNDST command accepts all the nodes except the node defined as NOPNDST.

ISC TCP/IP sessions do not support the MODE keyword.

NODE

Specifies the node with which IMS initiates a session.

The /OPNDST NODE ALL command opens sessions for all static terminals except ISC parallel sessions. The command has considerable concurrent activity, both for IMS and for VTAM. Ensure that the system has sufficient pool sizes, buffer sizes, and number of concurrent IMS tasks defined.

If the USER keyword is not specified in the command, the NODE parameter can be generic or ALL, or a range of static nodes, or there can be multiple NODE parameters. If a generic, ALL, or range of node names is specified, any nodes defined with users are ignored and flagged with an error message.

The /OPNDST NODE USER command logs on and signs on a user at the same time, except for ISC terminals. On ISC terminals, the session is allocated.

The following list includes sample /OPNDST NODE USER commands:

• To log on and sign on to a static non-ISC terminal:

    /OPNDST NODE nodename USER username UDATA userdata

  This command marks a statically defined terminal as signed on by the user.
• To log on and sign on to an ETO non-ISC terminal:

    /OPNDST NODE nodename USER username MODE modename
    LOGOND logondname USERD userdname UDATA userdata

  This command creates the terminal and user structures, and allocates the newly created user structure to the terminal structure created to indicate signed on status.
• To log on and sign on to a static ISC terminal:

    /OPNDST NODE nodename USER username ID idname

  This command finds the subpool structure and allocates the subpool (user) structure to the statically defined ISC terminal. If the terminal is defined to use ISC TCP/IP, the ID keyword does not apply and is ignored by IMS.

• To log on and sign on to an ETO ISC VTAM terminal:

    /OPNDST NODE nodename USER username ID idname MODE modename
    LOGOND logondname USERD userdname UDATA userdata

  This command creates the terminal and subpool (user) structure and allocates the newly created user structure to the terminal structure created. The command also signs on the user with the username (the username must be defined to RACF®), and remains signed on until the user issues a /SIGN OFF command, or the session is terminated.
• To log on and sign on to an ETO ISC TCP/IP terminal:

    /OPNDST NODE nodename USER username LOGOND logondname

  This command creates the terminal and subpool (user) structure and allocates the newly created user structure to the terminal structure created. The command also signs on the user with the username (the username must be defined to RACF), and remains signed on until the user issues a /SIGN OFF command, or the session is terminated.

  For ISC TCP/IP parallel sessions, a logon descriptor must exist that specifies the LCLICON keyword for TCP/IP support. IMS uses the value of the NODE keyword to search for a logon descriptor only when the LOGOND keyword is not specified. If the logon descriptor does not exist or does not specify TCP/IP support, IMS attempts to open the session as a VTAM node.

To restart failing ETO sessions (for example, ETO only or printer sessions), use the /OPNDST NODE USER command.

In an IMSplex, /OPNDST NODE specifies a VTAM node with which IMS initiates a session. Specify ROUTE(imsid), if you want to log the node onto a particular IMS. If ROUTE(imsid) is not specified, and /OPNDST is routed to all the IMS systems, IMS processes the command only on the IMS system designated as the command master. If the ROUTE keyword specifies multiple IMS systems so that the /OPNDST command is routed to more than one IMS systems, IMS processes the command only on the IMS system designated as the command master. On the other IMS systems, the /OPNDST command is rejected.

Q

Causes IMS to request VTAM to queue SIMLOGON requests for VTAM/SNA-supported terminals.

The /OPNDST NODE Q command also allows IMS to request another subsystem to share a node (usually printers) with IMS. If the other subsystem is using the printer, VTAM queues the SIMLOGON request for IMS for the printer, schedules the owning subsystem's RELREQ VTAM exit, and acquires the printer for IMS after the current owning system releases the printer. Multiple requests for the same printer are queued by VTAM for processing.

The /DISPLAY NODE command is used to determine whether IMS has acquired the printer.

ISC TCP/IP sessions do not support the Q keyword.

UDATA

Indicates the user data used with the signon.

The UDATA keyword is valid only if the USER keyword and parameter are also specified. The UDATA keyword is valid for static and dynamic users. It is not valid for ISC nodes. The user data can be up to 256 bytes long. Passwords can be mixed case or lowercase depending on what is specified on the PSWDC keyword in the DFSPBxxx IMS.PROCLIB member.

ISC TCP/IP sessions do not support the UDATA keyword.

RACF password phrases are not supported with UDATA.

USER

Identifies the logical terminal user to be allocated to the half-session to be created for the ISC node that is specified on the NODE keyword.

For dynamic non-ISC users, it specifies the user ID to be signed on to the dynamic node nodename.

The USER keyword applies to ISC sessions when allocating a user to an ISC node, to dynamic users when signing a dynamic user on to a dynamic node, and to static user IDs when signing a user on to a static node.

USER username must be specified to open parallel session ISC nodes with users. It must not be specified for a single session ISC node.

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
• The /OPNDST NODE USER commands are valid for ISC and non-ISC nodes and users.

USERD

Specifies the user descriptor to be used with the signon. It is valid only if the USER keyword and parameter are specified. USERD is only supported for dynamic users and is only valid for dynamic non-ISC nodes. The user descriptor can also be provided through the logon or signon exits.

ISC TCP/IP sessions do not support the USERD keyword.

Usage notes

All forms of logging-on a remote VTAM terminal to IMS, including the use of the /OPNDST command, do not work until the /START DC command has been entered and accepted by IMS.

All /OPNDST formats require an EOM indication to denote end-of-message. An EOS indication must be included for all segments that precede the last segment.

You can issue /OPNDST on the XRF alternate to restart a failed backup session for a class 1 ETO terminal. To do this, the node and the user structure must still exist and be coupled together, and an active session must exist on the active system. If the node and the user are not coupled, or an active session does not exist on the active system, the command is rejected.

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

A period is normally used as the delimiter at the end of IMS commands. When support for special characters is enabled in RACF, a period becomes a valid character in the RACF password. Therefore, when a password is specified at the end of the /OPNDST command, you must insert a space before the period that you are using as the end-of-command delimiter. If a space is not added before the period that is intended to be the end-of-command delimiter and support for special characters is enabled in RACF, the period is treated as part of the password and not as a delimiter.

One or more equal signs (=) can normally be used as a valid delimiter between a keyword and the keyword value on the /OPNDST command. However, when support for special characters is enabled in RACF, an equal sign becomes a valid character in the RACF password. If you use the equal sign as a delimiter when support for special characters is enabled in RACF, you can specify only one delimiter immediately preceding the password on the UDATA keyword. Any equal sign that follows the delimiter is interpreted as the first character of the password.