Chapter 30 EMS (Event Management Service) Messages

ldev	identifies the logical device. NOTE: If device ldev is a communications controller, see also Expand message 3. If device ldev is a Multilan controller (D-series only), see also TLAM message 3. If device ldev is an X.25 controller, see also X25AM message 3.
CU %ccu	indicates the input/output (I/O) address associated with this message.
CU %...	is displayed instead of CU %ccu when the device supports extended I/O addressing or when the system is a multiple-channel system; that is, it can support more than one channel per processor. When the extended format of the message is used, (cpu,chan,%ctlr,%unit) is displayed at the end of the message.
#errnum	identifies a file-system error, except for the values listed in Table 30-1.

Cause   These errors might occur during a transfer between ldev 3 and the Remote Maintenance Interface (RMI):

Effect  The operation is retried; then the other path is tried. If errnum is in the range 210 through 229, the operation can switch to the other processor.

If a controller is generating a continuous I/O power-on interrupt, the application trying to communicate with the device receives an error code (usually 231, I/O power on) in response to its I/O request. For D-series RVUs, a Tandem Maintenance and Diagnostic System (TMDS) message is generated.

If ldev is $OSP, the operation is simply retried.

Recovery  If ldev is $OSP, this is an informational message only; no corrective action is needed. See Appendix B, for a definition of the error errnum. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Take the appropriate action, or contact your service provider and provide all relevant information:

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.

ldev	identifies the logical device. NOTE: If device ldev is a communications controller, see also Expand message 3. If device ldev is an X.25 controller, see also X25AM message 3.
CU %ccu	For X25AM, indicates the input/output (I/O) address associated with this message.
CU %...	is displayed instead of CU %ccu when the device supports extended I/O addressing or when the system is a multiple-channel system; that is, it can support more than one channel per processor. When the extended format of the message is used, (cpu,chan,%ctlr,%unit) is displayed at the end of the message.
%dev-status	indicates device status information, as described in Appendix A.

Cause  An error has occurred on the indicated device, and the I/O retry did not succeed.

For 6100/6105, 3650/3605, or 6203/6204/3604 controllers, this error is usually caused by a timeout of a CIU-to-LIU bus (CLB) transmission or a hardware error (controller or channel) problem.

The parameter values and the effect and recovery information for each hardware type are:

Data Communications Lines (other than SNAXLink)

Effect  A retry is made. If the problem persists, another path or processor is tried. If a path or processor is not available, the device goes down.

Recovery  This error is usually a hardware problem. Check the rank and priority of the communications interface unit (CIU) controllers and correct any problems found. Check the hardware not made by Compaq for problems. If you cannot solve the problem, contact your service provider and provide all relevant information:

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.

LDEV 3

Effect  The operation is retried.

Recovery  Informational message only; no corrective action is needed.

Tape Controllers

Effect  The operation is not finished.

Recovery  Corrective action might be needed; for example, the tape drive could be dirty, or the tape could be defective.

5512 Serial Matrix Printer

Effect  The system waits until the problem is corrected.

Recovery  Check the printer.

5515, 5516, and 5518 Line Matrix Printers

Effect  The system waits until the problem is corrected.

Recovery  Check the printer.

5520 Serial Matrix Printer

Effect  The system waits until the problem is corrected.

Recovery  Check the printer.

5530 Letter-Quality Printer

For controller error (%param2=139), %dev-status contains the interrupt status from the asynchronous controller and %param1 is always zero.

Effect  The system waits until the problem is corrected.

Recovery  Check the printer.

5530 Letter-Quality Printer 5573 Nonimpact Page Printer

Effect  The system waits until the problem is corrected.

Recovery  Check the printer.

SNAXLink Controller

Effect  The system waits until the problem is corrected.

Recovery  Contact your service provider and provide all relevant information:

Cause  An error occurred on device ldev, and the I/O operation is being retried.

The parameter values and the effect and recovery information for each hardware type are described here.

$OSP

Unexpected messages were received from the Operations and Service Processor (OSP). As long as the $OSP‑to‑$OSP protocol can recover from these errors, these messages are not significant, except as an indication of the quality of the communication between the OSP and $OSP. The message reads:

RETRY %overrun %bad-lrc %condition %000000

Effect  A retry is made. If the problem persists, another path or processor is tried. If a path or processor is not available, the device goes down.

Recovery  See the description of EMS message 97. Take recovery action for the error indicated by the parameters, or contact your service provider and provide all relevant information:

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.

5515, 5516, and 5518 Line Matrix Printers

A data parity error was retried.

Effect  The system waits until the problem is corrected.

Recovery  Check the printer.

5520 Serial Matrix Printer

A data parity error or a vertical format unit (VFU) load error was retried.

Effect  The system waits until the problem is corrected.

Recovery  Check the printer.

5530 Letter-Quality Printer

