Chapter 95 SNAX‑APC Messages

The messages in this chapter are sent by the SNAX Advanced Program Communication (SNAX/APC) subsystem. The subsystem ID displayed by these messages includes SNAX‑APC as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

proc-name: State violation, [LU = lu-name,] FSM = fsm-name, current state = #fsm-state, current event = #fsm-evt

proc-name

is the name of the SNAX/APC process for which the error occurred.

lu-name

identifies the name of the logical unit (LU).

fsm-name

identifies a finite state machine (FSM). The following are text values for this parameter:

FSM_BIS_BIDDER	is the finite state machine FSM_BIS_BIDDER, which represents the status of a bidder half-session.
FSM_BIS_FSP	is the finite state machine FSM_BIS_FSP, which represents the status of a first-speaker half-session.
FSM_BSM_FMP19	is the finite state machine FSM_BSM_FMP19, which enforces the bracket protocol.
FSM_CHAIN_RCV_FMP19	is the finite state machine FSM_CHAIN_RCV_FMP19, which enforces the chaining protocol for received chains.
FSM_CHAIN_SEND_FMP19	is the finite state machine FSM_CHAIN_SEND_FMP19, which enforces the chaining protocol for sending chains.
FSM^CONVERSATION	is the finite state machine FSM_CONVERSATION, which represents the status of a conversation.
FSM^ERROR^OR^FAILURE	is the finite state machine FSM_ERROR_OR_FAILURE, which represents if any error or failure message unit records have been received by Presentation Services.
FSM_IMMEDIATE_RQ_MODE_RCV	is the finite state machine FSM_IMMEDIATE_RQ_MODE_RCV, which enforces the immediate request-mode receive protocol.
FSM_IMMEDIATE_RQ_MODE_SEND	is the finite state machine FSM_IMMEDIATE_RQ_MODE_SEND, which enforces the immediate request-mode send protocol.
FSM_PAC_RQ_RCV	is the finite state machine FSM_PAC_RQ_RCV, which represents the ability to send a session-pacing response for receive pacing.
FSM_PAC_RQ_SEND	is the finite state machine FSM_PAC_RQ_SEND, which represents the ability to send a session-level pacing request for send pacing.
FSM_POST	is the finite state machine FSM_POST, which represents the posting status of a conversation.
FSM_QRI_CHAIN_RCV_FMP19	is the finite state machine FSM_QRI_CHAIN_RCV_FMP19, which enforces the setting of the Queued Response Indicator (QRI) in the request/response header (RH).
FSM_RCB_STATUS_BIDDER	is the finite state machine FSM_RCB_STATUS_BIDDER, which represents the status of a conversation resource associated with a bidder half-session.
FSM_RCB_STATUS_FSP	is the finite state machine FSM_RCB_STATUS_FSP, which represents the status of a conversation resource associated with a first-speaker half-session.
FSM_RCV_PURGE_FMP19	is the finite state machine FSM_RCV_PURGE_FMP19, which represents a purging state for received Begin Bracket (BB) chains (indicating a bracket error).
FSM_SCB_STATUS_BIDDER	is the finite state machine FSM_SCB_STATUS_BIDDER, which represents the status of a bidder half-session.
FSM_SCB_STATUS_FSP	is the finite state machine FSM_SCB_STATUS_FSP, which represents the status of a first-speaker half-session.
ZAPC-STATUS	is the finite state machine FSM_STATUS, which represents the status of an LU‑LU session.

fsm-state

identifies the state value for FSM error messages.

fsm-evt

identifies the error that triggered the FSM error.

Cause SNAX/APC encountered an unexpected finite state machine (FSM) error.

Effect The process continues, but some sessions may encounter unpredictable difficulties.

Recovery Some messages are not easily recoverable and require you to seek additional help. In this case, follow the standard procedures at your site for contacting the appropriate support personnel. Before reporting this problem to the Global Mission Critical Solution Center (GMCSC), collect any relevant information. The minimal information required for reporting a problem against T9096 SNAX/APC includes:

