P messages

All messages from the OSI-TP protocol stack start with the letter “P”.

P messages with openUTM occur between the proxy container and the EIS partner.

P messages with CICS can occur in the proxy container or in the openUTM-LU62 Gateway. If the term "proxy component" is used for the description of the P message, the proxy container or the openUTM-LU62 Gateway is meant, depending on the component where the message occurred.

P001

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

Error on OSI-TP communication between the proxy container and the EIS partner or between the proxy components.

If the error has been reported by the transport system, message P012 is also output.

Action: Inform system service.

P002

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

Error on OSI-TP connection generation between the proxy container and the EIS partner or between the proxy components.

If the error has been reported by the transport system, message P012 is also output.

Action: Inform system service.

P003

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

Action: Inform system service.

P004

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

This message is issued if a request to establish an association was rejected by the EIS partner.

Action: See the table below.

XPRJCT	Action
1 - 16	Inform system service.
17	Unknown partner application. Action: Check the generation in the proxy container and in the EIS system openUTM resp. in the proxy components. Possibly the generation input which is generated by the Management Console was not activated at one of the partners or at the components.
18 - 33	Inform system service.
34 - 35	Configuration problem. A different number of connections was generated on both sides. Action: Check the generation in the proxy container and in the EIS system openUTM resp. in the proxy components. Possibly the generation input which is generated by the Management Console was not activated at one of the partners or at the components.
36 - 39	Inform system service.
40	Timeout during connection establishment. Connection establishment was started but could not be completed in the specified time. Action with UTM partner: See the messages of the EIS partner. Alternatively, inform system service. Action with CICS partner: See the messages of the EIS partner and the proxy components and try to find out which component did not respond. Alternatively, inform system service.
41 - 46	Inform system service.

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.

Action: Check the generation in the proxy container and in the EIS system openUTM resp. in the proxy components. Possibly the generation input which is generated by the Management Console was not activated at one of the partners or at the components.

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.

Action: Check the generation in the proxy container and in the EIS system openUTM resp. in the proxy components. Possibly the generation input which is generated by the Management Console was not activated at one of the partners or at the components.

P007

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

This message is output when 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.

Action: Inform system service.

P008

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

This message is issued when an association has been established.

Action: Normal behavior.

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 communication partner cannot be accepted.

Action: Inform system service.

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 which is unknown to the local application.

Action: Inform system service.

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.

Action: Check the generation in the proxy container and in the EIS system openUTM resp. in the proxy components. Possibly the generation input which is generated by the Management Console was not activated at one of the partners or at the components.

P012

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

Action:

XPCVAL > 15: Error code from the transport system. Inform system service.

XPCVAL <other value>: Inform system service.

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 a connection to the EIS system resp. between the proxy components is rejected by the remote partner.

Action:

• If XP1BOOL, XP2BOOL or XP4BOOL are set to TRUE: Inform system service.

• If XP3BOOL = TRUE: Temporary shortage concerning the number of connections.

• If XP5BOOL = TRUE: Action depends on XPNDIA, see the table below.

XPNDIA	Action
1	Inform system service.
2 - 10	Configuration problem. Action: Check the generation in the proxy container and in the EIS system openUTM resp. in the proxy components. Possibly the generation input which is generated by the Management Console was not activated at one of the partners or at the components. With UTM partners: Check that the host name specified in the Management Console for the EIS partner corresponds to the host name used in the connection request. In the event of an error, the correct name is output in message U315 of the proxy container. If message U315 contains the value *ANY for the host name, you must add the host name of the UTM partner application to the host file of the system.
11 - 24	Inform system service.

P014

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

Action: Inform system service.

P015

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

This message is issued when an OSI-TP association is cleared.

Action: See the table below.

XPINI	Meaning
0	Normal behavior.
401	The local transport system has cleared the association. The subsequent message P012 contains the detailed CMX return code.
402	UTM partner: The EIS partner's transport system has cleared the connection. CICS partner: The openUTM-LU62 proxy component's transport system has cleared the connection. &XP1INFO contains the reason for the connection cleardown. The following is a subset of &XP1INFO values: 0 (T_USER) The communication partner cleared the connection, possibly as a result of a user error on the partner side. 258 (T_RSAP_NOTATT) The partner cleared the connection because the addressed communication endpoint was not registered there. 482 (T_RLNOCONN) The local transport system could not establish the connection because no network connection is available.
403 - 406	Inform system service.
407	The originator is the local proxy component.
408	The EIS partner or the proxy component openUTM-LU62 Gateway 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.

Action: See the table below.

XPNDIA	Meaning
0	NO_REASON_GIVEN
21 - 23	The association is cleared by the EIS partner or by the partner proxy component with release.

P017

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

Action: Inform system service.

P018

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

Action: Inform system service.

P019

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

Action: Inform system service.