Chapter 127 TTALK (TandemTalk) Messages

Cause  This message is displayed when a backup process becomes the primary process due to an operator request, processor failure, or internal error.

Effect  The operation of the specified process changes from one processor to another.

Recovery  If the switch occurred as a result of an operator request, this is an informational message only; no corrective action is needed.

If the switch occurred as a result of a processor failure, you may want to reload the processor. Communications applications must reestablish all connections. Distributed systems management (DSM) applications are not affected by a processor switch.

Cause  This message is displayed when a process or a subnet changes state. This happens because an operator requested a START, STOP, or ABORT operation.

Effect  The specified process or subnet changes state.

Recovery  Informational message only; no corrective action is needed.

Cause  This message is displayed when an unrecoverable internal error occurs.

Effect  The primary process stops. If a backup process exists, it takes over.

Recovery  If an internal error occurs, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.

Cause  This message is displayed when a process enters the trap handler. This error represents an unrecoverable internal error.

Effect  The primary process stops. If a backup process exists, it takes over.

Recovery  If a trap message occurs, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.

Cause  This message is displayed when a backup process is started and the initial checkpoint is complete. This can happen at startup time or when a backup process is restarted after a failure.

Effect  The backup process is started and the initial checkpoint is completed.

Recovery  Informational message only; no corrective action is needed.

Cause  This message is displayed when a backup process fails. This can happen because of a processor failure or an internal error.

Effect  The backup process no longer exists.

Recovery  Informational message only; no corrective action is needed. You may want to restart the process pair in order to configure a backup process. If the backup went down due to a processor failure, you should reload the processor.

Cause  This message is displayed when a backup process cannot be created through a NEWPROCESS command. This can happen because of configuration problems, resource shortages, or internal errors.

Effect  The NEWPROCESS command fails.

Recovery  Informational message only; no corrective action is needed.

You may want to restart the process pair in order to configure a backup process.

See Appendix C, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  This message is displayed when a checkpoint cannot be completed to the backup process. This can happen because of resource shortages or internal errors.

Effect  The specified process stops the old backup process and attempts to start a new backup process.

Recovery  Informational message only; no corrective action is needed.

Cause  This message is displayed when an input/output (I/O) to a Tandem local area network (LAN) Access Method (TLAM) or Subsystem Control Point (SCP) port fails. This can happen because of resource shortages.

Effect  There is no effect unless the port repeatedly fails.

Recovery  Informational message only; no corrective action is needed.

See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

If this error persists, contact your Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.

Cause  In general, this message should not be displayed. It can be displayed, however, if a SPI error occurs on either of the two following requests:

INFO SERVICE #L18023, ADD PORT, ALTER PORT, START PORT

or

ABORT PORT SPI (a request that TandemTalk issues to TLAM)

.This message probably is displayed with several other TandemTalk messages, which should also be considered.

The INFO SERVICE, ADD, ALTER, and START PORT requests are issued when the subnet is starting (the result of a START SUBNET command or an autostart). The ABORT PORT request is issued when the subnet is stopping or aborting (the result of an ABORT SUBNET command, a STOP SUBNET command, or an error that forces the subnet to go down).

Effect  The subnet does not start if an SPI error occurs on an INFO SERVICE, ADD, ALTER, or START port request. The subnet enters the aborting state and then goes to the stopped state.

The TLAM ports remain started, but TandemTalk closes them if an SPI error occurs on an ABORT PORT request. This may cause TLAM to issue errors to show that packets are arriving, but nobody is listening.

Recovery  The recommended recovery depends on the error and when it occurs.

If the error occurs on starting the SUBNET, then the retcode value should be examined. See either the TLAM Management Programming Manual or the SCP Management Programming Manual.

If the error occurs when stopping the subnet, no recovery is needed for TandemTalk. You may want to abort the TLAM ports, but this is not required.

Since TandemTalk sends the SPI requests, recovery may not be possible; however some retcode values indicate a configuration error. A retcode of -22 indicates that SCP does not allow the command because of a security problem. In this case, TandemTalk is probably not running as a super-group user (255, n) and cannot perform ADD, ALTER, START, or ABORT commands.

If the retcode shows a value that indicates something other than a configuration error, such as invalid parameters or an invalid SPI buffer, then contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

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.