Chapter 109 SXCM (SNAX/CM) Messages

The messages in this chapter are sent by the SNAX Connection Manager (SNAX/CM) subsystem. The subsystem ID displayed by these messages includes SXCM as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message, see Chapter 15.

The SNAX/CM subsystem works together with the SNAX Extended Facility (SNAX/XF) subsystem to manage connections, and operator messages might be issued by both subsystems about a particular operation.

For information about messages issued by the SNAX/XF subsystem, see the chapter in this manual about “SNAX/APN and SNAX/XF Messages.”
For general information about the SNAX/CM as well as information about messages issued to a log file for the SNAX/CM, see the SNAX Connection Manager (SNAX/CM) Manual.

In this chapter, for D-series RVUs, some messages contain conditional parameters that identify a port or physical unit (PU) name. (A port is a unique name used by the SNAX/CM to identify and access an X25AM line handler subdevice for an X.25 network or a particular Tandem Local Area Network Access Method (TLAM) session for a Token Ring network.)

Whether or not a conditional parameter is displayed depends upon the configuration in use at the time and the command that failed.

For information about SNAX/CM return codes, as well as status and error messages issued by the SNAX/CM, see Appendix B, “SNAX/CM Messages and Codes,” in the SNAX Connection Manager (SNAX/CM) Manual. For detailed information about file‑system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual.

SXCMGR APPL cmappl-name, OPEN SUCCESSFUL

cmappl-name

is the name of the APPL object specified for a connection management operation using the Subsystem Control Facility (SCF) ADD APPL command (parm = $SSCP.napplname, APPLTYPE CMAPPL).

Cause The APPLNAME command finished successfully.

Effect The named APPL object is opened. This message is equivalent to SNAX/CM log message 1, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.

SXCMGR APPL cmappl-name, OPEN FAILED RC = nnnn, FE = nnnn

`cmappl-name`	is the name of the APPL object specified for a connection management operation using the Subsystem Control Facility (SCF) ADD APPL command (parm = $SSCP.`napplname`, APPLTYPE CMAPPL).
RC = `nnnn`	is a SNAX/CM return code.
FE = `nnnn`	is a file-system error that indicates why the error occurred.

Cause See the return code and file-system error message to determine the cause.

Effect The SNAX/CM APPLNAME command fails. This message is equivalent to SNAX/CM log message 2, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that the SNAX Extended Facility (SNAX/XF) APPL object was added using the SCF and that the correct password was defined. See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name][, PU pu-name], COMMAND REJECTED BY APPL cmappl-name RC = nnnn, FE = nnnn

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
`pu-name`	is the name of the physical unit for which this error occurred. This is displayed only if a port has been configured for this connection.
`cmappl-name`	is the name of the APPL object specified for a connection-management operation using the Subsystem Control Facility (SCF) ADD APPL command (parm = $SSCP.`napplname`, APPLTYPE CMAPPL).
RC = `nnnn`	is a SNAX/CM return code.
FE = `nnnn`	is a file-system error that indicates why the error occurred.

Cause The SNAX/CM has issued a SNAX/CM command to the SNAX Extended Facility (SNAX/XF) and received an error. See the return code and file-system error message to determine the cause.

Effect The connection manager operation cannot be initiated. This message is equivalent to SNAX/CM log message 8, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery On D-series RVUs, verify that the SNAX/XF line and physical unit have been started and that the X25AM or Token Ring line and subdevice have been started also, then try the SNAX/CM command again.

On G-series RVUs, verify that the SNAX/XF line and physical unit have been started and that the X25AM line and subdevice have been started also, then try the SNAX/CM command again.

See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], CALL-OUT CONNECTED, STATUS: line-status ALIAS LU alias-lu, LU COUNT lu-count

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

line-status

reports the status of the line, which can have the following values:

Value	Meaning
1	Not available
2	Disconnected
3	Disconnecting
4	Allowing
5	Calling
6	Connected

alias-lu

