• Name of the structure
• An indicator specifying a reason why the structure was not dumped, if applicable (reason codes are defined in IXLYSTRC)
• A structure number by which you can identify different COMPDATA spaces with the structure
• A pointer to the structure trailer.

• The structure dump space header, which appears in each structure COMPDATA space, is mapped by IXLYCOMP (COMPSTRHDR mapping). The information in the dump space header includes:
  • A pointer to the dump header for a given structure
  • A pointer to the object map index within the structure COMPDATA space.
• The dump header, which appears only in the first structure COMPDATA space for a structure, is mapped by IHADWHDR. The dump header includes the following:
  • Information about the dump of the structure and the structure controls associated with the structure
    • IXLYDCAC maps cache structure controls
    • IXLYDLIC maps list structure controls
  • The associated request block, mapped by IHAARB, which contains the list of objects and ranges that were requested for the structure.
• The object map index is mapped by IXLYCOMP (COMPSTROBJMAPINDEX mapping). The information includes:
  • A list of pointers to the beginning of each object that was dumped for the structure
  • The minimum value and maximum value of the identifier for each object.
• The object map, which can span more than one structure COMPDATA space, is mapped by IXLYCOMP (COMPSTROBJMAP mapping). For each object, the information includes:
  • The object type and identifier
  • A pointer to the object header in the object header COMPDATA space
  • A sequence number (xx) to identify an object header COMPDATA space with the object.

• Status of the object
• Controls that are associated with the object
• A pointer to the appropriate object COMPDATA space for the first entry dumped for the object
• A sequence number (xx) to identify the object COMPDATA space with the object.

If the object is a lock table, the sequence number and the address of the first entry dumped for the lock table appear in the object header. If the object is the user controls for a structure, the sequence number and the address of the first entry dumped for the user controls appear in the object header.

• The hash table header, mapped by IXLYCOMP (COMPHASHTABLEHDR mapping), indicates the number of slots that are in the hash table and points to the hash table slot array.
• The hash table slot array, mapped by IXLYCOMP (COMPHASHSLOTARRAY mapping), is an array of pointers to the lists of hash elements
• A hash table element, mapped by IXLYCOMP (COMPHASHELEM mapping), contains the following information for each entry on the list:
  • An indicator to specify whether the element corresponds to an entry name or entry identifier
  • A pointer to the appropriate entry control COMPDATA space associated with the hash table element
  • A sequence number (xx) to associate the entry control COMPDATA space with the element.

• Index of the lock table entry
• Contents of the lock table entry

• Connection identifier
• Whether the EMC is queued to this connector's event queue
• List number with which the EMC is associated
• List entry key of the sublist with which the EMC is associated
• User notification control data.

• Connection identifier
• Whether the list transition exit is to be driven when a list transition occurs
• Whether event queue monitoring is in effect
• Vector index associated with the event queue
• Counts of EMCs queued to the event queue and event queue transitions.

• The entry control header, mapped by IXLYCOMP (COMPENTRYCNTL mapping), includes the following information for each entry that was dumped for castout classes, storage classes, or list numbers.
  • Status data about the items that were dumped
  • Pointers to the entry's adjunct data in the adjunct COMPDATA space and entry data in the entry data COMPDATA space, if applicable
  • Length of the entry data, if applicable
  • Sequence numbers (xx) to identify the adjunct COMPDATA space and the entry data COMPDATA space with the entry
• The entry controls associated with the entry are mapped by IXLYDDIB (DDIL mapping for a list structure and DDIC mapping for a cache structure). Entry controls that were located in storage-class memory at the time of the dump are identified by a placeholder DDIB that contains a storage-class memory token rather than actual entry data.