General inserts for the XAP-TP messages

XPRET	Meaning
2	Not first process of application
-1	Function call not successful due to permanent error.
-2	Function call not successful due to transient error. Retry the call later
-3	Function call not successful, data flow stopped Continue after event GO
-4	Session call: Expedited function call stopped due to expedited data flow control shortage Continue after event S_XGO/S_GO
	Presentation call: Function call not successful, apref invalid
	Local function call: Invalid connection reference
	ACSE call: Function call not successful, apref resp. aref invalid
-5	Invalid waiting point reference
-6	Invalid application reference
-7	Waiting period to obtain a lock on a shared association expired

XPERR	Meaning
1	No memory available (temporary)
100	Call sequence error
101	Application not attached
102	Sending of data not allowed; wait for GO event
103	Internal error
104	Shared association is not locked
200	Missing ACSE/presentation reference
201	Invalid ACSE/presentation reference
202	Presentation call: missing AVX list (o_attach) ACSE call: missing application reference
203	Presentation call: invalid AVX list ACSE call: invalid application reference
204	Presentation call: invalid abstract syntax name in AVX ACSE call: missing ACSE parameters
205	Presentation call: invalid decoding mode in AVX ACSE call: missing presentation parameters
206	Presentation call: invalid user data length ACSE call: missing session parameters
207	Presentation call: invalid context id in p_udl ACSE call: missing application context name
208	Presentation call: invalid next parameter in p_udl ACSE call: invalid application context name
209	Presentation call: invalid pdv parameter in p_udl ACSE call: invalid calling AP Title
210	Presentation call: invalid chaining parameter ACSE call: invalid calling AE Qualifier
211	Presentation call: missing token parameter ACSE call: invalid called AP Title
212	Presentation call: invalid token parameter ACSE call: invalid called AE Qualifier
213	Presentation call: missing rtype parameter ACSE call: invalid responding AP Title
214	Presentation call: invalid rtype parameter ACSE call: invalid responding AE Qualifier
215	Presentation call: missing type parameter ACSE call: missing called p_address
216	Presentation call: invalid type parameter ACSE call: invalid called p_address
217	Presentation call: invalid syncp parameter ACSE call: missing calling p_address
218	Presentation call: missing syncp parameter ACSE call: missing responding p_address
219	Presentation call: invalid ctxlst parameter ACSE call: no mode parameter
220	Presentation call: invalid number of abstract syntaxes passed to OSS ACSE call: invalid mode parameter
221	Presentation call: invalid transfer syntax name ACSE call: missing result
222	Presentation call: invalid number of transfer syntaxes ACSE call: invalid result
223	Presentation call: invalid number of abstract syntaxes ACSE call: missing result source
224	Presentation call: same abstract syntax occurred already in transparent or non-transparent mode ACSE call: invalid result source
225	Presentation call: invalid data separation parameter ACSE call: invalid diagnostic
226	ACSE call: missing reason
227	ACSE call: invalid reason
228	ACSE call: missing provider reason
229	ACSE call: invalid provider reason
230	ACSE call: missing abort source
231	ACSE call: invalid p-requirements
232	ACSE call: invalid s-requirements
233	ACSE call: invalid syntax identifier
234	ACSE call: invalid p-context identifier
235	ACSE call: invalid p-context definition list
236	ACSE call: invalid p-context definition result list
237	ACSE call: invalid result in p-context definition result list
238	ACSE call: invalid default p-context result
239	ACSE call: invalid default p-context name
240	ACSE call: invalid user data length
241	ACSE call: invalid quality of service
242	ACSE call: invalid sync point serial number
243	ACSE call: invalid tokens
244	ACSE call: invalid SS-user reference
245	ACSE call: invalid SS-common reference
246	ACSE call: invalid SS-additional reference
250	Presentation call: ASN encoding error ACSE call: ASN encoding error
251	Presentation call: ASN decoding error ACSE call: ASN decoding error
252	Presentation call: ASN: invalid value in data struct ACSE call: ASN: invalid value in data struct
253	Presentation call: ASN: invalid object id in data struct ACSE call: ASN: invalid object id in data struct
254	Presentation call: ASN: invalid length in data struct ACSE call: ASN: invalid length in data struct
255	Presentation call: ASN: invalid index in data struct ACSE call: ASN: invalid index in data struct
256	Presentation call: ASN: invalid tag in syntax table ACSE call: ASN: invalid tag in syntax table
300	Presentation call: invalid protocol state ACSE call: invalid protocol state Local function call: error on system call
301	Presentation call: protocol error ACSE call: protocol error Local function call: error on transport system call
302	Local function call: error on local function call
305	Local function call: error on session call
306	Local function call: error on presentation call
307	Local function call: error on ACSE call

