Messages of the XAP-TP provider

The messages from the XAP-TP provider all start with the letter “P”. The values for the inserts are either described following the message or (if the insert occurs a number of times) in section “General inserts for the XAP-TP messages”.

P001

Error on OSS call (&XPFUNC): &ACPNT, &XPRET, &XPERR, &XP1INFO, &XP2INFO

This message is output if a call to an OSS function (&XPFUNC) returns an error. If the error has been reported by the transport system, message P012 is also output.

The inserts have the following meaning:

&XPFUNC	Name of the OSS function
&ACPNT	Name of the local ACCESS-POINT
&XPRET	See table on "General inserts for the XAP-TP messages"
&XPERR	See table on "General inserts for the XAP-TP messages"
&XP1INFO	Supplementary OSS information
&XP2INFO	Supplementary OSS information

P002

Error on association establishment (&XPFUNC): &ACPNT, &OSLPAP, &XPRET, &XPERR, &XP1INFO, &XP2INFO

This message is issued if the call to an OSS function (&XPFUNC) required to establish an association returns an error. If the error has been reported by the transport system, message P012 is also output. If the error has not been reported by the transport system, the application is terminated with “Termapplication”.

The inserts have the following meaning:

&XPFUNC	Name of the OSS function
&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPRET	See table on "General inserts for the XAP-TP messages"
&XPERR	See table on "General inserts for the XAP-TP messages"
&XP1INFO	Supplementary OSS information
&XP2INFO	Supplementary OSS information

P003

Association rejected (a_assin() ):&ACPNT, reason: &XPRJCT, length: &XPLTH

This message is issued if a request to establish an association was rejected from outside.

The inserts have the following meaning:

&ACPNT	Name of the local ACCESS-POINT
&XPLTH	Incorrect length
&XPRJCT	See table on "General inserts for the XAP-TP messages"

P004

Association rejected (a_assin() ):&ACPNT, &OSLPAP, reason: &XPRJCT

This message is issued if a request to establish an association was rejected from
outside.

The inserts have the following meaning:

&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPRJCT	See table on "General inserts for the XAP-TP messages"

Possible causes in the case of &XPRJCT = 34 or &XPRJCT = 35 (NO_MORE_CONTENTION_LOSER / WINNER_ASSOCIATIONS, "General inserts for the XAP-TP messages"):

• Associations have been disconnected without the local UTM application being informed of this. The local UTM application considers that these associations still exist. The OSI-TP partner application attempts to re-establish these associations. However, these cannot be re-established until either the affected associations have been disconnected due to the expiry of the idle timer or all associations to the relevant partner have been disconnected at the administrative level.

• More associations are generated in the OSI-TP partner application than in the local UTM application.

• Different numbers of contention losers/winners in the local and partner applications

P005

Association rejected (a_assin() ):&ACPNT, reason: unknown partner
N-SEL: &XPNSEL, T-SEL: &XPTSEL
S-SEL: (&XPLSSEL,&XPCSSEL,&XPHSSEL)
P-SEL: (&XPLPSEL,&XPCPSEL,&XPHPSEL)

This message is issued if a request to establish an association was rejected from outside because the remote partner is not known to the local application.
The inserts have the following meaning:

&ACPNT	Name of the local ACCESS-POINT
&XPNSEL	Network selector of the remote partner
&XPTSEL	Transport selector  of the remote partner
&XPLSSEL	Length of the session selector of the remote partner
&XPCSSEL	Session selector (printable) of the remote partner
&XPHSSEL	Session selector (hexadecimal) of the remote partner
&XPLPSEL	Length of the presentation selector of the remote partner
&XPCPSEL	Presentation selector (printable) of the remote partner
&XPXPSEL	Presentation selector (hexadecimal) of the remote partner

P006

Association rejected (a_assin() ): &ACPNT, &OSLPAP, reason: wrong application context name ( &XP0OBID, &XP1OBID, &XP2OBID, &XP3OBID, &XP4OBID, &XP5OBID, &XP6OBID, &XP7OBID, &XP8OBID, &XP9OBID )

This message is issued if a request to establish an association was rejected from outside. The application context name for the remote partner does not match the application context name generated for this partner in the local application.

