/EXIT command

The conversation can be either active or in hold status at the time /EXIT is entered. Depending upon the conversational processing options selected for the IMS™ system, the application program might or might not be notified of the conversation termination.

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 command and keywords.

Syntax

>>-+-/EXIT-+---------------------------------------------------->
   '-/EXI--'   

>--+---------------------------------------------------------+-><
   '-CONV--conv#--+----------------------------------------+-'   
                  +-LINE--line#--PTERM--pterm#-------------+     
                  +-LUNAME--luname-------------------------+     
                  +-NODE--nodename--+----------------+-----+     
                  |                 '-USER--username-'     |     
                  +-TMEMBER--tmembername--TPIPE--tpipename-+     
                  '-USER--username-------------------------'     

Keywords

The following keywords are valid for the /EXIT command:

CONVERSATION

Terminates the specified conversation. The conversation is terminated whether it was active or held. The conversation identifier (conv#) must be specified as a 4-digit number, including leading zeros.

LINE PTERM

Terminates the conversation on the physical terminal specified, regardless of whether the conversation was active or held. The line specified must be in stopped and idle status.

LUNAME

Terminates the IMS conversation and the APPC conversation on the specified luname. In an IMSplex environment, /EXIT LUNAME needs to be issued on the IMS that owns the conversation. Within an IMS system, the conversation ID is unique.

NODE

Terminates the conversation on the node specified, regardless of whether the conversation was active or held. The node specified must be stopped or idle. This form of the command does not support dynamic nodes or LU 6.2 nodes defined with users.

The NODE USER combination applies only to the specified half-session of the ISC parallel session node allocated to USER The half-session must have been stopped and idled. The command must be issued from a terminal or node other than the one in the conversation.

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
• /EXIT (CONV) NODE USER commands are valid for ISC, LUP, and 3600 nodes only.

TMEMBER TPIPE

Terminates the IMS conversation on the specified tmembername tpipename. In an IMSplex environment, /EXIT TMEMBER TPIPE must be issued on the IMS that owns the conversation. Within an IMS system, the conversation ID is unique.

USER

Terminates the conversation associated with the specified user. The user must not be signed on to a node. The user must be dynamic.

Usage notes

Transactions that are queued for processing when the /EXIT command is issued are discarded. If a transaction is being processed or was sent to a remote system for processing when /EXIT is issued, the command is still processed; however, the conversation will be terminated, but the conversational transaction will still be issued. When the conversational response is received, the Conversational Abnormal Termination exit (DFSCONE0) is called, and the response message is queued to the response terminal.

The /EXIT command with no keywords can only be used if the conversation is active.

If global resource information is kept in Resource Manager (RM), /EXIT NODE or /EXIT USER terminates the conversation in RM. If global resource information is not kept in RM, /EXIT NODE or /EXIT USER terminates a conversation on the IMS where the /EXIT command is entered or routed to by the OM SPOC.

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

/EXIT is not valid from an LU 6.2 device or OTMA device. DEALLOCATE the APPC conversation after receiving all output from an iteration. When the /EXIT command specifies only the CONVERSATION keyword, the command can be entered only from the terminal that owns the conversation.