is an ASCII string that identifies the logical unit (LU) name, in the form #ppnnnnn (where pp is a letter and a number or two letters derived by SNAX/CM from the physical unit (PU) identity, and nnnnn is a 5-digit decimal number that identifies the current connection).

lu-count

is an unsigned integer from 1 through 255 that identifies the number of configured LUs.

Cause A call-out operation has been finished and the line is connected.

Effect The SNAX/CM command finishes successfully. This message is equivalent to SNAX/CM log message 9, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.

SXCMGR BUFFER FAILURE line-name[, PORT port-name]

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

Cause The SNAX/CM could not get sufficient buffer space to continue processing.

Effect The SNAX/CM abends. This message is equivalent to SNAX/CM log message 10, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Verify that the CONNECTAPPL line attribute has been added using the Subsystem Control Facility (SCF) ADD APPL command and is the correct type. Redistribute the workload using the SNAX/CM ENABLE and CONNECT commands to support additional connections.

Also ensure that compatible versions of the SNAX Extended Facility (SNAX/XF) and the SNAX/CM are being used. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
SNAX/XF configuration (D-series RVUs)
SNAX/XF SYSGEN and SCF configuration files (G-series RVUs)
X25AM or Tandem Local Area Network Access Method (TLAM) SYSGEN and SCF configuration files (D-series RVUs)
X25AM configuration files (G-series RVUs)
SXCMGR SAVEABEND file
SNAX/CM command (OBEY) file, if any
Trace files from the SNAX/CM, X25AM or TLAM (D-series RVUs only), and SNAX/XF or SNAX/APN service‑manager and line‑handler processes
Supporting documentation such as Event Management Service (EMS) logs and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

SXCMGR LINE line-name[, PORT port-name], CALL-OUT OPERATION FAILED, STATUS: line-status RC = nnnn, FE = nnnn

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

line-status

reports the status of the line, which can have the following values:

Value	Meaning
1	Not available
2	Disconnected
3	Disconnecting
4	Allowing
5	Calling (not probable to receive this status)
6	Connected (not probable to receive this status)

RC = nnnn

is a SNAX/CM return code.

FE = nnnn

is a file-system error that indicates why the error occurred.

Cause See the status message, the return code, and the file-system error message to determine the cause.

Effect The call-out operation fails, and the line is unavailable or is disconnected. This message is equivalent to SNAX/CM log messages 11 and 12, which are described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery On D-series RVUs, verify that the SNAX/XF line and physical unit (PU) were started, and that the X25AM or Token Ring line and subdevice were started also. Retry the failing SNAX/CM CONNECT command.

On G-series RVUs, verify that the SNAX/XF line and physical unit (PU) were started, and that the X25AM line and subdevice were started also. Retry the failing SNAX/CM CONNECT command.

See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], CALL-IN DISCONNECTED, STATUS: line-status, RC: nnnn, FE: nnnn

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

line-status

reports the status of the line, which can have the following values:

Value	Meaning
1	Not available
2	Disconnected
3	Disconnecting
4	Allowing
5	Calling
6	Connected

RC = nnnn

is a SNAX/CM return code.

FE = nnnn

is a file-system error that indicates why the error occurred.

Cause See the status message, the return code, and the file-system error message to determine the cause. This message is equivalent to SNAX/CM log messages 13 and 14, which are described in the SNAX Connection Manager (SNAX/CM) Manual.

Effect The call-in operation fails and the line is disconnected or is unavailable.

Recovery Verify that the SNAX/XF line and physical unit were started, and that the X25AM line and subdevice were started also. The SNAX/CM ENABLE command retries automatically after a short delay. See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], DISCONNECTED, STATUS: line-status, RC = nnnn, FE = nnnn

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

line-status

reports the status of the line, which can have the following values:

Value	Meaning
1	Not available
2	Disconnected
3	Disconnecting
4	Allowing
5	Calling
6	Connected

RC = nnnn

is a SNAX/CM return code.

FE = nnnn

is a file-system error that indicates why the error occurred.

