SNAX/APC Application Programming Manual

Interprocess Communications and Units of Work
SNAX/APC Application Programming Manual—138786
2-8
IPC Return Code Details
IPC Return Code Details
Table 2-2 describes the values that can be returned in the HEADER-RETURN-CODE-
DETAIL field of the IPC header.
8 INVALID-REQ-
CODE
The value in the REQUEST-CODE field was invalid.
9SNAX-FILE-
ERROR
The SNAX/APC process received an operating system error
from SNAX/XF or SNAX/CDF while processing the verb
request. The HEADER-RETURN-CODE-DETAIL field
contains the operating system error number. If a TP
receives a SNAX-FILE-ERROR, it must assume that
SNAX/APC aborted the conversation. See Table 2-2.
10 OUT-OF-
RESOURCES
The local TP issued an ALLOCATE or TP-READY with Y
in LOCAL-ATTACH, but no resources are available. This
request can be retried.
Table 2-2. IPC Return Code Details (page 1 of 3)
HEADER-RETURN-
CODE
HEADER-RETURN-
CODE-DETAIL
Value Label Value Label Meaning
2 INVALID-
RESOURCE-
ID
310 CONFIG-
ERROR
One or more of the configuration
database entries for the local LU is in
error.
3SERVICE-
DENIED
401 PROCESS-
RESET
The primary CPU of the SNAX/APC
process failed, and the backup took
over. The local TP may or may not
receive an operating system error 201.
The local TP must issue a new TP-
READY request.
402 MULT-UOW-
NOT-
ALLOWED
An IPC message containing a TP-
READY request also contained
another UOW.
403 PREVIOUS-
IPC-NOT-
COMPLETED
The local TP sent an IPC message to
SNAX/APC before a previous message
for the same resource ID completed.
404 MULT-
ALLOC-NOT-
ALLOWED
The local TP issued two or more
ALLOCATE verbs after a single TP-
READY verb. Only one ALLOCATE
verb can be issued for each
TP-READY verb issued.
405 TP-RQ-NOT-
SUPPORTED
SNAX/APC did not recognize a
request issued by the local TP.
Table 2-1. IPC Header Return Codes (page 2 of 2)
Value Label Meaning