%dev-status	The primary status returned from the printer. For descriptions of primary status, see Appendix A. NOTE: For controller error (%param2=139), %dev-status contains the interrupt status from the asynchronous controller.
%param1	The auxiliary status if the primary status indicates that one is available. For descriptions of the auxiliary status, see Appendix A. NOTE: For controller error (%param2=139), %param1 is always zero.
%param2	The file-system error number. For file-system error 139 (CONTROLLER ERROR), this RETRY EMS message is issued each time a parity or character-overrun error is detected and retried on the asynchronous controller.

Effect  The operation is retried.

Recovery  Informational message only; no corrective action is needed. If the retry is not successful, another message (retry or error) is displayed.

5573 Nonimpact Page Printer

A data parity error was retried.

Effect  The system waits until the problem is corrected.

Recovery  Check the printer.

SNAXLink Controller

Effect  The operation is retried.

Recovery  Informational message only; no corrective action is needed.

ldev	identifies the logical device. NOTE: If device ldev is a communications controller, see also Expand message 3. If device ldev is a Multilan controlle (D-series only), see also TLAM message 3. If device ldev is an X.25 controller, see also X25AM message 3.
CU %ccu	indicates the input/output (I/O) address associated with this message.
CU %...	is displayed instead of CU %ccu when the device supports extended I/O addressing or when the system is a multiple-channel system; that is, it can support more than one channel per processor. When the extended format of the message is used, (cpu,chan,%ctlr,%unit) is displayed at the end of the message.

Cause  The operator successfully returned the device or device path to the system.

For D-series I/O processes, the operator issued a Peripheral Utility Program (PUP) UP or a Communications Management Interface (CMI) START command. For G-series I/O processes, the operator issued a Subsystem Control Facility (SCF) START DISK command.

Effect  The operation is completed.

Recovery  Informational message only; no corrective action is needed.

ldev	identifies the logical device. NOTE: If device ldev is a communications controller, see also Expand message 3. If device ldev is a Multilan controller (D-series only), see also TLAM message 3. If device ldev is an X.25 controller, see also X25AM message 3.
CU %ccu	indicates the input/output (I/O) address associated with this message.
CU %...	is displayed instead of CU %ccu when the device supports extended I/O addressing or when the system is a multiple-channel system; that is, it can support more than one channel per processor. When the extended format of the message is used, (cpu,chan,%ctlr,%unit) is displayed at the end of the message.

Cause  The operator has removed the device or device path from the system, or the system has detected a hardware failure.

For D-series I/O processes, the operator has issued one of these commands:

For G-series I/O processes, the operator has issued a Subsystem Control Facility (SCF) ABORT DISK or SCF STOP DISK command.

Or the process has brought itself down because it found an error.

Effect  The device goes down.

Recovery  If an operator command did not cause this message, contact your service provider and provide all relevant information:

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.

For all subsystems except the D-Series Communications Subsystem Manager (CSM) For the CSM (D-series only)

For the CSM (D-series only)

Cause  A data communications line error count either exceeded its designated threshold value or was closed.

Effect  The operation finishes.

Recovery  Informational message only; no corrective action is needed.

For all subsystems except the D-series Communications Subsystem Manager (CSM)

For the CSM

Cause  A data communications line error count either exceeded its designated threshold value or was closed.

Effect  The operation finishes.

Recovery  Informational message only; no corrective action is needed.

Cause  The sender processor detected what appeared to be a continually interrupting controller, and the system issued an execute input/output (I/O) “kill” command to the controller.

Effect  The sender processor cannot use this controller until the associated processor module is reloaded.

Recovery  Try reloading the processor module or resetting the controller by turning its power off and on. If these actions fail, contact your service provider and provide all relevant information:

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  The device has issued more than 14 I/O bus-error and retry messages within an 11‑minute logging period. Occasionally, a faulty device generates a large number of errors of these types:

Effect  The operating system suspends logging of the recurring messages until the next logging period begins.

Recovery  Contact your service provider and provide all relevant information:

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.

#ldev	identifies the logical device. NOTE: #ldev is 0 if you are logging to $0 on system #sysnum. If #ldev is not 0, it identifies the terminal on system #sysnum where messages are logged.
#sysnum	identifies the affected system.

Cause  The Peripheral Utility Program (PUP) CONSOLE command has enabled logging to disk file $SYSTEM.SYSTEM.OPRLOG or has changed logging to a remote terminal.

Effect  The operation is completed.

Recovery  Informational message only; no corrective action is needed.

#ldev	identifies the logical device. NOTE: #ldev is 0 if you are logging to $0 on system #sysnum. If #ldev is not 0, it identifies the terminal on system #sysnum where messages are logged.
#sysnum	identifies the affected system.

Cause  The Peripheral Utility Program (PUP) CONSOLE command has disabled logging to disk file $SYSTEM.SYSTEM.OPRLOG or has changed logging to a remote terminal.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