XPRJCT	Meaning
0	NO_REJECT
1	APPLICATION_CONTEXT_NAME_TOO_LONG The object identifier received from the partner, which forms the application context name, contains more elements than supported by openUTM.
2	CALLING_APT_TOO_LONG A length was specified for the application process title in the association indication which is not supported by openUTM.
3	CALLING_AEQ_TOO_LONG A length was specified for the application entity qualifier in the association indication which is not supported by openUTM.
4	CALLED_APT_TOO_LONG The application process title which was called is longer than that supported by openUTM.
5	CALLED_AEQ_TOO_LONG The application entity qualifier which was called is longer than that supported by openUTM.
6	CONTEXT_DEFINITION_LIST_TOO_LONG More abstract syntaxes were passed for the association indication than are supported by openUTM.
7	CONTEXT_RESULT_LIST_TOO_LONG The list of supported abstract syntaxes passed when establishing an association (association indication or confirmation) contains more elements than are supported by openUTM.
9	ADDRESS_NO_PSAPINFO The address passed for association indication or confirmation does not contain any information on PSAP.
10	ADDRESS_NO_INFOVERS_0_PSAP The address passed for association indication or confirmation contains an incorrect version for the PSAP information.
11	ADDRESS_INVALID_P_SEL_LENGTH The address passed for association indication or confirmation contains an invalid length for the presentation selector.
12	ADDRESS_NO_SSAPINFO The address passed for association indication or confirmation does not contain any information on SSAP.
13	ADDRESS_NO_INFOVERS_0_SSAP The address passed for association indication or confirmation contains an incorrect version for the SSAP information.
14	ADDRESS_INVALID_S_SEL_LENGTH The address passed for association indication or confirmation does not contain a valid part for the session selector.
15	ADDRESS_NO_PARTNER_MODE The address passed for association indication or confirmation does not contain a valid part for the network and transport selector.
16	ADDRESS_TNSX_ERROR The address passed for association indication or confirmation has been rejected by TNS.
17	UNKNOWN_PARTNER The address passed for association indication or confirmation is not known in the local application.
18	WRONG_APPLICATION_CONTEXT_NAME The application context passed for association indication or confirmation does not correspond to the application context name generated in the local application.
19	ABSTRACT_SYNTAX_MISSING The association indication or confirmation supports less abstract syntaxes than are generated in the local application.
20	OSITP_SYNTAX_MISSING The association indication or confirmation does not support the abstract syntax for OSI-TP.
21	NO_TP_INITIALIZE No TP-INITIALIZE-RI/RC PDU was passed with the association indication or confirmation.
22	OSITP_NO_VERSION_1 The partner does not support Version 1 of the OSI-TP protocol.
23	OSITP_RCH_WRONG_LENGTH The recovery context handle passed with the TP-INITIALIZE-indication or TP-INITIALIZE-confirmation is of a length not supported by openUTM.
24	NO_CCR_INITIALIZE The CCR-INITIALIZE-RI PDU is missing.
25	CCR_NOT_VERSION_2 The partner does not support Version 2 of the CCR protocol.
26	SESSION_NO_FDX Session functionality “full duplex” has not been set.
27	SESSION_NO_DATA_SEPARATION Session functionality “data separation” has not been set although CCR is in the context.
28	SESSION_NO_TYPED_DATA Session functionality “typed data” has not been set although CCR is in the context.
29	SESSION_NO_MINOR_SYNCHRONIZE Session functionality “minor synchronize” has not been set although CCR is in the context.
30	SESSION_NO_RESYNCHRONIZE Session functionality “resynchronize” has not been set although CCR is in the context.
31	TOKEN_CONTENTION_WINNER_AND_NO_TOKEN The local application is the contention winner, but does not possess the “token” (only if CCR is in the context).
32	TOKEN_CONTENTION_LOSER_AND_TOKEN The local application is the contention loser, but possesses the “token” (only if CCR is in the context).
33	INITIAL_SYNC_POINT_SERIAL_NUMBER_NOT_SET The initial syncpoint serial number is not set, although CCR is in the context.
34	NO_MORE_CONTENTION_LOSER_ASSOCIATIONS The request to establish an association from outside is rejected because all the contention loser associations have already been established in the local application.
35	NO_MORE_CONTENTION_WINNER_ASSOCIATIONS Request to establish an association from outside is rejected because all the contention winner associations have already been established in the local application.
36	CCR_BUT_NO_PARTNER_AET Partner did not specify an application entity title, although CCR is in the context.
37	CCR_BUT_NO_OWN_AET No application entity title is specified in the local application, although CCR is in the context.
38	RESPONDING_APT_TOO_LONG The application process title specified in the association confirmation is longer than that supported by openUTM.
39	RESPONDING_AEQ_TOO_LONG The application entity qualifier specified in the association confirmation is longer than that supported by openUTM.
40	ASS_ESTABLISHMENT_TIMEOUT The establishment of an association started by the local application cannot be completed in the specified time.
41	PARTNER_IS_IN_QUIET_STATE The request for establishment of an association will be rejected because the partner in the local application has been set to Quiet.
42	NO_SPACE_FOR_RCH The PutElement call for storing the recovery context handle returned a bad value.
43	REMOTE_AET_2_BIG The application entity title of the partner is longer than that supported by openUTM.
44	REMOTE_AET_CHANGED When establishing parallel associations to a partner the partner did not provide the same application entity title as for the first association established.
45	NO_SPACE_FOR_REMOTE_AET The PutElement call for storing the application entity title of the partner returned a bad value.
46	PARTNER_HAS_STATUS_OFF The establishment of the association is rejected because the partner is locked in the local UTM application (STATUS=OFF is set).