Cause This message occurs anytime there is a disconnection; for example, a remote device disconnects, a DISCONNECT command issued by the user completes successfully, or the opener of the last logical unit (LU) issues a CONTROL 12 or CLOSE call. This message also occurs when a SNAX/CM DISCONNECT operation is started after receiving a call reject from the call validate or XID validate server process. See the status message, the return code, and the file-system error message to determine the cause.

Effect A SNAX/CM disconnect operation finishes successfully, or a port is disconnected by the opener of an LU. This message is equivalent to SNAX/CM log message 15, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.

SXCMGR LINE line-name[, PORT port-name], DISCONNECT FAILED, STATUS: line-status RC = nnnn, FE = nnnn

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

line-status

reports the status of the line, which can have the following values:

Value	Meaning
1	Not available
2	Disconnected
3	Disconnecting
4	Allowing
5	Calling
6	Connected

RC = nnnn

is a SNAX/CM return code.

FE = nnnn

is a file-system error that indicates why the error occurred.

Cause This message occurs when a SNAX/CM DISCONNECT command is issued by the user, and the line has not been started or is not a line configured for SNAX/CM operations using the CONNECTAPPL system generation line attribute. This message also occurs when a SNAX/CM DISCONNECT operation is started after receiving a CALL REJECT message from the call validate or XID validate server process. See the status message, the return code, and the file-system error message to determine the cause.

Effect A SNAX/CM disconnect operation fails because a line is unavailable. This message is equivalent to SNAX/CM log message 16, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery On D-series RVUs, verify that the SNAX Extended Facility (SNAX/XF) line and physical unit (PU) were started and that the X25AM or Token Ring line and subdevice were started. Also check that the APPL object was added using the Subsystem Control Facility (SCF) ADD APPL command and is the correct type. Retry the failing operation.

On G-series RVUs, verify that the SNAX Extended Facility (SNAX/XF) line and physical unit (PU) were started, and that the X25AM line and subdevice were started also. Also check that the APPL object was added using the Subsystem Control Facility (SCF) ADD APPL command and is the correct type. Retry the failing operation.

See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], STATUS: line-status UNEXPECTED, RC = nnnn, FE = nnnn

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

line-status

reports the status of the line, which can have the following values:

Value	Meaning
1	Not available
2	Disconnected
3	Disconnecting.
4	Allowing
5	Calling
6	Connected

RC = nnnn

is a SNAX/CM return code.

FE = nnnn

is a file-system error that indicates why the error occurred.

Cause See the status message, the return code, and the file-system error message to determine the cause.

Effect The SNAX/CM logs this message if the SNAX/XF or SNAX/APN service manager returns a status that is not expected as a response to the current connection manager operation. This message is equivalent to SNAX/CM log message 19, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that compatible versions of the SNAX Extended Facility (SNAX/XF) and the SNAX/CM are being used. If the problem persists, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
SNAX/XF configuration (D-series RVUs)
SNAX/XF SYSGEN and SCF configuration files (G-series RVUs)
X25AM or Tandem Local Area Network Access Method (TLAM) SYSGEN and SCF configuration files (D-series RVUs)
X25AM configuration files (G-series RVUs)
SXCMGR SAVEABEND file
SNAX/CM command (OBEY) file, if any
Trace files from the SNAX/CM, X25AM or TLAM, and SNAX/XF or SNAX/APN service‑manager and line‑handler processes
Supporting documentation such as Event Management Service (EMS) logs and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

SXCMGR LINE line-name[, PORT port-name], RECEIVED UNSUPPORTED STATUS VALUE: status, RC = nnnn, FE = nnnn

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

status

reports the status of the line, which can have the following values:

Value	Meaning
0	Unknown
1	Not available
2	Disconnected
3	Disconnecting.
4	Allowing
5	Calling
6	Connected

RC = nnnn

is a SNAX/CM return code.

FE = nnnn

is a file-system error that indicates why the error occurred.

Cause See the return code and file-system error message to determine the cause.