The inserts have the following meaning:

&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XP0OBID - &XP9OBID	These are (up to) ten elements of the object identifier which form the application context name of the remote partner. -1 is output for elements which do not have a value assigned.

P007

Error on association establishment (a_assrs() ): &ACPNT, &OSLPAP, &XPRET, &XPERR, &XP1INFO, &XP2INFO

This message is output when a call to the OSS function a_assrs() to respond to a request to establish an association from outside returns an error. If the error has been reported by the transport system, message P012 is also output.

The inserts have the following meaning:

&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPRET	See table on "General inserts for the XAP-TP messages"
&XPERR	See table on "General inserts for the XAP-TP messages"
&XP1INFO	Supplementary OSS information
&XP2INFO	Supplementary OSS information

P008

Association (&XPOSAS ) established: &ACPNT, &OSLPAP

This message is issued when an association has been established.

The inserts have the following meaning:

&XPOSAS	Index of the relevant association
&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application

P009

Association (&XPOSAS ) rejected (a_asscf() ): &ACPNT, &OSLPAP, reason: &XPRJCT, length: &XPLTH

This message is issued when active establishment of an association is rejected because the confirmation from the partner cannot be accepted.

The inserts have the following meaning:

&XPOSAS	Index of the relevant association
&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPRJCT	See table on "General inserts for the XAP-TP messages"
&XPLTH	Possible incorrect length

P010

Association (&XPOSAS ) rejected (a_asscf() ): &ACPNT, &OSLPAP, reason: unknown partner
N-SEL: &XPNSEL, T-SEL: &XPTSEL
S-SEL: (&XPLSSEL,&XPCSSEL,&XPHSSEL)
P-SEL: (&XPLPSEL,&XPCPSEL,&XPHPSEL)

This message is issued when active establishment of an association is rejected, because the remote partner confirms establishment of an association with an address (&XPADDR) which is unknown to the local application.

The inserts have the following meaning:

&XPOSAS	Index of the relevant association
&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPNSEL	Network selector of the remote partner
&XPTSEL	Transport selector  of the remote partner
&XPLSSEL	Length of the session selector of the remote partner
&XPCSSEL	Session selector (printable) of the remote partner
&XPHSSEL	Session selector (hexadecimal) of the remote partner
&XPLPSEL	Length of the presentation selector of the remote partner
&XPCPSEL	Presentation selector (printable) of the remote partner
&XPXPSEL	Presentation selector (hexadecimal) of the remote partner

P011

Association (&XPOSAS ) rejected (a_asscf() ): &ACPNT, &OSLPAP, reason: wrong application context name ( &XP0OBID, &XP1OBID, &XP2OBID, &XP3OBID, &XP4OBID, &XP5OBID, &XP6OBID, &XP7OBID, &XP8OBID, &XP9OBID )

This message is issued when active establishment of an association is rejected, because the remote partner confirms establishment of an association with an application context name other than the one configured for this partner in the local application.

The inserts have the following meaning:

&XPOSAS	Index of the relevant association
&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XP0OBID - &XP9OBID
	These are (up to) ten elements of the object identifier which form the application context name of the remote partner. -1 is output for elements which do not have a value assigned.

P012

CMX diagnostic information: &XPCTYPE, &XPCCLS, &XPCVAL

This message is issued if a preceding message is issued as a result of an error reported by the transport system. The diagnostic code of the transport system is print-edited. The following table describes a number of values for &XPCTYPE, &XPCCLS and &XPCVAL. The CMX header file cmx.h contains a complete list.

XPCTYPE	Meaning (CMX error type)
0	T_CMXTYPE: CMX error detected by the CMX library
2	T_DSTEMPERR: Temporary TNS error
3	T_DSCALL_ERR: TNS call error
4	T_DSPERM_ERR: Permanent TNS error
5	T_DSWARNING: TNS warning
>15	CMX error on the basis of error codes from the transport system

XPCCLS	Meaning (CMX error class, valid for &XPCTYPE < 15)
0	T_CMXCLASS: CMX class
2	T_DSNOT_SPEC: TNS class not specified
3	T_DSPAR_ERR: TNS parameter error
4	T_DSILL_VERS: Invalid TNS version
5	T_DSSYS_ERR: TNS system error
6	T_DSINT_ERR: Internal TNS error
7	T_DSMESSAGE: TNS note

