Format of received communication events

This section explains the format of the communication events that indicate the association status. Before a communication event can be received, the service group name and service name of the SPP for a communication event must be specified in the XATMI communication service definition. What type of communication event can be received depends on which operand is assigned the service group name and service name.

xat_aso_con_event_svcname operand:: Communication event for association establishment notification

xat_aso_discon_event_svcname operand:: Communication event for normal release of association

xat_aso_failure_event_svcname operand:: Communication event for abnormal release of association

One SPP for a communication event can handle multiple communication events if you specify the same service group name and service name to multiple operands.

The contents of communication event indicating association status are shown below.

01  unique-name-1.
    02  data-name-A   PIC S9(9)  COMP.
    02  data-name-B   PIC X(9).
    02  FILLER       PIC X(3).
    02  data-name-C   PIC S9(9)  COMP.
    02  data-name-D   PIC 9(9)  COMP.
    02  data-name-E   PIC X(9).
    02  FILLER       PIC X(63).

data-name-A

Will be assigned the identifier of the communication event. The identifier is one of the following codes. The number enclosed in parentheses is the numerical representation (decimal) of the code.

DCXAT_ASO_CONNECT (00000001): Association establishment

DCXAT_ASO_DISCONNECT (00000002): Normal release of association

DCXAT_ASO_FAILURE (00000003): Abnormal release of association

data-name-B

Will be assigned the name of the association whose status is to be reported by the communication event.

data-name-C

Will be assigned the value that indicates whether the local system is the initiating or recipient for the established connection. The value assigned is one of the following codes. The number enclosed in parentheses is the numerical representation (decimal) of the code.

DCXAT_ASO_INIT (00000001): The local system is the initiating.

DCXAT_ASO_RESP (00000002): The local system is the recipient.

data-name-D

Will be assigned the reason code which will be returned when the association is released. The value assigned is one of the following codes. The number enclosed in parentheses is the numerical representation (decimal) of the code.

For the normal releasing of an association, one of the following values is assigned:

00000001: Releasing of an association by executing a command

00000005: Releasing of an association by the XATMI

00000007: Normal releasing of an association from the remote system

00000008: Normal releasing of an association by the TP layer

For the abnormal releasing of an association, one of the following values is assigned:

00000001: Forced releasing of an association by executing a command

00000003: Failure in a lower layer (such as a line failure and communication management failure)

00000005: Forced releasing of an association by an XATMI communication service

00000006: Failure in association establishment

00000007: Forced releasing of an association from the remote system

data-name-E

Will be assigned the XATMI communication service name.