IXL014I
requesttype REQUEST FOR STRUCTURE structure-name WAS SUCCESSFUL. JOBNAME: jobname ASID: asid CONNECTOR NAME: connector name CFNAME: cfname[statusinfo]

Explanation

A connect to a coupling facility structure via the IXLCONN macro was successful. In the message text:
requesttype
One of the following request types:
IXLCONN
IXLCONN macro service
IXLCONN REBUILD
IXLCONN macro service for a REBUILD connect
structure-name
Name of the structure for which information is recorded.
jobname
Jobname of the application issuing the IXLCONN.
asid
ASID of the application issuing the IXLCONN.
connector-name
Connection name specified by the application issuing the IXLCONN or generated by XES.
cfname
Name of the coupling facility in which the structure was allocated.
statusinfo
Additional status information, which may include:
ADDITIONAL STATUS INFORMATION:
This line is issued whenever the XES Connect (IXLCONN) service completes with the IxlRetCodeWarning return code and the IxlRsnCodeSpecialConn reason code, and additional status information has been provided in the ConaFlags field of the Connect Answer Area. It is followed by one or more of the following lines to summarize the status returned in the ConaFlags field.
  • CONNECTION HAS BEEN REESTABLISHED

    The ConName specified on connect matched the ConName of a failed persistent connection. The connection has been reestablished. Issued when ConaReconnected is set.

  • REBUILD IS IN PROGRESS

    Rebuild is in progress for this structure. Issued when ConaRebuild is set.

  • REBUILD STOP IS IN PROGRESS

    Rebuild Stop or Stop Duplex is in progress for this structure. Issued when ConaRebuildStop is set.

  • USER SYNC POINT EVENT IS SET

    A user sync point event is set. Issued when ConaUsyncEventSet is set.

  • ALTER IS IN PROGRESS

    Alter is in progress for the structure. Issued when ConaAlterInProgress is set.

System action

The system continues. The program that issued the IXLCONN is now able to use the structure. The system writes this message to the system hardcopy log.

System programmer response

None. However, please note that one or more IXL013I messages may have been issued prior to this success message. This is due to the program attempting several IXLCONNs in an attempt to maximize the available resources. This message negates the errors issued in those related IXL013I messages.

Also, note that an IXL message might have been issued prior to this message, providing additional information about where the system allocated the structure and why.

Source

Cross System Extended Services (XES)

Module

IXLC1CON

Routing code

10

Descriptor code

12