TERM Commands
RESUME TCPTERM
Considerations
If a TERM object is suspended by the TCP because of a fatal TERM error, you
might not be able to restart the TERM object using the RESUME TCPTERM
command. Instead, you might have to issue the ABORT TCPTERM command and
then restart the TERM object using the START TCPTERM command.
After a RESUME TCPTERM command, the SCREEN COBOL program starts
executing at the point where the TERM object was suspended; screen recovery is
performed before the program resumes normal execution.
If a TERM object was in TMF transaction mode (that is, the TMF subsystem
backed out the transaction) when it was suspended and the TERM object is in a
restartable state, the RESUME TCPTERM command initiates TERM activity by
restarting the logical transaction at the BEGIN-TRANSACTION verb. When the
logical transaction is restarted, the Pathway subsystem increments the RESTART-
COUNTER special register by 1.
The RESUME TCPTERM command is most useful when a TERM object is in the
SUSPENDED state because of an operator-initiated SUSPEND command.
NonStop Pathway/iTS Management Programming Manual—426749-002
8- 18
Need help?
Do you have a question about the NonStop Pathway/iTS and is the answer not in the manual?