XPCVAL	Meaning (CMX error value)
0	T_NOERROR: No error
5	T_EIO: Temporary bottleneck or error in the transport system
14	T_EFAULT: IO_Area not allocated
100	T_UNSPECIFIED: Unspecified error, generally a system call error
101	T_WSEQUENCE: Invalid call sequence
103	T_WPARAMETER: Invalid parameter
104	T_WAPPLICATION: The task is not authorized to sign on to the application or the application has already been opened by this task.
105	T_WAPP_LIMIT: The limit for the number of simultaneously active applications has already been reached.
106	T_WCONN_LIMIT: The limit for the number of simultaneously active connections has already been reached.
107	T_WTREF: Invalid transport reference or the transport connection has already been established.
111	T_NOCCP: The transport system does not support the requested application or connection.
114	T_CCP_END: The transport system has been terminated or the application was closed by the administrator.
255	T_WLIBVERSION: No connection to the CMX subsystem possible.
-100	T_INVREF: Invalid evid. CMX cannot assign the call to a wait point.

P013

Association (&XPOSAS ) rejected (a_asscf() ): &ACPNT, &OSLPAP, reason:
&XPCRES, &XPSRC, &XPNDIA
CCR V2 = &XP1BOOL, Version Incompatibility = &XP2BOOL
ContWin Assignment rejected = &XP3BOOL
Bid mandatory rejected = &XP4BOOL, No reason = &XP5BOOL

This message is issued when active establishment of an association is rejected by the remote partner.

The inserts have the following meaning:

&XPOSAS	Index of the relevant association
&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPCRES	Specifies whether the rejection is temporary or permanent: 0= permanent reject 1= transient reject
&XPCSRC	Specifies who has rejected establishment of the association: 0 = ACSE service user 1 = ACSE service provider 2 = Presentation service provider
&XPNDIA	See table on "General inserts for the XAP-TP messages"
&XP1BOOL - &XP5BOOL
	These inserts can take the values TRUE or FALSE. Values of TRUE indicate the reasons the partner reported for rejecting the request to establish an association: &XP1BOOL: CCR Version 2 is not available &XP2BOOL: The TP protocol versions are not compatible &XP3BOOL: The contention winner assignment has been rejected &XP4BOOL: The specification “Bidding is mandatory” or “Bidding is not mandatory” has been rejected &XP5BOOL: No reason is specified

Possible causes for the rejection of the contention winner assignment (&XP3BOOL=TRUE):

• Fewer associations are generated in the OSI-TP partner application than in the local UTM application.

• Different number of contention losers/winners in the local and the partner application.

• Associations have been disconnected without the OSI-TP partner application being informed of this. The OSI-TP partner application rejects the establishment of associations since it considers that they are still established.
  In this situation, the message P004 with &XPRJCT = 34 or &XPRJCT = 35 is generated in the OSI-TP partner application (NO_MORE_CONTENTION_LOSER / WINNER_ASSOCIATIONS, "General inserts for the XAP-TP messages").

P014

Error on association disconnection (&XPOSAS ) (&XPFUNC): &ACPNT, &OSLPAP, &XPRET, &XPERR, &XP1INFO, &XP2INFO

This message is issued if the call to an OSS function (&XPFUNC) required to establish an association returns an error. If the error has been reported by the transport system, message P012 is also output. If the error has not been reported by the transport system, the application is terminated with “Termapplication”.

The inserts have the following meaning:

&XPOSAS	Index of the relevant association
&XPFUNC	Name of the OSS function
&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPRET	See table on "General inserts for the XAP-TP messages"
&XPERR	See table on "General inserts for the XAP-TP messages"
&XP1INFO	Supplementary OSS information
&XP2INFO	Supplementary OSS information, currently always set to zero.

P015 

Association (&XPOSAS ) disconnected (&XPFUNC): &ACPNT, &OSLPAP, &XPLNK, &XPSRC, &XPNDIA, &XPINI, &XP1INFO, &XP2INFO

