/RSTART command
The /RSTART command starts lines, lines and physical terminals, logical links, nodes, and users when you do not want to reset all associated conditions such as a conversation or special operating mode.
Subsections:
Environment
The following table lists the environments (DB/DC, DBCTL, and DCCTL) in which you can use the commands and keywords.
Command / Keywords | DB/DC | DBCTL | DCCTL |
---|---|---|---|
/RSTART | X | X | |
CONTINUOUS | X | X | |
LINE | X | X | |
LINK | X | X | |
LOPEN | X | X | |
MODE | X | X | |
MSPLINK | X | X | |
NODE | X | X | |
PTERM | X | X | |
USER | X | X |
Syntax
Keywords
The following keywords are valid for the /RSTART command:
- LINE
- Specifies the line or line/physical terminal to be started with all terminals on the line in the same mode of operation they were in when they were stopped. The /RSTART LINE command allows all input, output, and queuing to start on the line and take the line out of response mode if the line was in this mode. The /RSTART LINE PTERM command does not reset line response mode, but does reset the non-VTAM-attached 3270 terminal response mode and looptest mode.
- LOPEN
- LOPEN
enables stopped and idle remote non-VTAM lines. Enter the /RSTART
LINE LOPEN command before any /RSTART LINE PTERM command
to avoid having a line that is stopped and idle reset before it can
be enabled again. If the line is not stopped or process stopped, and
idle, or if enabling is not applicable, the LOPEN keyword is ignored
and processing continues.
/RSTART LINE and /RSTART NODE cannot reset terminal response mode if Fast Path is active for a specified physical terminal or node. The /DEQUEUE command must be entered to discard Fast Path output before using the /RSTART command.
- LINK
- Specifies the logical links
to be started, either individually or all at once.
For TCP/IP and VTAM® links, the /RSTART LINK command can be issued in either one of the two partner systems to start communication. For CTC or MTM links, communication does not begin until the /RSTART LINK command is entered in both partner IMS systems.
The /RSTART LINK command is rejected unless the link is in a stopped and idled status and the assigned physical link is open, as shown in the /DISPLAY command.- MODE
- The MODE keyword allows you to specify mode table entries to be used when activating an IMS VTAM MSC session. Use of the MODE keyword with non-VTAM links is invalid. If non-VTAM links are referred to specifically in the /RSTART LINK command with the MODE keyword, they will be marked in error.
- MSPLINK
- Resets the PSTOPPED status of MSC TCP/IP or VTAM links to enable logons. If the TCP/IP link is used with TCP/IP generic resources, this keyword also resets the PSTOPGEN status.
- NODE
- Specifies
the VTAM node for which input,
output, and queuing will start. The /RSTART NODE nodename
USER username command restarts the ISC half-session allocated
to username for nodename.
The USER keyword is valid only with the NODE keyword and restarts
the specified half-session. If the USER keyword is omitted, all half-sessions
of the specified node are affected. 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 /RSTART NODE USER commands are valid for ISC, LUP, and 3600 nodes only.
The NODE parameter can be generic if the USER keyword is not specified. The generic parameter specifies nodes that already exist. If the node was created temporarily to retain status data and the status conditions have been reset, then the node is deleted at the next simple checkpoint.
If global resource information is not kept in Resource Manager, the /RSTART NODE command allows a node to logon to the local IMS, without resetting local status. If global resource information is kept in Resource Manager, the /RSTART NODE command allows a node to logon to any IMS in the IMSplex, without resetting global node status kept in Resource Manager. If the node no longer has significant status, it is deleted by Resource Manager.
- Commands with the NODE USER keyword pair are valid only if:
- USER
- Specifies
the USER for which input, output, and queuing are to start. This command
starts the USER without resetting conditions such as conversation
mode, exclusive mode, and test mode. The /RSTART USER command
applies only to dynamic users.
The USER parameter can be generic where the generic parameter specifies already existing users.
If the user structure is temporary and was created solely to retain status that is now reset, the temporary user is deleted at the next simple checkpoint.
If global resource information is not kept in Resource Manager, the /RSTART USER command allows a user to sign on to the local IMS. If global resource information is kept in Resource Manager, the /RSTART USER command allows a user to sign on to any IMS in the IMSplex. If the user no longer has significant status in Resource Manager, it is deleted.
Usage notes
The /RSTART command checks the validity of all parameters entered by the terminal operator. If an error is detected on parameters that are independent of one another, only the invalid parameters are flagged as being in error and the /RSTART command processes the rest of the parameters.
The /RSTART command can be used to reset conditions previously established by the /START, /STOP, /PSTOP, /PURGE, /MONITOR, /COMPT, or /RCOMPT command.
This command can be issued to an IMSplex using the Batch SPOC utility.
Equivalent IMS type-2 commands
The following table shows variations of the /RSTART command and the IMS type-2 commands that perform similar functions.
Task | /RSTART command | Similar IMS type-2 command |
---|---|---|
Resets MSC TCP/IP or VTAM links to enable logons. | /RSTART MSPLINK msplinkname | ALL | UPDATE MSPLINK NAME(msplinkname | *) START(LOGON) |
Examples
The following are examples of the /RSTART command:
Example 1 for /RSTART command
/RSTART LINE 4,5,6,7,8,9,10,11
DFS058I RSTART COMMAND COMPLETED
DFS059I TERMINAL RSTARTED
Explanation: LINES 4,5,6,7,8,9,10, and 11 are started.
Example 2 for /RSTART command
/RSTART LINE 4 5 6 700
DFS058I RSTART COMMAND COMPLETED EXCEPT LINE 700
Example 3 for /RSTART command
/RSTART LINE 4 PTERM 1, 2
DFS058I RSTART COMMAND COMPLETED
DFS059I TERMINAL RSTARTED
Explanation: LINE 4 PTERM 1 and 2 are started.
Example 4 for /RSTART command
/RSTART LINK ALL
DFS058I RSTART COMMAND COMPLETED
Explanation: All of the logical links are started. For CTC and MTM links, communication across the link does not begin until the partner in the remote system is started with the /RSTART LINK command.
DFS2168I CONNECTION ESTABLISHED ON LINK 2
Explanation: The connection for communication between two IMS systems is established. The partner link is started with a /RSTART LINK command. After each connection, the message DFS2168 is returned.
Example 5 for /RSTART command
/RSTART LINK 2
DFS058I RSTART COMMAND COMPLETED
Explanation: Logical link 2 is started.
DFS2168I CONNECTION ESTABLISHED ON LINK 2
Explanation: The two IMS systems are connected.
Example 6 for /RSTART command and a TCP/IP link
/RSTART LINK 23
DFS2168I 17:37:39 CONNECTION ESTABLISHED ON LINK 0023
DFS2160I 17:37:39 LINK 028 STARTED BY PARTNER TB NODE IMS1
DFS2168I 17:37:39 CONNECTION ESTABLISHED ON LINK 0028
Explanation: In the Response ET at the partner system, IMS1 is the IMS ID of the partner system in which the /RSTART command was issued.
Example 7 for /RSTART command and a VTAM link
/RSTART LINK 10
DFS058I 17:34:36 RSTART COMMAND COMPLETED
DFS2168I 17:34:36 CONNECTION ESTABLISHED ON LINK 0010
DFS2160I 17:34:36 LINK 013 STARTED BY PARTNER AK NODE L6APPL3
DFS2168I 17:34:36 CONNECTION ESTABLISHED ON LINK 0013
Explanation: In the Response ET at the partner system, L6APPL3 is the APPLID of the partner system in which the /RSTART command was issued.
Example 8 for /RSTART command
/RSTART NODE EAST
DFS058I RSTART COMMAND COMPLETED
Explanation: The node named EAST is started.