Version 8.2.5
 —  Utilities  —

TEMP Data Set Space Usage

ADALOD uses the TEMP data set to store the following information:


Sequential TEMP Data Set

If the TEMP data set is filled while collecting descriptor values from the input data set, ADALOD temporarily writes the remaining descriptors to the sequential temp file DD/FILEA (if specified in the JCL). The descriptors are later read back in when the new index is built.

If actually called, DD/FILEA makes ADALOD operation considerably slower than specifying a TEMP data set that is large enough to hold all descriptor values. The DD/FILEA TEMP data set should normally be used only as a safety net to ensure adequate space for all descriptors during ADALOD operation. Specifying the DD/FILEA TEMP file therefore avoids an ADALOD abend caused by a temp area overrun.

Notes:

  1. ADALOD writes only descriptor values from the DD/EBAND input file to DD/FILEA.
  2. The normal TEMP data set must be large enough to hold all values for each single descriptor.
  3. The estimated number of TEMP blocks for ADALOD UPDATE may need to be adjusted upwards if forward index compression is in effect for the file since the NI is written to the TEMP data set without forward compression.

If you are running ADALOD UPDATE only to delete ISNs, the size of the TEMP data set must be calculated as the sum of the calculations in the following three steps:

  1. Part 1 of TEMP data set contains:

  2. Part 2 of the TEMP data set contains the list of ISNs to be deleted, plus the belonging DS-RABNs, 8 bytes per element. Calculate:

    (8 * to-be-deleted-ISNs) / (TEMPBLKSIZE - 16) = needed-blocks
  3. Part 3 contains the complete NI:

    count NI-BLKS * ASSOBLKSIZE) / (TEMPBLKSIZE - 16) = needed blocks

Top of page