This message is issued when an association is cleared. The inserts have the following meaning:

&XPOSAS	Index of the relevant association
&XPFUNC	Name of the OSS function
&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPLNK	Represents the internal status of the association 0 = Association not linked 1 = Association linked to channel 2 = Association linked to instance
&XPCSRC	Originator of clear-down 0 = ACSE service user 1 = ACSE service provider 2 = Presentation service provider
&XPNDIA	See table on "General inserts for the XAP-TP messages"
&XP1INFO	Supplementary OSS information
&XP2INFO	Supplementary OSS information
&XPINI	See table below

XPINI	Meaning
0	Association was cleared internally.
401	O_LOC_TRAN The originator is the local transport system. &XP1INFO contains the CMX return code. This is output in detail in the subsequent message P012.
402	O_REM_TRAN The originator is the remote transport system. &XP1INFO contains the reason for the CMX event t_disin. The values are defined in cmx.h. Some of the possible values for &XP1INFO and their meaning are contained in the list below. The following abbreviations are used: CCP (Communication Control Program) for the application program that controls communication TSAP (Transport Service Access Point) for the access point to the transport service, NSAP (Network Service Access Point) for the access point to the network service. PDU (Protocol Data Unit) for data elements in a protocol layer. &XP1INFO can, for example, take on the following values:
	0 (T_USER) The communication partner cleared the association, possibly as a result of a user error on the partner side.
	1 (T_RTIMEOUT) The connection was cleared locally by CMX because the connection had been inactive for too long according to the t_timeout parameter.
	2 (T_RADMIN) The connection was cleared locally by CMX because the administrator closed down CCP.
	3 (T_CCPEND) The connection was cleared locally by CMX because CCP failed.
	256 (T_RUNKOWN) Either the partner or CCP cleared the connection. No reason was given.
	257 (T_RSAP_CONGEST) The partner CCP cleared the connection because of a TSAP-specific bottleneck.
	258 (T_RSAP_NOTATT) The partner CCP cleared the connection because the addressed TSAP was not registered there.
	259 (T_RUNSAP) The partner CCP cleared the connection because the addressed TSAP was not known there.
	261 (T_RPERMLOST) The connection was cleared by the network administrator or the partner CCP administrator.
	262 (T_RSYSERR) Error in the network
	385 (T_RCONGEST) The partner CCP cleared the connection as a result of a resource bottleneck.
	386 (T_RCONNFAIL) No connection could be established. The partner CCP aborted the attempt due to failure.
	387 (T_RDUPREF) The partner CCP cleared the connection because a second connection reference was assigned for an NSAP pair (system error).
	388 (T_RMISREF) The partner CCP cleared the connection because a connection reference could not be assigned (system error).
	389 (T_PROTERR) The partner CCP cleared the connection because of a protocol error (system error).
	391 (T_PREFOFLOW) The partner CCP cleared the connection because of a connection reference overflow.
	392 (T_RNOCONN) The partner CCP rejected the request to establish a network connection.
	394 (T_RINLNG) The partner CCP cleared the connection because of an incorrect length header or parameter (system error).
	448 (T_RLCONGEST) The local CCP cleared the connection because of a resource bottleneck.
	449 (T_RLNOQOS) The local CCP cleared the connection because the “quality of service” could not be maintained.
	451 (T_RILLPWD) Invalid connection password.
	452 (RNETACC) Access to the network was refused.
	464 (T_RLPROTERR) The local CCP cleared the connection because of a transport protocol error (system error).
	465 (T_RLINTIDU) The local CCP cleared the connection because it received an interface data unit which was too long (system error).
	466 (T_RLNORMFLOW) The local CCP cleared the connection because of an infringement of the flow control rules for normal data (system error).
	467 (T_RLEXFLOW) The local CCP cleared the connection because of an infringement of the flow control rules for expedited data (system error).
	468 (T_RLINSAPID) The local CCP cleared the connection because it received an invalid TSAP identification (system error).
	469 (T_RLINCEPID) The local CCP cleared the connection because it received an invalid TCEP identification (system error). TCEP = Transport Connection End Point.
	470 (T_RLINPAR) The local CCP cleared the connection because of an invalid parameter value (e.g. user data too long or expedited data not permitted).
	480 (T_RLNOPERM) The administrator of the local CCP prevented establishment of a connection.
	481 (T_RLPERMLOST) The administrator of the local CCP cleared the connection.
	482 (T_RLNOCONN) The local CCP could not establish the connection because no network connection is available.
	483 (T_RLCONNLOST) The local CCP cleared the connection because the network connection was lost. Most common cause: generation error on the CCP and PDN side, e.g. incorrect link addresses. Other possible causes: partner is not available, modem is faulty or has been set incorrectly, data transfer connection not plugged in, data transfer card faulty.
	484 (T_RLNORESP) The local CCP cannot establish the connection, because the partner did not respond to the CONRQ.
	485 (T_RLIDLETRAF) The local CCP cleared the connection because the connection was lost (Idle Traffic Timeout).
	486 (T_RLRESYNC) The local CCP cleared the connection because the resynchronization was not successful (more than three attempts were made).
	487 (T_RLEXLOST) The local CCP cleared the connection because the expedited data channel is faulty (more than three attempts were made).