#ldev

identifies the logical device. NOTE: #ldev is 0 if you are logging to $0. If #ldev is not 0, it identifies the terminal where messages are logged.

Cause  The Peripheral Utility Program (PUP) CONSOLE command has enabled logging to disk file $SYSTEM.SYSTEM.OPRLOG or has changed logging to a local terminal.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

#ldev

identifies the logical device. NOTE: #ldev is 0 if you are logging to $0. If #ldev is not 0, it identifies the terminal where messages are logged.

Cause  The Peripheral Utility Program (PUP) CONSOLE command has disabled logging to disk file $SYSTEM.SYSTEM.OPRLOG or has changed logging to a local terminal.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  Either a file-system input/output (I/O) error occurred while the operator process was logging to the console; or during cold load, $0 encountered an error in finding a console for logging. In this second case, the logical device number ldev of the console in error is also displayed.

Effect  The operator process cannot log to the console. When an error occurs in writing to the console, the console is closed and its logging state is flagged as OFF. No further messages are written to the console.

In the cold-load case, by searching through the device table, $0 may still find another console device for logging.

Recovery  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 you are unable to resolve the problem, contact your service provider and provide all relevant information:

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.

For D-series RVUs, once you have corrected the error, use the Peripheral Utility Program (PUP) CONSOLE command to reenable logging to the console.

Cause  A file-system I/O error occurred while the operator process was logging to the application process named $AOPR.

Effect  The operator process cannot log to $AOPR.

Recovery  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 you are unable to resolve the problem, contact your service provider and provide all relevant information:

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  A file-system input/output (I/O) error occurred while the operator process was logging to the disk file $SYSTEM.SYSTEM.OPRLOG.

Effect  The disk log file is closed and its logging state is flagged as OFF. No further messages are written to the log file.

Recovery  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 you are unable to resolve the problem, contact your service provider and provide all relevant information:

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.

For D-series RVUs, once you have corrected the error, reenable logging to OPRLOG by issuing a Peripheral Utility Program (PUP) CONSOLE command, then bring the device up and cold load the system. Or, if OPRLOG is full, rename it, and then enter the PUP CONSOLE command with the SWITCH option.

ldev	identifies the logical device. NOTE: If device ldev is a communications controller, see also Expand message 3. If device ldev is an X.25 controller, see also X25AM message 3.
number	indicates the quality of the line, in a range from 100 (best quality) through 0 (lowest quality). NOTE: If number is less than 95, then a noisy line is causing many retransmissions of frames on the line.

Cause  A network line handler has reported a change in the line quality. This report occurs whenever a change greater than or equal to 5 percent occurs.

Effect  The system reports the problem and continues processing.

Recovery  If number is less than 95, examine the transmission quality of the communications lines and correct the cause of the transmission errors.

Cause  The buffer in which the operator messages are stored before they are logged is full.

Effect  The system continues to lose messages.

Recovery  Determine why messages are lost and what the source of the messages is (for example, a looping process or a hardware problem), then correct the problem.

If you cannot correct the problem, contact your service provider and provide all relevant information:

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.

%status1	is the read interrupt cause (RIC) word. It is a parameter returned from the offending interrogate input/output (IIO) or high-priority interrogate I/O (HIIO) instruction. Figure 30-1 illustrates the format of the %status1 RIC word, where PON is the power-on interrupt. Figure 30-1 Format of status1 for EMS Message 37
%status2	is the read interrupt status (RIST) word. It is a parameter returned from the offending interrogate I/O (IIO) or high-priority interrogate I/O (HIIO) instruction. Figure 30-2 illustrates the format of the %status2 RIST word, where: O = Ownership. If set to 1, indicates that the device is owned by other port. I = Interrupt pending. If set to 1, indicates that the device is signaling interrupt. A = Abort. If set to 1, indicates that the device transfer aborted. P = Parity error. If set to 1, indicates that a parity error was detected during a channel-to-device transfer. X = Value depends on the controller. Figure 30-2 Format of status2 for EMS Message 37
%status3	is the channel status word that defines a possible channel error, which can have these values: %status3 Meaning %000000 No error detected by channel. %000100 Interrupt status word bits <0:3> were not all zeros. %000200 Channel detected a parity error in the RIC word. %000400 Channel detected a parity error in the RIST word. %177777 Channel has been disabled. %1XXXXX If bit 0 is set to 1, a handshake or timeout error occurred during an attempt to communicate with the controller. In this case, status3 is defined as the contents of the channel tag in (CTI) register, which contains the I/O control field.

Cause  One or more I/O interrupts failed with a condition code less (CCL) or a parity channel error; both indicate a channel failure.

Effect  If the system detects too many channel errors in a short time, the I/O interrupt handler attempts to reset the channel; if the channel reset fails, the system kills the channel. If the channel is killed, the processor remains up but unable to perform I/O through that channel.

