Remote Link Manager Logging Location Codes

CAUSE: RLM's data structures are corrupted.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Send_msg procedure returned a bad status to the RLM.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Link Error occurred in unexpected state.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not rendezvous (`bind') with the MCM.

ACTION: Check the LAN hardware on the HP 3000. If no problem is found, see Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal state mismatch within the RLM module.

ACTION: See Appendix A “Submitting an SR ” of this manual.

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 Appendix A “Submitting an SR ” of this manual.

CAUSE: Either the RLM or code that it invoked encountered an unexpected trap.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not get a buffer to send an outbound packet (PARM = Status returned by 'bmgr_get_buffer').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not release some internal resources (PARM = Status returned by 'new_release_table_entry').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM attempted to release a resource that had already been released.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM received a connect reply message from the link that it did not recognize.

ACTION: See Appendix A “Submitting an SR ” of this manual.

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 Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM's data structures are corrupted.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not release internal resources.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM received disconnect reply that did not match any transaction in progress.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: State mismatch within RLM's data structures.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM received an inbound data packet over a connection that is down.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not write outbound packet to buffer.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not read buffer containing inbound packet.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Mismatch in states between the DTC and the HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual. (Make sure a dump is taken of both the DTC and the HP 3000.)

CAUSE: Mismatch in states between DTC and HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual. (Make sure a dump is taken of both the DTC and the HP 3000.)

CAUSE: Mismatch in states between the DTC and the HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual. (Make sure a dump is taken of both the DTC and the HP 3000.)

CAUSE: Mismatch in states between the DTC and the HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual. (Make sure a dump is taken of both the DTC and the HP 3000.)

CAUSE: DTC returned bad status during link shutdown (PARM = status returned by DTC).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Subsystem (NS Transport) specified invalid link.

ACTION: See Appendix A “Submitting an SR ” of this manual.

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.

CAUSE: Disconnect reply received from linkn contained bad status.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Subsystem specified a bad parameter in a connect or disconnect request.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Control mismatch between DTC and HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual. (Make sure a dump is taken of both the DTC and the HP 3000.)

CAUSE: DTC sent bad packet to HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual. (Make sure a dump is taken of both the DTC and the HP 3000.)

CAUSE: Could not separate ('unbind') with link.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM attempted to send on a connection that was down.

ACTION: See Appendix A “Submitting an SR ” of this manual. (Make sure a dump is taken of both the DTC and the HP 3000.)

CAUSE: Close request received while resources were outstanding.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Received packet from link on unknown connection.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not free a buffer.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not free a buffer.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: State mismatch between DTC and Host.

ACTION: See Appendix A “Submitting an SR ” of this manual. (Make sure a dump is taken of both the DTC and the HP 3000.)

CAUSE: DTC sent unknown packet to HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual. (Make sure a dump is taken of both the DTC and the HP 3000.)

CAUSE: Data Structure state mismatches detected while processing a link failure.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM's data structures are corrupted.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM's data structures are corrupted.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: A shutdown occurred with resources outstanding.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not release a semaphore.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM data structures are in an invalid state for the event.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Unexpected status sent by DTC.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Interface problem between DTC and HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Link sent a disconnect event for an unknown connection.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: AFCP connection is in an invalid state for the event.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: DTC sent an invalid packet to the HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The DTC sent an invalid packet to the HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: The DTC sent bad status to HP 3000.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not find the expected timer message.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not release timer resource.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not set a timer.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: State mismatch within RLM.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Could not release timer.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Invalid message received for current state.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Link has gone down.

ACTION: Run appropriate diagnostics. If no error is found, see Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal State Error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Link State Error.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Subsystem (NS Transport) specified an invalid link.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: DTC link was closed successfully.

ACTION: None. (This is just an informative log.)

CAUSE: DTC link was closed while it was in a bad state.

ACTION: Check status of X.25 card on DTC.

CAUSE: DTC link was opened successfully.

ACTION: None.

CAUSE: HP 3000 link failure occurred while attempting to shut down the DTC link.

ACTION: Check status of LAN hardware.

CAUSE: Contact with DTC was lost while attempting to shut down the DTC link.

ACTION: Check status of DTC.

CAUSE: Link went down abnormally during shutdown.

ACTION: Check status of X.25 card on DTC.

CAUSE: RLM could not release a semaphore.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM's port is out of message frames.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not release message frame.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not get a semaphore (PARM = 'netfc_get' status).

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal error within RLM.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Internal error within RLM.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: HP 3000 could open link on DTC.

ACTION: Check error messages on console to determine problem.

CAUSE: RLM could not release semaphore pool.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not release semaphore pool.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not free buffer.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not delete semaphore pool.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Link went down in an error condition.

ACTION: Check the status of the DTC.

CAUSE: RLM could not release semaphore.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: DTC Link has gone down.

ACTION: Check the DTC X.25 card status.

CAUSE: X.25 Level3 Protocol on DTC is ready.

ACTION: None.

CAUSE: X.25 Level3 Protocol on DTC is not ready.

ACTION: Check the status of the DTC.

CAUSE: Host has lost contact with DTC.

ACTION: Check status of DTC.

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.

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 Appendix A “Submitting an SR ” of this manual.

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.

CAUSE: Could not create the port for the RLM server (PARM = status returned from 'create_port').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Could not create the port for the RLM server (PARM = status returned from 'create_port').

ACTION: See Appendix A “Submitting an SR ” of this manual.

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 Appendix A “Submitting an SR ” of this manual.

CAUSE: Could not send message to the RLM server. (PARM = status returned from 'send_msg').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Could not obtain information on per process port (PARM = status returned from 'port_info').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Error encountered while receiving information from RLM Server (PARM = status returned by 'extend_receive').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Message received on process port if not the expected type.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: Link buffer size is too small.

ACTION: Check X.25 and DTC Link configuration. If no problems are found, see Appendix A “Submitting an SR ” of this manual.

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 Appendix A “Submitting an SR ” of this manual.

CAUSE: Could not read the Node Name from NMCONFIG.PUB.SYS (PARM = status returned by 'nmconfgetdata').

ACTION: Add nodename to configuration.

CAUSE: RLM could not close NMCONFIG.PUB.SYS (PARM = status returned by 'nmconfclose').

ACTION: See Appendix A “Submitting an SR ” of this manual.

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 Appendix A “Submitting an SR ” of this manual.

CAUSE: Could not release the RLM's inbound buffer pool (PARM = status returned by 'bmgr_delete_pool').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not deconfigure AFCP protocol module (PARM = status returned by 'mcm_module_config').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not release plabel for 'remote_link_manager' (PARM = status returned by 'hprelsysplabel').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not delete the RLM's entry from the CM port dictionary (PARM = status returned by 'dict_delete').

ACTION: See Appendix A “Submitting an SR ” of this manual.

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 Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not reset subqueue mask (PARM = status returned by 'change_subqueue').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not update port dictionary (PARM = status returned by 'dict_update').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not update port dictionary (PARM = status returned by 'dict_update').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not delete the outbound buffer pool (PARM = status returned by 'bmgr_delete_pool').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could purge its port (PARM = status returned by 'purge_port').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM could not release its port data area object (PARM = status returned by 'release_object').

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: RLM has been created (PARM = RLM's port id).

ACTION: None.

CAUSE: RLM has been shutdown.

ACTION: None.