403	O_LOC_SESS The originator is the local session provider. &XP1INFO can take the following values:
	4 (S_PROTERROR) Protocol error: Incorrect establishment of the session PDU or incorrect SPDU parameter
	16 (S_PICSREST) Violation of implementation-specific restrictions.
404	O_REM_SESS The originator is the remote session provider. &XP1INFO can take the following values:
	1 (S_TCDISCON) transport disconnect
	4 (S_PROTERROR) protocol error
	8 (S_UNDEFINED) undefined
	16 (S_PICSREST) violation against restriction stated in PICS
405	O_LOC_PRES The originator is the local presentation provider. &XP1INFO can take the following values:
	0 (P_ARRNO) reason not specified A decoding buffer requested internally cannot be provided due to a lack of memory. Overflow of the internal data buffer when reassembling fragmented messages An unknown session event was reported. System bottleneck or system error.
	1 (P_ARNRPDU) unrecognized PPDU No session user data is available or the presentation part of the session user data cannot be decoded (system error).
	4 (P_ARNRPAR) unrecognized PPDU parameter Error on decoding the ACSE, presentation or user syntax.
	5 (P_ARNEPAR) unexpected PPDU parameter PPDU parameter not in normal mode.
	6 (P_ARNIPAR) invalid PPDU parameter Invalid context identifier on decoding. Invalid PPDU parameter, e.g. incorrect length. This “abort” can be triggered by the UTM user by specifying invalid presentation or session selectors.
406	O_REM_PRES The originator is the remote presentation provider. &XP1INFO can take the following values:
	-1 (O_NOVALUE) Optional parameter is not present
	0 (P_ARNNO) Reason not specified
	1 (P_ARNRPDU) Unrecognized PPDU
	2 (P_ARNEPDU) Unexpected PPDU
	3 (P_ARNESSP) Unexpected session service primitive
	4 (P_ARNRPAR) Unrecognized PPDU parameter
	5 (P_ARNEPAR) Unexpected PPDU parameter
	6 (P_ARNIPAR) Invalid PPDU parameter value
407	O_LOC_ACSE The originator is the local ACSE provider &XP1INFO always has the following value:
	1 (A_ABSASP) ACSE service provider initiated the abort The instance is specified which initiated the abort (“abort source”) from the point of view of ACSE.
408	O_REM_ACSE The originator is the ACSE service provider. &XP1INFO can take the following values:
	0 (A_ABSASU) ACSE service user initiated the abort
	1 (A_ABSASP) ACSE service provider initiated the abort

P016

Association (&XPOSAS ) disconnected (a_relin() ): &ACPNT, &OSLPAP, &XPLNK, &XPNDIA

This message is issued if an association is cleared because a “release indication” was received. The inserts have the following meaning:

&XPOSAS	Index of the relevant association
&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPLNK	Represents the internal status of the association 0 = Association not linked 1 = Association linked to channel 2 = Association linked to instance
&XPNDIA	See table on "General inserts for the XAP-TP messages"

P017

OSS decoding error: &XPPDU, &XP1DIA, &XP2DIA, &XP3DIA

