Table entries are added during a CICS run either explicitly via CEMT or EXEC CICS commands, or implicitly, with default values, if a dump is requested for which an entry does not exist. These entries can be changed or deleted via CEMT or EXEC CICS commands. Explicitly added entries are written to the global catalog. Further blocks of storage are obtained if necessary as each block fills up. Storage for deleted entries is not reused, because activity on the table is low.
The DU domain anchor block contains pointers to the table, to the first and last active entries in the table, and to the next available entry. The table contains forward and backward pointers so that the table can be accessed in dump code sequence, and additional blocks are chained off the header of the previous block.
Table entries are added during a CICS run either explicitly via CEMT or EXEC CICS commands, or implicitly, with default values, if a dump is requested for which an entry does not exist. These entries can be changed or deleted via CEMT or EXEC CICS commands. Explicitly added entries are written to the global catalog. Further blocks of storage are obtained if necessary as each block fills up. Storage for deleted entries is not reused, because activity on the table is low.
The DU domain anchor (DUA) block contains pointers to the table, to the first and last active entries in the table, and to the next available entry. The table contains forward and backward pointers so that the table can be accessed in dump code sequence, and additional blocks are chained off the header of the previous block.
Storage for this table is obtained when the first dump table browse session of a CICS run is started. More storage is obtained when the table is full. Storage for deleted entries is not reused.
The structure of the table is the same as for the dump tables, as shown in Figure 109.
For a detailed description of these control blocks, see the CICS Data Areas manual.
[[ Contents Previous Page | Next Page Index ]]