Operator Messages Manual
Chapter 11 CL2 (Common Level 2) Messages
The messages in this chapter are sent by Common Level 2 (CL2)
modules. CL2 modules provide level-2 data link functions for SNAX
Extended Facility (SNAX/XF) and SNAX Advanced Peer Networking (SNAX/APN).
The subsystem ID displayed for these messages includes CL2 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 S7011 LDEV ldev [I/O
ADR:(cpu,chan,%ctlr,%unit)] | | cpu | identifies the processor number. | | chan | identifies the channel number. | | ctlr | identifies the controller number. | | unit | identifies the unit number. |
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 For SNAXLink controllers, the system waits until the problem
is corrected. 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 service
provider, 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 S7011 LDEV ldev I/O
ADR:(cpu,chan,%ctlr,%unit) LINE $line RETRY %dev-status %ctlr-err | | cpu | identifies the processor number. | | chan | identifies the channel number. | | ctlr | identifies the controller number. | | unit | identifies the unit number. | | 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: For BITSYNC controllers (6203/6204/3604), refer to Table 11-1. For CLIP controllers (3650/3605), refer to Table 11-3. For SNAXLink controllers and outbound interrupts,
refer to Table 11-4. For SNAXLink controllers and inbound interrupts, refer
to Table 11-5.
| | 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 11-1 Interrupt Cause Word Format for BITSYNC Controllers (6203/6204/3604)
for CL2 Message 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 11-2 describes the modem status bits. Table 11-2 Modem Status Bits for BITSYNC Controllers (6203/6204/3604)
for CL2 Message 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 11-3 Interrupt Cause Word Format for CLIP Controllers (3650/3605)
for CL2 Message 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. | | | %23 LOCS block invalid format. | | 11-15 | (continued) | | | %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. |
For the SNAXLink controller, the interpretation of bits 0 through
7 of the interrupt cause word differs depending on whether an outbound
or an inbound interrupt has occurred; in bits 8 through 15, the interpretation
is the same for both outbound and inbound interrupts. Figure 11-1 shows the format
of the interrupt cause word for outbound interrupts. Table 11-4 shows the interpretation
of bits 0 through 7 for outbound interrupts. Table 11-4 Interrupt Cause Word Bits 0:7—Outbound Interrupts for
SNAXLink Controllers for CL2 Message 5 | Bit | Meaning (if ON) |
|---|
| 0 | The controller has completed the power-on
sequence and is ready to accept EIO instructions. | | 1 | Channel underrun. The CIU controller has
timed out a reconnect request, or it cannot keep up with the SNAXLink
link. | | 2 | Channel abort. | | 3 | Channel parity error. | | 4:7 | None. |
Figure 11-2 shows the format
of the interrupt cause word for inbound interrupts. Table 11-5 shows the interpretation
of bits 0 through 7 for inbound interrupts. Table 11-5 Interrupt Cause Word Bits 0:7—Inbound Interrupts for
SNAXLink Controllers for CL2 Message 5 | Bit | Meaning (if ON) |
|---|
| 0 | None. | | 1 | Channel overrun. The CIU controller has
timed out a reconnect request, or it has received a SNAXLink link
frame larger than the allocated buffer. | | 2 | Channel abort. | | 3 | None. | | 4:7 | None. |
Table 11-6 shows the interpretation
of bits 8 through 15 of the interrupt cause word. Bits 8 and 9 are
type bits; their value indicates how you should interpret the values
in bits 10 through 15. Bits 10:15 indicate the actual interrupt cause. Table 11-6 Interrupt Cause Word Bits 8:15 for SNAXLink Controllers for
CL2 Message 5 | Value of Bits 8:9 | Value of Bits 10:15 | Meaning |
|---|
| 00 | | Operational interrupts,
which indicate the result of an EIO instruction issued to the CIU
controller. They are nonfatal; the CIU controller continues to function
normally, and the unit generating the interrupt goes into an inactive
state and awaits the next EIO instruction. | | | %1 | Operation completed without
error. | | | %2 | Write operation terminated
without any data being transferred across the SNAXLink link. | | | %3 | The TX SNAXLink link controller
aborted the frame being transferred across the SNAXLink link. | | | %4 | Not used for SNAXLink. | | | %5 | The CIU controller detected
a frame size smaller than the minimum (2 bytes). | | | %6 | Not used for SNAXLink. | | | %7 | Read completion code indicating
that the frame transferred to the NonStop processor contained a frame-check
sequence error. | | | %10 | Read completion code
indicating that the frame transferred to the NonStop processor was
aborted by the sender. | | | %11 | Read completion code
indicating that the RX SNAXLink link controller has been overrun.
This error code can occur if the CIU controller has not been configured
with a high enough priority on the I/O channel. | | | %12 | Read completion code
indicating that the last byte of the frame received by the NonStop
processor did not contain 8 bits. | | | %13-%17 | Not used for SNAXLink. | | | %20 | The specified LOCS starting
address is out of range. | | | %21 | The specified LOCS starting
address and byte count result in an ending address that is out of
range. | | | %22 | The specified LOCS byte
count plus 10 exceeds the IOC buffer size. | | | %23 | The required two bytes
of zeros did not appear before the LOCS address or byte count. | | | %24 | The LOCS block checksum
was not equal to the checksum calculated by the CIU controller during
transfer to the CIU controller. | | | %25 | The START EXECUTION EIO
instruction specified a starting address that was not within the proper
range ($D200 through $EFFF). | | 00 | (continued) | | | | %26 | The CIU controller has
not been downloaded. The START EXECUTION EIO instruction will not
be accepted until the CIU controller has been downloaded. | | | %27 | The EIO instruction issued
is not supported on this unit. | | | %30 | The parameter word transferred
with this EIO instruction is not supported on this unit. | | | %31 | Reserved for future use. | | | %32 | The NVRAM either was
programmed incorrectly or was not programmed at all. It is impossible
to return a valid identification block. | | 01 | | Microcode interrupts,
which indicate that a failure in the microcode has been detected,
either a software queue overflow or a state failure. They are fatal
and are reported only on unit 0. The CIU controller disables
the SNAXLink link and all I/O channel activity. | | | %0, %1, %2, %3, %4, %5, %6, %7, %11, %12,
%13, %14, %15, %16, %20, %21, %22, %23. | When bits 8:9
are set to 01 (microcode type interrupts), bits 10:15 indicate a microcode
state failure or other microcode error. Contact your representative
and be sure to include the contents of the RIC word in your service
request. | | 10 | | Hardware interrupts, which
indicate a hardware failure. They are fatal and are reported on unit
1. The CIU controller disables the SNAXLink link and all I/O channel
activity. The hardware interrupt codes are documented in the 3840
SNAXLink Maintenance Manual. | | 11 | | Illegal interrupts should
never be generated by the CIU controller. A cause word with bits 8
and 9 set indicates that the CIU controller malfunctioned in an undetectable
manner. Shut down the CIU controller and contact your HP representative. |
When GUARDIO message 100 is displayed for a SNAXLink line, the
EIO status word (RDST) is returned for %dev-status in the TMDS FIND
DETAIL ON command. The CIU controller returns this status code to
indicate: Whether or not it has accepted the EIO instruction Whether or not it has been downloaded and is executing
from the downloaded microcode
Figure 11-3 shows the format
of the EIO status word. Table 11-7 lists the meanings
of the individual bits in the EIO status word. Table 11-7 Bits in EIO Status Word for CL2 Message 5 | Bit | Meaning |
|---|
| 0 | Ownership error. The CIU controller received
an EIO instruction on an I/O channel port that did not “own”
the CIU controller. In such a case, the CIU controller discards all
EIO instructions except for TAKEOWNERSHIP and KILLPORT. | | 1 | Interrupt bit. An EIO instruction has
been directed to a CIU controller that has an interrupt pending in
the port interface interrupt registers. | | 2 | Busy bit. The possible causes are as follows:The CIU controller is busy executing another operation
and can be interrupted only by a privileged EIO instruction. The CIU controller is unable to accept any EIO instructions
except TAKEOWNERSHIP, KILLPORT, and RESET. The CIU controller received a PON, a front-panel reset
on the owning I/O channel port. A RESET or TAKEOWNERSHIP EIO received on the owning
I/O channel port.
| | 3 | A parity error was detected during transfer
of the parameter word. The CIU controller discards the EIO instruction.
If the error was detected during the transfer of a command word, the
CIU controller is not selected and the I/O channel times out the EIO
instruction. The CIU controller remains unaware of the EIO and subsequent
timeout. | | 4 | The CIU controller is executing microcode
out of its bootstrap EPROM. | | 5 | The CIU controller received an invalid
EIO instruction. | | 6 | The CIU controller has been shut down
because of a parity error or because the parity-checking circuitry
was disabled. | | 7 | The CIU controller is performing or has
failed a self-test. Self-tests occur after a PON, a front-panel reset,
or a RESET EIO command. | | 8 | The CIU controller has enabled the SNAXLink
link controllers. | | 9 | The CIU controller has set the SNAXLink
link controllers into loopback mode. |
Cause This message is usually caused by a hardware error and applies
to BITSYNC controllers (6203/6204/3604), CLIP controllers (3650/3605),
and SNAXLink controllers. For controllers other than SNAXLink controllers: 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. For SNAXLink controllers: An error occurred
on the specified device.
Effect The operation is retried. Recovery For controllers other than SNAXLink controllers, check the BOB
and the CLIP modules. For SNAXLink controllers, this is an informational message only;
no corrective action is needed unless otherwise indicated in Table 11-6. |
| 74 S7011 LDEV ldev I/O
ADR:(cpu,chan,%ctlr,%unit) LINE $line Process Internal Error Program
Register = %P Register, Env Register =
%E Register X1-X4 %000000 %000000 %000000 %000000 | | cpu | identifies the processor number. | | chan | identifies the channel number. | | ctlr | identifies the controller number. | | unit | identifies the unit number. |
Cause This message applies to the CLIP controllers (3650/3605) only.
A request was issued to CL2, but no stations were configured. This
request may also be caused by an invalid state action. Effect CL2 performs recovery; however, this recovery could stop all
link protocol. Recovery If CL2 stops all link protocol, obtain a trace if you can replicate
the problem, contact your service provider, 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. |
| 100 S7011 LDEV ldev I/O
ADR:(cpu,chan,%ctlr,%unit) LINE $line SNAX SNAXLINK location microcode Load Failed %fs-err1 [%fs-err2] | | cpu | identifies the processor number. | | chan | identifies the channel number. | | ctlr | identifies the controller number. | | unit | identifies the unit number. | | location | identifies the SNAXLink component that could not be
downloaded. It is one of the following: | | fs-err1 | identifies a file-system error. | | fs-err2 | identifies the specific file-system error for disk
errors (fs-err1 is %301). Otherwise, fs-err2 is 0. |
Cause This message applies to the SNAXLink controller only. The input/output
(I/O) process could not download the appropriate SNAXLink microcode
into either the CIU or the CAU. Table 11-8 lists SNAXLink
generated file-system errors. If the error is not listed in this table,
refer to Appendix B. Table 11-8 SNAXLink Generated File-System Errors for CL2 Message 100 | %fs‑err1 | Meaning |
|---|
| 0 | Operation was successful; no errors occurred. | | 11 | Download microcode file was not found. | | 31 | Unable to obtain memory (LOCALPOOL) needed
by SNAX/XF. | | 33 | Unable to obtain memory (XPOOL) needed
by SNAX/XF. | | 49 | Attempted to access a microcode file
that had an invalid file code. | | 59 | Microcode file was invalid (that is,
it contained a bad directory or a bad record count), or a bad condition
code occurred during a read of the microcode file. | | 66 | The SNAXLink line was down, or the SNAXLink
line was stopped and requests were aborted because of the stop. | | 73 | The SNAXLink CAU was inaccessible (locked
up) because the SNAXLink key was in the OFFLINE position. | | 120 | SNAXLink encountered a fatal checksum
error. This error generally represents an internal problem for which
you should call your HP representative. Sometimes, however, the error
is caused by the IBM channel cables exceeding 200 feet in length. | | 121 | Text underrun. Data late arriving at
SNAXLink. | | 122 | Mode-setting reset command was received
from SNAXLink, or a link error occurred. | | 139 | Fatal error in CIU controller, or the
controller was reset to BOOT state. | | 160 | Request was invalid for current state,
or an attempt was made to download the SNAXLink CAU but the AUTOLOAD
option was OFF, or the incoming XID was invalid. | | 162 | Expected a response from SNAXLink and
did not get one. Operation timed out. | | 164 | Mode-setting disconnect command received
from SNAXLink. The physical unit (PU) is disconnected.When the IBM
operator issues a VARY NET, INACT command for the PU or the SNAXLink
Major Node, this is a normal condition. If no such command was issued,
VTAM detected an error and declared SNAXLink inoperable. Check the
console log, run an EREP report, and send the report and the error
messages to your HP representative. This error is also caused by an
IBM application sending more than 4096 bytes of data to the NonStop
system. | | 169 | PU station undefined. | | 172 | Improper or invalid frame reply; or
frame function, modifier, or length is invalid. | | 175 | An HDLC FRMR was sent or received by
SNAX/XF. This internal error should be reported to your HP representative. | | 177 | Text overrun. Input frame exceeded maximum
frame size. | | 179 | Active modeset occurred during information
transfer state or disconnected state. | | 193 | Retries exhausted during an attempt
to download microcode, or identification information from microcode
file did not match information received from device, or verification
of microcode downloaded failed, or microcode execution failed. | | 210 | Ownership changed during operation. | | 219 | A CIU-E was replaced with a CIU, but
during system generation, product number 3841 was specified rather
than 3840. This error occurs only on the VLX system. | | 224 | A controller problem occurred; either
an I/0 operation issued to a CIU controller was rejected, or the CIU
controller returned an error status. | | 230 | Processor powered down and up. | | 231 | CIU controller and/or SNAXLink CAU powered
down and up, or a SNAXLink CAU reset occurred, or SNAX/XF detected
a fatal error on the NonStop K-series system channel. | | 301 | A disk file error has occurred. %fserr2
is the specific file system error. |
Effect The controller cannot be used until the microcode is downloaded. Recovery Look at the file-system error code in the message. See Table 11-8 or to Appendix B, for a definition
of the specified error. For more detailed information, including recovery
actions, refer to the Guardian Procedures Errors and Messages
Manual. |
| 101 S7011 LDEV ldev I/O
ADR:(cpu,chan,%ctlr,%unit) LINE $line SNAX SNAXLINK location microcode Execution Failure. | | cpu | identifies the processor number. | | chan | identifies the channel number. | | ctlr | identifies the controller number. | | unit | identifies the unit number. | | location | identifies the SNAXLink component that could not be
downloaded. It is one of the following: |
Cause This message applies to the SNAXLink controller only. The appropriate
SNAXLink microcode was not downloaded into either the CIU or the CAU. Effect The controller 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 service
provider, 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 S7011 LDEV ldev I/O
ADR:(cpu,chan,%ctlr,%unit) LINE $line SNAX SNAXLINK location microcode Download Successful | | cpu | identifies the processor number. | | chan | identifies the channel number. | | ctlr | identifies the controller number. | | unit | identifies the unit number. | | location | identifies the SNAXLink component that was downloaded.
It is one of the following: |
Cause This message applies to the SNAXLink controller only. The appropriate
SNAXLink microcode was downloaded into either the CIU or the CAU. Effect The specified SNAXLink component is now operational. Recovery Informational message only; no corrective action is needed. |
| 235 S7011 LDEV ldev I/O
ADR:(cpu,chan,%ctlr,%unit) LINE $line INVALID OPERATION REASON
= reason LINE TYPE: x21 | | cpu | identifies the processor number. | | chan | identifies the channel number. | | ctlr | identifies the controller number. | | unit | identifies the unit number. |
Cause This message applies to CLIP controllers (3650/3605) only. 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 service provider, 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 S7011 LDEV ldev I/O
ADR:(cpu,chan,%ctlr,%unit) LINE $line ENVOYACP/XF CLIP Dial Number: dial-num | | cpu | identifies the processor number. | | chan | identifies the channel number. | | ctlr | identifies the controller number. | | unit | identifies the unit number. |
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. |
|
