SDLC Link Driver Error Messages

MPE documents

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: An incorrect version of the download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is installed.

ACTION: Check the version of the download file with NMMAINT and call your Hewlett-Packard support contact if it is incorrect.

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: An incorrect version of the download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is installed.

ACTION: Check the version of the download file with NMMAINT and call your Hewlett-Packard support contact if it is incorrect.

CAUSE: A catastrophic internal resource error was found.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The host system is transmitting data before the HP e3000 sends a final bit in its frame to relinquish control of the line.

ACTION: Run the SNACONTROL STATUS command, and check the Frames Retransmitted value in the link-level status information (see Chapter 6 "MPE Commands" of this manual). If the value is not zero, ensure that the REPLYTO operand of the GROUP macro in the IBM host's ACF/NCP generation is large enough to account for all network delays

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: Bad PSI hardware.

ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: Bad PSI hardware.

ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: Bad PSI hardware.

ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: Bad PSI hardware.

ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: Bad PSI hardware.

ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: An incorrect version of the download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is installed.

ACTION: Check the version of the download file with NMMAINT and call your Hewlett-Packard support contact if it is incorrect.

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: An incorrect version of the download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is installed.

ACTION: Check the version of the download file with NMMAINT and call your Hewlett-Packard support contact if it is incorrect.

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: An incorrect version of the download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is installed.

ACTION: Check the version of the download file with NMMAINT and call your Hewlett-Packard support contact if it is incorrect.

CAUSE: The download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupt.

ACTION: Replace the download file from your latest system update tape.

CAUSE: An incorrect version of the download file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is installed.

ACTION: Check the version of the download file with NMMAINT and call your Hewlett-Packard support contact if it is incorrect.

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Bad PSI hardware.

ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.

CAUSE: Wrong path name in NMMGR.

ACTION: Use NMMGR or the configuration file critical summary to verify that the configured Physical Path is correct.

CAUSE: Wrong card type.

ACTION: Verify that the target card is a PSI card.

CAUSE: Bad PSI hardware.

ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.

CAUSE: Wrong path name in NMMGR.

ACTION: Use NMMGR or the configuration file critical summary to verify that the configured Physical Path is correct.

CAUSE: Wrong card type.

ACTION: Verify that the target card is a PSI card.

CAUSE: The version of the PSI is not compatible with this driver.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Bad PSI hardware.

ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.

CAUSE: Unknown.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Bad PSI hardware.

ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.

CAUSE: Bad PSI hardware.

ACTION: Your Hewlett-Packard support contact will have to run diagnostics on the PSI.

CAUSE: The driver was manually instructed to dump via diagnostic utilities, but the driver had not encountered previous errors.

ACTION: If the dump was taken as a snapshot of a problem, call your Hewlett-Packard support contact, and save the dump file to show to the HP person.

CAUSE: The dump module WANDMPSURRVERS is missing.

ACTION: Run NMMAINT to verify that the dump module is present.

CAUSE: The driver encountered an error while trying to produce a dump. The driver has unlocked itself and reported to upper levels the error which originally caused the dump attempt; these levels will now destroy the driver. Any dump file produced is probably incomplete.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: A message received by the driver was not recognized or processing of it could not begin. It also is possible the source port is not operating with the required capabilities. The message was logged and dropped.

ACTION: The diagnostic system log file should contain a partial image of the ignored message. Write down the information from this log file as well as the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Top-plane Activity Block (TAB) internal data structures are used whenever the driver tries to start new hardware activity. A limited number of these data structures are available. Unexpected use of an incorrect port and subqueues might have created excessive pending hardware activity. This problem can also occur if a buffer manager buffer could not be obtained.

ACTION: Unsupported programs must not contact the driver through incorrect subqueues. This problem should produce a dump. Keep the dump file along with the error information displayed on the console, call your Hewlett-Packard support contact, and submit an CR.

CAUSE: The hardware was successfully downloaded, but the downloaded code is for a different driver. A download file might have been incorrectly renamed to have the name of the file expected by the driver, or your download file or installed driver might be extremely old and not matched.

ACTION: Run NMMAINT to verify the version of the download file (PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS) and driver (WANSDLCVERS). If the file is incorrect, try to restore a copy from a system backup tape. If this does not solve the problem, you might have to update your system and download file. Call your Hewlett-Packard support contact.