Effect The SNAX/XF or SNAX/APN service manager returns an unsupported type or status value. This message is equivalent to SNAX/CM log message 20, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
SNAX/XF configuration (D-series RVUs)
SNAX/XF SYSGEN and SCF configuration files (G-series RVUs)
X25AM or Tandem Local Area Network Access Method (TLAM) SYSGEN and SCF configuration files (D-series RVUs)
X25AM configuration files (G-series RVUs)
SXCMGR SAVEABEND file
SNAX/CM command (OBEY) file, if any
Trace files from the SNAX/CM, X25AM or TLAM, and SNAX/XF or SNAX/APN service‑manager and line‑handler processes
Supporting documentation such as Event Management Service (EMS) logs and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

SXCMGR LINE line-name[, PORT port-name], CALL VALIDATE IN PROGRESS, STATUS: line-status

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

line-status

reports the status of the line, which can have the following values:

Value	Meaning
1	Not available
2	Disconnected
3	Disconnecting
4	Allowing (most probable to receive this status)
5	Calling (most probable to receive this status)
6	Connected (most probable to receive this status)

Cause A command to validate a call string has been sent.

Effect A call string validation is in progress. This message is equivalent to SNAX/CM log message 21, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.

SXCMGR LINE line-name[, PORT port-name], XID VALIDATE IN PROGRESS, STATUS: line-status

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

line-status

reports the status of the line, which can have the following values:

Value	Meaning
1	Not available
2	Disconnected
3	Disconnecting
4	Allowing (most probable to receive this status)
5	Calling (most probable to receive this status)
6	Connected (most probable to receive this status)

Cause A command to validate an XID string has been sent.

Effect An XID-string validation is in progress. This message is equivalent to SNAX/CM log message 22, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.

SXCMGR LINE line-name[, PORT port-name], CALL VALIDATE OK

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

Cause The SNAX/CM gave control to the validation process to check the call string; if the validation finished successfully, the SNAX/CM logs this message.

Effect The call string validation process finishes successfully. This message is equivalent to SNAX/CM log message 23, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.

SXCMGR LINE line-name[, PORT port-name], XID VALIDATE OK

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

Cause The SNAX/CM gave control to the validation process to check the XID string; if the validation finished successfully, the SNAX/CM logs this message.

Effect The XID-string validation process finishes successfully. This is equivalent to log message 24, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.

SXCMGR LINE line-name[, PORT port-name], CALL-IN CONNECTED, STATUS: line-status ALIAS LU alias-lu, LU COUNT #lu-count

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

line-status

reports the status of the line, which can have the following values:

Value	Meaning
1	Not available
2	Disconnected
3	Disconnecting
4	Allowing
5	Calling
6	Connected (most probable to receive this status)

alias-lu

is an ASCII string that identifies the logical unit (LU) name, in the form #ppnnnnn (where pp is a letter and a number or two letters derived by SNAX/CM from the PU identity, and nnnnn is a 5-digit decimal number that identifies the current connection).

lu-count

is an unsigned integer in the range from 1 through 255 that identifies the number of configured LUs.

Cause The call-in operation has been finished.

Effect The line is connected, and activation of System Network Architecture (SNA) objects can begin. This message is equivalent to SNAX/CM log message 25, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.

SXCMGR LINE line-name[, PORT port-name], CALL VALIDATE FAILED, PROCESS: server-name RC = nnnn, FE = nnnn

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
`server-name`	is an ASCII string that identifies the server process name.
RC = `nnnn`	is a SNAX/CM return code.
FE = `nnnn`	is a file-system error that indicates why the error occurred.

Cause The SNAX/CM failed to open or write to the validation process for one of the following reasons:

The validation process failed to validate the call string within the timeout limits. The timeout value is either the default (60 seconds) or is set by the user in a timeout.
The validation process has rejected the call string.
The validation process has returned a bad response.
The validation process did not exist.
An unauthorized device may have been attempting to connect.

See the return code and file-system error message to determine the cause.

Effect The call validation process fails. This message is equivalent to SNAX/CM log message 26, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that the VALCALL server process is running. If it is, use the Subsystem Control Facility (SCF) TRACE command to ensure that the CALLADDR value being used by the calling physical unit (PU) is known to the server process. See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], XID VALIDATE FAILED, PROCESS: server-name RC = nnnn, FE = nnnn

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
`server-name`	is an ASCII string that identifies the server process name.
RC = `nnnn`	is a SNAX/CM return code.
FE = `nnnn`	is a file-system error that indicates why the error occurred.