System number and version procedure from the APCOBJ module; the version procedure can be obtained by entering VPROC or BIND:
VPROC Enter filename: >$system-volume.subvolume.APCOBJ
Versions of all related products.
Problem description and symptoms—include a description of the problem and the accompanying symptoms.
SNAX/APC trace file showing the problem—the trace file is assigned either at SNAX/APC startup or when a dynamic trace is invoked. It is recommended that the trace be taken specifying SELECT ALL so that support and problem resolution personnel can see the entire picture. A trace of the problem is mandatory for problem resolution.
If the problem seems to be in establishing sessions, specify tracing using the SNAX/APC startup parameters (see the SNAX/APC Planning and Configuration Manual).
EMS logs—include the event (EMS) logs that were active when the problem occurred.
Saveabend file—if SNAX/APC abends or hangs, it is important to get the SAVE file of the SNAX/APC server. To accomplish this, when SNAX/APC drops into Inspect, or if it hangs and you invoke Inspect using the DEBUG command, issue the SAVE command.
Configuration/Startup files—if a configuration problem is suspected, the Subsystem Control Facility (SCF) configuration file or an SCF command display of the following command can be useful:
INFO PROCESS $apc-process-name, SUB ALL, DETAIL
Other files—other files might include APCLMAP, which resides on the SNAX/APC installation subvolume and is used in formatting traces, and SNAX line trace files from the underlying access method (SNAX/XF, SNAX/APN, or SNAX/CDF). SNAX line trace files might be helpful when all else fails or when a low-level problem (that is, within the lower SNA layers or basic line connectivity) is encountered. The SNAX line trace should be accompanied by the SCF displays of the SNAX lines, physical units (PUs) and logical units (LUs) that SNAX/APC utilizes.

proc-name: Initialization failure, Reason: init-err [, Error: file-error] [inv-param]

proc-name

is the name of the SNAX/APC process for which the error occurred.

init-err

identifies the reason for initialization failure. The following are the text values for this parameter:

invalid param	indicates that the error was caused by an invalid parameter.
invalid param value for	indicates that the error was caused by an invalid parameter value.

file-error

identifies a file-system error.

inv-param

identifies the name of the parameter that is invalid.

Cause The SNAX/APC startup parameters contained an invalid PARAM.

Effect The process terminates abnormally.

Recovery Correct the startup parameter. If you receive a file-system error, see Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

proc-name: config-err[, LU = lu-name][, Error: file-error]

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`config-err`	identifies the fault in an invalid configuration file. The following are the text values for this parameter: bad CONFIG file indicates that the error was caused by an invalid configuration file. bad CONFIG file code indicates that the error was caused by an invalid configuration file code. CONFIG version mismatched indicates that the error was caused by a configuration version mismatch. failed to convert old CONFIG file indicates that the error was caused by a failure to convert an old configuration file.
`lu-name`	identifies the name of the logical unit (LU).
`file-error`	identifies a file-system error.

Cause SNAX/APC detected an error in a configuration file during startup.

Effect The process terminates.

Recovery Specify a correct configuration file. If you receive a file-system error, see Appendix B, for a definition of the specified error, if applicable. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

proc-name: Abending - SNAX/APC internal error

proc-name

is the name of the SNAX/APC process for which the error occurred.

Cause SNAX/APC detected an operational failure.

Effect The process terminates abnormally.

