G06.24 ReadMe

Recovery: Halt and dump the processor of the TCP6MAN backup process;
then reload the processor to restart the TCP6MAN backup process.
If the problem persists, do not reload the backup; contact your
support representative and provide the following:
-Descriptions of the problem and accompanying symptoms
-Details from this, and any other relevant messages
-Supporting documentation such as Event Management Service (EMS) logs,
trace files, and a processor dump, if applicable.
If your local operating procedures require contacting the Global
Customer Support Center, supply your system number and the numbers
and versions of all related products.
202 (Noncritical Event)
TCP6MAN Switched from CPU from_cpu to CPU to_cpu.
Cause: An operator requested a processor switch through SCF.
Effect: The TCP6MAN is running in a different processor.
Recovery: Informational message only; no corrective action is needed.
203 (Noncritical Event)
TCP6MAN Error notification. Function notif-func,
Error notif-err. Info1 notif-info1, Info2 notif-info2,
Line line-num, Module mod-name [ , Name notif=name ].
Cause: The cause depends on the notif-func and notif-err.
Effect: TCP6MAN continues to run.
Recovery: Contact your service provider and provide all relevant
information.
204 (Critical Event)
TCP6MAN Process Abended. Error = #err-code, Cause: #reason, Line:
line-num, Module: module-name.
Cause: The TCP6MAN process detected an error during process
initialization and cannot proceed.
Effect: TCP6MAN terminates abnormally.
Recovery: Restart TCP6MAN. If the process abends again, contact your
service provider and provide the following:
-Descriptions of the problem and accompanying symptoms
-Details from the message or messages generated
-Supporting documentation such as Event Management Service (EMS) logs,
trace files, and a processor dump, if applicable.
If your local operating procedures require contacting the Compaq
Global Customer Support Center, supply your system number and the
numbers and versions of all related products.
205 (Noncritical Event)
Master TCP6MON Process tcp6mon-name started on CPU cpu-num.
Cause: No master TCP6MON exists.
Page
17
of
21