CXXMAINT (Maintain Directory) › CXXMAINT DDPROD (Update Directory) › Processing a DDPROD Request

Processing a DDPROD Request

As CA Datacom/DB processes each table definition, the current Directory content is compared to the CA Datacom/DB definitions.

If any tables in the database being updated are not loaded, they are deleted from the Directory at the start of the process. A report of the Directory taken at this time does not provide area space information. The next LOAD of the area restores the information.

The action taken by CA Datacom/DB depends on the situation encountered, as follows:

New Area, New Table

If an area is new and no match exists in the Directory, CA Datacom/DB adds the area with no initialization information. CA Datacom/DB adds the new table with no initialization information, and sets it as not loaded.

Existing Area, New Table

If the table is new, CA Datacom/DB adds it. If the area containing the table exists and is loaded, CA Datacom/DB sets the new table as loaded and having zero records.

If you are adding a table to an existing area, CA Datacom/DB updates the area with the new CA Datacom/DB entity-occurrence information, data set space option, and slack information to the new values. If the block size differs, CA Datacom/DB saves the new block size in the area definition as the next block size until the next INIT of the data area.

Existing Area, Existing Table

If the table currently exists, CA Datacom/DB compares the Directory and CA Datacom/DB versions. If a critical change has occurred, CA Datacom/DB leaves the current table in *HISTORY* status and adds the new table as not loaded.

Special codes on the Impact Report indicate critical changes and the reason. The codes and reasons associated with an Impact Report are as shown in the following list.

Impact Report Codes and Reasons

00

NOT LOADED (00) in the Impact Report means that a table was NOT LOADED for reasons other than a CATALOG or DDPROD. This indicates that the area has been loaded since the last DDPROD or CATALOG but is not loaded now. The current NOT LOADED status is of no importance with regard to the last DDPROD or CATALOG. For information about requesting an Impact Report as a DBUTLTY function independent of a DDPROD, that is, a TYPE=I CXX report, see Type I - Impact Report.

01

New table name

02

Area name change

08

Table ID change

09

Recover yes/no change

10

CA Datacom/DB compression or user compression change

11

Record length change

13

User compression name change

14

Special field processing change

• When you have to reload the data area to make the new table definition usable, you can run a SEQ=NATIVE BACKUP or EXTRACT function which use the *HISTORY* definition to access the old data, change its format if necessary, and reload the area. When the reload completes, CA Datacom/DB marks the new table definition loaded.

  Caution If you have changed table definitions in multiple areas in the database, be sure that you back up all affected areas before reloading any data. The first reload of any data area in the database deletes all *HISTORY* database definitions. If you have not unloaded all changed areas before doing a reload, the *HISTORY* definition is no longer available.

  If you are moving a table from one area to another, back up the area or extract the table before cataloging or using DDPROD to update the definition.

  Do not use the CXXMAINT DDPROD option for SQL accessible tables or on a database containing SQL accessible tables. Instead, use the CA Datacom/DB CATALOG transaction.

• If a key change occurs, CA Datacom/DB removes the *HISTORY* version, adds the new table with the data loaded but the Index is marked as not loaded. (Run the RETIX function to correct the Index.)
• If neither of these situations occurs, CA Datacom/DB regards the changes as noncritical, removes the *HISTORY* version, and adds the new table as loaded.