System number and version procedure from the APCOBJ module; the version procedure can be obtained by entering VPROC or BIND:
VPROC Enter filename: >$system-volume.subvolume.APCOBJ
Versions of all related products.
Problem description and symptoms—include a description of the problem and the accompanying symptoms.
SNAX/APC trace file showing the problem—the trace file is assigned either at SNAX/APC startup or when a dynamic trace is invoked. It is recommended that the trace be taken specifying SELECT ALL so that support and problem resolution personnel can see the entire picture. A trace of the problem is mandatory for problem resolution.
If the problem seems to be in establishing sessions, specify tracing using the SNAX/APC startup parameters (see the SNAX/APC Planning and Configuration Manual).
EMS logs—include the event (EMS) logs that were active when the problem occurred.
Saveabend file—if SNAX/APC abends or hangs, it is important to get the SAVE file of the SNAX/APC server. To accomplish this, when SNAX/APC drops into Inspect, or if it hangs and you invoke Inspect using the DEBUG command, issue the SAVE command.
Configuration/Startup files—if a configuration problem is suspected, the Subsystem Control Facility (SCF) configuration file or an SCF command display of the following command can be useful:
INFO PROCESS $apc-process-name, SUB ALL, DETAIL
Other files—other files might include APCLMAP, which resides on the SNAX/APC installation subvolume and is used in formatting traces, and SNAX line trace files from the underlying access method (SNAX/XF, SNAX/APN, or SNAX/CDF). SNAX line trace files might be helpful when all else fails or when a low-level problem (that is, within the lower SNA layers or basic line connectivity) is encountered. The SNAX line trace should be accompanied by the SCF displays of the SNAX lines, physical units (PUs) and logical units (LUs) that SNAX/APC utilizes.

proc-name: Bid rejected - out of resources

proc-name

is the name of the SNAX/APC process for which the error occurred.

Cause SNAX/APC rejected a request from a remote logical unit (LU) for a conversation with a local LU because it could not obtain the required resources.

Effect None; the process continues.

Recovery Informational message only; no corrective action is needed.

proc-name: Process takeover by backup

proc-name

is the name of the SNAX/APC process for which the error occurred.

Cause The backup processor has taken over the process.

Effect None; the process continues.

Recovery Informational message only; no corrective action is needed.

proc-name: Deallocate segment error

proc-name

is the name of the SNAX/APC process for which the error occurred.

Cause SNAX/APC was not able to deallocate an extended data segment used for tracing.

Effect The process terminates abnormally.

Recovery If you do not have a backup process configured to take over, restart the process.

proc-name: init-info

proc-name

is the name of the SNAX/APC process for which the error occurred.

init-info

provides SNAX/APC initialization status information. The following are text values for this parameter:

SNAX/APC initialization started indicates that SNAX/APC initialization has started.

SNAX/APC initialization complete indicates that SNAX/APC initialization has completed.

SNAX/APC reinitialization complete indicates that SNAX/APC reinitialization has completed.

Cause SNAX/APC started or ended initialization or reinitialization.

Effect None; the process continues.

Recovery Informational message only; no corrective action is needed.

proc-name: Device type inquiry failed, LU = lu-name, Error: file-error

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`lu-name`	identifies the name of the logical unit (LU).
`file-error`	identifies a file-system error.

Cause A device type inquiry for an LU failed.

Effect The process continues; however, the LU does not start.

Recovery Use the file-system error returned in this message to identify why the error occurred, and take appropriate actions. See Appendix B, for a definition of the specified error. For more detailed information including recovery actions, see the Guardian Procedure Errors and Messages Manual.

Issue a START LU command to verify the correction.

proc-name: LU connect failed, LU = lu-name, Error: file-error

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`lu-name`	identifies the name of the logical unit (LU).
`file-error`	identifies a file-system error.

Cause A connect for an LU failed. (A connect is a CONTROL 11 call to the underlying access method for the LU.)

Effect The process continues; however, the LU does not start.

Issue a START LU command to verify the correction.

proc-name: LU open failed, LU = lu-name, Error: file-error

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`lu-name`	identifies the name of the logical unit (LU).
`file-error`	identifies a file-system error.

Cause SNAX/APC was unable to open the underlying SNAX access method.

Effect The process continues; however, the LU does not start.

Issue a START LU command to verify the correction.

proc-name: Invalid device type, LU = lu-name

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`lu-name`	identifies the name of the logical unit (LU).

Cause An LU device type is invalid.

Effect The process continues, but this LU cannot be used.