Recovery  Reload the processor to enable the channel, taking into consideration any applications already running on that processor. If the error persists, the system stops displaying this message and starts displaying EMS message 39.

If this error recurs, contact your service provider and provide all relevant information:

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  #num condition code less (CCL) errors have occurred on the indicated channel %c. #num is typically 100.

Effect  The system continues to collect CCLs for each channel. The message is posted again each time 100 CCL errors are collected on a channel.

If the system detects too many channel errors in a short time, the input/output (I/O) interrupt handler attempts to reset the channel; if the channel reset fails, the system kills the channel. If the channel is killed, the processor remains up but unable to perform I/O through that channel.

Recovery  Contact your service provider and provide all relevant information:

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  A connection to the specified system was lost.

Effect  The NCP attempts to reestablish the connection over the same path; if it fails, the line handler seeks an alternate path.

Recovery  Informational message only; no corrective action is needed unless other messages are displayed.

Cause  The line is ready to accept network requests.

Effect  A connection is successfully established with a remote device.

Recovery  Informational message only; no corrective action is needed.

Cause  The operator has brought down a line, or a file-system error has occurred that brought it down.

Effect  The network control process (NCP) must find an alternate communication path if one is available.

Recovery  See Appendix B, for a definition of the specified error. (For SNAXLink lines, see Table 30-2; if the error is not in this table, see Appendix B.) For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

For an X.21 line, abort the line, and then restart it.

Cause  A successful connect exchange occurred with the network control process at the remote system number.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  A line handler did not receive an end-to-end acknowledgment within the configured L4TIMEOUT time. The line handler retried the request L4RETRIES times before the network control process (NCP) issued this message.

Effect  The connection to the destination node is lost. The NCP attempts to reestablish the connection first over the same line, then over another line, if available.

Recovery  Recovery is application-dependent.

Cause  A change in processor status at system number has occurred.

This message is sent only by a network control process (NCP) with network monitor center (NMC) status.

Effect  The system reports the problem and continues processing.

Recovery  Informational message only; no corrective action is needed.

Cause  A network control process (NCP) did not receive a status message from the NCP at system number for three time periods. The NCP automatically seeks an alternate path.

Effect  The system reports the problem and continues processing.

Recovery  Informational message only; no corrective action is needed unless other, related messages are displayed.

ldev	identifies the logical device of the line handler. NOTE: If device ldev is a Multilan controller (D-series only), see also TLAM message 3.
lev	is the level reporting the error (2 or 3).
%state	identifies the state in error.
#event	identifies the event number in error.

Cause  A protocol failure has occurred. In some cases, this message displays an I/O address of (cpu,chan,%ctlr,%unit) when the device supports extended I/O addressing or when the system is a multiple-channel system; that is, it can support more than one channel per processor.

Effect  Levels 2 and 3 are reset to the idle state. The system continues to respond to all requests.

Recovery  Usually this message is informational only and no corrective action is needed. However, if this error occurs with other, related messages, contact your service provider and provide all relevant information:

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  An operation or a request to a subdevice was incorrect.

Effect  If you cannot recover from the error, bring down the device.

Recovery  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.

Cause  When a non-fatal internal error occurs, the subsystem generates a message 74, which includes an error code, %param, that is either a “common cause” code or a system-specific internal error. This can occur when the subsystem determines that the SYSGEN/Configuration Utility Program (COUP) modifiers were specified incorrectly, and the Communications Management Interface (CMI) cannot be used to correct the problem. Usually these messages are informational and do not require any further action. Sometimes, however, the line will go down, and you will have to restart it using CMI or the Subsystem Control Facility (SCF) START command.

Effect  If the process recovers from the internal error, the system continues operating.

For SNAX/XF, the finite-state machine (FSM) goes into the reset or recovery state.

Recovery  If the I/O process does not recover, see the appropriate table for the error code and recovery information.

If directed to contact your service provider, provide all relevant information:

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  There were too many false channel interrupts. Usually, these interrupts occur when a controller connected to the processor (specified in the message header) fails. Either the controller does not identify itself when polled (see messages 37 and 39), or the controller asserts a continuous stream of interrupts (see message 61). The operating system receives no indication of which controller has failed.

Effect  The operating system disables channel %c of the specified processor and wakes all input/output (I/O) processes (IOPs) in that processor channel on IOPON. Then, all IOPs using that channel start to use their backup processes. Although channel-based I/O cannot be performed through this processor channel, the processor remains up and can run processes.

Recovery  Identify and replace the failing controller. To restore the channel to operation, reload the processor; any processes running on the processor terminate.

Cause  There were too many false channel interrupts. Usually, these interrupts occur when a controller connected to the processor (specified in the message header) fails. Either the controller does not identify itself when polled (see messages 37 and 39), or the controller asserts a continuous stream of interrupts (see message 61). The operating system receives no indication of which controller failed.

