Concurrent Prefix Update

Use Concurrent Prefix Update to run the Prefix Update function concurrently during the Prefix Resolution function. Concurrent Prefix Update resolves and updates the prefix of each segment whose information was affected by database load, database reorganization, or both, in a single job step.

The following figure shows the general data flow for Concurrent Prefix Update.

Figure 1. Overview of Concurrent Prefix Update

This figure depicts the data flow of Concurrent Prefix Update. Concurrent Prefix Update has seven types of input data: the FABYIN control statements, the DFSURWF1 data set, the DFSURCDS data set, the sort work data set. the DBD library, the RECON data set, and databases. It has six types of output data: the sort work data set, reports, the DFSURIDX data set, the RECON data set, and databases. WF3 records created by the Prefix Resolution function are passed directly to the Prefix Update function by using HPPRPIPE.

Concurrent Prefix Update uses a data transfer service called HPPRPIPE. HPPRPIPE provides high performance data transfer between tasks running in the address space of IMS™ HP Prefix Resolution. By using HPPRPIPE, the intermediate Work File 2 (WF2) data set and the intermediate Work File 3 (WF3) data sets are eliminated, which results in eliminating much of the I/O for a tape or a direct-access device. If DBRC is active, Concurrent Prefix Update issues a NOTIFY.REORG command for each database that has been updated.