Cause The SNAX/CM failed to open or write to the XID validation process for one of the following reasons:

The validation process failed to validate the XID string within timeout limits. The timeout value is either the default (60 seconds) or is set by the user using a timeout.
The validation process has rejected the XID string.
The validation process has returned a bad response.
The validation process did not exist.
An unauthorized device may have been attempting to connect.

See the return code and file-system error message to determine the cause.

Effect The XID validation process fails. This message is equivalent to SNAX/CM log message 27, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that the VALXID server process is running. If it is, use the Subsystem Control Facility (SCF) TRACE command to ensure that the XID value being used by the calling physical unit is known to the server process.

SXCMGR LINE line-name[, PORT port-name], TACL: tacl-name, NEWPROCESS OF TACL PROCESS FAILED NEWPROCESS ERROR: (%,%)

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
`tacl-name`	is an ASCII string that identifies the configured Tandem Access Command Language (TACL) process name.
`newproc-err`	is an error code from a NEWPROCESS call. See the Guardian Procedure Errors and Messages Manual to determine the reason for the command not being accepted.

Cause See the error and code values returned from a NEWPROCESS call to determine the cause. Use the file-system error value to further diagnose and correct the problem with the TACL process.

Effect The SNAX/CM fails to start a named TACL process using a NEWPROCESS call. This message is equivalent to SNAX/CM log message 28, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that the correct TACL object code is available in $SYSTEM.SYSTEM and that sufficient space is available on the swap disk. See Appendix B, for information on the specified file-system error. See Appendix C, for information on NEWPROCESS errors.

SXCMGR LINE line-name[, PORT port-name], TACL: tacl-name, OPEN OF TACL PROCESS FAILED FE = nnnn

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
`tacl-name`	is an ASCII string that identifies the configured Tandem Access Command Language (TACL) process name.
FE = `nnnn`	is a file-system error that indicates why the error occurred.

Cause See the file-system error message to determine the cause.

Effect The SNAX/CM cannot open the named TACL process. This message is equivalent to SNAX/CM log message 29, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that the correct TACL object code is available in $SYSTEM.SYSTEM and that sufficient space is available on the swap disk. See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], TACL: tacl-name, WRITE TO TACL PROCESS FAILED FE = nnnn

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
`tacl-name`	is an ASCII string that identifies the configured Tandem Access Command Language (TACL) process name.
FE = `nnnn`	is a file-system error that indicates why the error occurred.

Cause See the file-system error message to determine the cause.

Effect The SNAX/CM cannot successfully write to the named TACL process. This message is equivalent to SNAX/CM log message 30, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that the correct TACL object code is available in $SYSTEM.SYSTEM and that sufficient space is available on the swap disk. See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], TACL: tacl-name, STARTED FOR ALIAS LU: alias-lu

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
`tacl-name`	is an ASCII string that identifies the configured Tandem Access Command Language (TACL) process name.
`alias-lu`	is an ASCII string that identifies the logical unit (LU) name, in the form #`ppnnnnn` (where `pp` is a letter and a number or two letters derived by the SNAX/CM from the physical unit (PU) identity, and `nnnnn` is a 5-digit decimal number that identifies the current connection).

Cause The user specified a TACL process with the specified TACL process name. The SNAX/CM starts a TACL process on the first alias LU after the line is connected by either a call-in or call-out operation.

Effect The SNAX/CM starts the named TACL process successfully. This message is equivalent to SNAX/CM log message 31, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.

SXCMGR LINE line-name[, PORT port-name], SERVER: server-name , OPEN OF SERVER PROCESS FAILED FE = nnnn

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
`server-name`	is an ASCII string that identifies the server process name.
FE = `nnnn`	is a file-system error that indicates why the error occurred.

Cause See the file-system error message to determine the cause of the problem with the server process.

