Data areas

The next sections provide graphic representation of the data areas used by the agent for z/OS.

Data areas appear alphabetically, by name of the mapping macro. The data areas in this publication are not intended to be used as a customer user interface, but knowing their layout can be useful for debugging The areas are product sensitive and can be changed at any time during the current release without documentation updates to this publication.

The data area map

Each data area is described field by field. These field descriptions are taken directly from the system code.

The cross-reference table

DQE - Data queue element

   Name : DCLDQE
    Function:

   This segment maps queue elements for several HCL Workload Automation
   queues. The mapping of the DQEDATA field varies depending on the  
   value of DQETYPE. If data buffers are used (indicated by
   dqebptr ^= 0), they are always allocated in subpool 2 by queue adders,
   and are freed when no longer needed by queue servers.

Dynamic Critical Path:
dqedata containing data sent to critical path handler
when an MCP action is performed on a critical predecessor
and the dataspace has to be updated consequently

External buffer for dqecrt
It contains WLM data: Policy and Service Class

Dynamic Critical Path:
dqedata containing data sent to critical path handler
when a status change (EM) occurs or when the job is late or
long running (WA)

AR restart only
structure mapped into DQEARC buffer:

Cross reference

ESP - map of event record in the HTDS

   Name : DCLESP

   Function:
   Allows for continuation of events passed to the Data Router via the Event
   Writer queue and the event data set. This mapping should be used only
   when more than 80 bytes should be propagated using the above. The ESP
   is transformed into a DQE, using the ESP_dqetype as the DQE type, the  
   data in the type F ESP as the DQE internal buffer,and the remainder of  
   ESP data as the DQE external buffer. The subpool of the allocated
   external buffer should be indicated in the ESP_sp. The EW will freemain
   this area.
   Zeroes yields SP0.
   Use only key 0 storage.

Cross reference

EVT - Map of record layout in event data sets

   Name : DCLEVT

   Function:
   This segment describes the record layout in the event data sets.

Cross reference

EXI - Ix event definition

   Name : DCLEXI

   Function:
   This segment declares an initialization event. This event contains
   information about an initiated operation. Initialization events are
   created by the SUBMIT task and added to the Event Writer
   queue. Note that the beginning of exi
   must be mapped as exr.

Cross reference

EXK - Kx event definition

   Name : DCLEXK

   Function:
   This segment declares an initialization event. This event contains
   information about an initiated operation. Initialization events are  
   created by the SUBMIT task and added to the Event Writer
   queue. Note that the beginning of exk
   must be mapped as exr.

Cross reference

EXR - Exit record

   Name : DCLEXR

   Function:
   This segment declares an exit record. Exit records are built by SMF and
   JES exits, passed to the event writer via CSA buffers, and are written
   to an event data set as part of an event record by the event writer.

Cross reference

HTI - HTTP Interface from C side to PLX side (EELHTCEC module)

   Name : DCLHTI

   Function:
   The array contains information for the PLX inteface
   implemented in the EELHTCEC module.

------------------------------------------------------------------------------------
Checkpoint update (UPCP) ==> zHTTPDqe.h eventTypeUpdCP
------------------------------------------------------------------------------------

------------------------------------------------------------------------------------
Joblog request (JLGT) ==> zHTTPDqe.h eventTypeGetJoblog
Each JL record has 133 chars
htiStageArea is 150 records long
------------------------------------------------------------------------------------