CAUSE: The hardware was successfully downloaded, but the revision of the download file cannot be used with the version of the corresponding installed driver because their interfaces are incompatible.

ACTION: Ensure that the latest download file (PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS) was restored during a recent system update. If not, try restoring the file from a system backup tape. If this does not solve the problem, you might have to update your system and download file. Call your Hewlett-Packard support contact.

CAUSE: Terminating user programs have not freed buffers or buffer pools they were using.

ACTION: Warmstart the system and correct the user programs.

CAUSE: Some other process has obtained buffers reserved for use by the driver while the driver was trying to initialize itself.

ACTION: Try restarting the driver. If repeated link restarts fail, a system dump will be required. Call your Hewlett-Packard support contact.

CAUSE: The driver tried to free memory that the buffer manager did not recognize as a valid buffer because of a driver problem or memory data corruption. Also, a problem somewhere might have caused the driver to try to free a buffer that was not in use

ACTION: A system dump will probably be required. Call your Hewlett-Packard support contact.

CAUSE: A call to obtain a timer resource returned in error. Too many timers might be in use.

ACTION: If you suspect your system might be low on timer resources because of heavy loading, try restarting the link later. If repeated attempts fail, try warmstarting your system. If the problem continues, a system dump will be required. Call your Hewlett-Packard support contact.

CAUSE: The system rejected an attempt by the driver to reset a timer supposedly owned by the driver. Memory data corruption might have occurred.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The driver tried to free a timer that was not recognized by the system as a valid timer. Memory data corruption might have occurred.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The driver could not obtain a reply message frame from the source port of a newly-arrived request message, or from a transport port in the case of a driver-detected asynchronous event. If the system is operating well otherwise, modules trying to communicate with the driver might not be operating with the required capabilities.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: A call to the system message send routine returned in error. The destination port might belong to a process that no longer exists or is not operating with the required capabilities.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: A call to the system message freeing routine returned in error. The port might belong to a process that no longer exists or is not operating with the required capabilities. Also, the message frame might not have been recognized by the system as a valid message frame.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The system rejected an attempt by the driver to locate message frames on its own port. Memory data corruption might have occurred.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The driver tried to enter a state that it should never be able to get into, and ceased operations. Memory data corruption, a driver bug, or a problem with the execution priorities of the driver or its hardware might exist. The hardware might also be confused.

ACTION: This problem should produce a dump. Keep the dump along with the error information displayed on the console, call your Hewlett-Packard support contact, and submit an CR.

CAUSE: The driver was notified that power returned after a power failure of any duration.

ACTION: The driver is not capable of recovering from power failures, and modem connections were probably lost. Restart the link.

CAUSE: The driver had to reject a request message because it had previously stopped working for another reason. The rejected request cannot be processed while the driver is not working.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The driver received a request message during a short time interval after shutdown completed, but before the driver's port had been destroyed by the system. The driver should not be receiving new requests after shutdown, and it cannot successfully complete them.

ACTION: If this problem occurs repeatedly, call your Hewlett-Packard support contact.

CAUSE: The hardware was not ready to process a request message that required hardware participation.

ACTION: Retry the request at a later time. If the problem continues, call your Hewlett-Packard support contact.

CAUSE: The driver could not obtain enough context storage to begin processing a request, so the request was rejected. Unexpected use of incorrect port subqueues might have created excessive pending hardware activity.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The driver received a sequencing message at the wrong time. This was a startup, shutdown, or dump control message that arrived out of sequence.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The driver recognized a request message but the feature it requested is not applicable to that driver. The message descriptor was known but the message or its subfunction codes are not implemented.

ACTION: Call your Hewlett-Packard support contact and explain what you were trying to do.

CAUSE: The path to the hardware might not be configured correctly.

ACTION: Use NMMGR or the configuration file critical summary to ensure that the configured Physical Path is correct for the slot the PSI is in.

CAUSE: The physical path to the hardware might be faulty, or a previously undetected hardware failure might have occurred since system startup.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The configuration buffer that was passed to the driver during startup was not correctly formatted for the driver it was sent to. That driver did not find its own subsystem number in the expected buffer field.

ACTION: Run NMMAINT to verify that the software versions between the driver (WANSDLCVERS) and module configurator (WANMCVERS) are correct. Also check your configuration screens, and if necessary, restore NMCONFIG.PUB.SYS from a system backup tape. If the problem continues, call your Hewlett-Packard support contact.