Effect A port connection remains active, but the SNAX/CM can not open the process specified by an ENABLE or CONNECT command. This message is equivalent to SNAX/CM log message 32, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that the server process is running correctly. See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], SERVER: server-name, WRITE TO SERVER PROCESS FAILED FE = nnnn

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
`server-name`	is an ASCII string that identifies the server process name.
FE = `nnnn`	is a file-system error that indicates why the error occurred.

Cause When the connection status for a port changed, the SNAX/CM opened the process‑name provided using the ENABLE or the CONNECT command and issued a server message to signal the status change. See the file‑system error message to determine the cause of the problem with the server process.

Effect A write operation to a server process fails; the SNAX/CM leaves the connection active. This message is equivalent to SNAX/CM log message 33, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that the server process is running correctly. See Appendix B, for information on the specified error.

SXCMGR UNABLE TO ACCESS APPL cmappl-name RC = nnnn, FE = nnnn

`cmappl-name`	is the name of the APPL object specified for a connection management operation using the Subsystem Control Facility (SCF) ADD APPL command (parm = $SSCP.`nnnnapplname`, APPLTYPE CMAPPL).
RC = `nnnn`	is a SNAX/CM return code.
FE = `nnnn`	is a file-system error that indicates why the error occurred.

Cause This error usually occurs when the APPL object being used to access the SNAX Extended Facility (SNAX/XF) has been aborted or deleted. See the return code and file-system error message to determine the cause. This message is also displayed if the APPL object exists but is not of the type cmappl.

Effect The SNAX/CM could not access the SNAX/XF. If the error is recoverable, the SNAX/CM retries the failing connection manager operation; otherwise, the SNAX/CM abends. This message is equivalent to SNAX/CM log message 34, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that the APPL object being used to access SNAX/XF is active. See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], DISABLED BY OPERATOR

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

Cause The operator disabled a line or port that was previously enabled.

Effect A port that was previously enabled is disabled. This message is equivalent to SNAX/CM log message 35, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.

SXCMGR LINE line-name[, PORT port-name], CALL-ACCEPT OPERATION FAILED RC = nnnn, FE = nnnn

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
RC = `nnnn`	is a SNAX/CM return code.
FE = `nnnn`	is a file-system error that indicates why the error occurred.

Cause See the return code and file-system error message to determine the cause.

Effect A SNAX/CM CALL-ACCEPT operation issued to the SNAX Extended Facility (SNAX/XF) fails. This message is equivalent to SNAX/CM log message 36, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that the SXCMGR line, physical unit (PU), and the X25AM line or Tandem Local Area Network Access Method (TLAM) line and subdevice have not been deleted and are active. See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], INTERNAL ERROR, NOT IN DATABASE

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

Cause The SNAX/CM line database has been corrupted.

Effect The SNAX/CM abends. This message is equivalent to SNAX/CM log message 37, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
SNAX/XF configuration
X25AM or Tandem Local Area Network Access Method (TLAM) configuration
SXCMGR SAVEABEND file
SNAX/CM command (OBEY) file, if any
Trace files from the SNAX/CM, X25AM or TLAM, and SNAX/XF or SNAX/APN service‑manager and line‑handler processes
Supporting documentation such as Event Management Service (EMS) logs and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

SXCMGR LINE line-name[, PORT port-name], server-type MESSAGE NOT SENT, NO BUFFER AVAILABLE

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

server-type

is the type of server. The server types are:

Value	Meaning
1	Process server
2	Call validation server
3	XID validation server
4	Tandem Access Command Language (TACL) server

Cause The SNAX/CM encountered a buffer shortage.

Effect The SNAX/CM fails to send a message to either the PROCESS server, the CALL VALIDATE server, or the XID VALIDATE server process. This message is equivalent to SNAX/CM log message 38, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Reduce the number of connection commands (for example, by deleting the ENABLE or CONNECT command) being supported by the SNAX/CM process. This is usually a temporary condition; the SNAX/CM retries the message after a 3-second delay and should be able to recover.

