>>-+-/RSTART-+--------------------------------------------------> '-/RST----' .-------. V | >--+-LINE--+-+---line#-+-+--+-------+-----+---------+---------->< | | '-ALL-------' '-LOPEN-' | | | | .--------. | | | | V | | | | '-line#--PTERM--+---pterm#-+-+-' | | '-ALL--------' | | .-------. | | V | | +-LINK--+---link#-+-+--+----------------+--| A |-+ | '-ALL-------' '-MODE--modename-' | | .-------------. | | V | | +-MSPLINK--+---msplinkname-+-+-------------------+ | '-ALL-------------' | | .---------------. | | V | | +-NODE--+-+---+-nodename--+-+----------------+-+-+ | | | '-nodename*-' | | | | | | .----------. | | | | | | V | | | | | | '-nodename--USER--+---username-+-+-' | | | | '-ALL----------' | | | '-ALL----------------------------------' | | .---------------. | | V | | '-USER--+---+-username--+-+-+--------------------' | '-username*-' | '-ALL---------------' A: |--+---------------------------+--------------------------------| '-CONTINUOUS--+-----------+-' '-blocksize-'
Table 146 lists the environments (DB/DC, DBCTL, and DCCTL) from which the command and keywords can be issued.
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 |
/RSTART 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.
/RSTART 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.
/RSTART can be used to reset conditions previously established by the /START, /STOP, /PSTOP, /PURGE, /MONITOR, /COMPT, or /RCOMPT command.
/RSTART LINE and /RSTART NODE cannot reset terminal response mode if Fast Path is active for a specified physical terminal or node. /DEQUEUE must be entered to discard Fast Path output before using /RSTART.
If the size is not specified, it defaults to 2 bytes. The maximum size of the dummy data blocks to be sent is equal to the size of the link buffer minus 80 bytes.
The CONTINUOUS keyword is ignored if the link is not BTAM. If multiple links are restarted and the CONTINUOUS keyword is specified, only the BISYNC links are restarted in continuous mode.
A /PSTOP LINK command resets continuous mode. If a link is stopped because of an error while in continuous mode, a /RSTART command that does not specify the CONTINUOUS parameter will reset continuous mode.
These conditions apply to ISC, dynamic 3600 and dynamic LUP.
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.
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 signon to the local IMS. If global resource information is kept in Resource Manager, the /RSTART USER command allows a user to signon to any IMS in the IMSplex. If the user no longer has significant status in Resource Manager, it is deleted.
Entry ET:
/RSTART LINE 4,5,6,7,8,9,10,11
Response ET:
DFS058I RSTART COMMAND COMPLETED
Response RT:
DFS059I TERMINAL RSTARTED
Explanation: LINES 4,5,6,7,8,9,10, and 11 are started.
Entry ET:
/RSTART LINE 4 5 6 700
Response ET:
DFS058I RSTART COMMAND COMPLETED EXCEPT LINE 700
Entry ET:
/RSTART LINE 4 PTERM 1, 2
Response ET:
DFS058I RSTART COMMAND COMPLETED
Response RT:
DFS059I TERMINAL RSTARTED
Explanation: LINE 4 PTERM 1 and 2 are started.
Entry ET:
/RSTART LINE 4 LOPEN
Response RT:
DFS058I RSTART COMMAND COMPLETED
Response ET:
DFS059I TERMINAL RSTARTED
Explanation: If line 4 is a 3270 remote BTAM line that is idle and stopped, the line is restarted and re-enabled.
Entry ET:
/RSTART LINK ALL
Response ET:
DFS058I RSTART COMMAND COMPLETED
Explanation: All of the logical links are started. Communication across the link will not begin until the partner in the remote system is started with the /RSTART LINK command.
Response ET:
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.
Entry ET:
/RSTART LINK 2
Response ET:
DFS058I RSTART COMMAND COMPLETED
Explanation: Logical link 2 is started.
Response ET:
DFS2168I CONNECTION ESTABLISHED ON LINK 2
Explanation: The two IMS systems are connected.
Entry ET:
/RSTART LINK 4
Response ET:
DFS058I RSTART COMMAND COMPLETED
Response ET at Partner System:
DFS2160I LINK 4 STARTED BY PARTNER AB NODE WEST
Explanation: Link 4 was started at the request of the primary system.
Entry ET:
/RSTART NODE EAST
Response ET:
DFS058I RSTART COMMAND COMPLETED
Explanation: The node named EAST is started.