Chapter 120 TMDS (Tandem Maintenance and Diagnostic System) Messages

The messages in this chapter are sent by the Tandem Maintenance and Diagnostic System (TMDS). The subsystem ID displayed by these messages includes TMDS as the subsystem name.




	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.

220

$ZLOG started OK

Cause TMDSAUTO has started $ZLOG successfully, without using the Syshealth Persistence Monitor. TMDSAUTO starts $ZLOG because $ZLOG is a NonStop process pair, and should be started even if Syshealth is not present on the system.

Effect TMDS event logging is performed properly on the system, unless $ZLOG encounters errors itself.

Recovery Informational message only; no corrective action is needed.

221

$ZLOG could not be started due to { Newprocess error newprocess-error, with program file filename } { File error file-error when performing proc-failing } { TMDSAUTO internal error during proc-failing } { An internal error in $ZLOG or failure of $ZLOG’s CPU before it created a backup } No TMDS event logging does be performed on the system.

`newprocess-error`	identifies the error associated with a NEWPROCESS failure.
`filename`	specifies the program file used by the NEWPROCESS call.
`file-error`	identifies a file-system error.
`proc-failing`	is the procedure associated with the failure.

Cause TMDSAUTO has attempted to start $ZLOG directly, without using the Syshealth Persistence Monitor. ($ZLOG is a NonStop process pair and should be started even if Syshealth is not present on the system.) One of the startup functions has failed.

The possible startup function failures are listed below. Each of these numbered causes corresponds to the recovery action with the same number under “Recovery.”

TMDSAUTO was unable to determine the current SYSnn for starting $ZLOG.
TMDSAUTO was unable to allocate sufficient memory for starting $ZLOG.
The TMDS alternate collector reported an error while trying to access its log files.
TMDSAUTO encountered an error while attempting the NEWPROCESS procedure with $ZLOG.
TMDSAUTO encountered an error while opening $ZLOG or sending a startup message to $ZLOG.
TMDSAUTO encountered an error while sending a Subsystem Programmatic Interface (SPI) command to $ZLOG.

Effect $ZLOG is the TMDS alternate collector. It logs TMDS events on a system to the TMDS event log. If $ZLOG has not been started, no TMDS events on the system are logged to the TMDS event log.

Recovery Each of the following recovery actions corresponds to the cause with the same number under “Cause” above.

Try again. If this problem persists, 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.
Check the disk space on the $SYSTEM volume.
Examine this message for the cause of the failure. See the Event Management Services (EMS) Manual for the proper recovery procedure for the alternate collector.
Look at the NEWPROCESS error code in the message. See Appendix C, in this manual, for information about the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.
Look at the file-system error code in the message. 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.
Contact the Global Mission Critical Solution Center (GMCSC).

In each of the cases above, you can start $ZLOG manually by typing the following command at the Tandem Advanced Command Language (TACL) prompt:

1>RUN $SYSTEM.SYSnn.EMSACOLL / NAME $ZLOG, CPU nn / &
1>&BACKUP nn, LOGSUBVOL $SYSTEM.ZSYH, SECURITY NNOO, TMDS, &
1>&SUPPRESS (N 25, T1 100, T2 120, T3 300, S 6)




	NOTE: The processor numbers you specify in the CPU and backup parameters must be different from each other.

225

EMS Routing Distributor process-name started OK.

Cause EMS successfully started the routing distributor process.

Effect The specified routing distributor process is started.

Recovery Informational message only; no corrective action is needed.

226

EMS Routing Distributor startup failed. Unable to send message to process-name.#SPI. AWAITIO failed with FE n

Cause EMS was unable to send a message to the routing distributor process.

Effect AWAITIO failed with an FE error.

Recovery Copy the filter files, the EMSDIST file, and the fault analyzers into the SYSnn if they do not already reside there.