Terminal Control Process (TCP) Commands
NonStop Pathway/iTS Management Programming Manual—426749-002
7-7
CONTROL TCP
•
If the primary TCP process is running in the processor defined for the backup TCP
process because of a SWITCH command or some other processor change,
assigning a value to the ZBACKUPCPU field causes the PATHMON process to
change the PATHMON configuration file so that it contains the current processor
numbers for both the primary and backup TCP processes.
•
If the processor you specify for the ZBACKUPCPU field is the processor on which
the TCP primary process is running, the PATHMON process returns the following
error:
*1095* ILLEGAL CPU NUMBER
and does not change the location of the backup process.
If the processor you specify for ZBACKUPCPU is a processor that does not exist
or that is not operational, the PATHMON process returns the following error:
*1093* BACKUP PROCESSOR DOWN
•
If the processor you specify for ZBACKUPCPU is the processor on which the
backup process currently resides, the TCP still stops its backup process and starts
a new backup process in the same processor.
•
If the TCP was configured with the ZNONSTOP field set to ZPWY-VAL-
NONSTOP0, ZBACKUPCPU only changes the backup processor value in the
PATHMON configuration file; no processor change occurs.
•
When you cool start Pathway after using the CONTROL TCP command, the TCP
processes start according to the changes recorded in the PATHMON configuration
file.
•
If you request the help of your service provider in analyzing a problem, the
representative will likely require a dump file. It is therefore recommended that you
always set the ZDUMP option to ON for production systems.
•
If you specify values for the ZDUMPINFO fields, those values override the values
defined for ZDUMPINFO with the ADD TCP command.
To Next Page
Loading...
Need help?
General