Open ClientConnect and Open ServerConnect Messages and Codes

Home

Open ClientConnect and Open ServerConnect Messages and Codes

Appendix B: Standard Communications Error Subcodes

Appendix B

Standard Communications Error Subcodes

This appendix lists the Common Programming Interface for Communications (CPIC) communications error subcodes that can be returned to Gateway-Library programs and to DirectConnect for MVS. The following is the subcode categories in this appendix:

Within Gateway-Library programs, these codes are returned to TDACCEPT and TDSTATUS. See the Open ServerConnect Programmer's Reference for more information about these functions.

DirectConnect for DB2 converts error codes to U.S. English before returning them.

Subcodes Returned During Allocates, Sends, and Receives

The following subcodes indicate allocate errors that occur when allocating a conversation, sending data, and receiving data.

Table B-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.

**Table B-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 indicate errors that occur while sending or receiving data.

Table B-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.

**Table B-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 indicate deallocation errors.

Table B-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.

**Table B-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 indicate general resource failures that can occur while allocating a conversation, sending data, or receiving data.

Table B-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.

**Table B-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.

Subcodes Indicating Programming Errors

The following subcodes indicate programming errors on the part of the application programmer or in Sybase's code.

Table B-5: Subcodes for application programming errors
No.
Error Subcode
Explanation
70
XC_SNASTATE
Command was not issued in allowed state.
71
XC_GDSBOUND
Command was not issued on logical record boundary.
72
XC_INVALPARMS
Input parameters are invalid.
73
XC_INVALCMD
SNA Services command is invalid.
74
XC_BADADDRESS
Address for buffer or parameter is invalid.
75
XC_RESID
Resource ID (RID) is invalid.
76
XC_NORESTART
Recovery-level = restart is not supported.
77
XC_MAPS
Map name/Map execution errors.
78
XC_FMHS
Function Management Header (FMH) data is not supported by mapped conversion.
79
XC_NMVTLENGTH
Specified network management vector transport (NMVT) length is invalid.
80
XC_NMVTHDR
Specified NMVT HEADER is invalid.

**Table B-5: Subcodes for application programming errors**
No.	Error Subcode	Explanation
70	XC_SNASTATE	Command was not issued in allowed state.
71	XC_GDSBOUND	Command was not issued on logical record boundary.
72	XC_INVALPARMS	Input parameters are invalid.
73	XC_INVALCMD	SNA Services command is invalid.
74	XC_BADADDRESS	Address for buffer or parameter is invalid.
75	XC_RESID	Resource ID (RID) is invalid.
76	XC_NORESTART	Recovery-level = restart is not supported.
77	XC_MAPS	Map name/Map execution errors.
78	XC_FMHS	Function Management Header (FMH) data is not supported by mapped conversion.
79	XC_NMVTLENGTH	Specified network management vector transport (NMVT) length is invalid.
80	XC_NMVTHDR	Specified NMVT HEADER is invalid.

Subcodes Indicating Errors Related to IBM Software

The following subcodes indicate programming errors that are internal to IBM software.

Table B-6: Subcodes for internal IBM programming errors
No.
Error Subcode
Explanation
81
XC_PROTOCOL
SNA protocol violation.
82
XC_SNACODEFAIL
SNA system failure.
83
XC_NORCB
No RCB.
84
XC_NOMODECB
Cannot find the mode control block.
85
XC_SENSE
Sense code included.
86
XC_NOSESACT
Session was not established.
87
XC_IBMOTHER
Other, non-LU6.2 related errors.
88
XC_INOP
INOP received.
89
XC_HIERRESET
Hierarchical Reset received.
90
XC_NOLUREGIS
No LU registered.
91
XC_PUERP
SNA ACTPU (ERP) received.
92
XC_FILE_TOOBIG
File is too big (Error number 27).
93
XC_UNKNOWN_CODE
Unknown, unrecognized vendor code.

**Table B-6: Subcodes for internal IBM programming errors**
No.	Error Subcode	Explanation
81	XC_PROTOCOL	SNA protocol violation.
82	XC_SNACODEFAIL	SNA system failure.
83	XC_NORCB	No RCB.
84	XC_NOMODECB	Cannot find the mode control block.
85	XC_SENSE	Sense code included.
86	XC_NOSESACT	Session was not established.
87	XC_IBMOTHER	Other, non-LU6.2 related errors.
88	XC_INOP	INOP received.
89	XC_HIERRESET	Hierarchical Reset received.
90	XC_NOLUREGIS	No LU registered.
91	XC_PUERP	SNA ACTPU (ERP) received.
92	XC_FILE_TOOBIG	File is too big (Error number 27).
93	XC_UNKNOWN_CODE	Unknown, unrecognized vendor code.

Subcodes Indicating Errors Related to CNM

The following subcodes indicate errors related to Communication Network Management (CNM).

Table B-7: Subcodes for CNM-related errors
No.
Error Subcode
Explanation
94
XC_UNDEF_SVR
Application server not defined.
95
XC_SSIDINVALID
Invalid System Services Control Point identifier (SSCP-ID) specified.
96
XC_SSCPPU
Errors in available SSCP-PU session.
97
XC_SSCPNOTACT
SSCP-PU session not active.

**Table B-7: Subcodes for CNM-related errors**
No.	Error Subcode	Explanation
94	XC_UNDEF_SVR	Application server not defined.
95	XC_SSIDINVALID	Invalid System Services Control Point identifier (SSCP-ID) specified.
96	XC_SSCPPU	Errors in available SSCP-PU session.
97	XC_SSCPNOTACT	SSCP-PU session not active.

Subcodes Indicating Errors Related to TDS or Other Protocols

The following subcodes are returned when Gateway-Library forces an abend, due to Tabular Data Stream (TDS), or other protocol violations.

Table B-8: Subcodes for Gateway-Library abends and protocol violations
No.
Error Subcode
Explanation
100
XC_TDSABEND
TDS-level protocol violation.
101
XC_TDSPARMERR
TDS: internal parameter error.

No.	Error Subcode	Explanation
100	XC_TDSABEND	TDS-level protocol violation.
101	XC_TDSPARMERR	TDS: internal parameter error.


	Expand Search