Pathway/iTS System Management Manual (G06.24+)

Terminal Control Process (TCP) Commands
HP NonStop Pathway/iTS System Management Manual—426748-002
9-8
CONTROL TCP Command
Considerations
•
If the TCP primary process is running in the CPU defined for the TCP backup
process because of a SWITCH command or some other processor change, the
BACKUPCPU attribute causes the PATHMON process to change the PATHMON
configuration file so that it contains the current CPU numbers for both the primary
and backup TCPs.
•
If a TCP was configured with the NONSTOP attribute set to 0, changing the
BACKUPCPU attribute only changes the backup CPU value in the PATHMON
configuration file; no processor change occurs.
•
When you cool start a PATHMON environment after using the CONTROL TCP
command, the TCPs 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 DUMP option to ON for production systems.
The DUMPMEMORY option is not a substitute for setting the DUMP option to ON.
DUMPMEMORY is primarily useful in a controlled troubleshooting situation where
you need to take a snapshot of the TCP’s internal state at a particular time -before
it encounters a fatal error.
Errors
The following table lists the most common errors that can occur during the processing
of the CONTROL TCP command:
This Message… Is Displayed When…
*1070* TCP BACKUP NOT UP You have issued a CONTROL TCP, BACKUPCPU
command or a SWITCH TCP command directly after
issuing a PRIMARY TCP command and the TCP
backup process has not had enough time to be
restarted.
*1093* BACKUP PROCESSOR
DOWN
For a multiprocessor system, you specified a backup
CPU that does not exist or is not operational.
For a single processor system, you included the
BACKUPCPU attribute.
*1095* ILLEGAL CPU NUMBER You specified for the BACKUPCPU attribute the same
CPU in which the primary PATHMON process is
running. The location of the TCP backup process is not
changed in this case.
*3197* TCP tcp-name, TCP
MEMORY DUMP NOT TAKEN -
(10)
An internal error has occurred, but 10 dump files
already exist. The TCP does not create more dump files
in this situation.