Operator Messages Manual
Chapter 35 EXF (EnvoyACP/XF) Messages
The messages in this chapter are sent by EnvoyACP/XF. EnvoyACP/XF
provides level‑2 data link functions for other HP products and user
applications. The subsystem ID displayed by these messages includes
EXF 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. | | | | |
| 4 T9088 LDEV ldev LINE
$line [ RETRY %dev-status %ctlr-err ] | | dev-status | contains the interrupt cause word. The interrupt cause
word (RIC) is used by the communications interface unit (CIU) to report
CIU or CIU-to-LIU bus (CLB) error conditions and to report the successful
completion of input/output (I/O) operations. The interrupt cause word
has two formats: one for input (reading) and one for output (writing).
The interrupt cause word returned to the I/O channel during the interrupt
sequence contains the controller-specific status information that
forced the generation of an interrupt by the controller. For a description of the interrupt cause word, refer to the table
or figure that corresponds to the controller: | | ctlr-err | is a file‑system error. ctlr‑err is either 213 (octal for file-system error 139) or 336 (octal for
file-system error 222). Table 35-1 Interrupt Cause Word Format for BITSYNC Controllers (6203/6204/3604)
for EXF Messages 4 and 5 | Bit | Meaning |
|---|
| 0 | Not used (always 0). | | 1 | Channel overrun. | | 2 | Channel abort. | | 3 | Not used (always 0). | | 4 | Modem loss interrupt. | | 5 | Number of characters read that exceeded
the count specified in the input/output controller (IOC). | | 6 | Receiver overrun. | | 7 | Not used (always 0). | | 8 | Receiver detected an error in the frame
check sequence. | | 9-11 | Assembled bit count of the number of
residue bits in the last data character. | | 12 | Receiver overrun (same as bit 6). | | 13 | Abort received. | | 14 | End-of-message received. | | 15 | Not used (always 0). |
If bits 1, 2, or 5 are set, then bits 8 through 15 are set to
the controller ending state count. If bit 4 is set, then bits 8 through
15 indicate the modem status. Table 35-2 describes the modem status bits. Table 35-2 Modem Status Bits for BITSYNC Controllers (6203/6204/3604)
for EXF Messages 4 and 5 | Bit | Meaning |
|---|
| 8 | Not Data Set Ready. | | 9 | Not Data Carrier Detect. | | 10 | Not Clear to Send. | | 11 | Transmit Overrun. | | 12 | Bit-synchronous controller configured
for RS422 or RS449. | | 13 | Maintenance Mode. | | 14 | Request to Send. | | 15 | Data Terminal Ready. |
Table 35-3 Interrupt Cause Word Format for CLIP Controllers (3650/3605)
for EXF Messages 4 and 5 | Bit | Meaning |
|---|
| 0 | Power on (unit 0). | | 1 | Channel overrun (input).Channel underrun
(output). | | 2 | Channel abort. | | 3 | CIU detected channel parity error. | | 4 | Not used. | | 5 | Not used. | | 6 | Not used. | | 7 | Not used. | | 8 | CIU internal hardware error detected. | | 9 | CIU internal microprogram error detected. | | 10 | Not used. | | 11-15 | % 0 No data complete. | | | % 1 Data transfer complete. | | | % 2 Write ended and data not sent. | | | % 3 CLB underrun. | | | % 4 Invalid CLB frame A field. | | | % 5 CLB frame less than two bytes long. | | | % 6 Invalid CLB frame C field. | | | % 7 FCS error on incoming CLB frame. | | | %10 Incoming CLB was aborted by the sender. | | | %11 CLB receiver underrun. | | | %12 Incoming CLB bits not modulo 256. | | | %13 CLB output wait-for-acknowledgment
(WACK) response timeout. | | | %14 CLB input enable wait-for-acknowledgment
(WACK) response timeout. | | | %15 FLAK response timeout to a FLUSH frame. | | | %16 CLIP/BOB received a wait-for-acknowledgment
(WACK) response unexpectedly. | | | %17 Reserved. | | | %20 LOCS starting address out of range. | | | %21 LOCS block exceeds end of random-access
memory (RAM). | | | %22 LOCS block sizes don’t match
input/output controller (IOC) buffer size. | | 11-15 continued | %23 LOCS block invalid
format. | | | %24 LOCS block bad checksum. | | | %25 Execution execute I/O (EIO) address
invalid. | | | %26 Start Execution issued and CIU not
loaded. | | | %27 Invalid EIO command for unit used. | | | %30 Invalid EIO parameter word. | | | %31 Reserved. | | | %32 Invalid nonvolatile random access memory
(NVRAM) program. | | | %33 - %37 Reserved. |
|
Cause For BITSYNC controllers (6203/6204/3604) or CLIP controllers
(3650/3605): This error is usually caused by a timeout of a CIU-to-LIU
bus (CLB) transmission, or a controller or channel problem. For SNAXLink
controllers: An error has occurred on the specified device, and the
input/output (I/O) retry did not succeed. Effect None. Recovery Check the rank and priority of the communications interface
unit (CIU) controllers and correct any problems found. If necessary,
save the information returned in this message, contact your Global
Mission Critical Solution Center (GMCSC), 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. |
| 5 T9088 LDEV ldev LINE
$line RETRY %dev-status %ctlr-err | | dev-status | contains the interrupt cause word. The interrupt cause
word (RIC) is used by the communications interface unit (CIU) to report
CIU or CIU-to-LIU bus (CLB) error conditions and to report the successful
completion of input/output (I/O) operations. The interrupt cause word
has two formats: one for input (reading) and one for output (writing).
The interrupt cause word returned to the I/O channel during the interrupt
sequence contains the controller-specific status information that
forced the generation of an interrupt by the controller. For a description of the interrupt cause word, refer to the table
or figure that corresponds to the controller: | | ctlr-err | is a file‑system error. ctlr‑err is either 213 (octal
for file-system error 139) or 336 (octal for file-system error 222). |
Cause This message is usually caused by a hardware error and applies
to BITSYNC controllers (6203/6204/3604), CLIP controllers (3650/3605). After the CIU transfers a write data frame to a communications
line interface processor/break-out board (CLIP/BOB) from the processor,
the CIU times the wait-for-acknowledgment (WACK) response from the
CLIP/BOB to which the frame was sent. If the response is timed out by the CIU, then an interrupt is
generated to the appropriate communications access process/Communications
Subsystem Manager (CAP/CSM) with a timed-out indication. The CIU suspends
further transfers to the failing CLIP/BOB. To reactivate transfers
to the CLIP/BOB, the CAP/CSM issues either a LINK CLEAR EIO or INITIATE
WRITE EIO instruction with a retry parameter. Effect The operation is retried. Recovery Check the BOB and the CLIP modules. |
| 6 T9088 Line Started | The SCF START command initiates the operation of an object.
The successful completion of the START command leaves the object in
the STARTED state. Cause The operator issued SCF START LINE. The line is ready to accept
network requests. Effect The line is in the STARTED state. A connection is successfully
established with a remote device. Recovery This is an informational message only; no corrective action
is needed. |
| 7 T9088 Line Stopped | The EnvoyACP/XF subsystem issues a warning when the line is
in a STOPPED state. Cause The operator brought down the line. Some problem might have
made it necessary for the line to go to the STOPPED state. Also, the
line must be stopped before an ALTER LINE command can be issued. Effect The line goes down and is not usable. Communication with the
remote line is not possible. Recovery Correct the problem that caused the line to go down. Issue the
SCF START LINE command to bring the line back up. |
| 11 T9088 FCS Error | The frame-check sequence is a 16-bit field containing the cyclic
redundancy check (CRC) value for the frame, which is used for error-checking.
The CRC value is computed by the sending controller’s hardware,
using the address field, control field, and information field (if
present) as a continuous bit stream. The ending flag follows the frame-check
sequence field. Cause The receiver detected an error in the frame check sequence.
The line aborted due to a modem error. Effect The line is not usable. Communication with the remote line is
not possible. Recovery Correct the problem and issue the SCF START LINE command to
bring the line back up. |
| 12 T9088 LDEV ldev,
LINE $line Status : SCF COMMAND ERROR | Cause An SPI error was encountered while processing an SCF command. Effect SCF commands will not work. Recovery Contact your support representative. |
| 32 T9088 DSR Loss | DSR (Data Set Ready) is a signal coming from a modem that usually
indicates to the computer equipment that the modem is powered on.
DTE (Data-terminal Equipment) is the terminal or host computer to
which a modem (called the DCE) is connected. Your application establishes a link and performs line-control
operations through calls to the CONTROL procedure. These calls include
numerical operation codes, several of which vary from one protocol
to another. When you use switched-line facilities, you must set the Data
Terminal Ready (DTR) modem signal before establishing the link. You
do this by issuing either a CONTROL 17 or a CONTROL 11. For both calls,
you can specify that Data Set Ready (DSR) be asserted before the call
completes. For more information, refer to the subsection, “Establishing
and Controlling a Data Link” in Section 1 of the EnvoyACP/XF Application Programming Manual. Cause A problem with a modem, cabling, or other hardware. Effect The line is not usable. Recovery Correct the problem and start the line. The application process
must reissue any CONTROL requests that were previously issued to initialize
the line and place it in the information-transfer state. (See Appendix
A of the EnvoyACP/XF Application Programming Manual.) |
| 34 T9088 CARRIER LOSS | When two modems decide that they can talk to each other, they
generate a signal on the serial RS-232 interface called carrier detect
(CD). CD remains present as long as the two modems are connected,
thought it can be interrupted by a call-waiting signal. Sometimes
this interruption is enough to drop the data connection and cause
the CD signal to go down and carrier loss will be detected. Cause The carrier is lost. Effect The line is not usable. Recovery Correct the problem and issue the SCF START LINE command to
bring the line back up. |
| 35 T9088 CTS Loss | The CTS (Clear To Send) signal that comes from a modem indicates
to the computer equipment that the modem is ready to accept data for
transmission. Cause The CTS signal is lost. Effect The modem is unable to accept data for transmission. Recovery Reinitialize the line and place it in the information-transfer
state. |
| 41 T9088 Text overrun | Cause A hardware data-overrun error occurred and persisted through
several retries of the operation. Effect The procedure sets the error code and returns without performing
the requested operation. Recovery Corrective action is device-dependent. If you cannot solve the
problem, save the information returned in this message, contact your
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. |
| 53 T9088 CONTROLLER ERROR: ctlr-err is a file-system error. ctrl-err is either
213 (octal for file-system error 139) or 336 (octal for file-system
error 222). | Cause The controller failed its internal diagnostics. The controller
has a fatal error that was recognized by its resident microcode. Effect The procedure sets the error code and returns without performing
the requested operation. All paths through the controller are down. Recovery Check the CLIP modules. If this does not solve the problem,
save the information returned in this message, contact your 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. |
| 54 T9088 LDEV ldev, LINE $line status : DRIVER SEND ERROR DEVSTATUS/RIC = dev-status ERROR = error | | dev-status | identifies the interrupt cause word. The interrupt
cause word (RIC) is used by the communications interface unit (CIU)
to report CIU or CIU-to-LIU bus (CLB) error conditions and to report
the successful completion of input/output (I/O) operations. The interrupt
cause word has two formats: one for input (reading) and one for output
(writing). The interrupt cause word that is returned to the I/O channel
during the interrupt sequence contains the controller-specific status
information that forced the generation of an interrupt by the controller. | | error | is a file-system error. |
Cause The cause is a controller or channel problem. Effect The operation halts. Recovery Contact your support representative. |
| 74 T9088 LDEV ldev LINE
$line Status: Process Internal Error Program
Register = %P Register, Env Register = %E Register X1-X4 %000000 %000000 %000000 %000000 | Cause This message applies to the CLIP controllers (3650/3605) only.
A request was issued to EXF, but no stations were configured. This
request may also be caused by an invalid state action. Effect EXF performs recovery; however, this recovery could stop all
link protocol. Recovery If EXF stops all link protocol, obtain a trace if you can replicate
the problem, contact your 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. |
| 90 T9088 LDEV ldev,
LINE $line Status : PROCESS ABENDED ERROR
= error-code | Cause See the error codes listed in Table 133-3. The error code accompanying this message
is decimal. Effect The input/output (IO) process abends. Recovery See the recovery actions described in Table 133-3. There are four minor deviations from the
table for EnvoyACP/XF: The first column, “Message 74 Code in Octal,”
is not applicable. Code value 23 and above are not applicable. “Cause” is the same as given for X25AM. “Effect” for all of the codes is: “EnvoyACP/XF
terminates.”
|
| 100 T9088 Microcode Load Failed | Microcode is any machine code or data that can run in a microprocessor.
HP produces two types of microcode: volatile and nonvolatile. Volatile
microcode is loaded into the volatile random-access memory (RAM) of
some types of printed wiring assemblies (PWAs) and is not retained
in a host PWA when power to the PWA is interrupted. Nonvolatile microcode is firmware, which is code in memory that
is necessary for the power-up initialization and communication with
a host or device. The software for components of the ServerNet architecture
(for example, an adapter) is called firmware. Some firmware for ServerNet
components is downloaded when the system or component is loaded. Cause The communications line interface processor (CLIP) process failed.
An error occurred when a microcode file was accessed. The controller
microcode was not loaded for the line. Effect Paths through the controller are down. The line cannot be used
until the microcode is downloaded. Recovery Use a different microcode file. If this does not solve the problem,
save the information returned in this message, contact your 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. |
| 101 T9088 Microcode Execution Failure | Microcode is any machine code or data that can run in a microprocessor.
HP produces two types of microcode: volatile and nonvolatile. Volatile
microcode is loaded into the volatile random-access memory (RAM) of
some types of printed wiring assemblies (PWAs) and is not retained
in a host PWA when power to the PWA is interrupted. Nonvolatile microcode is firmware, which is code in memory that
is necessary for the power-up initialization and communication with
a host or device. The software for components of the ServerNet architecture
(for example, an adapter) is called firmware. Some firmware for ServerNet
components is downloaded when the system or component is loaded. Cause The microcode file was not executed. Effect The line cannot be used until the microcode is downloaded. Recovery Use a different microcode file. If this does not solve the problem,
save the information returned in this message, contact your 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. |
| 102 T9088 Microcode Download Successful | Microcode is any machine code or data that can run in a microprocessor.
HP produces two types of microcode: volatile and nonvolatile. Volatile
microcode is loaded into the volatile random-access memory (RAM) of
some types of printed wiring assemblies (PWAs) and is not retained
in a host PWA when power to the PWA is interrupted. Nonvolatile microcode is firmware, which is code in memory that
is necessary for the power-up initialization and communication with
a host or device. The software for components of the ServerNet architecture
(for example, an adapter) is called firmware. Some firmware for ServerNet
components is downloaded when the system or component is loaded. Cause A CLIP download was requested. Effect The CLIP is downloaded. Recovery This is an informational message only; no action is necessary. |
| 147 Status Probe Failure | If the EnvoyACP/XF line is in the STARTED state and no requests
are pending from the application, the status probe request is sent
by the EnvoyACP/XF IO process to check the link between the host and
the adapter CLIP. If no response returns for the sent status probe
request within the timeout period, the lack of response results in
status probe failure and the above message is displayed in the EMS. Cause Loss of communication between the EnvoyACP/XF IO process and
the adapter CLIP; for example, due to a path failure or when the CLIP
is not responding. Effect EMS displays the message Status Probe Failure. Activate path
request is issued by the EnvoyACP/XF IO process. Recovery The IOP process tries to recover the link by issuing the repeated
activate path requests. |
| 235 T9088 LDEV ldev LINE $line INVALID OPERATION REASON = reason LINE TYPE: x21 | Cause There is a problem with the modem, or a timer has expired. Effect The X.21 connection is not established. Recovery Ensure that the modem and modem connections are operating correctly.
If this does not solve the problem, save the information returned
in this message, contact your 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. |
| 236 T9088 LDEV ldev LINE $line ENVOYACP/XF CLIP Dial Number: dial-num | Cause This message applies to CLIP controllers (3650/3605) only. The
call operation was successful. Effect None. Recovery Informational message only; no corrective action is needed.
|
| 237 Activate Path Request status [successful
| failed] On Path path (A/B/None) from
CPU cpuno | IOP requests CONMGR to download the program file onto the CLIP.
IOP issues this activate path request to NSK, and NSK forwards the
same request to CONMGR. | status | indicates whether the path request succeeded or failed. | | path | is A (no response from CLIP); B (ownership), or unknown. | | cpuno | is the IOP primary CPU number. |
Cause successful: IOP successfully issued an activate path request.
failed: IOP failed to issue an activate path request to NSK because
IOP has not done initialization properly. Effect successful: None. failed: The line is stopped in the STOPPED
state. Recovery successful: Informational message only; no corrective action
is necessary. failed: Stop, then restart the device/IOP. |
| 238 SUSPENDED due to path failure | If the EnvoyACP/XF line is in the STARTED state and the communication
between the host and the adapter CLIP is lost for more than 90 seconds,
the above message is displayed in the EMS. Cause Loss of communication between the EnvoyACP/XF IO process and
the adapter CLIP due to a path failure. Effect EMS displays the message SUSPENDED due to path failure; the
line enters the SUSPENDED state. Recovery The line restarts when the path is up. |
|