SDLC Link Startup Error Messages

Listed below are the messages that might occur when you are starting the SDLC linkduring messages;SDLC link startupmessages. These messages occur when the SNACONTROL START command calls the WAN_Module_Config procedure and encounters an error. Depending on the logging configuration for the SDLC Link subsystem, these messages are logged to the console, to disk, or both. The messages are logged in this format:

   Linkname        = LinkName      Event Type     = EventType

   Log Class       = LogClass       Path           = Path

   Error Num       = ErrorNumber    Status         = Status

(Note that LinkName is the same as the name of the node.) The messages are listed below in numerical order according to ErrorNumber.

1

MESSAGE: The link type is not SDLC or LAP-B or RJEBSC.
CAUSE: The caller of this module did not set the link type to SDLC, LAP-B, or RJE BSC. For an SDLC link, the link type must be set to SDLC.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

2

MESSAGE: Could not open NMCONFIG.PUB.SYS.
CAUSE: The configuration file NMCONFIG.PUB.SYS was purged or renamed.
ACTION: Restore the file from a backup tape and try to start the SDLC link again.
CAUSE: The configuration file NMCONFIG.PUB.SYS might be opened with exclusive access.
ACTION: Wait for the program or process that has this file opened exclusively to close it.

3

MESSAGE: Link data not found in NMCONFIG.PUB.SYS.
CAUSE: The link data was not found in the configuration file NMCONFIG.PUB.SYS.
ACTION: Use NMMGR to create the link data for the link you are trying to start (use the "SNA Node Configuration: SDLC Link Data" screen), and try to start the SDLC link again.

4

MESSAGE: Could not close NMCONFIG.PUB.SYS.
CAUSE: The configuration file NMCONFIG.PUB.SYS could not be closed. This did not prevent the link from starting, but it is worth noting because this should not happen. The file system integrity might be questionable.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

5

MESSAGE: Could not open download file.
CAUSE: The file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS was purged or renamed.
ACTION: Restore the file from a backup tape and try to start the SDLC link again.
CAUSE: The file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS might be opened with exclusive access.
ACTION: Wait for the program or process that has this file opened exclusively to close it.

6

MESSAGE: Could not determine size of download file.
CAUSE: The file PSISDLC0.PUB.SYS or PSISDLC1.PUB.SYS is corrupted.
ACTION: Restore the file from a backup tape and try to start the SDLC link again.

7

MESSAGE: Could not freeze download file in memory.
CAUSE: Memory shortage problems are occurring.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

8

MESSAGE: Could not open trace file TraceFileName.
CAUSE: The indicated trace file might be invalid.
ACTION: Try specifying a different file name or let it default to NMTCnnnn.PUB.SYS (nnnn is the next available four-digit number).
CAUSE: The indicated trace file might be opened with exclusive access.
ACTION: Wait for the program or process that has the trace file opened exclusively to close it.

9

MESSAGE: Could not start trace.
CAUSE: Many causes exist; the Status field provides more-detailed information about the specific cause of the problem.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact. You also can try running without tracing on.

10

MESSAGE: Could not stop trace.
CAUSE: Tracing might have been turned off with the SNACONTROL TRACEOFF command, but the link software status indicates that it was on.
ACTION: Ignore this problem unless you are experiencing other problems. If you are, write down the error information displayed on the console and call your Hewlett-Packard support contact.

11

MESSAGE: Could not freeze the driver configuration data.
CAUSE: Memory shortage problems are occurring.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

12

MESSAGE: Could not send the configuration message.
CAUSE: An internal system ports problem has occurred.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

13

MESSAGE: Could not receive the config reply message.
CAUSE: An internal system ports problem has occurred.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

14

MESSAGE: Timeout waiting for the config reply message.
CAUSE: The link software or the PSI card could not be configured.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

15

MESSAGE: Received message was not the config reply.
CAUSE: A wrong message was left on the process port data communications subqueue.
ACTION: Try to start the SDLC link again. If the problem continues, write down the error information displayed on the console and call your Hewlett-Packard support contact.

16

MESSAGE: Link configuration data is invalid.
CAUSE: The configuration information has been corrupted.
ACTION: Use NMMGR to recreate the link data for the node (use the "SNA Node Configuration: SDLC Link Data" screen), and try to start the SDLC link again. If this does not correct the problem, write down the error information displayed on the console and call your Hewlett-Packard support contact.

17

MESSAGE: Could not unfreeze the configuration data.
CAUSE: Memory problems are occurring.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

18

MESSAGE: Unable to obtain dump/diag ports.
CAUSE: The Diagnostic User Interface (DUI) software or the Network Dump Process was not installed properly.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

19

MESSAGE: Could not create the auxiliary buffer pool.
CAUSE: An internal error has occurred.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

20

MESSAGE: Could not create or bind with the driver.
CAUSE: (Status = C3xx00D8) The wrong path number is configured for the installed PSI card.
ACTION: Use NMMGR to correct the Physical Path for the link.
CAUSE: Status = CDxx00D5) The card for the configured path number is bad.
ACTION: Use NMMGR or the configuration file critical summary to check that the Physical Path configured for the link corresponds to a good PSI card. To determine whether the PSI card is good, your Hewlett-Packard support contact will have to run diagnostics on the PSI.
CAUSE: (Status = DAxx00D5) No card is in the slot for the path number configured for the link.
ACTION: Use NMMGR or the configuration file critical summary to check the configured Physical Path for the link, and correct it if necessary. Or, call your Hewlett-Packard support contact to install a PSI card.
CAUSE: (Status = E0xx00D5) The bus converter is not configured.
ACTION: Your local Hewlett-Packard support contact will have to check the bus converter configuration in SYSGEN and reconfigure it, if necessary (for Series 950 only).
CAUSE: (Status = FAxx00D8) The I/O subsystem still has the card configured and marked active.
ACTION: First, try shutting down the link. If the problem continues, restart the system. If this does not correct the problem, write down the error information displayed on the console and call your Hewlett-Packard support contact.

21

MESSAGE: Could not add the link name to the link table.
CAUSE: Another link with the same name has already started.
ACTION: Try shutting down the link and starting it up again.
CAUSE: The link table does not exist.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.
CAUSE: The link table has been corrupted.
ACTION: Restart the system.

22

MESSAGE: Could not unfreeze the download file DownloadFileName.
CAUSE: Memory problems are occurring.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

23

MESSAGE: Could not close download file DownloadFileName.
CAUSE: File system problems are occurring.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

24

MESSAGE: Manager entry not found in the system library.
CAUSE: The link software was not installed properly.
ACTION: Write down the error information displayed on the console and call your Hewlett-Packard support contact.

25

MESSAGE: The link has already been started.
CAUSE: Another link of the same name is currently active. You cannot start the same link twice.
ACTION: Stop the link and try starting it up again. If you cannot stop the link, restart the system.

26

MESSAGE: The Path Name does not point to a PSI card.
CAUSE: The wrong path number is configured for the installed PSI card.
ACTION: Use NMMGR to correct the Physical Path for the link, or call your Hewlett-Packard support contact to install a PSI card.

SDLC Link Startup Error Messages

Technical documentation

» Table of Contents

» Index