Terminal Control Process (TCP) Commands
START TCP
Use the START TCP command to initiate operation of a TCP. This command cannot
initiate an external TCP (a TCP that is controlled by another PATHMON process and is
therefore outside this PATHMON environment). If the primary processor defined for a
TCP is unavailable, the PATHMON process starts the TCP in the backup processor
defined for that TCP.
Continuation
To start all TCPs, initialize the ZTCP field in ZPWY-DDL-SEL-TCP to
ZPWY-VAL-ALLTCP. Reissue the command repeatedly, using the context token
returned by the PATHMON process, until no data is returned in the reply buffer.
When you specify continuation, responses are returned only for TCPs in the stopped
state. For more information, see
Command Syntax
For tokens that may be present in the command and response buffers but are not
listed, see
Unlisted Tokens
Section 4 through Section 6.
Command
ZPWY-CMD-START
Object Type
ZPWY-OBJ-TCP
Tokens in Command Buffer
ZSPI-TKN-CONTEXT
ZPWY-MAP-SEL-TCP
ZPWY-MAP-QUAL-TCP
Tokens in Response Buffer
ZSPI-TKN-CONTEXT
ZPWY-MAP-SEL-TCP
ZSPI-TKN-RETCODE
NonStop Pathway/iTS Management Programming Manual—426749-002
Specifying Continuation
on page 3-36. For descriptions of tokens and fields, see
token-type ZSPI-TYP-BYTESTRING.
token-type ZPWY-DDL-SEL-TCP.
token-type ZPWY-DDL-QUAL-TCP.
token-type ZSPI-TYP-BYTESTRING.
token-type ZPWY-DDL-SEL-TCP.
token-type ZSPI-TYP-INT.
7- 15
START TCP
on page 3-21.
!r
Need help?
Do you have a question about the NonStop Pathway/iTS and is the answer not in the manual?