SXCMGR LINE line-name[, PORT port-name], DISABLED, BUT COULD NOT NOTIFY APPL cmappl-name, RC = nnnn, FE = nnnn

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
RC = `nnnn`	is a SNAX/CM return code.
FE = `nnnn`	is a file-system error that indicates why the error occurred.
`cmappl-name`	is the name of the APPL object specified for a connection management operation using the Subsystem Control Facility (SCF) ADD APPL command (parm = $SSCP.`napplname`, APPLTYPE CMAPPL).

Cause The SNAX/CM attempted to send a DISABLE request to the SNAX Extended Facility (SNAX/XF); however, the request failed because the port was already disabled. This message is equivalent to SNAX/CM log message 39, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Effect A SNAX/CM CALL DISCONNECT command fails.

Recovery Ensure that the SXCMGR line is active, or for a port, verify that the SXCMGR line and either the Tandem Local Area Network Access Method (TLAM) line or X25AM line are active. See Appendix B, for information on the specified error.

SXCMGR LINE line-name[, PORT port-name], cm-ops OPERATION TIMED OUT

line-name

is the fully qualified name of the line-handler process for the line on which the error occurred.

port-name

is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.

cm-ops

reports the type of connection manager operation expected. This parameter can have the following values:

Value	Meaning
0	Unknown
1	Allow call-in
2	Call out
3	Accept call after call validation
4	Accept call after XID validation
5	Call disconnect
6	Wait for connection after call‑out
7	Wait for connection after call validation
8	Wait for connection after XID validation
9	Wait for disconnect after call disconnect
10	Wait for XID after call validation

Cause There is a problem in the SNAX Extended Facility (SNAX/XF), in the X25AM or in the Tandem Local Area Network Access Method (TLAM), or in the network. If a timeout occurs for an enabled line, the SNAX/CM issues a disconnect request; call-in is enabled after a 1-minute delay.

Effect For lines that are not enabled, the port is disconnected, and no retry is attempted. A connection management procedure failed to return an expected completion or status within the 1-minute timeout period allowed. (The 1-minute timer is internal to the SXCMGR process and cannot be controlled by the user.) This message is equivalent to SNAX/CM log message 40, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
SNAX/XF configuration (D-series RVUs)
SNAX/XF SYSGEN and SCF configuration files (G-series RVUs)
X25AM or Tandem Local Area Network Access Method (TLAM) SYSGEN and SCF configuration files (D-series RVUs)
X25AM configuration files (G-series RVUs)
SXCMGR SAVEABEND file
SNAX/CM command (OBEY) file, if any
Trace files from the SNAX/CM, X25AM or TLAM, and SNAX/XF or SNAX/APN service‑manager and line‑handler processes
Supporting documentation such as Event Management Service (EMS) logs and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

SXCMGR LINE line-name[, PORT port-name], INTERNAL ERROR, RECEIVED A BAD ALIAS LU NAME FROM APPL cmappl-name

`line-name`	is the fully qualified name of the line-handler process for the line on which the error occurred.
`port-name`	is the name of the subdevice for which this error occurred. This is displayed only if a port has been configured for this connection.
`cmappl-name`	is the name of the APPL object specified for a connection management operation using the Subsystem Control Facility (SCF) ADD APPL command (parm = $SSCP.`napplname`, APPLTYPE CMAPPL).

Cause A version mismatch occurred between the SNAX/CM process and the SNAX Extended Facility (SNAX/XF).

Effect The alias logical unit (LU) name returned by the SNAX/XF to the SNAX/CM is in an invalid format. This message is equivalent to SNAX/CM log message 41, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Ensure that compatible versions of the SNAX/XF and the SNAX/CM are being used.

SXCMGR TAKEOVER BY BACKUP PROCESS

Cause The primary process is stopped, a processor failure occurred, or a software failure occurred in the primary processor.

Effect The backup process has taken over execution for the connection manager. This message is equivalent to SNAX/CM log message 46, which is described in the SNAX Connection Manager (SNAX/CM) Manual.

Recovery Informational message only; no corrective action is needed.