Most of the information that IXCQUERY provides is mapped by the IXCYQUAA macro. IXCYQUAA provides information related to:

• Header record that describes the data records returned (QUAHDR topic).
• Sysplex data (QUASYS, QUASYS1 and QUASYS2 sections )
• Group data (QUAGRP topic)
• Member data (QUAMEM, QUAMEM1, and QUAMEM2 topic)
• Coupling facility data (QUACF, QUACF1, QUACFSC, QUACFSC1, QUACFSTR, and QUACFSTR1 topics)
• Coupling facility structure data (QUASTR, QUASTR1, QUASTRPL, QUASTRPL1, QUASTRXL, QUASTRXL1, QUASTRCF, QUASTRCF1, QUASTRUSER, and QUASTRUSER1 topics)
• Automatic restart management data (QUAARMS topic)
• Software features installed on a system (QUREQREATURES topic).

The information about record contents provided here is only partial. See IXCYQUAA in z/OS® MVS™ Data Areas in the z/OS Internet library for complete information on field names and lengths, offsets and descriptions of the fields mapped by the IXCYQUAA macro.

Header Record

When you request the information mapped by IXCYQUAA, the IXCQUERY macro also provides a header record. This record (QUAHDR topic) includes the following information:

• Number of system, group, member, coupling facility, or structure records that will follow
• Number of system, group, member, coupling facility, or structure records not returned because of insufficient space
• Total length of the answer area needed to contain all the requested information (including the area for the records that were successfully returned on this call).

Sysplex Data

When you request information about the systems in the sysplex, the information returned includes the following for each system:

• System name
• Failure detection interval and operator notification interval specified at IPL time
• System status
• System token.

When you request a level-1 IXCYQUAA record mapping about a system in a sysplex, the following information is returnd in addition to that listed above:

• Whether the system is in LPAR mode, and when in LPAR mode, the LPAR number within the CEC in which the system is running.
• Serial number and model number of the CEC on which the system is running.

Group Data

When you request information about the groups in the sysplex, the information returned includes the following for each group:

• Group name
• Number of members in the group
• Whether the group has any stalled members

Member Data

When you request information about all members in a specific group, or a specific member in a specific group, the information returned includes the following for each member:

• Member name
• Member token
• Member state
• Additional status information (for example, system status update missing, member status update missing, etc.)
• System name for the system on which the member is currently active or was last active
• System token for the system on which the member is currently active or was last active
• JOB, STC, MOUNT, or LOGON name from the primary ASID current when IXCJOIN was issued
• Timestamp (in Greenwich mean time) of the last event that affected the member
• Length of the member's user state field (specified on IXCCREAT or IXCJOIN)
• The member's status-checking interval (specified on IXCJOIN or changed on IXCMOD)
• User data returned by the member's status user routine in GPR 0
• The member's space token (STOKEN) for the primary address space at the time IXCJOIN was issued.
• Protocols that are supported for the member. Protocols include whether the member can receive message, participate in XCF-managed response collection, and support large message (up to 128M bytes) delivery.
• Whether the member is stalled, causing signaling sympathy sickness, being deactivated, or being terminated by SFM.

Coupling Facility Data

When you request information about all coupling facilities in a sysplex, the information returned includes the following for each coupling facility:

• Coupling facility name
• Node descriptor (mapped by the IXLYNDE macro)
• Size of the dump space (in multiples of 4K)
• Status indicators
• Number of coupling facility structures in this facility that cannot be added to the policy
• Number of systems connected to the coupling facility
• Number of coupling facility structures in the coupling facility
• Information about the active policy in effect for this coupling facility, including policy name, the times the policy was last updated and activated, and storage limitations.
• Information about the site affiliation of the coupling facility, if applicable, including the name of the SITE specified in the CFRM policy and the state of the Recovery Manager.

When you request information about a specific coupling facility in a sysplex, the following information is returned in addition to that listed above:

