LOAD (Build CXX or Data Area) › LOAD CXX (Build CXX) › When to Use › Directory Database Load

Directory Database Load

CA Datacom/DB updates the date/time of the maintenance each time the database is cataloged through the CA Datacom Datadictionary. This catalog can be a direct catalog using CA Datacom Datadictionary online or batch CATALOG or an indirect catalog using CA Datacom Datadictionary DDCFBLD and the CXXMAINT utility function (option=DDPROD). CA Datacom/DB also updates the date/time of each DELETE. Therefore, create a new backup of the Directory after each maintenance. The CXXMAINT ALTER options change the Directory but are not considered maintenance. For additional information, see CXXMAINT (Maintain Directory).

Loading a single database definition with the same or a different database ID is possible. Verify that no maintenance has occurred since the backup being processed was made by comparing the maintenance dates with the current Directory. If these values do not match, CA Datacom/DB aborts the LOAD.

If you know that a backup is actually valid for all data areas even if the date/time is different, you can force the LOAD to leave the tables loaded. To do this:

1. Use the DELETE option of the CXXMAINT function to delete the database (see CXXMAINT DELETE (Delete CXX Definitions) for details),
2. Load the database (this load sets all the tables to not loaded status), then
3. Load the database again.

The last load in the procedure just given leaves the database information as CA Datacom/DB found it on the backup. The last load does not provide a loaded status or initialized information if, at the time you performed the backup, the area was not then loaded.

CA Datacom/DB uses the database ID being loaded to find the desired database on the backup file. If a new database ID is not specified, CA Datacom/DB processes all information using the existing database ID.

If the database does not currently exist in the Directory, CA Datacom/DB adds the database and related definitions and information. However, CA Datacom/DB assumes the Index and data areas are not loaded since the database is new and the tables reflect that status. The Index and data areas are set as not initialized (unknown device type, zero blocks, zero tracks, and so on). Therefore, initialize the Index and data areas and load them from the backups, new input, or null load.

If the database currently exists in the Directory, CA Datacom/DB verifies that the update and read-only counts are zero and the date/time of the last maintenance is the same in the Directory and on the backup.

Without Simplify mode, the load of one or more databases is always performed using the MUF, which must be enabled and the database closed. This is also the expected way to execute with Simplify mode. However, with Simplify mode it is possible for the LOAD of a database to occur with MUF down if the function follows a function that executes only with MUF down and therefore provides CXX protection, or it must occur after you define the MUF to be down using the function SET OPTION1=MUF_NOT_ENABLED. Possible (but we do not recommend) is function SET OPTION1=MUF_ENABLED_OR_DISABLED.