Operator Messages Manual
Chapter 6 ATP6100 Messages
The messages in this chapter are generated by the ATP6100 subsystem.
The subsystem ID displayed by these messages includes ATP6100 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. | | | | |
| 67 LDEV ldev SUBDEV ddd ERROR errnum: PROCESS
INTERNAL ERROR | | ldev | identifies the logical device (LDEV). | | ddd | identifies the subdevice. | | errnum | identifies a file-system error |
Cause An operation or a request to the indicated ATP6100 subdevice
was incorrect Effect The subdevice is placed in the STOPPED state. Recovery Appropriate recovery action depends on the file-system error
that has occurred. See Appendix B, for a definition of the specified error.
For more detailed information including recovery actions, refer to
the Guardian Procedure Errors and Messages Manual. If you cannot recover from the error, bring down the subdevice. |
| 74 LDEV ldev ATP6100:
PROCESS INTERNAL ERROR %param3 %param4 %param5 | | ldev | identifies the logical device (LDEV). | | %param3 %param4 %param5 | provides information used by HP personnel. See Table 6-1 for information on the ATP6100
specific error codes. Table 6-1 %param3 Error Descriptions for Message
74 | %param3 Code in Octal | Description |
|---|
| %1001 | The ATP6100 line handler process tried
to receive a frame while level 3 was still using the receive buffer. | | %1002 | An invalid CLIP function was received.
%param4 indicates the function modifier
fields. | | %1003 | One of the following occurred:The request to activate a path timed out. The request to reset sequence numbers timed out. The request to set frame size timed out. The response to abort the previous frame timed out.
| | %1004 | A problem in queuing or dequeuing
a subdevice. %param4 indicates the subdevice
number. | | %1005 | A bad subdevice number was detected
during a checkpoint operation. %param4 indicates the subdevice number. | | %1006 | A subdevice error was received on
a CMI message to the CLIP. %param4 indicates
the function modifier fields. %param5 indicates
the error returned. | | %1011 | The requested buffer size is greater
than the MAXLOCALAREA. | | %1012 | Level 3 tried to release a non-existent
I/O buffer. This is a fatal error and the process goes into an error
loop. | | %1013 | The I/O process failed to get a request
buffer. | | %1014 | The CLIP Test interval is set to zero. | | %1015 | The frame size is larger than the
CLB buffer size. | | %1016 | An improper frame size was received
for the available receive buffer space. %param4 indicates the received size of the frame. %param5 indicates the CLB buffer size. | | %1023 | The CLIP received a frame which contained
one of the following format errors:The CLIP request ID differs from the active requests
LCB address. The CLIP TIN field is less than 2 bytes.
| | %1026 | The CONMgr replied with an error during
an ACTIVATE PATH request. %param4 indicates
the error returned by the CONMgr. %param5 indicates the status word from the CONMgr reply. | | %1031 | The CONMgr is reporting too many errors.
param4 indicates the error returned by
the CONMgr. %param5 indicates the status
word from the CONMgr reply. | | %1033 | An irrecoverable ATP6100 internal
error occurred. This is normally followed by a CPU halt. | | %1034 | An unsupported Baud rate was specified.
An example of an unsupported baud rate for terminals is 38.4K. | | %1035 | An IOPRM/SPI procedure returned an
error. Depending on the severity of the error, one of the following
occurred:the IOP continued after the error.
| | %1040 | An unsupported interface was specified.
An example is CL which is no longer supported on the concentrator. | | %1042 | The wrong interrupt handler was specified. | | %1043 | An illegal value for the CLB frame
size was used. The value must be between 150 - 600 words. | | %1045 | An error was received when attempting
to deallocate a memory segment. | | %1046 | The primary IOP was unable to create
a backup IOP. The primary IOP will automatically retry backup creation
following a time-out. param4 indicates
the error returned from PROCESS_LAUNCH_IT_. param5 indicates the error detail returned from PROCESS_LAUNCH_IT_. |
|
Cause The ATP6100 line handler process detected an internal problem.
%param3 is the reason for the error.
The descriptions for %param3 errors are
listed in Table 6-1. Effect Application requests are aborted, and ATP6100 recovers. Recovery Contact your service provider and provide all relevant information
as follows: Description 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
NonStop Solution Center (GNSC) supply your system number and the numbers
and versions of all related products as well. |
| 90 LDEV ldev ATP6100:
I/O PROCESS ABEND, code: errcode | | ldev | identifies the logical device (LDEV). Table 6-2 errcode Error Descriptions for Message
90 | errcode Code in Decimal | Description |
|---|
| 1 | Failure in call to ALLOCATESEGMENT. | | 2 | Failure in call to USESEGMENT. | | 3 | Failure in call to DEALLOCATESEGMENT. | | 4 | Failure in call to LOCKMEMORY. | | 5 | Failure in call to DEFINEPOOL. | | 6 | Failure in call to GETPOOL. | | 15 | Failure in call to WANSD_IOGET_. | | 19 | Failure in call to DCT_GET_BY_LDEV. | | 26 | Brother called IOPRM_ABORT or a premature
takeover by the backup (before the initial checkpoint). | | 28 | Failure in call to WANSD_INITIALIZE_
or WANSD_ESTIMATE_MEMORY_. | | 200 | Too many lines multied. With the SWAN
concentrator, the maximum number of MULTIed lines per ATP6100 line
handler process is six. | | 201 | Cannot allocate read or write buffer. | | 202 | Lines are configured across a concentrator
boundary. With the SWAN concentrator, only lines from the same concentrators
can be multied. | | 203 | CLB address is invalid. | | 204 | Unknown subdevice. | | 205 | Cannot reallocate the read or write
buffer. | | 206 | A level-3 buffer initialization failed. | | 207 | The backup process performed an unexpected
action. | | 208 | More localpool was requested than is
available. | | 209 | A license check failed | | 210 | WANSD_GETPHYSADDR_ returned an error. | | 211 | The device subtype is out of range. | | 249 | Unable to add the subdevice at init
time due to an IOPRM procedure error. | | 251 | The device subtype is out of range.
For ATP6100, the SWAN concentrator only supports a subtype of 0 (i.e.
53,0). | | 254 | Invalid subdevice name which does not
start with #. This could be caused by an incorrect PROFILE. |
|
Cause The ATP6100 line handler process detected a severe internal
problem. The descriptions for the abend codes (errcode) are listed in Table 6-2. Effect The input/output (I/O) process abends. Message 74 always precedes
message 90. Recovery Contact your service provider and provide all relevant information
as follows: Description 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
NonStop Solution Center (GNSC) supply your system number and the numbers
and versions of all related products as well. |
| 106 LDEV ldev ATP6100:
INSUFFICIENT BUFFER MESSAGE | | ldev | identifies the logical device (LDEV). |
Cause The MAXLOCALAREA modifier contained in the specified PROFILE
does not specify the necessary buffer space. Effect The ATP6100 line handler process does not accept any operations. Recovery Reconfigure the system specifying a larger buffer with the MAXLOCALAREA
modifier. The MAXLOCALAREA modifier specifies the largest buffer
obtainable from the local pool. |
| 147 LDEV ldev ATP6100:
CSS STATUS PROBE ERROR, CIU path %param3 | | ldev | identifies the logical device (LDEV). | | path | identifies the path associated with this message. | | %param3 | provides information used by HP personnel. See Table 6-3 for information on the ATP6100
specific error codes. Table 6-3 %param3 Error Descriptions for Message
147 | %param3 | Description |
|---|
| -1 | The status probe timed out. | | -2 | An unexpected probe from the CLIP | | 2 | CLB type-field. An unexpected status
from the CLIP. |
|
Cause The Concentrator Manager (CONMgr) or the I/O process received
a status-probe response from the CLIP associated with an ATP6100 line.
The probe indicates that this CLIP is in the boot state instead of
the run state, either because it was powered off and then on again
or because of some internal software or hardware problem. Effect The communications access process (CAP) attempts to download
the CLIP again. If the CAP cannot do so on the primary path, it attempts
a download on another path. Recovery Decode the CLIP status byte to determine which error occurred.
If the CLIP does not restart automatically, try to restart it manually.
If the problem persists and if the CLIP status indicates a software
problem, take a CLIP dump. Note the CLIP status value, contact your
service provider and provide all relevant information as follows: Description 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
NonStop Solution Center (GNSC) supply your system number and the numbers
and versions of all related products as well. |
| 157 LDEV ldev ATP6100:
CSS FRAME ERROR, CIU path %param3 %param4 %param5 | | ldev | identifies the logical device (LDEV). | | path | identifies the path associated with this message. | | %param3 %param4 %param5 | provides information used by HP personnel. See Table 6-4 for information on the ATP6100
specific error codes. Table 6-4 %param3 Error Descriptions for Message
157 | %param3 | Description |
|---|
| 2 | An invalid C field. param4 indicates CLB “A” and “C” fields. param5 indicates CLB “T” and “S”
fields. | | 3 | An invalid T field. param4 indicates CLB “A” and “C” fields. param5 indicates CLB “T” and “S”
fields. | | 4 | An invalid S field. param4 indicates CLB “A” and “C” fields. param5 indicates CLB “T” and “S”
fields. | | 6 | Not the expected response to the Reset
Sequence request. param4 indicates CLB
“A” and “C” fields. param5 indicates CLB “T” and “S” fields. | | 7 | A type 6 error message was received from
the CLB task. param4 indicates the reason
and expected “S” field. param5 indicates the original “T” and “S” fields. | | 8 | A wrong data type frame was received for
a multi frame sequence. param4 indicates
CLB “A” and “C” fields. param5 indicates CLB “T” and “S” fields. |
|
Cause An invalid frame was received. It is normal for this error
to occur when the communications line interface processor (CLIP) resets
itself. %param3 indicates the reason for
the error. The descriptions for %param3 errors are listed in Table 6-4. Effect Generally, the ATP6100 subsystem recovers automatically. Recovery If this error did not occur during a path switch, contact your
service provider and provide all relevant information as follows: Description 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
NonStop Solution Center (GNSC) supply your system number and the numbers
and versions of all related products as well. |
| 158 LDEV ldev ATP6100:
CSS UNEXPECTED BREAKPOINT, CIU path %param3 | | ldev | identifies the logical device (LDEV). | | path | identifies the path associated with this message. | | %param3 | provides information used by HP personnel. |
Cause The communications line interface processor (CLIP) associated
with an ATP6100 line has hit an unexpected breakpoint. Effect The CLIP stops. Recovery Note the values of all parameters, contact your service provider
and provide all relevant information as follows: Description 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
NonStop Solution Center (GNSC) supply your system number and the numbers
and versions of all related products as well. |
| 164 LDEV ldev ATP6100:
CSS LINE ERROR, CIU path %param3 %param4 %param5 | | ldev | identifies the logical device (LDEV). | | path | identifies the path associated with this message. | | %param3 | identifies the function/modifier field. | | %param4 | identifies the first data word. | | %param5 | identifies the second data word. |
Cause The communications line interface processor (CLIP) associated
with an ATP6100 line has responded to the I/O process with an invalid
function modifier. The message is sent due to one of the following: A bad subdevice number in a message from the CLIP. A non-zero CLIP status byte in a response to a CLIP
START, STOP, or SET CONFIGURATION request.
Effect The ATP6100 subsystem tries to clear the error by reloading
the CLIP. If this action does not succeed or if it cannot be done,
the ATP6100 subsystem resets the CLIP and brings the line down. Recovery Note the values of all parameters, contact your service provider
and provide all relevant information as follows: Description 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
NonStop Solution Center (GNSC) supply your system number and the numbers
and versions of all related products as well. |
| 165 LDEV ldev ATP6100:
CSS SUBDEVICE ERROR, CIU path %param3 %param4 %param5 | | ldev | identifies the logical device (LDEV). | | path | identifies the path associated with this message. | | %param3 | identifies the subdevice number. | | %param4 | identifies the function/modifier field. | | %param5 | identifies the CLIP status field. Table 6-5 %param5 CLIP Error Descriptions
for Message 165 | %param5 Code in Decimal | Description |
|---|
| 1 | EOF character detected | | 2 | Break was detected | | 3 | Operation timed out | | 4 | Modem error detected | | 5 | Modem was disconnected | | 6 | Parity error detected | | 7 | SIO overrun occurred | | 8 | Character framing error | | 9 | Unrecoverable terminal error | | 10 | No buffer available for read | | 11 | Line not configured | | 12 | Line not started | | 13 | Trace already active | | 14 | No trace is active | | 15 | Request is not valid | | 16 | Invalid subdevice specified | | 17 | Internal state machine error | | 18 | Terminal was powered on | | 19 | Invalid ETX parameter | | 20 | Invalid baud rate parameter | | 21 | Invalid character size | | 22 | Invalid parity specified | | 23 | Invalid number of stop bits | | 24 | Invalid special term mode | | 25 | Invalid backspace type | | 26 | Request was cancelled | | 27 | No active request to cancel | | 28 | Invalid write count specified | | 29 | Invalid read count specified | | 30 | Invalid L4 specified | | 31 | Line already started | | 32 | Active request is pending | | 33 | Modem failure due to CTS | | 34 | Modem failure due to SDCD | | Note: The following are errors for CLIP-IV only | | | 35 | Baud rate selected conflicts with other
channel’s baud rate on 2681 chip | | 36 | Baud rate not supported by this interface |
|
Cause The returned modifier byte will have its high order bit turned
on when an error is returned by the CLIP. %param5 is the error returned by the CLIP. The descriptions for %param5 errors are listed in Table 6-5. Effect The ATP6100 line handler process is in the STOPPED state. Recovery Contact the Global NonStop Solution Center (GNSC) and provide
all relevant information as follows: Description 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 Your system number and the numbers and versions of
all related products as well.
|
| 1001 ACTIVATE PATH REQUEST status ON PATH path FROM CPU cpuno | | status | indicates whether the activate path request succeeded
or failed. | | path | indicates the path on which the request was sent. | | cpuno | IOPs primary CPU number. |
Cause IOP requests CONMGR to download the programfile into the clip.
IOP issues the activate path request to NSK and NSK will forward the
request to CONMGR. Effect none Recovery Informational message only; no corrective action is needed. |
|