Appendix A: Standard communications error subcodes

Subcodes returned during allocates, sends, and receives

The following subcodes in Table A-1indicate allocate errors that occur when allocating a conversation, sending data, and receiving data.

**Table A-1: Subcodes for allocate errors**
No.	Error subcode	Explanation
1	XC_UNSUCCESSFUL	Call was unsuccessful.
2	XC_TPNNOTRECOG	Did not recognize transaction program name.
3	XC_INVALIDACC	An invalid account type was specified.
4	XC_CONVTYPE	Conversation type mismatch.
5	XC_BADSYNCLVL	Specified sync level is not supported.
6	XC_LUNSYNCVL	Specified sync level is not supported by the current LU.
7	XC_PNSYNCVL	Specified sync level is not supported by the current program.
8	XC_ALLOCFAILNR	Allocation failure. No retry.
9	XC_ALLOCFAILR	Allocation failure. Retry.
10	XC_TPSTARTNR	Transaction program cannot be started. No retry.
11	XC_TPSTARTR	Transaction program cannot be started. Retry.
12	XC_NORECONN	Reconnect is not supported.
13	XC_NOTPRECONR	Cannot reconnect TP. Retry.
14	XC_NOTPRECONN	Cannot reconnect TP. No retry.
15	XC_NOPGRECONN	Reconnect is not supported by the current program.
16	XC_NOLURECONN	Reconnect is not supported by the current LU.
17	XC_NOPIP	Program initialization parameter (PIP) data is not supported.
18	XC_INVALPIP	The wrong PIP was specified.
19	XC_SVCTYPE	An unsupported datatype was specified.
20	XC_SHUTSESS	A shutdown request was received.
22	XC_WOULDBLOCK	Allocate will block waiting for session.
24	XC_SYM_DEST_NOT_ FOUND	Could not find SYM-DEST-NAME in table.
25	XC_BADPATH	SNA Bad path name prefix or suffix, or path name is read only.
26	XC_SECVIOLATE	Allocation failed due to security violation.
27	XC_TRAN_FAILED	The transaction failed or there is deadlock.

The following subcodes in Table A-2 indicate errors that occur while sending or receiving data.

**Table A-2: Subcodes for send and receive errors**
No.	Error subcode	Explanation
30	XC_PROGPURG	Program error: purging.
31	XC_PROGPURGNOTR	Program error: no truncate.
32	XC_PROGPURGTR	Program error: truncate.
33	XC_SVCPURG	Switched virtual circuit (SVC) error: purging.
34	XC_SVCPURGNOTR	SVC error: no truncate.
35	XC_SVCPURGTR	SVC error: truncate.
37	XC_TOO_MANYPARMS	Too many parameters were specified for this operation.
38	XC_VIOLATED_RULE	The operation violated one or more rules.

The following subcodes Table A-3 indicate deallocation errors.

**Table A-3: Subcodes for deallocate errors**
No.	Error subcode	Explanation
40	XC_PGMDEAL	Deallocate_abend_program.
41	XC_SVCDEAL	Deallocate_abend_svc (switched virtual circuit).
42	XC_TIMDEAL	Deallocate_abend_timer.
43	XC_NDELAY	Delay_allocation is not supported.

The following subcodes in Table A-4 indicate general resource failures that can occur while allocating a conversation, sending data, or receiving data.

**Table A-4: Subcodes for general resource failure errors**
No.	Error subcode	Explanation
50	XC_RESFAILR	Resource failure. Retry.
51	XC_RESFAILNR	Resource failure. No retry.
52	XC_RESFAILNOSES	No session: resource failure.
53	XC_SESLIMSET0	No session; session limit was set to 0.
54	XC_CONNSTOP	SNA connection stopped.
55	XC_LINEDOWN	SNA Link is down or inaccessible.
56	XC_CONNDOWN	SNA Connection (Profile) is not up.
57	XC_SNADOWN	SNA Services is stopped.
58	XC_NORESOURCES	SNA is out of resources.
59	XC_TIMEOUT	SNA Allocate timed out.
60	XC_INVALGEN	There is a problem with one of the AIX SNA Services profiles.
61	XC_BADFILENUM	SNA Services file number is invalid.
62	XC_HIT_MAXFILES	No more files can be opened; the maximum number allowed are already open.
63	XC_TXTBUSY	SNA path -- busy executable.
64	XC_TEMPSOS	SNA internal storage allocation failed.
65	XC_FNS	CMxxx function not supported. (IMS)
66	XC_WRONG_ENVIRON	Wrong environment for this call. (IMS)
67	XC_TOO_SHORT	Length of the buffer or parameter is too short.
68	XC_TOO_LONG	Length of the buffer or parameter is too long.
69	XC_IO_ERROR	An I/O error was detected.

View this book as PDF