This message is issued if OSS detects an error on decoding a TP PDU, CCR PDU or user data PDU. The insert &XPPDU indicates the type of PDU in question.

The inserts have the following meanings:

XPPDU	Meaning
0	PDU_UNKNOWN (unknown PDU type)
1	TP_BEGIN_DIALOGUE_RI
2	TP_BEGIN_DIALOGUE_RC
3	TP_BID_RI
4	TP_BID_RC
5	TP_END_DIALOGUE_RI
6	TP_END_DIALOGUE_RC
7	TP_U_ERROR_RI
8	TP_U_ERROR_RC
9	TP_ABORT_RI
10	TP_GRANT_CONTROL_RI
11	TP_REQUEST_CONTROL_RI
12	TP_HANDSHAKE_RI
13	TP_HANDSHAKE_RC
14	TP_HSK_AND_GRT_CTRL_RI
15	TP_HSK_AND_GRT_CTRL_RC
16	TP_DEFER_RI
17	TP_PREPARE_RI
18	TP_HEURISTIC_REPORT_RI
19	TP_TOKEN_GIVE_RI
20	TP_TOKEN_PLEASE_RI
21	TP_RECOVER_RI
22	TP_INITIALIZE_RI
23	TP_INITIALIZE_RC
24	CCR_INITIALIZE_RI
25	CCR_INITIALIZE_RC
26	CCR_BEGIN_RI
27	CCR_BEGIN_RC
28	CCR_PREPARE_RI
29	CCR_READY_RI
30	CCR_COMMIT_RI
31	CCR_COMMIT_RC
32	CCR_ROLLBACK_RI
33	CCR_ROLLBACK_RC
34	CCR_RECOVER_RI
35	CCR_RECOVER_RC
50	PDU_ANY
51	PDU_UASE_RI

XP1DIA / XP2DIA	Meaning
1	not supported parameter was received and skipped
2	received data truncated
4	required transfer syntax name missing in user data or not specified in AVX list, error codes in &XP2DIA
6	no transfer syntax name in user data though presentation negotiation was not completed
7	transfer syntax name encoded in user data not found in AVX list
10	invalid value in data structure
11	invalid object identifier in data structure
12	invalid length or count in data structure
13	invalid index in data structure (EXTERNAL, CHOICE)
14	invalid value of ax_typtag in corresponding syntax table

&XP3DIA         Corresponding index in the syntax table

P018

FSM protocol error: &ACPNT, &OSLPAP, &XPPTYP, &XPFSMN

This message is issued when the finite state machine reports an error.

The inserts have the following meaning:

&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPPTYP	Type of the service protocol element
&XPFSMN	Name of the finite state machine

P019

APDU contains invalid value: &ACPNT, &OSLPAP, &XPAPDU, &XP3INFO

This message is issued if an invalid APDU is received.

The inserts have the following meanings:

&ACPNT	Name of the local ACCESS-POINT
&OSLPAP	Name of the partner in the local application
&XPAPDU	Type of the APDU
&XP3INFO	Supplementary information on the error

P020

OTRACE implicitly switched off. Reason: &XPTRFAIL

This message is issued when an attempt to write a trace record fails. The OSS trace is deactivated implicitly as a result of the error. After the error has been corrected, the administrator can reactivate the OSS trace.

The inserts have the following meaning:

XPTRFAIL	Meaning
1	The OSS function o_wutr() issued the return code O_ERROR. The preceding P001 message provides further information on the error.
2	The OSS function o_wutr() issued the return code O_INVEREF.
3	The OSS function o_wutr() issued an unknown return code.

P021

Unexpected event &XPEVT occurred for association (&XPOSAS ), event discarded: &ACPNT, &OSLPAP, &XPOSAS, &XPASST

This message is output if an event occurs which is incompatible with the current status of the association. XAPTP does not take account of this event.

The inserts in the message have the following meanings:

&XPEVT	Type of event that has occurred.
&ACPNT	Name of the local access point (KDCDEF statement ACCESS- POINT).
&OSLPAP	Name of the OSI-LPAP partner in the local application.
&XPOSAS	Index of the relevant association.
&XPASST	Status of the relevant association.