• Names of the systems connected to the specified coupling facility
• Names of the structures in the specified coupling facility
• Allocation status of each structure.

Coupling Facility Structure Data

When you request information about structures in a sysplex, the information returned includes the following for each structure:

• Name of the structure
• Size of the structure (as specified in the CFRM active policy)
• Pending size of the structure (if specified in a pending CFRM policy)
• Status indicators
• Number of associated preference list records
• Number of associated coupling facility exclusion list records
• Number of coupling facilities containing the structure
• Number of connectors to the structure
• Active policy data, including the policy name
• Information on structure rebuild
  • Type of processing (rebuild or duplexing rebuild)
  • Method of processing (user-managed or system-managed)
  • Phase
• Information on structure alter
• User-defined event information.
• Whether message-based processing is being used to coordinate event management for this structure. If so, managing system information, such as the system name and system ID, is also provided.

When you request information about a specific coupling facility structure in a sysplex, the following information is returned in addition to that listed above:

• Name of coupling facilities in the preference list for the structure
• Name of coupling facility structures in the exclusion list for the structure
• Name and node descriptor of the coupling facility in which the structure is allocated
• Structure version numbers (physical and logical)
• Allocation status of the structure
• Connection data about each connector to the structure:
  • Connection version
  • Connect data
  • Connect name
  • Connect token
  • System name
  • System token
  • Job name or started task name
  • State of the connection (for example, active, failed persistent, terminating, or keep disposition)
  • Connection identifier
  • Level of information returned for the connection
  • Failure/isolation information.
  • Structure rebuild information, including whether ALLOWAUTO has been specified and the SUSPEND= option, if applicable
  • Structure alter information, including whether ALLOWALTER has been specified and appropriate IXLCONN values.

When you request a level-1 IXCYQUAA record mapping about a structure in a sysplex, the following information is returned in addition to that listed above:

• Percent loss of connectivity when structure is undergoing an MVS-initiated rebuild based on the value of REBUILDPERCENT
• Additional USYNC-related completion code information
• Group name associated with the structure, if the structure is being used as a serialized structure
• Name of coupling facility for which the structure is a populate candidate
• Auto version (applicable only to system-managed processes)
• The structure user's current disconnect/failed confirm string (for unserialized stuctures only)
• System-specific information when process is system-managed, including system identification and phase of system-managed process.

Automatic Restart Management Data

When you request information about automatic restart manager elements and restart groups, the information returned includes the following for each element:

• Element name
• Name of the system where the element originally registered
• Name of the system where the element is running (or last ran if the element has failed and has not yet been restarted)
• Replication ID of the system where the element originally registered
• Job or started task name
• STOKEN for the element's address space
• ASID of the element's address space
• Level number associated with this element
• Name of the JES XCF group in which this element must run
• Date and time of initial registration
• Date and time of the first automatic restart manager restart
• Date and time of the most recent automatic restart manager restart
• Element type (or blank)
• Flags indicating:
  • Whether restarts by the automatic restart manager are enabled in the sysplex
  • Whether all systems capable of automatic restarts have connectivity to the ARM couple data set
  • Whether the current ARM policy prohibits a restart by the automatic restart manager for this element
  • The state of the element (for example: available, restarting, and so on)
  • Whether the element is a batch job, started task, or abstract resource
  • Whether the element has override JCL or command text
  • Whether the element is associated with another element
  • Whether the element has a minimum bind to the system on which it registered.
• Name of the element's event exit routine
• The number of restarts by automatic restart manager that have occurred since the element initially registered
• The number of restarts by the automatic restart manager that have occurred in the most recent restart interval for this element
• The number of restart attempts allowed for this element and the interval
• Name of the element to which this element is associated (or blank if no associations)
• An indication of whether the associated element is the element being backed up or is the back up for this element
• The total number of elements currently registered with the automatic restart manager
• The maximum number of elements that are able to be registered with the automatic restart manager.