Effect  The operating system resets channel %c of the specified processor and awakes all input/output (I/O) processes in that processor channel on IOPON. In most cases, the failing controller resets its internal status and resumes normal behavior.

Recovery  If the condition persists, identify and replace the failing controller, because the operating system will probably bring down the channel if its condition decays. (See message 76 for a description of the channel-down condition.)

Cause  A Peripheral Utility Program (PUP) CONSOLE, ENABLE number command was issued. This command enables console logging of the specified system message.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  A Peripheral Utility Program (PUP) CONSOLE, DISABLE number command was issued. This command disables console logging of the specified system message.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

To enable console logging of the specified message again, issue the command:

PUP CONSOLE, ENABLE number

Cause  A Peripheral Utility Program (PUP) CONSOLE, ENABLE * command was issued. This command enables console logging of all system messages.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  A Peripheral Utility Program (PUP) CONSOLE, DISABLE * command was issued. This command disables console logging of all system messages.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed. To enable the console logging of all system messages again, issue this command:

PUP CONSOLE,ENABLE *

Cause  When a fatal error occurs, the subsystem generates a message 90, which includes an errcode, that is either a “common cause” code or a subsystem-specific internal error. This can occur when the subsystem determines that the SYSGEN/ Configuration Utility Program (COUP) modifiers were specified incorrectly, and the Communications Management Interface (CMI) cannot be used to correct the problem.

Effect  The input/output (I/O) process or line handler stops and cannot be used. If the process is ATP6100, CP6100, AM3270, AM6520, or TR3271, the process deletes itself.

Recovery  Correct the problem and run SYSGEN again, or reconfigure the process into the system and restart the process. If directed to contact your service provider, provide all relevant information:

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  An Expand line handler or the network control process ($NCP) detected an internally inconsistent condition.

Effect  The process reports the condition and continues processing.

Recovery  The specific recovery action depends on the cause code displayed:

Cause  An error occurred on the indicated disk device, and the I/O retry did not succeed. This message is displayed only when the disk was accessed by PUP.

Effect  The operation fails.

Recovery  Decode this message and take the appropriate action, if possible, or contact your service provider and provide all relevant information:

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  An error has occurred on the indicated disk device; the I/O operation will be retried. This message is displayed only when the disk was accessed by the Peripheral Utility Program (PUP).

Effect  The retry finishes.

Recovery  If the retry is not successful, another message (retry or error) is displayed.

Cause  The I/O process could not download the appropriate SNAXLink microcode into either the communications interface unit (CIU) or the channel adapter unit (CAU). If param1 is %301, a disk file error occurred when the microcode file was accessed and param2 is the specific file-system error; otherwise, another file-system error occurred and is reported in param1. (For details on the file-system errors, see Table 30-2; if the error is not listed in this table, see Appendix B.)

Effect  The controller cannot be used until the microcode is downloaded.

Recovery   Look at the file-system error code in the message. See Table 30-2 or to Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Cause  The controller microcode was not loaded for the specified device. This event might occur following a controller power-on.

Effect  The controller cannot be used until the microcode is downloaded.

Recovery  Use a different microcode file.

If this does not solve the problem, contact your service provider and provide all relevant information:

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.

ldev	identifies the logical device.
CU %ccu	indicates the input/output (I/O) address associated with this message.
CU %...	is displayed instead of CU %ccu when the device supports extended I/O addressing or when the system is a multiple-channel system; that is, it can support more than one channel per processor. When the extended format of the message is used, (cpu,chan,%ctlr,%unit) is displayed at the end of the message.
%param	indicates which event has occurred: 0 The primary microcode file ($SYSTEM.Mhpn.hhhppp) was downloaded. 1 The backup microcode file ($SYSTEM.SYSnn.Mhpn) was loaded. NOTE: For the definitions of Mhpn.hhhppp and more information about loading the microcode, see the description of the PUP LOADMICROCODE command in the Peripheral Utilities Program (PUP) Reference Manual. For a SNAXLink device, %param indicates which event has occurred: 0 The SNAXLink controller was loaded. 1 The SNAXLink adapter box was loaded.
cpu	identifies the processor number.
chan	identifies the channel number.
ctlr	identifies the controller number.
unit	identifies the unit number.

Cause  The specified device was successfully downloaded.

This message always displays when the processor containing the primary I/O process for a tape is loaded.

Effect  The operation is completed.

Recovery  For a SNAXLink device, this is an informational message only; no corrective action is needed.

Otherwise, if %param is 1, restore the microcode-file subvolume from the site update tape (SUT). Then issue the Peripheral Utility Program (PUP) LOADMICROCODE command to reload the microcode.

Cause  A device was interrupted more than once before its I/O process processed the first interrupt.

Effect  The device goes down.

