SNACONTROL Error Messages
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| Index |
| MESSAGE: SNA COMMAND ESCAPE CODE: SUBSYS=SubsysID INFO=ErrorNum. (SNACIERR 1) |
| Level: SNACIERR 1
CAUSE: This message provides troubleshooting information. It is added to many SNA command interpreter (CI) error messages and aids in locating the possible source of a problem. ACTION: None. |
| MESSAGE: SNA TRANSPORT NOT PROPERLY INSTALLED. CHECK VERSIONS. (SNACIERR 2) |
| Level: SNACIERR 2
CAUSE: A version check of SNA Transport failed because of differences in module versions or because of missing modules. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: TRACE ALREADY IN PROGRESS FOR THIS ENTITY. (SNACIERR 3) |
| Level: SNACIERR 3
CAUSE: The SNACONTROL TRACEON command was issued for an LUName or link that is already executing tracing. ACTION: If you are turning on intrinsic tracing, ensure that you are specifying the correct LUName in the SNACONTROL TRACEON command. If you are, issue the SNACONTROL STATUS command to see whether tracing is already on for that LU. If you are turning on link-level tracing, ensure that you are specifying the LINKTRACE parameter in the SNACONTROL TRACEON command. |
| MESSAGE: TRACE NOT IN PROGRESS FOR THIS ENTITY. (SNACIERR 4) |
| Level: SNACIERR 4
CAUSE: The SNACONTROL TRACEOFF command was issued for an LUName or link that is not executing tracing. ACTION: If you are turning off intrinsic tracing, ensure that you are specifying the correct LUName in the SNACONTROL TRACEOFF command. If you are, issue the SNACONTROL STATUS command to see whether tracing is already off for that LU. If you are turning off link-level tracing, ensure that you are specifying the LINKTRACE parameter in the SNACONTROL TRACEOFF command. CAUSE: The SNACONTROL TRACEOFF command was issued after the SNA node has started to shut down. ACTION: None; tracing is automatically turned off when a node is shutting down. |
| MESSAGE: COULDN'T OPEN TRACE FILE. (SNACIERR 5) |
| Level: SNACIERR 5
CAUSE: An illegal TraceFile parameter was specified in an SNACONTROL START or SNACONTROL TRACEON command. ACTION: Ensure that the specified TraceFile is a legal file name (see the description of the command you issued). CAUSE: The user who issued the command might not have the proper system capabilities. ACTION: Verify that the user has the proper system capabilities. CAUSE: A trace manager problem might exist. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T CLOSE TRACE FILE. (SNACIERR 6) |
| Level: SNACIERR 6
CAUSE: A trace manager problem might exist. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T GET NODE CONFIGURATION DATA. (SNACIERR 7) |
| Level: SNACIERR 7
CAUSE: The network manager was unable to get the configuration data for the node from the NMCONFIG.PUB.SYS configuration file. ACTION: Use NMMGR to verify that the configuration file is valid. If it is, write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T OPEN CONFIGURATION FILE. (SNACIERR 8) |
| Level: SNACIERR 8
CAUSE: The NMCONFIG.PUB.SYS configuration file does not exist. ACTION: Use NMMGR to verify that the configuration file exists. If it does, write down the circumstances and call your Hewlett-Packard support contact. CAUSE: The NMCONFIG.PUB.SYS configuration file has been corrupted, and the file system cannot open it. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: NODE SPECIFIED NOT ACTIVE. (SNACIERR 9) |
| Level: SNACIERR 9
CAUSE: An SNACONTROL command was issued for an SNA node that is not active. The node either was never started or has been stopped. ACTION: Issue the SNACONTROL STATUS command to see whether the node is active. If the node is not active, issue the SNACONTROL START command for the node. Once the node is active, reissue the first SNACONTROL command. If the error still occurs, write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: NODE SPECIFIED IS ALREADY ACTIVE. (SNACIERR 10) |
| Level: SNACIERR 10
CAUSE: The SNACONTROL START command was issued for a node that is already active. ACTION: Ensure that you are specifying the correct NodeName in the SNACONTROL START command. |
| MESSAGE: NODE SPECIFIED NOT CONFIGURED. (SNACIERR 11) |
| Level: SNACIERR 11
CAUSE: No configuration data was found for the SNA node specified in the command. ACTION: Use NMMGR or the configuration file critical summary to verify that the configuration file NMCONFIG.PUB.SYS contains data for the specified node. If it does, ensure that the SNACONTROL command was issued correctly. |
| MESSAGE: MORE THAN ONE NODE IN CONFIGURATION. PLEASE SPECIFY. (SNACIERR 12) |
| Level: SNACIERR 12
CAUSE: An SNACONTROL command was issued without a NodeName parameter. Since more than one node is configured, the NodeName must be specified. ACTION: Reissue the command with the correct NodeName specified. |
| MESSAGE: NO SNA NODE IS CONFIGURED IN NMCONFIG.PUB.SYS. (SNACIERR 13) |
| Level: SNACIERR 13
CAUSE: An SNACONTROL START command was issued without a NodeName parameter. If this is done when the configuration file (NMCONFIG.PUB.SYS) contains data for only one node, that node is started, by default. However, no node data was found in the configuration file when the command was issued. So, the default could not be used. ACTION: Use NMMGR or the configuration file critical summary to verify that the configuration file contains data for at least one SNA node. If it does, ensure that the SNACONTROL START command was issued correctly. If the configuration file does not contain data for at least one node, configure the appropriate node and then reissue the SNACONTROL START command. |
| MESSAGE: UNABLE TO OPEN BUFFER POOL. (SNACIERR 14) |
| Level: SNACIERR 14
CAUSE: An internal system error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: UNABLE TO CREATE PORTS FOR SNA SERVERS. (SNACIERR 16) |
| Level: SNACIERR 16
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T START SNASSV PROCESS. (SNACIERR 17) |
| Level: SNACIERR 17
CAUSE: Either the SNASSV program module does not exist or an internal error has occurred. ACTION: Check the installation of SNA Transport. Use NMMAINT or the SNACONTROL VERSION command to verify that SNASSV.PUB.SYS is present and that the version is correct. If it is and the error still occurs, write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T ADD SNACSC'S PORT TO NMMON DICT. (SNACIERR 18) |
| Level: SNACIERR 18
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: UNABLE TO OBTAIN STARTUP INFO FROM SDLC. (SNACIERR 19) |
| Level: SNACIERR 19
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: UNABLE TO OPEN LINK. (SNACIERR 20) |
| Level: SNACIERR 20
CAUSE: For an SDLC link, (1) the PSI card is not installed, (2) the PSI card is installed incorrectly, or (3) the physical path is not configured. ACTION: Ensure that the PSI card is installed correctly, and use NMMGR or the configuration file critical summary to verify that the Physical Path field contains the correct information. If the error still occurs, write down the circumstances and call your Hewlett-Packard support contact. CAUSE: For an X.25 link, (1) X.25/XL System Access is not active, (2) the necessary hardware is not installed correctly, (3) the SNA/X.25 Link configuration and the X.25/XL System Access configuration are not compatible with each other, (4) no SVCs are available, or (5) the PVC number is not in the configured PVC range in the DTC X.25 configuration. ACTION: Issue the NETCONTROL command to verify the X.25 link status and start the link if necessary. When you check the link's status, verify that the X.25 Level 1 status is "connected," Level 2 is "on," and Level 3 is "ready." If the link status is correct, ensure that the SNA/X.25 Link configuration and the X.25/XL System Access configuration are compatible with each other and with the X.25 configuration on the DTC (see Chapter 2 "SNA Node and Link Configuration" of this manual). If the error still occurs, write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T OPEN LOG FILE. (SNACIERR 21) |
| Level: SNACIERR 21
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T START SNACSC PROCESS. (SNACIERR 22) |
| Level: SNACIERR 22
CAUSE: Either the SNACSC program module does not exist or an internal error has occurred. ACTION: Check the installation of SNA Transport. Use NMMAINT or the SNACONTROL VERSION command to verify that SNACSC.PUB.SYS is present and that the version is correct. If the error still occurs, write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: BAD START REPLY FROM SNACSC. (SNACIERR 23) |
| Level: SNACIERR 23
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T SEND STOP REQUEST TO SNACSC. (SNACIERR 24) |
| Level: SNACIERR 24
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: UNABLE TO ADD NODENAME TO NODE DIRECTORY. (SNACIERR 25) |
| Level: SNACIERR 25
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T RELEASE NODE DIRECTORY. (SNACIERR 26) |
| Level: SNACIERR 26
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T GET DIRECTORY INFO. (SNACIERR 27) |
| Level: SNACIERR 27
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: THE LUNAME MUST BE SPECIFIED. (SNACIERR 28) |
| Level: SNACIERR 28
CAUSE: The ROUTE, HSCB, or LURECORD parameter was specified in the SNACONTROL STATUS command, but no LUName parameter was specified. ACTION: Reissue the SNACONTROL STATUS command with the appropriate LUName parameter specified. |
| MESSAGE: COULDN'T FIND LUNAME SPECIFIED. (SNACIERR 29) |
| Level: SNACIERR 29
CAUSE: The LUName parameter specified in an SNACONTROL STATUS, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, or SNACONTROL TRACEON command could not be found in the NMCONFIG.PUB.SYS configuration file. ACTION: Ensure that the LUName is spelled correctly, and use NMMGR or the configuration file critical summary to ensure that the LU is actually configured. |
| MESSAGE: COULDN'T GET AN NCB FOR THIS SNA NODE. (SNACIERR 32) |
| Level: SNACIERR 32
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: NO SUCH ACTIVE SESSION. (SNACIERR 33) |
| Level: SNACIERR 33
CAUSE: An LUName for which no active session exists was specified in an SNACONTROL STOPSESS or SNACONTROL TRACEOFF command. ACTION: Issue the SNACONTROL STATUS command to see whether the session for the specified LUName exists. If it does, reissue the first command. If the error still occurs, write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: CAN'T SPECIFY NODENAME HERE. (SNACIERR 34) |
| Level: SNACIERR 34
CAUSE: The NodeName parameter was specified in an SNACONTROL VERSION command. NodeName is not a valid parameter for that command. ACTION: Reissue the SNACONTROL VERSION command without a NodeName parameter. |
| MESSAGE: CAN'T SPECIFY STYPE HERE. (SNACIERR 36) |
| Level: SNACIERR 36
CAUSE: The STYPE parameter was specified in an SNACONTROL command; none of the commands uses STYPE. ACTION: Reissue the command without an STYPE parameter. |
| MESSAGE: CAN'T SPECIFY STOP TYPE HERE. (SNACIERR 37) |
| Level: SNACIERR 37
CAUSE: The StopType parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STATUS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses StopType. ACTION: Reissue the command without a StopType parameter. |
| MESSAGE: CAN'T SPECIFY TRACE HERE. (SNACIERR 39) |
| Level: SNACIERR 39
CAUSE: The TRACE parameter was specified in an SNACONTROL command; none of the commands uses TRACE. ACTION: Reissue the command without a TRACE parameter. |
| MESSAGE: CAN'T SPECIFY ERROPT HERE. (SNACIERR 41) |
| Level: SNACIERR 41
CAUSE: The ERROPT parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL STATUS, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses ERROPT. ACTION: Reissue the command without an ERROPT parameter. |
| MESSAGE: CAN'T SPECIFY NCB HERE. (SNACIERR 42) |
| Level: SNACIERR 42
CAUSE: The NCB parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses NCB. ACTION: Reissue the command without an NCB parameter. |
| MESSAGE: CAN'T SPECIFY HSCB HERE. (SNACIERR 43) |
| Level: SNACIERR 43
CAUSE: The HSCB parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses HSCB. ACTION: Reissue the command without an HSCB parameter. |
| MESSAGE: CAN'T SPECIFY ROUTE HERE. (SNACIERR 44) |
| Level: SNACIERR 44
CAUSE: The ROUTE parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses ROUTE. ACTION: Reissue the command without a ROUTE parameter. |
| MESSAGE: CAN'T SPECIFY DEBUG HERE. (SNACIERR 45) |
| Level: SNACIERR 45
CAUSE: The DEBUG parameter was specified in an SNACONTROL command; none of the commands uses DEBUG. ACTION: Reissue the command without a DEBUG parameter. |
| MESSAGE: SNA SWITCH FROM COMPAT. MODE TO NATIVE MODE ERROR. (SNACIERR 46) |
| Level: SNACIERR 46
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: LINK TRACE SIO REQUEST FAILURE. (SNACIERR 47) |
| Level: SNACIERR 47
CAUSE: Link-level tracing is already on for the node. ACTION: None. CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: LINK TRACE DISABLE REQUEST FAILURE. (SNACIERR 48) |
| Level: SNACIERR 48
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: LINK TRACE FILE OPEN FAILURE. (SNACIERR 49) |
| Level: SNACIERR 49
CAUSE: An illegal TraceFile parameter was specified in an SNACONTROL START or SNACONTROL TRACEON command. ACTION: Ensure that the specified TraceFile is a valid file name (see the description of the command you issued). CAUSE: The user who issued the command might not have the proper system capabilities. ACTION: Verify that the user has node manager (NM) capabilities. CAUSE: A trace manager problem might exist. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: MAX DATA (PIU) TOO LARGE. (SNACIERR 50) |
| Level: SNACIERR 50
CAUSE: The value specified in the MAX DATA field of the "SNA Node Configuration: PU Data" screen is too large. ACTION: Enter a valid value in the MAX DATA field. CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: CAN'T SPECIFY LUNAME HERE. (SNACIERR 51) |
| Level: SNACIERR 51
CAUSE: The LUName parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, or SNACONTROL VERSION command. None of these commands uses LUName. ACTION: Reissue the command without an LUName parameter. |
| MESSAGE: CAN'T SPECIFY LINKTRACE HERE. (SNACIERR 52) |
| Level: SNACIERR 52
CAUSE: The LINKTRACE parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL STATUS, SNACONTROL STOP, SNACONTROL STOPSESS, or SNACONTROL VERSION command. None of these commands uses LINKTRACE. ACTION: Reissue the command without a LINKTRACE parameter. |
| MESSAGE: CAN'T SPECIFY NODETRACE HERE. (SNACIERR 53) |
| Level: SNACIERR 53
CAUSE: The NODETRACE parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL STATUS, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses NODETRACE. ACTION: Reissue the command without a NODETRACE parameter. |
| MESSAGE: CAN'T SPECIFY INTRINSIC HERE. (SNACIERR 54) |
| Level: SNACIERR 54
CAUSE: The INTRINSIC parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STATUS, SNACONTROL STOP, SNACONTROL STOPSESS, or SNACONTROL VERSION command. None of these commands uses INTRINSIC. ACTION: Reissue the command without an INTRINSIC parameter. |
| MESSAGE: TRACE COMMAND IGNORED. PLEASE SPECIFY TRACE TYPE. (SNACIERR 55) |
| Level: SNACIERR 55
CAUSE: The SNACONTROL TRACEOFF or SNACONTROL TRACEON command was issued, but a valid trace type was not specified. ACTION: Reissue the command with the LINKTRACE or INTRINSIC parameters. |
| MESSAGE: CAN'T SPECIFY "LINK" HERE. (SNACIERR 59) |
| Level: SNACIERR 59
CAUSE: The LINK parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK. ACTION: Reissue the command without a LINK parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=A" HERE. (SNACIERR 60) |
| Level: SNACIERR 60
CAUSE: The LINK=A parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=A. ACTION: Reissue the command without a LINK=A parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=C" HERE. (SNACIERR 61) |
| Level: SNACIERR 61
CAUSE: The LINK=C parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=C. ACTION: Reissue the command without a LINK=C parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=L" HERE. (SNACIERR 62) |
| Level: SNACIERR 62
CAUSE: The LINK=L parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=L. ACTION: Reissue the command without a LINK=L parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=S" HERE. (SNACIERR 63) |
| Level: SNACIERR 63
CAUSE: The LINK=S parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=S. ACTION: Reissue the command without a LINK=S parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=D" HERE. (SNACIERR 64) |
| Level: SNACIERR 64
CAUSE: The LINK=D parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=D. ACTION: Reissue the command without a LINK=D parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=R" HERE. (SNACIERR 65) |
| Level: SNACIERR 65
CAUSE: The LINK=R parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=R. ACTION: Reissue the command without a LINK=R parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=ALL" HERE. (SNACIERR 66) |
| Level: SNACIERR 66
CAUSE: The LINK=ALL parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=ALL. ACTION: Reissue the command without a LINK=ALL parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=CONF" HERE. (SNACIERR 67) |
| Level: SNACIERR 67
CAUSE: The LINK=CONF parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=CONF. ACTION: Reissue the command without a LINK=CONF parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=LINK" HERE. (SNACIERR 68) |
| Level: SNACIERR 68
CAUSE: The LINK=LINK parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=LINK. ACTION: Reissue the command without a LINK=LINK parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=STAT" HERE. (SNACIERR 69) |
| Level: SNACIERR 69
CAUSE: The LINK=STAT parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=STAT. ACTION: Reissue the command without a LINK=STAT parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=DIAG" HERE. (SNACIERR 70) |
| Level: SNACIERR 70
CAUSE: The LINK=DIAG parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=DIAG. ACTION: Reissue the command without a LINK=DIAG parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=RESET" HERE. (SNACIERR 71) |
| Level: SNACIERR 71
CAUSE: The LINK=RESET parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=RESET. ACTION: Reissue the command without a LINK=RESET parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=CONFIGURATION" HERE. (SNACIERR 72) |
| Level: SNACIERR 72
CAUSE: The LINK=CONFIGURATION parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=CONFIGURATION. ACTION: Reissue the command without a LINK=CONFIGURATION parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=LINKSTATE" HERE. (SNACIERR 73) |
| Level: SNACIERR 73
CAUSE: The LINK=LINKSTATE parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=LINKSTATE. ACTION: Reissue the command without a LINK=LINKSTATE parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=STATISTICS" HERE. (SNACIERR 74) |
| Level: SNACIERR 74
CAUSE: The LINK=STATISTICS parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=STATISTICS. ACTION: Reissue the command without a LINK=STATISTICS parameter. |
| MESSAGE: CAN'T SPECIFY "LINK=DIAGSTATS" HERE. (SNACIERR 75) |
| Level: SNACIERR 75
CAUSE: The LINK=DIAGSTATS parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LINK=DIAGSTATS. ACTION: Reissue the command without a LINK=DIAGSTATS parameter. |
| MESSAGE: MESSAGE CATALOG FILE (CATSNA.PUB.SYS) OPEN ERROR. (SNACIERR 76) |
| Level: SNACIERR 76
CAUSE: The SNA message catalog CATSNA.PUB.SYS is missing, or is not in the correct format. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T CREATE SNA'S PORT FACILITY PROCESS. (SNACIERR 77) |
| Level: SNACIERR 77
CAUSE: A call to Create_pfp to create SNA's port facility process during SNACSC's initialization failed. This is an internal error. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: COULDN'T GET THE PIN OF SNA'S PORT FACILITY PROCESS. (SNACIERR 78) |
| Level: SNACIERR 78
CAUSE: A call to Port_info to obtain the Process Identification Number (PIN) of SNA's port facility process failed. This is an internal error. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: BAD TRACE FILE SIZE SPECIFIED. (SNACIERR 79) |
| Level: SNACIERR 79
CAUSE: An illegal NumRecords value was specified for the TFILESIZE parameter in an SNACONTROL START or SNACONTROL TRACEON command. ACTION: Ensure that the specified NumRecords value is within the acceptable range (see the description of the command you issued). |
| MESSAGE: SNA/X.25 NOT PROPERLY INSTALLED. CHECK VERSIONS. (SNACIERR 80) |
| Level: SNACIERR 80
CAUSE: A version check of SNA/X.25 Link failed because of differences in module versions or because of missing modules. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: AN ATTEMPT TO SEE IF SNA/X.25 IS INSTALLED FAILED. (SNACIERR 81) |
| Level: SNACIERR 81
CAUSE: A call to FLabelInfo for the file SNAX25.PUB.SYS failed with a file system error. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: NMCAT.PUB.SYS OPEN FAILURE. (SNACIERR 82) |
| Level: SNACIERR 82
CAUSE: SNA Transport cannot open the message catalog NMCAT.PUB.SYS to enable the SDLC link to display link status information. ACTION: Use the MPE FLIST command to ensure that NMCAT.PUB.SYS is installed on your system. If it is, write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: LINK STATUS DISPLAY ERROR. (SNACIERR 83) |
| Level: SNACIERR 83
CAUSE: An attempt to display the X.25 link status information failed. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: CAN'T SPECIFY LURECORD HERE. (SNACIERR 84) |
| Level: SNACIERR 84
CAUSE: The LURECORD parameter was specified in an SNACONTROL AUTODIAL, SNACONTROL START, SNACONTROL STOP, SNACONTROL STOPSESS, SNACONTROL TRACEOFF, SNACONTROL TRACEON, or SNACONTROL VERSION command. None of these commands uses LURECORD. ACTION: Reissue the command without an LURECORD parameter. |
| MESSAGE: CAN'T SPECIFY FILESIZE HERE. (SNACIERR 85) |
| Level: SNACIERR 85
CAUSE: A file size was specified as a parameter to an SNACONTROL command. ACTION: Do not specify a file size as a parameter to a command. |
| MESSAGE: AN SNA LINK INTERNAL ERROR HAS OCCURRED. STATUS COMMAND NOT AVAILABLE. (SNACIERR 86) |
| Level: SNACIERR 86
CAUSE: An internal error has occurred. The SNACONTROL STATUS command cannot be executed at this time. ACTION: A memory dump will probably be required. Call your Hewlett-Packard support contact. |
| MESSAGE: ATTEMPT TO DISPLAY LINK STATUS FAILED. (SNACIERR 87) |
| Level: SNACIERR 87
CAUSE: An attempt to call the link status display procedure failed. ACTION: Use the MPE FLIST command to ensure that the file XL.PUB.SYS exists. Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: CANNOT AUTODIAL BECAUSE OF CABLING PROBLEMS. (SNACIERR 88) |
| Level: SNACIERR 88
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 attaching a different cable. If the error still occurs, write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: LOCAL AUTODIAL MODEM IS BUSY. (SNACIERR 89) |
| Level: SNACIERR 89
CAUSE: Someone else is using the local automatic-dial modem. ACTION: Check with other users on the system to ensure that no one else is using the modem. If no one is using the modem, powercycle the modem and try again. If someone is using the modem, wait until they are not using it and then try again. |
| MESSAGE: LOCAL AUTODIAL MODEM IS NOT POWERED ON. (SNACIERR 90) |
| Level: SNACIERR 90
CAUSE: The local automatic-dial modem is not turned on. ACTION: Turn the modem on. |
| MESSAGE: AUTODIAL NOT COMPLETED. (SNACIERR 91) |
| Level: SNACIERR 91
CAUSE: The automatic dial was not completed, possibly because the remote system's modem is not turned on or is not functional. ACTION: Ensure that the remote system's modems are turned on and functional. |
| MESSAGE: AUTODIAL PHONE NUMBER CONFIGURED INCORRECTLY. (SNACIERR 92) |
| Level: SNACIERR 92
CAUSE: The configured automatic-dial phone number is not correct. ACTION: Use NMMGR or the configuration file critical summary to ensure that the Phone Number field contains the correct number. |
| MESSAGE: AUTODIAL NOT ATTEMPTED BECAUSE NODE IS SHUTTING DOWN. (SNACIERR 93) |
| Level: SNACIERR 93
CAUSE: The automatic dial was not attempted because the node is in the process of shutting down. ACTION: Issue the SNACONTROL START command to restart the node, and then try the automatic dial again. |
| MESSAGE: BAD AUTODIAL REPLY. (SNACIERR 94) |
| Level: SNACIERR 94
CAUSE: An internal error has occurred. ACTION: Write down the circumstances and call your Hewlett-Packard support contact. |
| MESSAGE: AUTODIAL REQUEST IS ALREADY PENDING. (SNACIERR 95) |
| Level: SNACIERR 95
CAUSE: Another process has already issued an automatic dial request. ACTION: The node will become active after the other automatic dial request is successful; no action is needed. |
| MESSAGE: NMCONFIG.PUB.SYS LUDATA CONFIGURATION ERROR. RUN NMMGR CONDENSE AND VALIDATION ROUTINE. (SNACIERR 104) |
| Level: SNACIERR 104
CAUSE: SNANODE data configuration error. Mostly due to LU configuration (duplicate NAU, duplicate LUNAME, PU type not matching LU configuration). ACTION: Check NMCONFIG.PUB.SYS and run validate routine. |
| MESSAGE: CAN'T SPECIFY LFSID HERE. (SNACIERR 105) |
| Level: SNACIERR 105
CAUSE: LFSID was specified as a parameter to an SNACONTROL command other than SNACONTROL STATUS. Only SNACONTROL STATUS permits this parameter. ACTION: Don't specify LFSID as a parameter to any SNACONTROL command except SNACONTROL STATUS. |
| MESSAGE: CAN'T SPECIFY NAU HERE. (SNACIERR 106) |
| Level: SNACIERR 106
CAUSE: NAU was specified as a parameter to an SNACONTROL command other than SNACONTROL STATUS. Only SNACONTROL STATUS permits this parameter. ACTION: Don't specify NAU as a parameter to any SNACONTROL command except SNACONTROL STATUS. |
| MESSAGE: CAN'T SPECIFY STATE HERE. (SNACIERR 107) |
| Level: SNACIERR 107
CAUSE: STATE was specified as a parameter to an SNACONTROL command other SNACONTROL STATUS. Only SNACONTROL STATUS permits this parameter. ACTION: Don't specify STATE as a parameter to any SNACONTROL command except SNACONTROL STATUS. |
| MESSAGE: CAN'T SPECIFY SESSTYPE HERE. (SNACIERR 108) |
| Level: SNACIERR 108
CAUSE: SESSTYPE was specified as a parameter to an SNACONTROL command other than SNACONTROL STATUS. Only SNACONTROL STATUS permits this parameter. ACTION: Don't specify SESSTYPE as a parameter to any SNACONTROL command except SNACONTROL STATUS. |
| MESSAGE: BAD NAU SPECIFICATION. (SNACIERR 109) |
| Level: SNACIERR 109
CAUSE: A non-integer value was specified in the NAU= parameter. ACTION: The NAU= parameter must be an integer. |
| MESSAGE: BAD LFSID SPECIFICATION. (SNACIERR 110) |
| Level: SNACIERR 110
CAUSE: A non-hex value was specified in the LFSID= parameter. ACTION: The LFSID= parameter must be a hex value. |
| MESSAGE: NAU NOT FOUND. (SNACIERR 111) |
| Level: SNACIERR 111
CAUSE: The NAU specified in the SNACONTROL STATUS command does not exist. ACTION: The NAU= parameter must specify an existing NAU. |
| MESSAGE: LFSID NOT FOUND. (SNACIERR 112) |
| Level: SNACIERR 112
CAUSE: The LFSID specified in the SNACONTROL STATUS command does not exist. ACTION: The LFSID= parameter must specify an existing LFSID. |
| MESSAGE: BAD LUNAME SPECIFICATION. (SNACIERR 113) |
| Level: SNACIERR 113
CAUSE: A bad LUNAME was specified in the LUNAME= parameter. ACTION: Verify that the LUNAME= parameter was valid. |
| MESSAGE: NO SUCH SESSIONS FOUND. (SNACIERR 114) |
| Level: SNACIERR 114
CAUSE: No sessions were found that match the given STATE= and SESSTYPE= parameters. ACTION: None. This is a normal event. |
| MESSAGE: BAD TOKEN RING LINK NAME. (SNACIERR 115) |
| Level: SNACIERR 115
CAUSE: Link name specified in the SNA NODE configuration is not valid. ACTION: Change LINKNAME to a valid link name. |
| MESSAGE: SNA TOKEN RING NOT INSTALLED PROPERLY. (SNACIERR 116) |
| Level: SNACIERR 116
CAUSE: SNA TOKEN RING not installed. ACTION: Call your Hewlett-Packard contact. |
| MESSAGE: SNA SDLC NOT INSTALLED PROPERLY. (SNACIERR 117) |
| Level: SNACIERR 117
CAUSE: SNA SDLC LINK not installed. ACTION: Call your Hewlett-Packard contact. |
|
SDLC Link Driver Error Messages |
SNA Transport Error Messages |