HP 3000 Manuals HP 3000 Manuals
Remote Link Manager Logging Location Codes
1 CLAS0001 Cause: RLM's data structures are corrupted.
Action: See "Submitting an SR" in appendix A of this
manual.
3 CLAS0002 Cause: Send_msg procedure returned a bad status to
the RLM.
Action: See "Submitting an SR" in appendix A of this
manual.
4 CLAS0002 Cause: Link Error occurred in unexpected state.
Action: See "Submitting an SR" in appendix A of this
manual.
5 CLAS0002 Cause: RLM could not rendezvous ('bind') with the
MCM.
Action: Check the LAN hardware on the HP 3000. If no
problem is found, see "Submitting an SR" in appendix A
of this manual.
6 CLAS0001 Cause: Internal state mismatch within the RLM module.
Action: See "Submitting an SR" in appendix A of this
manual.
7 CLAS0003 Cause: RLM is out of internal resources.
Action: The operator may be attempting to bring up
more than the maximum supported DTC links. If not,
then see "Submitting an SR" in appendix A of this
manual.
8 CLAS0002 Cause: Either the RLM or code that it invoked
encountered an unexpected trap.
Action: See "Submitting an SR" in appendix A of this
manual.
9 CLAS0002 Cause: RLM could not get a buffer to send an outbound
packet (PARM = Status returned by 'bmgr_get_buffer').
Action: See "Submitting an SR" in appendix A of this
manual.
10 CLAS0003 Cause: RLM could not release some internal resources
(PARM = Status returned by 'new_release_table_entry').
Action: See "Submitting an SR" in appendix A of this
manual.
11 CLAS0001 Cause: RLM attempted to release a resource that had
already been released.
Action: See "Submitting an SR" in appendix A of this
manual.
12 CLAS0002 Cause: RLM received a connect reply message from the
link that it did not recognize.
Action: See "Submitting an SR" in appendix A of this
manual.
13 CLAS0003 Cause: The DTC is not responding to the HP 3000's
connection attempts. (i.e The HP 3000 could not
establish an AFCP link control connection with the
DTC.)
Action: Check state of DTC and Lan hardware. If no
problem can be found, see "Submitting an SR" in
appendix A of this manual.
14 CLAS0001 Cause: RLM's data structures are corrupted.
Action: See "Submitting an SR" in appendix A of this
manual.
15 CLAS0002 Cause: RLM could not release internal resources.
Action: See "Submitting an SR" in appendix A of this
manual.
16 CLAS0002 Cause: RLM received disconnect reply that did not
match any transaction in progress.
Action: See "Submitting an SR" in appendix A of this
manual.
17 CLAS0001 Cause: State mismatch within RLM's data structures.
Action: See "Submitting an SR" in appendix A of this
manual.
18 CLAS0002 Cause: RLM received an inbound data packet over a
connection that is down.
Action: See "Submitting an SR" in appendix A of this
manual.
19 CLAS0002 Cause: RLM could not write outbound packet to buffer.
Action: See "Submitting an SR" in appendix A of this
manual.
20 CLAS0002 Cause: RLM could not read buffer containing inbound
packet.
Action: See "Submitting an SR" in appendix A of this
manual.
21 CLAS0001 Cause: Mismatch in states between the DTC and the HP
3000.
Action: See "Submitting an SR" in appendix A of this
manual. (Make sure a dump is taken of both the DTC
and the HP 3000.)
22 CLAS0002 Cause: Mismatch in states between DTC and HP 3000.
Action: See "Submitting an SR" in appendix A of this
manual. (Make sure a dump is taken of both the DTC
and the HP 3000.)
23 CLAS0001 Cause: Mismatch in states between the DTC and the HP
3000.
Action: See "Submitting an SR" in appendix A of this
manual. (Make sure a dump is taken of both the DTC
and the HP 3000.)
24 CLAS0001 Cause: Mismatch in states between the DTC and the HP
3000.
Action: See "Submitting an SR" in appendix A of this
manual. (Make sure a dump is taken of both the DTC
and the HP 3000.)
25 CLAS0003 Cause: DTC returned bad status during link shutdown
(PARM = status returned by DTC).
Action: See "Submitting an SR" in appendix A of this
manual.
26 CLAS0002 Cause: Subsystem (NS Transport) specified invalid
link.
Action: See "Submitting an SR" in appendix A of this
manual.
27 CLAS0003 Cause: Subsystem (NS Transport) attempted to connect
X.25 card that was in a bad state.
Action: Check status of X.25 protocol on DTC.
Possible causes include bad/disconnected cable between
DTC and switch/X.25 network, or the switch/X.25
network is down. When problem is corrected, HP 3000
will display additional logging messages.
28 CLAS0002 Cause: Disconnect reply received from linkn contained
bad status.
Action: See "Submitting an SR" in appendix A of this
manual.
29 CLAS0002 Cause: Subsystem specified a bad parameter in a
connect or disconnect request.
Action: See "Submitting an SR" in appendix A of this
manual.
30 CLAS0001 Cause: Control mismatch between DTC and HP 3000.
Action: See "Submitting an SR" in appendix A of this
manual. (Make sure a dump is taken of both the DTC
and the HP 3000.)
31 CLAS0002 Cause: DTC sent bad packet to HP 3000.
Action: See "Submitting an SR" in appendix A of this
manual. (Make sure a dump is taken of both the DTC
and the HP 3000.)
32 CLAS0002 Cause: Could not separate ('unbind') with link.
Action: See "Submitting an SR" in appendix A of this
manual.
33 CLAS0002 Cause: RLM attempted to send on a connection that was
down.
Action: See "Submitting an SR" in appendix A of this
manual. (Make sure a dump is taken of both the DTC
and the HP 3000.)
34 CLAS0003 Cause: Close request received while resources were
outstanding.
Action: See "Submitting an SR" in appendix A of this
manual.
35 CLAS0002 Cause: Received packet from link on unknown
connection.
Action: See "Submitting an SR" in appendix A of this
manual.
36 CLAS0002 Cause: RLM could not free a buffer.
Action: See "Submitting an SR" in appendix A of this
manual.
38 CLAS0002 Cause: RLM could not free a buffer.
Action: See "Submitting an SR" in appendix A of this
manual.
39 CLAS0002 Cause: State mismatch between DTC and Host.
Action: See "Submitting an SR" in appendix A of this
manual. (Make sure a dump is taken of both the DTC
and the HP 3000.)
40 CLAS0002 Cause: DTC sent unknown packet to HP 3000.
Action: See "Submitting an SR" in appendix A of this
manual. (Make sure a dump is taken of both the DTC
and the HP 3000.)
41 CLAS0001 Cause: Data Structure state mismatches detected while
processing a link failure.
Action: See "Submitting an SR" in appendix A of this
manual.
42 CLAS0001 Cause: RLM's data structures are corrupted.
Action: See "Submitting an SR" in appendix A of this
manual.
43 CLAS0001 Cause: RLM's data structures are corrupted.
Action: See "Submitting an SR" in appendix A of this
manual.
44 CLAS0003 Cause: A shutdown occurred with resources
outstanding.
Action: See "Submitting an SR" in appendix A of this
manual.
45 CLAS0002 Cause: RLM could not release a semaphore.
Action: See "Submitting an SR" in appendix A of this
manual.
46 CLAS0002 Cause: RLM data structures are in an invalid state
for the event.
Action: See "Submitting an SR" in appendix A of this
manual.
47 CLAS0003 Cause: Unexpected status sent by DTC.
Action: See "Submitting an SR" in appendix A of this
manual.
48 CLAS0001 Cause: Interface problem between DTC and HP 3000.
Action: See "Submitting an SR" in appendix A of this
manual.
49 CLAS0002 Cause: Link sent a disconnect event for an unknown
connection.
Action: See "Submitting an SR" in appendix A of this
manual.
50 CLAS0001 Cause: AFCP connection is in an invalid state for the
event.
Action: See "Submitting an SR" in appendix A of this
manual.
51 CLAS0002 Cause: DTC sent an invalid packet to the HP 3000.
Action: See "Submitting an SR" in appendix A of this
manual.
52 CLAS0002 Cause: The DTC sent an invalid packet to the HP 3000.
Action: See "Submitting an SR" in appendix A of this
manual.
53 CLAS0003 Cause: The DTC sent bad status to HP 3000.
Action: See "Submitting an SR" in appendix A of this
manual.
54 CLAS0002 Cause: RLM could not find the expected timer message.
Action: See "Submitting an SR" in appendix A of this
manual.
55 CLAS0002 Cause: RLM could not release timer resource.
Action: See "Submitting an SR" in appendix A of this
manual.
56 CLAS0002 Cause: RLM could not set a timer.
Action: See "Submitting an SR" in appendix A of this
manual.
58 CLAS0001 Cause: State mismatch within RLM.
Action: See "Submitting an SR" in appendix A of this
manual.
59 CLAS0001 Cause: Could not release timer.
Action: See "Submitting an SR" in appendix A of this
manual.
60 CLAS0002 Cause: Invalid message received for current state.
Action: See "Submitting an SR" in appendix A of this
manual.
61 CLAS0003 Cause: Link has gone down.
Action: Run appropriate diagnostics. If no error is
found, see "Submitting an SR" in appendix A of this
manual.
62 CLAS0001 Cause: Internal State Error.
Action: See "Submitting an SR" in appendix A of this
manual.
63 CLAS0002 Cause: Link State Error.
Action: See "Submitting an SR" in appendix A of this
manual.
64 CLAS0002 Cause: Subsystem (NS Transport) specified an invalid
link.
Action: See "Submitting an SR" in appendix A of this
manual.
65 CLAS0005 Cause: DTC link was closed successfully.
Action: None. (This is just an informative log.)
66 CLAS0005 Cause: DTC link was closed while it was in a bad
state.
Action: Check status of X.25 card on DTC.
67 CLAS0005 Cause: DTC link was opened successfully.
Action: None.
68 CLAS0005 Cause: HP 3000 link failure occurred while attempting
to shut down the DTC link.
Action: Check status of LAN hardware.
69 CLAS0005 Cause: Contact with DTC was lost while attempting to
shut down the DTC link.
Action: Check status of DTC.
70 CLAS0005 Cause: Link went down abnormally during shutdown.
Action: Check status of X.25 card on DTC.
71 CLAS0002 Cause: RLM could not release a semaphore.
Action: See "Submitting an SR" in appendix A of this
manual.
73 CLAS0002 Cause: RLM's port is out of message frames.
Action: See "Submitting an SR" in appendix A of this
manual.
74 CLAS0002 Cause: RLM could not release message frame.
Action: See "Submitting an SR" in appendix A of this
manual.
76 CLAS0002 Cause: RLM could not get a semaphore (PARM =
'netfc_get' status).
Action: See "Submitting an SR" in appendix A of this
manual.
77 CLAS0001 Cause: Internal error within RLM.
Action: See "Submitting an SR" in appendix A of this
manual.
78 CLAS0001 Cause: Internal error within RLM.
Action: See "Submitting an SR" in appendix A of this
manual.
80 CLAS0003 Cause: HP 3000 could open link on DTC.
Action: Check error messages on console to determine
problem.
82 CLAS0002 Cause: RLM could not release semaphore pool.
Action: See "Submitting an SR" in appendix A of this
manual.
83 CLAS0002 Cause: RLM could not release semaphore pool.
Action: See "Submitting an SR" in appendix A of this
manual.
84 CLAS0002 Cause: RLM could not free buffer.
Action: See "Submitting an SR" in appendix A of this
manual.
85 CLAS0002 Cause: RLM could not delete semaphore pool.
Action: See "Submitting an SR" in appendix A of this
manual.
88 CLAS0004 Cause: Link went down in an error condition.
Action: Check the status of the DTC.
90 CLAS0002 Cause: RLM could not release semaphore.
Action: See "Submitting an SR" in appendix A of this
manual.
92 CLAS0005 Cause: DTC Link has gone down.
Action: Check the DTC X.25 card status.
93 CLAS0005 Cause: X.25 Level3 Protocol on DTC is ready.
Action: None.
94 CLAS0003 Cause: X.25 Level3 Protocol on DTC is not ready.
Action: Check the status of the DTC.
95 CLAS0003 Cause: Host has lost contact with DTC.
Action: Check status of DTC.
96 CLAS0003 Cause: Host has successfully communicated with DTC,
but X.25 level 3 protocol on DTC is not ready.
Action: Check status of X.25 protocol on DTC.
Possible causes include bad/disconnected cable between
DTC and switch/X.25 network, or the switch/X.25
network is down. When problem is corrected, HP 3000
will display additional logging messages and the
network will be usable.
100 CLAS0002 Cause: Could not create the RLM's Port Data Area
(PARM = 'create_object' status). Available virtual
space may have been exhausted.
Action: Contact your Hewlett-Packard representative
and/or see "Submitting an SR" in appendix A of this
manual.
101 CLAS0002 Cause: Could not obtain plabel for NL.PUB.SYS
procedure 'remote_link_manager.' Possible software
installation problem (PARM = status returned by
'hpgetsysplabel').
Action: Check the status of the DTC.
102 CLAS0002 Cause: Could not create the port for the RLM server
(PARM = status returned from 'create_port').
Action: See "Submitting an SR" in appendix A of this
manual.
103 CLAS0002 Cause: Could not create the port for the RLM server
(PARM = status returned from 'create_port').
Action: See "Submitting an SR" in appendix A of this
manual.
104 CLAS0003 Cause: Could not open AFCP protocol module (PARM =
status returned from 'mcm_module_config').
Action: Check X.25 and DTS Link configuration. If no
problem is found, see "Submitting an SR" in appendix A
of this manual.
105 CLAS0001 Cause: Could not send a message to the RLM server.
(PARM = status returned from 'send_msg'.)
Action: See "Submitting an SR" in appendix A of this
manual.
106 CLAS0002 Cause: Could not obtain information on per process
port (PARM = status returned from 'port_info').
Action: See "Submitting an SR" in appendix A of this
manual.
107 CLAS0001 Cause: Error encountered while receiving information
from RLM Server (PARM = status returned by
'extend_receive').
Action: See "Submitting an SR" in appendix A of this
manual.
108 CLAS0001 Cause: Message received on process port if not the
expected type.
Action: See "Submitting an SR" in appendix A of this
manual.
109 CLAS0002 Cause: Link buffer size is too small.
Action: Check X.25 and DTC Link configuration. If no
problems are found, see "Submitting an SR" in appendix
A of this manual.
110 CLAS0003 Cause: Could not open the file NMCONFIG.PUB.SYS (PARM
= status returned by 'nmconfopen').
Action: Check the nmconfig.pub.sys with the program
'FSCHECK'. If no obvious problem is found, see
"Submitting an SR" in appendix A of this manual.
111 CLAS0003 Cause: Could not read the Node Name from
NMCONFIG.PUB.SYS (PARM = status returned by
'nmconfgetdata').
Action: Add nodename to configuration.
112 CLAS0003 Cause: RLM could not close NMCONFIG.PUB.SYS (PARM =
status returned by 'nmconfclose').
Action: See "Submitting an SR" in appendix A of this
manual.
113 CLAS0002 Cause: Could not create the RLM's inbound buffer pool
(PARM = status returned from 'bmgr_create_pool').
Action: Check configuration file for excessive buffer
configuration. Reduce the number of buffers if
possible. If no problems are found, see "Submitting
an SR" in appendix A of this manual.
114 CLAS0002 Cause: Could not release the RLM's inbound buffer
pool (PARM = status returned by 'bmgr_delete_pool').
Action: See "Submitting an SR" in appendix A of this
manual.
115 CLAS0003 Cause: RLM could not deconfigure AFCP protocol module
(PARM = status returned by 'mcm_module_config').
Action: See "Submitting an SR" in appendix A of this
manual.
116 CLAS0003 Cause: RLM could not release plabel for
'remote_link_manager' (PARM = status returned by
'hprelsysplabel').
Action: See "Submitting an SR" in appendix A of this
manual.
117 CLAS0003 Cause: RLM could not delete the RLM's entry from the
CM port dictionary (PARM = status returned by
'dict_delete').
Action: See "Submitting an SR" in appendix A of this
manual.
118 CLAS0002 Cause: RLM could not create the outbound buffer pool
(PARM = status returned by 'bmgr_create_pool').
Action: Check configuration file for excessive buffer
configuration. Reduce the number of buffers if
possible. If no problems are found, see "Submitting
an SR" in appendix A of this manual.
119 CLAS0003 Cause: RLM could not reset subqueue mask (PARM =
status returned by 'change_subqueue').
Action: See "Submitting an SR" in appendix A of this
manual.
120 CLAS0001 Cause: RLM could not update port dictionary (PARM =
status returned by 'dict_update').
Action: See "Submitting an SR" in appendix A of this
manual.
121 CLAS0001 Cause: RLM could not update port dictionary (PARM =
status returned by 'dict_update').
Action: See "Submitting an SR" in appendix A of this
manual.
122 CLAS0003 Cause: RLM could not delete the outbound buffer pool
(PARM = status returned by 'bmgr_delete_pool').
Action: See "Submitting an SR" in appendix A of this
manual.
123 CLAS0003 Cause: RLM could purge its port (PARM = status
returned by 'purge_port').
Action: See "Submitting an SR" in appendix A of this
manual.
124 CLAS0003 Cause: RLM could not release its port data area
object (PARM = status returned by 'release_object').
Action: See "Submitting an SR" in appendix A of this
manual.
125 CLAS0004 Cause: RLM has been created (PARM = RLM's port id).
Action: None.
126 CLAS0004 Cause: RLM has been shutdown.
Action: None.