Recovery Specify a correct SNAX file name for the LU and restart the LU. The LU device type must be one of the supported access methods, such as a SNAX/XF LU or a SNAX/CDF APPL. If the LU is a parallel-session LU, the access method must be SNAX/APN.

proc-name: SNAX file error, LU = lu-name, Error: file-error

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`lu-name`	identifies the name of the logical unit (LU).
`file-error`	identifies a file-system error.

Cause SNAX/APC received a file-system error from the underlying access method.

Effect The process continues, but all of the sessions are lost and the conversations using these sessions are deallocated. A reopen is issued. If the open fails, the LU and its subordinates go into the STARTING state.

proc-name: TP-READY rejected - out of resources

proc-name

is the name of the SNAX/APC process for which the error occurred.

Cause SNAX/APC could not complete a TP-READY request because it could not obtain the necessary resources. The maximum number of conversations on the SNAX/APC process has been reached.

Effect The process continues, and the TP-READY request is rejected.

Recovery The transaction program should retry the TP-READY request at a later time. If the problem persists, try running an extra SNAX/APC process.

proc-name: Unexpected pacing req received, LU = lu-name

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`lu-name`	identifies the name of the logical unit (LU).

Cause A pacing request was received before SNAX/APC had responded to the last pacing request, or an unexpected pacing request was received.

Effect None; the process continues.

Recovery Informational message only; no corrective action is needed.

proc-name: Unknown message received

proc-name

is the name of the SNAX/APC process for which the error occurred.

Cause SNAX/APC received an unknown interprocess communication (IPC) message for processing.

Effect The process continues.

Recovery This is an application error. Check transaction programs for invalid IPC messages and correct them.

ptnr-lu: Received remote CNOS command

ptnr-lu

is the name of the partner logical unit (LU) for which the error occurred.

Cause A CNOS command was received.

Effect None.

Recovery Informational message only; no corrective action is needed.

ptnr-lu: CNOS conversation failed at conv-verb : RC = rc-retn, RC detail =rc-retn-detail

`ptnr-lu`	is the name of the partner logical unit (LU) for which the error occurred.
`conv-verb`	identifies the conversation verb at which the CNOS conversation failed. The following are text values for this parameter: Receive_and_Wait verb is returned if the CNOS conversation failed at the Receive_and_Wait verb. Send_Data verb is returned if the CNOS conversation failed at the Send_Data verb.
`rc-retn`	identifies the REP-RETURN-CODE of the failed CNOS conversation verb.
`rc-retn-detail`	identifies the REP-RETURN-CODE-DETAIL of the failed CNOS conversation verb.

Cause The CNOS conversation failed at the specified conversation verb.

Effect If the local logical unit (LU) is the source LU, the associated Distributed Systems Management (DSM) request is rejected. If the local LU is the target LU, this serves as an informational message; in this case, the remote LU should report a similar message. Whether the LU is the source LU or target LU, no session limit is changed.

Recovery If the local LU is the target LU, this is an informational message only; no corrective action is required. If the local LU is the source LU, retry the DSM request at the local LU, or reinitiate the CNOS operation at the remote LU.

ptnr-lu: CNOS command race occurred

ptnr-lu

is the name of the partner LU for which the error occurred.

Cause A CNOS command race was detected.

Effect Either the remote CNOS command or the local CNOS request or both are rejected.

Recovery Retry the rejected CNOS request.

ptnr-mode: Session limit changed by operator

ptnr-mode

is the name of the partner mode for which the error occurred.

operator

identifies whether the operator at the local or the remote logical unit (LU) initiated the change-session-limit operation. The following are text values for this parameter:

Local LU specifies that the command was initiated by the local LU.

Partner LU specifies that the command was initiated by the partner LU.

Cause The session limits of the specified PTNR-MODE object were changed by either the local or the remote LU.

Effect None

Recovery Informational message only; no corrective action is needed.

ptnr-lu: CNOS command negotiated

ptnr-lu

is the name of the partner logical unit (LU) for which the error occurred.