Recovery  Contact your service provider and provide all relevant information:

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.

ldev	identifies the logical device.
CU %ccu	indicates the input/output (I/O) address associated with this message.
CU %...	is displayed instead of CU %ccu when the device supports extended I/O addressing or when the system is a multiple-channel system; that is, it can support more than one channel per processor. When the extended format of the message is used, (cpu,chan,%ctlr,%unit) is displayed at the end of the message.
%dev-status	is the interrupt cause word returned from the controller (described in Appendix A).
%param1	for a tape controller, its value is 0; for a disk controller, it identifies the address where the error occurred.
%param2	for a tape controller, its value is 0; for a disk controller, it identifies the address where the error occurred.
%param3	for a tape controller, its value is 0; for a disk controller, it identifies the command that was being executed at the time the error occurred. NOTE: For a Multilan controller (D-series only), see TLAM message 3.

Cause  A fatal controller error has occurred.

Effect  The disk process brings down all paths to ldev that pass through the defective controller.

Recovery  On 3206 controllers, clear this error by using the Peripheral Utility Program (PUP) LOADMICROCODE command, powering off the controller power, or resetting a processor.

Take action depending on dev-status, or contact your service provider and provide all relevant information:

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.

ldev	identifies the logical device. NOTE: If device ldev is a Multilan controller (D-series only), see also TLAM message 3.

Cause  The dedicated buffer size for this line handler was too small. The line handler cannot operate properly.

Effect  The line handler does not accept any operations.

Recovery  Reconfigure the system specifying a larger buffer size.

Cause  A SLOWPOLL state changed for a particular data communications subdevice.

Effect  The operation is finished.

Recovery  Use the Communications Utility Program (CUP) or the Communications Management Interface (CMI) to identify the subdevice name from the specified number. Once you know the subdevice name, correct the problem.

Cause  (For TR3271 subdevices only) The line handler was initiated at SYSGEN with an INITSTATUS of %177777. Subdevice #ddd was selected (by the host) but not opened by an application process or joined to an AM3270 subdevice. The application process might be in error.

Effect  The operation is completed.

Recovery  Use the Communications Utility Program (CUP) to identify the subdevice name from the number. Check to see whether the subdevice was opened. If so, check to see whether the subdevice was joined to another subdevice on an AM3270 line.

Cause  The Transaction Monitoring Facility (TMF) received a disk process request that prevented release of the specified audit trail.

Effect  The operation is completed except for the excluded volume.

Recovery  Use the TMFCOM EXCLUDE command to force continuation. Perform a rollforward to recover the EXCLUDED volume.

Cause  An event that has aborted network traffic has occurred.

Effect  A message is sent for each system where traffic was aborted.

Recovery  Informational message only; no corrective action is needed. If cause codes 01, 02, or 03 occur frequently, you might want to trace the problem. Run traces on the network control process (NCP) and the line handler (if you know which line handler to trace).

Cause  The BREAK key was pressed while a process was attempting to write to a terminal. The process retried and entered a loop.

Effect  Continually retrying an error can tie up the terminal-handler I/O process in another processor, locking out all application programs.

Recovery  Recovery is application-dependent, so stopping the process might or might not be appropriate. Suspend the process indicated by cpu,pin and determine the identity of the application. Modify the application to delay between retries.

If the application did not initiate the break, retry the operation, delaying at least 10 seconds between retries.

If the application initiated the break, check $RECEIVE for the system break message, and take the appropriate action.

Cause  The BREAK key was pressed while a process was attempting to write to a terminal. The process retries and enters a loop.

Effect  Continually retrying an error can tie up the terminal-handler I/O process in another processor, locking out all application programs.

This message appears three times for each event: first with the volume name, second with the subvolume name, and third with the file name.

Recovery  Recovery is application-dependent, so stopping the process might or might not be appropriate. Suspend the process, and determine the identity of the application. Then modify the application to delay between retries.

If the application did not initiate the break, retry the operation, delaying at least 10 seconds between retries.

If the application initiated the break, check $RECEIVE for the system break message and take the appropriate action.

Cause  The BREAK key was pressed while a process was attempting to write to a terminal. The process retries and enters a loop.

Effect  Continually retrying an error can tie up the terminal-handler input/output (I/O) process in another processor, locking out all application programs.

Recovery  Since the application program is remote, use the Peripheral Utility Program (PUP) DOWN command on $nnnn, and then bring it back up.

Cause  The BREAK key was pressed while a process was attempting to write to a terminal. The process retries and enters a loop.

Effect  Continually retrying an error can tie up the terminal-handler I/O process in another processor, locking out all application programs.

Recovery  Use the Communications Management Interface (CMI) INFO command to determine the subdevice name corresponding to the logical device number; then abort and restart the subdevice:

INFO LINE $ldev, DETAIL
ABORT SU $ldev.#subdev
START SU $ldev.#subdev