XPNDIA	Meaning
0	NO_REASON_GIVEN
1	NO_COMMON_ACSE_VERSION The partner rejected the request to establish an association because there is no common ACSE version.
2	APPL_CONTXT_NAM_NOT_SUPPORTD The partner rejected the request to establish an association because it does not support the application context name.
3	CALLING_AP_TITLE_NOT_RECON The partner rejects the request to establish a connection because the partner has not been generated correctly at the sender (e.g. incorrect N-SEL). or (only for heterogeneous links): The partner rejects the request to establish a connection because it does not know the Calling Application Process Title
4	CALLING_AE_QUALI_NOT_RECON The partner rejected the request to establish an association because it does not know the calling application entity qualifier.
5	CALLING_AP_INVOC_ID_NOT_RECON The partner rejected the request to establish an association because it does not know the calling application process invocation identifier.
6	CALLING_AE_INVOC_ID_NOT_RECON The partner rejected the request to establish an association because it does not know the calling application entity invocation identifier.
7	CALLED_AP_TITLE_NOT_RECON The partner rejected the request to establish an association because it does not know the called application process title.
8	CALLED_AE_QUALI_NOT_RECON The partner rejected the request to establish an association because it does not know the called application entity qualifier.
9	CALLED_AP_INVOC_ID_NOT_RECON The partner rejected the request to establish an association because it does not know the called application process invocation identifier.
10	CALLED_AE_INVOC_ID_NOT_RECON The partner rejected the request to establish an association because it does not know the called application entity invocation identifier.
11	PERMANENT_FAILURE The partner cleared the association because a permanent error occurred.
12	BEGIN_TRANSACTION_REJECT The partner cleared the association because it rejected the start of a transaction.
13	TRANSIENT_FAILURE The partner cleared the association because a temporary error occurred.
14	PROTOCOL_ERROR The partner cleared the association because a protocol error occurred.
15	UNRECOGNIZED_PDU The association was cleared from outside with P-ABORT because the presentation layer received an unknown presentation PDU.
16	UNEXPECTED_PDU The association was cleared from outside with P-ABORT because the presentation layer received an unexpected presentation PDU.
17	UNEXPECTED_SESSION_SERVICE_PRIMITIVE The association was cleared from outside with P-ABORT because the session layer received an unexpected session service primitive.
18	UNRECOGNIZED_PDU_PARAMETER The association was cleared from outside with P-ABORT because the presentation layer received an unknown PPDU parameter.
19	UNEXPECTED_PPDU_PARAMETER The association was cleared from outside with P-ABORT because the presentation layer received an unexpected PPDU parameter.
20	INVALID_PPDU_PARAMETER_VALUE The association was cleared from outside with P-ABORT because the presentation layer received an invalid PPDU parameter value.
21	RELEASE_NORMAL The association was cleared by the partner with release. The partner specified release normal as the reason.
22	RELEASE_URGENT The association was cleared by the partner with release. The partner specified release urgent as the reason.
23	RELEASE_USER_DEFINED The association was cleared by the partner with release. The partner specified user defined as the reason
24	IDLE_TIMEOUT_ABORT The association was cleared by the local application because the association was not used in the time generated with IDLETIME.
25	ABORT_BY_ASS_INDICATION The association was terminated by the local UTM application because a request to establish an association was received and no suitable, non-established association was available.
26	ABORT_BY_ADM_OR_SHUT The association was cleared by the local application using administration facilities or because the application was shut down.