Cause The remote CNOS command is in effect, and the session limits have been negotiated. The CNOS reply was returned to the remote logical unit (LU) with the negotiated session limits.

Effect The CNOS command is in effect and the process continues.

Recovery Informational message only; no corrective action is needed.

ptnr-lu: CNOS command rejected - reason

ptnr-lu

is the name of the partner logical unit (LU) for which the error occurred.

reason

identifies the reason the CNOS command was rejected. The following are text values for this parameter:

mode name is not recognized specifies that the partner mode name is not recognized.

session limit is zero specifies that the session limit is set to 0.

Cause The remote CNOS command was rejected for the specified reason.

Effect The remote CNOS command is rejected. A reply is returned with the specified reason. No session limit is changed.

Recovery Correct and reissue the CNOS command at the remote logical unit (LU).

session-id: (-RSP) received, MU =mut Sense Data : %Hsense1 sense2 sna-err-text

`session-id`	identifies the session for which the error occurred.
`mut`	is the SNA response unit (RU).
`sense1`	is the first two bytes of sense data in hexadecimal. As much of the session name is supplied as is known at the time the response is sent. For example, if SNAX/APC receives a BIND request, it may reject the request before it has located the partner logical unit (LU) (or because it does not recognize the partner LU). In this case, the session name in the error contains only the local LU name of the LU sending the response.
`sense2`	is the second two bytes of sense data in hexadecimal.
`sna-err-text`	is an English-language explanation of the message for the first two bytes of the SNA sense data.

Cause A negative response was received on an SNA session.

Effect Inspect the sense data to determine the effect of the negative response.

Recovery Recovery depends upon the reason for the negative response, as given by the SNA sense code. See the IBM Systems Network Architecture Formats manual for further information on sense codes.

session-id: (-RSP) sent, MU =mut Sense Data : %Hsense1 sense2 sna-err-text

`session-id`	identifies the session for which the error occurred.
`mut`	is the SNA response unit (RU).
`sense1`	is the first two bytes of the SNA sense data. As much of the session name is supplied as is known at the time the response is sent. For example, if SNAX/APC receives a BIND request, it may reject the request before it has located the partner logical unit (LU) (or because it does not recognize the partner LU). In this case, the session name in the error contains only the local LU name of the LU sending the response.
`sense2`	is the second two bytes of sense data.
`sna-err-text`	is an English-language explanation of the first two bytes of sense data.

Cause A negative response was sent on an SNA session.

Effect Inspect the sense data to determine the effect of the negative response.

proc-name: Received RU exceeded MAXRUSIZE, LU = lu-name, SESSION = session-id

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`lu-name`	identifies the name of the logical unit (LU).
`session-id`	identifies the session.

Cause SNAX/APC received a response unit (RU) that exceeds the maximum RU size.

Effect Upon receipt of an oversized RU, SNAX/APC brings down the session. Any conversation using this session is therefore terminated.

Recovery The maximum RU size is decided at session establishment. No RU should be sent with a size greater than this value. Verify the current RU size setting in the remote LU.

proc-name: Switching configuration database to config-file

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`config-file`	identifies the name of the new configuration file database.

Cause Either an unexpected file error on the original configuration file or a Subsystem Programmatic Interface (SPI) or Subsystem Control Facility (SCF) ALTER PROC command has occurred which initiated a configuration file switch.

Effect None: the process continues.

Recovery Informational message only; no corrective action is needed. You should wait for the message that follows to determine the success or failure of the switch. Either message 34 (switching complete) or message 36 (switching failed) follows this message.

If the switch fails, an additional message precedes the operator message 36. This message shows the error that caused the switch to fail.

proc-name: Switching configuration database to config-file ‑COMPLETE

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`config-file`	identifies the name of the new configuration file database.

Cause A successful configuration file database switch to the named configuration file has occurred.

Effect None; the process continues.

Recovery Informational message only; no corrective action is needed.

proc-name: CONFIG file was BAD on takeover

proc-name

is the name of the SNAX/APC process for which the error occurred.