Cause  The interprocessor bus-monitor process brought down the specified Fiber Optic Extension (FOX) interprocessor bus path.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  The interprocessor bus monitor process brought up the specified Fiber Optic Extension (FOX) interprocessor bus path.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified Fiber Optic Extension (FOX) interprocessor bus path was taken out of service because too many errors occurred in a ten-minute interval.

Effect  Traffic is automatically routed to other available paths as long as at least one path is available.

Recovery  Try to open the path again. Issue this Subsystem Control Facility (SCF) command:

CONNECT $IPB.#{X | Y}, {LEFT | RIGHT}

If the error persists, contact your service provider and provide all relevant information:

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  On the specified Fiber Optic Extension (FOX) interprocessor bus path, messages to the specified cluster and processor resulted in #s-num of SEND instruction timeouts or #w-num of WACK timeouts.

Effect  If the error rate exceeds the preset threshold, the path goes down and the system issues EMS message 135.

Recovery  Informational message only; no corrective action is needed.

Cause  The FOX interprocessor bus messages from the specified cluster and processor have caused #c-num checksum errors and #r-num routing errors on the X bus.

Effect  The operation is finished.

Recovery  Usually, this message is informational only; no corrective action is needed. However, if the error persists, contact your service provider and provide all relevant information:

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  The Fiber Optic Extension (FOX) interprocessor bus messages from the specified cluster and processor caused #c-num checksum errors and #r‑num routing errors on the Y bus.

Effect  The operation is finished.

Recovery  Usually, this message is informational only; no corrective action is needed. However, if the error persists, contact your service provider and provide all relevant information:

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  The Fiber Optic Extension (FOX) interprocessor bus messages from the specified cluster and processor have caused #s-num sequence errors and #u-num unexpected packet interrupts on the X bus.

Effect  The operation is finished.

Recovery  Usually, this message is informational only; no corrective action is needed. However, if the error persists, contact your service provider and provide all relevant information:

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  The Fiber Optic Extension (FOX) interprocessor bus messages from the specified cluster and processor have caused #s-num sequence errors and #u-num unexpected packet interrupts on the Y bus.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed. If the error persists, contact your service provider and provide all relevant information:

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  The communications line interface processor (CLIP) of the 6100 Communications Subsystem (CSS) was successfully downloaded.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  An error was detected in the I/O buffer pool, causing the process to terminate.

Effect  The process enters a loop, terminating incoming messages with a device-down error.

Recovery  Contact your service provider and provide all relevant information:

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   For BOB messages, #param1 reports the BOB event frames, and #param2 reports the number of failures to allocate to the I/O buffer.

For CLIP messages, #param1 reports the number of times the CLIP was downloaded, and #param2 reports the number of failures allocated to the I/O buffer.

Effect  The operation is finished.

Recovery  Check the I/O address to determine whether the message comes from the BOB or the CLIP. Generally, if bits 4 through 6 of the subchannel address are zeros, it is a BOB message. If bits 4 through 6 are nonzero, it is a CLIP message.

If you get a number of retryable errors, you should schedule maintenance as soon as possible.

If you get fatal errors, contact your service provider and provide all relevant information:

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  The trace segment was filled, and looping (recircling the buffer) was not specified. There are no parameter values.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  The 3650/6100 Communications Subsystem (CSS) download file could not access the disk. Causes of this error include a missing download file, an incorrect communications line interface processor (CLIP) or line interface module (LIM) part number, or a software or hardware configuration error.

Effect  The object is not downloaded and remains in the starting and boot states.

Recovery  If #param3 is a file-system error, 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 #param3 is a CSM error (D-series only), see Table 30-15 for a list of CSM error codes. Issue a Communications Management Interface (CMI) STOP command against the object before trying to start it again.

If directed to contact your service provider, provide all relevant information:

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.

The error codes returned by the 3650/6100 Communications Subsystem (CSS) appear in %param3 in EMS messages 145 through 149.

Cause  The 3650/6100 Communications Subsystem (CSS) hardware failed while attempting to download the CLIP or the CIU. This message is usually reported with EMS message 154 or 155 or with a file-system error message.

Effect  The object is not downloaded and remains in the starting and boot states.

Recovery  Analyze the failure indicated by the CSM error code in #param3 and the accompanying message. Issue a Communications Management Interface (CMI) STOP command against the object before trying to start it again.

Cause  The 3650/6100 Communications Subsystem (CSS) or I/O process received a status probe response from the CLIP. The probe indicates that the CLIP is in the boot state instead of the run state.

Effect  The communications access process (CAP) attempts to download the CLIP again. If it cannot download the primary path, the CAP attempts a download on another path.

Recovery  Decode the status byte to determine which error has occurred. Note the error and contact your service provider. If the CLIP does not restart automatically, try to restart it manually.