CAUSE: Data was requested from the driver but the length of the buffer specified in the request was too small to accept all of the data. The driver is not capable of returning partial data. The driver also imposes a minimum size limit on trace buffers.

ACTION: If the problem occurred when starting a trace, try specifying a larger trace buffer size. A version mismatch between your driver (WANSDLCVERS) and other supporting software might exist; call your Hewlett-Packard support contact.

CAUSE: The driver received a trace disable request when tracing was already off. The trace manager module should not have passed the request to the driver when tracing was off.

ACTION: This is intended as a warning. You do not have to turn tracing off when it is not on.

CAUSE: The driver received a trace enable request when tracing was already on. The trace manager module should not have passed the request to the driver when tracing was on. The driver does not support altering the active trace level in this way.

ACTION: This is intended as a warning. You cannot turn tracing on when it is already on.

CAUSE: The memory address of an open download file must be in a configuration buffer passed during startup. However, the driver found an address of zero, which is an invalid address. The module configurator should not have sent the configure message if it could not open the download file. Also, configuration buffer formats might be mismatched.

ACTION: Run NMMAINT to verify the versions of the driver (WANSDLCVERS), module configurator (WANMCVERS), and download file (PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS). If the problem cannot be solved by using this information, call your Hewlett-Packard support contact.

CAUSE: The buffer pool ID of a pool that is to be used for read/write data communications line frames must be in a configuration buffer passed during startup. However, the driver found an ID of zero, which is an invalid ID. The transport should not have invoked the module configurator if the buffer pool could not be opened. Also, configuration buffer formats might be mismatched.

ACTION: See whether the transport reported any initialization errors. Run NMMAINT to verify the versions of the driver (WANSDLCVERS), module configurator (WANMCVERS), and download file (PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS). If the problem cannot be solved by using this information, call your Hewlett-Packard support contact.

CAUSE: The buffer pool ID of a pool that is to be used for PSI tracing and other internal I/O must be in a configuration buffer passed during startup. However, the driver found an ID of zero, which is an invalid ID. The module configurator should not have sent the configure message if the buffer pool could not be opened. Also, configuration buffer formats might be mismatched.

ACTION: Run NMMAINT to verify the versions of the driver (WANSDLCVERS), module configurator (WANMCVERS), and download file (PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS). If the problem cannot be solved by using this information, call your Hewlett-Packard support contact.

CAUSE: The driver startup timer expired between the time the driver received its configure message and the time it completed all hardware and software startup. The PSI is probably hung because of a hardware failure, download bug, or corrupt download data not otherwise found. Though unlikely, it also is possible that completions for driver requests were excessively delayed due to heavy system loading.

ACTION: The driver normally allows about 30 seconds for all of startup. On a heavily loaded system, this problem might appear intermittently; try restarting the link. If the problem continues, call your Hewlett-Packard support contact.

CAUSE: The driver selftest timer expired between the time the driver received its DO_BIND message and the time the hardware completed selftest. The PSI probably failed selftest so badly it was unable to report the selftest error.

ACTION: The driver normally allows about 30 seconds for selftest to complete. Your PSI hardware is probably not working. Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: This timeout should occur only if the PSI hardware hangs because of a hardware failure or a bug in the downloaded code. The driver solicited activity from the hardware "local timeout" seconds ago, and that activity has still not completed. The driver has stopped the hardware and requested a dump

ACTION: This problem should produce a dump. Submit an CR, keep the dump, and call your Hewlett-Packard support contact.

CAUSE: The driver detected an error, but did not say what type of error was found.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The DCE's level 1 signals were never enabled. Your cabling might be broken or improperly installed, or your modem might be turned off or broken.

ACTION: Check the cabling and the modem.

CAUSE: The automatic dial completed, but the level 1 connection was not established. You might have a broken cable or modem.

ACTION: Check the cabling and the modem.

CAUSE: The remote system never sent a Set Normal Response Mode (SNRM) frame with the POLL bit set.

ACTION: See whether the remote system is running. Also check the receive data line in the cabling.

CAUSE: The remote system sent a Set Normal Response Mode (SNRM) frame with the POLL bit set, but never sent a Receive Reader (RR), Receive Not Ready (RNR), or Information (I) frame.

