Operator Messages Manual
Chapter 112 TAG (Transport Agent) Messages
The messages in this chapter are sent on behalf of the Transport
Agent. The Transport Agent is the interface between Open System Services
(OSS) socket applications and Tandem’s NonStop Transmission
Control Protocol/Internet Protocol (TCP/IP). The Transport Agent can
generate events during startup, initialization, and run time. Additionally,
it generates events when certain QIO errors occur. The subsystem ID displayed for these messages is ZTAG. The following
example shows the format for Transport Agent operator messages as
they are sent to printers, log files, or terminals: 96-05-13 09:01:01 \MANCHU.$ZTA00 *TANDEM.ZTAG.D40
000001 TAGENT process abended, error: -1,
TA PRIV_MAIN: TA and FS version incompatible,
Transport agent version: 5,OSS File System version: 3, stage #: 1
|
| | | |  | NOTE: Negative-numbered messages are common to most subsystems. If
you receive a negative-numbered message that is not described in this
chapter, see Chapter 15. | | | | |
| 000001 000001 TAGENT process abended, error: err-num, err-text, Transport
agent version: ta-version, OSS File System
version: fs-version, stage #: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA PRIV_MAIN: TA and FS version incompatible |
| | ta-version | is the version of the Transport Agent. | | fs-version | the version of the Open System Services (OSS) file
system. | | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The versions of the Transport Agent and the OSS file system
were incompatible. Effect The Transport Agent process stops. No sockets can be created. Recovery Use VPROC to obtain the versions of the T8306 and T8397 products
and consult the softdocs to ensure that product dependencies are met. |
| 000002 000002 TAGENT process error: err-num, err-text, TAGENT process continues running,
waiting indefinitely for OSS to start, stage #: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA PRIV_MAIN: OSS not running |
| | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The Open System Services (OSS) environment has not started. Effect This message appears periodically until the OSS environment
has been started. Recovery Determine why the OSS file manager process has not completed
initialization of the OSS environment. |
| 000003 000003 TAGENT process error: err-num, err-text, Using default value, TAGENT
process continues running, stage #: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Server_Init: Unable to set RCVXLBLIMIT | | TA_Server_Init: Unable to set SENDXLBLIMIT |
| | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The Transport Agent has issued a warning message. Effect This event has no effect on socket communications. Recovery Informational only; no corrective action is needed. |
| 000004 000004 TAGENT process abended, error: err-num, err-text, recovery
action: Use valid process name $ZTAxx,
stage #: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Globals_Init: Process started with invalid process name |
| | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The Transport Agent has been started with an invalid process
name. This can occur when the Transport Agent is started manually
by using the RUN command from the TACL prompt or by starting it from
a command (OBEY) file. Effect The Transport Agent process stops. No sockets can be created
using that Transport Agent. Recovery The Transport Agent process starts automatically. Do not attempt
to start it from the TACL prompt or from a command file. |
| 000005 000005 TAGENT process error: err-num, err-text, TAGENT process continues
running, waiting indefinitely for QIO segment to be initialized, stage
#: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Globals_Init: QIO attach segment failed |
| | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The QIO process was not started, or its version was incompatible
with that of the Transport Agent. Effect This message appears periodically until the QIO segment is initialized.
No sockets can be created. Recovery Use the Subsystem Control Facility (SCF) to determine if QIO
is running. (The QIO Monitor object file is QIOMON, and the process
name is $ZMxx, where xx is the processor in which the monitor is to run). If QIO is running,
check the Transport Agent and QIO software versions for compatibility
by obtaining version information and consulting the appropriate softdocs. |
| 000006 000006 TAGENT process abended, QIO error: err-num, err-text, stage
#: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Globals_Init: Unable to create QIO module ID for TA | | TA_Globals_Init: Unable to create QIO module ID for FS | | TA_Globals_Init: Unable to get pool from QIO for TA QCB | | TA_Globals_Init: Unable to create TA queue | | TA_Globals_Init: Unable to get Pool for crtlbuf | | TA_Globals_Init: Unable to get Pool for databuf | | TA_Globals_Init: Unable to get Pool for QidInfo struct | | TA_Globals_Init: Unable to get MD for aggbuf |
| | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The versions of the Transport Agent and QIO software were incompatible. Effect The Transport Agent process stops. No sockets can be created. Recovery Check the Transport Agent and QIO software versions for compatibility
by obtaining version information and consulting the appropriate softdocs. |
| 000007 000007 TAGENT process abended, PXS error: err-num,
err-text, stage #: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Globals_Init: Unable to get memory from PXS for SRE Template |
| | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause Not enough memory was available in the Portability Extended
Segment (PXS). Effect The Transport Agent process stops. No sockets can be created. Recovery Determine the reason for the lack of available PXS memory and
correct the problem, or contact the Global NonStop Solution Center
(GNSC) and provide all relevant information as follows: 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 Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 000008 000008 TAGENT process abended, error: err-num, err-text, stage
#: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Globals_Init: Socket table initialization failed |
| | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause Not enough memory was available in the Portability Extended
Segment (PXS). Effect The Transport Agent process stops. No sockets can be created. Recovery Determine the reason for the lack of available PXS memory and
correct the problem, or contact your HP support representative and
provide all relevant information as follows: 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 Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 000009 000009 TAGENT process abended, error: err-num, err-text, stage
#: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Globals_Init: Request table initialization failed |
| | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause Not enough memory was available in the Portability Extended
Segment (PXS). Effect The Transport Agent process stops. No sockets can be created. Recovery Determine the reason for the lack of available PXS memory and
correct the problem, or contact the Global NonStop Solution Center
(GNSC) and provide all relevant information as follows: 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
Recovery If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 000010 000010 TAGENT process error: err-num, err-text, QIO Pool Put will be retried,
TAGENT process continues running, stage #: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TASM_Pool_Put: Unable to return buffer to QIO Pool |
| | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause An error was encountered while trying to return memory to QIO.
There may be a memory leak in the system. Effect The operation will be retried. Recovery Informational only; no corrective action is needed. |
| 000011 000011 TAGENT process in processor current-cpu error: err-num, err-text, A bad aggregate request from
Transport Provider tp-name running in processor tp-cpu-number, TAGENT process continues running, stage
#: stage-num | | current-cpu | is the current processor in which the Transport Agent
is running. | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Do_LdoneTaTpAggregate: Aggregate reply from TP corrupted | | TA_Do_TpTaReq: Error while processing the aggregate request
from Transport Provider |
| | tp-name | is the transport provider process name. | | tp-cpu-number | is the processor number where the transport provider
process is running. | | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The Transport Agent has detected an invalid message from a transport
provider. Effect Sockets using that transport provider process can no longer
be used. This is an internally detected consistency error. Recovery Sockets that were using this transport provider process are
unusable and can only be closed. Contact your HP support representative and provide all relevant
information as follows: 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. A processor dump of the processor where the transport
provider process was running.
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 000012 000012 TAGENT process error: err-num, err-text, Transport Provider tp-name,
TAGENT process continues running, stage #: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the specific error associated with the event, which
can be: | TAMSG_GetSoPtrFromFsopenid: Invalid fsopenid from TP |
| | tp-name | is the transport provider’s process name, for
example, $ZTC0. | | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The transport provider process has sent a message that refers
to a socket that does not exist. The socket it refers to might have
been closed. Effect The error has no effect on socket communications. Recovery Informational only; no corrective action is needed. |
| 000013 000013 TAGENT process error: err-num, err-text, Transport Provider tp-name, TAGENT process continues running, stage #: stage-num | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TAMSG_FsTpRecvReturnDataRsp_Handle: unexpected error in TP's
message |
| | tp-name | is the transport provider process name. | | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The transport provider process has replied to a message with
an unexpected error. Effect The error has no effect on socket communications. Recovery Informational only; no corrective action is needed. |
| 000014 000014 TAGENT process in Processor current-cpu error: err-num, err-text, all sock-family sockets corresponding to Transport Provider tp-name running in Processor tp-cpu-number are
reset, TAGENT process continues running, stage #: stage-num | | current-cpu | is the current processor in which the Transport Agent
is running. | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_TpDeath_Cleanup: Resetting sockets |
| | sock-family | is the socket family of the sockets that are reset. | | tp-name | is the name of the transport provider process. | | tp-cpu-number | is the processor number where the transport provider
process is running. | | stage-num | identifies the location within the module named in err_text at which the error occurred |
Cause There was no socket activity in the transport provider process
or a consistency error was internally detected. Effect Sockets using that transport provider process can no longer
be used. Recovery Sockets that were using this transport provider process are
unusable and can only be closed. Check for events logged before this
event was logged to get additional information. |
| 000015 000015 TAGENT process in Processor current-cpu error: err-num, err-text, An invalid Request id request-id in the message, { [ Transport Provider tp-name running in Processor tp-cpu-number,] | [Transport Provider not running, ] } TAGENT process continues
running, stage #: stage-num | | current-cpu | is the current processor in which the Transport Agent
is running. | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Do_OPTXFER_Send_Rsp: Invalid Request id in reply from Tranport
Provider | | TA_Do_FsTaReply: Invalid Request id in the request from the
Socket Library | | TA_Do_LdoneTaTpOpen: Invalid Request id in the reply from
Transport Provider | | TASM_Request_Reply_FC: Invalid Request id in the request from
the Socket Library | | TAMSG_Do_FsTpReply: Invalid request id in the reply from the
Transport Provider |
| | request-id | is the request id of the request for which Transport
Agent received a reply. | | tp-name | is the name of the transport provider process. | | tp-cpu-number | is the processor number where the transport provider
process is running. | | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The Transport Agent has detected an invalid message from the
transport provider process or the socket library. Effect This is an internally detected consistency error. If the invalid
message is from: The socket library, an OSS application might stop
functioning The transport provider process, sockets using that
transport provider process can no longer be used
Recovery Sockets that were using this transport provider process are
unusable and can only be closed. If an application stops functioning, restart the application
if possible. If you are forced to stop the application, the processor
where the application was running should be reloaded. Contact your HP support representative and provide all relevant
information as follows: 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. A processor dump of the processor where the transport
provider process was running.
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 000016 000016 TAGENT process in Processor current-cpu error: err‑num, err-text, No socket activity for more
than six hours corresponding to the Transport Provider tp-name running in Processor tp-cpu-number TAGENT process continues running, stage #: stage-num | | current-cpu | is the current processor in which the Transport Agent
is running. | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Get_Msg: No socket activity in TP queue |
| | tp-name | is the name of the transport provider process. | | tp-cpu-number | is the processor number where the transport provider
process is running. | | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause There was no socket activity in that transport provider process
for more than six hours. Effect None Recovery Informational only; no corrective action is needed. |
| 000017 000017 TAGENT process in Processor current-cpu error: err-num, err-text, Transport Provider tp-name in Processor tp-cpu-number, restarted or switched primary-backup, TAGENT process continues
running, stage #: stage-num | | current-cpu | is the current processor in which the Transport Agent
is running. | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Get_Msg: TP Phandle stored in TA does not match with the
current TP Phandle in DCT | | TA_Do_FsTaQcheck: TP Phandle stored in TA does not match with
the current TP Phandle |
| | tp-name | is the name of the transport provider process. | | tp-cpu-number | is the processor number where the transport provider
process is running. | | stage-num | identifies the location within the module named in err_text at which the error occurred |
Cause The transport provider process restarted or switched primary-backup. Effect Sockets using that transport provider can no longer be used.
This is an internally detected consistency error. Recovery Sockets that were using this transport provider process are
unusable and can only be closed. |
| 000018 000018 TAGENT process in Processor current-cpu error: err-num, err-text, Processor tp-cpu-number went down where Transport Provider tp-name was running, TAGENT process continues running, stage #: stage-num | | current-cpu | is the current processor in which the Transport Agent
is running. | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_GetAndDo_SystemStatusReq: Processor Failure |
| | tp-cpu-number | is the processor number where the transport provider
process is running. | | tp-name | is the name of the transport provider process. | | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause Processor failure occurred where the transport provider primary
process was running. Effect Sockets using that transport provider process can no longer
be used. Recovery Sockets that were using this transport provider process are
unusable and can only be closed. |
| 000019 000019 TAGENT process in Processor current-cpu error: err-num, err-text, a failure indication sent
by parallel TCP process tp-name running
in Processor tp-cpu-number, TAGENT process
continues running, stage #: stage-num | | current-cpu | is the current processor in which the Transport Agent
is running. | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Do_FsTaFailInd: TCPSAM process terminated |
| | tp-name | is the name of the transport provider process. | | tp-cpu-number | is the processor number where the transport provider
process is running. | | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The TCPSAM process terminated. Effect Sockets using that transport provider process can no longer
be used. Recovery Sockets that were using this transport provider process are
unusable and can only be closed. |
| 000020 000020 TAGENT process in Processor current-cpu error: err-num, err-text, Unexpected reply from the
Transport Provider tp-name, running in
Processor tp-name, TAGENT process continues
running, stage #: stage-num | | current-cpu | is the current processor in which the Transport Agent
is running. | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Do_LdoneTaTpSimple: Unexpected simple Reply from the Transport
Provider |
| | tp-name | is the name of the transport provider process. | | tp-cpu-number | is the processor number where the transport provider
process is running. | | stage-num | identifies the location within the module named in err_text at which the error occurred |
Cause The Transport Agent has detected an invalid message from the
transport provider process. Effect Sockets using that transport provider process can no longer
be used. This is an internally detected consistency error. Recovery Sockets that were using this transport provider process are
unusable and can only be closed. Contact your HP support representative and provide all relevant
information as follows: 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. A processor dump of the processor where the transport
provider process was running.
If your local operating procedures require contacting the Global
Mission Critical Solution Center (GMCSC), supply your system number
and the numbers and versions of all related products as well. |
| 000021 000021 TAGENT process in Processor current-cpu error: err-num, err-text, Transport Agent is shutting
down, Deleting TP Queue of the Transport Provider tp-name, running in processor tp-cpu-number,
stage #: stage-num | | current-cpu | is the current processor in which the Transport Agent
is running. | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TASTOP_StopQs: TA Shutdown |
| | tp-name | is the name of the transport provider process. | | tp-cpu-number | is the processor number where the transport provider
process is running. | | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause The Transport Agent has been shut down through the Subsystem
Control Facility (SCF). Effect Sockets cannot be created in the affected processor until the
Transport Agent is started again. Recovery Informational only; no corrective action is needed. |
| 000022 000022 TAGENT process in Processor current-cpu error: err-num, err-text, QIO MD Get Error, TAGENT process
continues running, stage #: stage-num | | current-cpu | is the current processor in which the Transport Agent
is running. | | err-num | is the error number that the Transport Agent received. | | err-text | is the error text associated with the event, which
can be: | TA_Allocate_MsgSysReqBufs: Unable to get MD from QIO | | TA_Get_TpTaReq: Unable to get MD from QIO | | TA_Get_TpTaReq: Unable to get MD from QIO, will be retried
indefinitely | | TA_Get_TpTaReq: Error recovery message, able to get MD from
QIO after retry | | TA_Get_TpTaReq: Error recovery message, able to get MD from
QIO after retry or got qcb's last MD | | TA_Allocate_MsgSysReplyBuf: Unable to get MD from QIO | | TA_Get_Msg: Unable to get MD from QIO | | TAMSG_ConfMsg_Send: Unable to get MD from QIO, will be retried
indefinitely | | TAMSG_ConfMsg_Send: Error recovery message, able to get MD
from QIO after retry | | TAMSG_FsTpRecvDataInd_Handle: Unable to get MD from QIO | | TAMSG_FsTpSendContInd_Handle: Unable to get MD from QIO | | TAMSG_FsTpRecvContInd_Handle: Unable to get MD from QIO | | TASM_TpQcb_Allocate: Unable to get MD from QIO | | TA_RDF_GC_Processing: Unable to get MD from QIO |
| | stage-num | identifies the location within the module named in err_text at which the error occurred. |
Cause QIO was unable to allocate a message descriptor (MD). Effect Either the Transport Agent experiences a delay in processing
the request, or the error ENOMEM or ENOBUF is returned to the application. Recovery Informational only; no corrective action is needed. |
|