>>-+-/LOOPTEST-+--LINE--line#--PTERM--pterm#------------------->< '-/LOO------'
Table 75 lists the environments (DB/DC, DBCTL, and DCCTL) from which the command and keywords can be issued.
Command / Keywords | DB/DC | DBCTL | DCCTL |
---|---|---|---|
/LOOPTEST | X | X | |
LINE | X | X | |
PTERM | X | X |
/LOOPTEST is a multisegment command that creates an output write loop that tests for output errors. It causes a single-segment message to be repeatedly transmitted to the terminal being tested.
Multisegment input is combined into a single segment for output transmission. For the terminal in looptest mode to receive the complete message, the cumulative output segment must not exceed the terminal's output size restrictions.
/LOOPTEST requires an EOM indication to denote end-of-message; an EOS indication must be included for all segments that precede the last segment. See Multisegment Command Input for more detail on using EOS and EOM.
/LOOPTEST causes all I/O error detection and notification procedures within IMS to be bypassed. Depending on the types of errors involved, some write loops might result in high processor utilization.
The /END command terminates looptest mode.
If the device specified is not powered on and ready, intervention-required messages will be sent to the master terminal.
The /DISPLAY LINE PTERM command identifies a terminal in looptest mode.
Entry ET:
/LOOPTEST LINE 5 PTERM 1 (EOS) DATA TEST (EOS) 12345 (EOM)
Response ET:
DFS058I LOOPTEST COMMAND COMPLETED
Response RT:
DATA TEST 12345 DATA TEST 12345 and so forth.
Explanation: DATA TEST 12345 is repetitively sent to PTERM 1 on LINE 5.