ACTION: See whether the remote system is still running. Use NMMGR to ensure that the configured Connect Timeout value is large enough. Also, check the transmit data link in the cabling.

CAUSE: The remote system never acknowledged one or more Information (I) frames sent to it. You might have a very noisy line, or the remote system might not be running.

ACTION: See whether the remote system is still running.

CAUSE: The remote system never sent the DISConnect (DISC) frame response to the HP e3000's Request for Disconnect (RD) frame.

ACTION: See whether the remote system is still running.

CAUSE: The PSI or the backplane bus the PSI is attached to is broken.

ACTION: Call your Hewlett-Packard support contact.

CAUSE: The remote system sent an unrecognized frame before acknowledging one or more Information (I) frames sent to it.

ACTION: Call the remote system's operator to ensure that the remote system is functioning properly.

CAUSE: The remote system did not send a frame with the POLL bit set after the PSI transmitted a frame with the FINAL bit set. Either the connection to the remote system was severed or the remote system is down.

ACTION: Check your cabling and modem, ensure that the remote system is still running, and check with your phone company representative to ensure that the connection is still active.

CAUSE: The driver attempted to retransmit an Information (I) frame larger than the configured transmit retry limit. This I frame was never acknowledged by the remote system. You might have noisy lines or the remote system might have a problem.

ACTION: Check with your phone company representative to see if your phone lines are noisy, and check to see if the remote system is having problems.

CAUSE: The I frame was never acknowledged, because the frame was delayed by the network longer than the configured REPLYTO parameter on the host system.

ACTION: Check all possible network delays, and increase the REPLYTO operand of the GROUP macro in the host's ACF/NCP generation accordingly.

CAUSE: The PSI is experiencing problems.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The host system is transmitting data before the HP e3000 sends a final bit in its frame to relinquish control of the line.

ACTION: Run the SNACONTROL STATUS command, and check the Frames Retransmitted value in the link-level status information (see Chapter 6 "MPE Commands" of this manual). If the value is not zero, ensure that the REPLYTO operand of the GROUP macro in the IBM host's ACF/NCP generation is large enough to account for all network delays.

CAUSE: The level 1 connection was severed. The PSI detects this when Data Set Ready (DSR) or Clear To Send (CTS) is disabled unexpectedly.

ACTION: Ensure that your modem is still on and functional, and that the cables are connected properly. Also, check with your phone company to ensure that your line is still active.

CAUSE: In SDLC, the only PSI internal timer not noted elsewhere is the Clear To Send (CTS) timer. The CTS timer pops when the modem never enables CTS in response to the PSI enabling Request To Send (RTS).

ACTION: Ensure that your modem is still on and functional.

CAUSE: Before attempting to automatically dial, the PSI detected something wrong. Specifically, the PSI detected an active ACR line before attempting to automatically dial.

ACTION: Check your automatic dialer and the modem.

CAUSE: The configured automatic dial phone number is wrong.

ACTION: Use NMMGR or the configuration file critical summary to ensure that the Phone Number configured for the link is correct.

CAUSE: The automatic dial was not completed. This can happen when the remote system's modem is not turned on or is not functional.

ACTION: Check with the remote system to ensure that its modems are turned on and functional.

CAUSE: Your local automatic-dial modem has not been turned on.

ACTION: Turn on your local automatic-dial modem.

CAUSE: Someone else is using your automatic-dial modem.

ACTION: Check with other users of your system to see whether they are using the modem. If they are not, powercycle the modem and try again.

CAUSE: A previous user of the modem failed to disconnect from it.

ACTION: Powercycle the modem and try again. If you try again and get the same error message, your automatic-dial modem might be broken.

CAUSE: No cable is attached, a non-automatic-dial cable is attached, or a bad automatic-dial cable is attached.

ACTION: Ensure that the cable is properly attached. If it is, try another cable. If you still get this error, write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: The PSI sent an asynchronous event with bad data in it.

ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard support contact.

CAUSE: Some other process used one of the buffers reserved for the SDLC driver during the driver's initialization. This can happen when some higher priority process interrupts the driver while it is initializing, and the higher priority process gets some of the buffers reserved for the driver by the buffer manager.

ACTION: Try to start the driver again. You might have to warmstart your system. If repeated attempts fail and the warmstart fails, call your Hewlett-Packard support contact.