When contacting your service provider, provide all relevant information:

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  The CIU of the 3650/6100 Communications Subsystem (CSS) has stopped.

Effect  The CIU error is logged on one processor path while a second processor, if available, attempts to restart the CIU. If the same error occurs on the second processor, the second processor retries on the original processor. Then, if an error occurs on the original processor, the process terminates.

Recovery  %param3 and %param4 provide details about the last error. Take the appropriate action. The EIO status word (RDST) returned by the CIU provides two levels of information:

The EIO status word appears in %param4 of EMS message 148 (see Figure 30-3).

Figure 30-3 Format of param4 for EMS Message 148

	NOTE: This RDST word for extended CIU is identical to the nonextended RDST word.

Table 30-16 lists the EIO status word bits and their meaning.

Cause  An unanticipated change has occurred in the status of the CIU on the 3650/6100 Communications Subsystem (CSS). To identify the CIU, a status change is sent when a CIU is coming up. This action is helpful in single-port CIU configurations, where both CIUs might have the same address.

Effect  Generally the CIU is brought down, and a switch to the other CIU occurs.

Recovery  Note the information returned by this error. Try to restart the CIU by issuing the appropriate Communications Management Interface (CMI) commands. If this procedure fails, contact your service provider and provide all relevant information:

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.

ldev	identifies the logical device.
CU %ccu	indicates the input/output (I/O) address associated with this message.
CU %...	is displayed instead of CU %ccu when the device supports extended I/O addressing or when the system is a multiple-channel system; that is, it can support more than one channel per processor. When the extended format of the message is used, (cpu,chan,%ctlr,%unit) is displayed at the end of the message.
path	indicates the communications interface unit (CIU) path: Path A = %020101 Path B = %020102
%param3	is the requestor process identification.
%param4	indicates the path and the communications line interface processor (CLIP) status byte. If bit 0 (the most significant bit) is set to 1, path A is the path the CSM activates. If bit 1 is set to 1, path B is the path the CSM activates. For example, if %param4 is %040020, the bit translation is 0 100 000 000 010 000. Since bit 1 is set to 1, the CSM is activating path B. This information is contained in the path field. The second word of %param4 reports the CLIP status. The CSM probes the CLIP periodically to determine its status. The results of the most recent probe are reported in this status word. The Communications Management Interface (CMI) interprets the CLIP status code. Note that %20 indicates that the CSM has determined that the CLIP should be downloaded.
%param5	is the error data returned by the CLIP. Table 30-17 lists the error codes for the status field %param5 for the ATP6100. Table 30-17 param5 Error Codes for EMS Message 150 %param5 Meaning %000001 EOF character detected %000002 Break was detected %000003 Operation timed out %000004 Modem error detected %000005 Modem was disconnected %000006 Parity error detected %000007 SIO overrun occurred %000010 Character framing error %000011 Unrecoverable terminal error %000012 No buffer available for read %000013 Line not configured %000014 Line not started %000015 Trace already active %000016 No trace is active %000017 Request is not valid %000020 Invalid subdevice specified %000021 Internal state machine error %000022 Terminal was powered on %000023 Invalid ETX parameter %000024 Invalid baud rate parameter %000025 Invalid character size %000026 Invalid parity specified %000027 Invalid number of stop bits %000030 Invalid special term node %000031 Invalid backspace type %000032 Request was canceled %000033 No active request to cancel %000034 Invalid write count specified %000035 Invalid read count specified %000036 Invalid L4 specified %000037 Line already started %000040 Active request is pending %000041 Modem failure due to CTS %000042 Modem failure due to SDCD %000043 Baud rate selected conflicts with other channel's baud rate on 2681 chip (CLIP4 only) %000044 Baud rate not supported by this interface (CLIP4 only) %000045 No response received from printer %000046 Printer is not ready %000047 Printer error %000050 Printer paper out %000051 VFU buffer error   NOTE: If %param5 is %000047, %param4 is the primary/auxiliary status returned from 5520/5530 printers. %param4 <0:7> is the primary status and %param4 <8:15> is the auxiliary status.

Cause  The 3650/6100 Communications Subsystem (CSS) received a download request from the CLIP.

Effect  The operation is finished.

Recovery  Informational message only; no corrective action is needed.

Cause  The BOB of the 3650/6100 Communications Subsystem (CSS) has reset itself.

Effect  The BOB and associated CIU path go down. The Communications Subsystem Manager (CSM) tries to bring up this path.

Recovery  Note the message parameters. If the problem persists, contact your service provider and provide all relevant information:

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  The break-out board (BOB) of the 3650/6100 Communications Subsystem (CSS) was not properly synchronized with the host. This message normally appears when the BOB is powered on or off, or when processors are switched.

Effect  In most cases, the BOB and the host recover (become synchronized).

Recovery  If this error persists, contact your service provider and provide all relevant information:

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.