Cause A backup takeover occurred when the configuration file could not be used because a configuration file switch was in progress.

Effect The process terminates abnormally.

Recovery If the switch occurred because the file became inaccessible, correct the disk failure before starting the SNAX/APC process.

If the switch was due to an ALTER PROCESS command, the SNAX/APC process can be started using the original configuration file.

proc-name: Switching configuration database - FAILED

proc-name

is the name of the SNAX/APC process for which the error occurred.

Cause A configuration database file switch has failed

Effect The process continues. If the switch failed because the old configuration database file was inaccessible, SNAX/APC has no current database file. SNAX/APC will continue to perform conversation related activities and to honor CNOS requests from the remote LU. However, SNAX/APC will not honor any sensitive Subsystem Programmatic Interface (SPI) or Subsystem Control Facility (SCF) commands. Any such commands will be rejected with the SNAX/APC error 39.

If the switch was prompted by an ALTER PROCESS command, and the original configuration file is still accessible, the SNAX/APC process reverts to the original file as its configuration database.

Recovery Informational message only; no corrective action is needed.

proc-name: Configuration database has been converted to current level; Old CONFIG file was renamed to config-file

`proc-name`	is the name of the SNAX/APC process for which the error occurred.
`config-file`	identifies the name of the new configuration file database.

Cause A warm start has occurred and SNAX/APC has automatically converted the configuration file database to the current level.

Effect The original configuration database file is renamed to \node.$volume.subvolume.ZZCFnnnn, where nnnn is a unique number derived from the timestamp and the node, volume, and subvolume values are the same as the node, volume and subvolume names for the new configuration file.

Recovery Informational message only; no corrective action is needed.

subj-lu: Invalid logon received from partner LU subj-ptnr-lu, user ID: lu62-userid

`subj-lu`	names the local SNAX/APC LU that received the attach with the invalid logon.
`subj-ptnr-lu`	names the partner (remote) LU that sent the attach with the invalid logon.
`lu62-userid`	is the user ID specified in the attach.

Cause SNAX/APC received an attach from a partner LU that contained an invalid user ID and password pair or an invalid user ID with the already verified indicator.

Effect SNAX/APC rejects the attach with sense code %H080F6051, security violation.

Recovery The security information supplied by the partner LU does not agree with the security information defined in the local security manager, Safeguard. There are three cases to consider.

The local security information is wrong. To recover, correct the security definitions in the security manager, Safeguard.
The remote security information is wrong. This could indicate an incorrect configuration at the remote LU. If the client transaction program permits a person to enter the user ID and password, this could simply indicate a typing error. Correct the security information at remote LU.
Someone is attempting to penetrate security. A number of these messages for the same user ID from the same remote LU in a short period of time would indicate an attempt to break security. If you suspect this, see the person in your organization responsible for information systems security.

subj-proc: Started security server server-name in CPU sec-server-cpu

`subj-proc`	names the SNAX/APC process that started the security server.
`server-name`	names the security server just started.
`sec-server-cpu`	is the number of the CPU in which the security server was started.

Cause SNAX/APC has started the security server.

Effect Informational message only, no corrective action is needed.

Recovery None

subj-proc: Error accessing security server sec-server-name, file system error file-err

`subj-proc`	names the SNAX/APC process.
`sec-server-name`	names the security server.
`file-err`	is the number of the file error.

Cause SNAX/APC attempted to access the security server and failed because of the error specified by FILE-ERR.

Effect If the error indicates that the security server has stopped, SNAX/APC starts a new security server and tries the operation again. If SNAX/APC is unable to recover automatically from the error, SNAX/APC deactivates the session; the UNBIND request contains the sense code %H084F0002, security component not available.

Recovery When SNAX/APC recovers automatically, no other recovery action is required. If SNAX/APC deactivates the session, examine the error number in this event. If the error number indicates a condition that can be corrected, correct the problem and try the operation again. If the problem cannot be corrected, get a trace of the problem and contact your service provider.