CA Datacom Datadictionary › Multiple Databases Definitions › Multiple Databases Implementation

Multiple Databases Implementation

Under CA Datacom/AD, a new CA Datacom Datadictionary definition is required for each new database. The simplest way to create this new definition is make a copy of the CA Datacom Datadictionary update transactions used to create the original database. Some products may produce alternative facilities for generating the transactions.

These transactions are in an 80-byte format that can be viewed and edited with any text editor. You should use your text editor to carefully change all instances of the database name (such as CA-ORIGINAL-DB) to the new database name (such as MY-CLONED-DB).

The transaction fields are positional, so using this method requires that you follow the CA naming scheme. Specifically for the database, use the 2900 DATABASE transaction (2900 in positions 1 through 4) to enter the DATACOM-ID attribute-value, and the new database ID number, in columns 6 through 10.

 -UPD DATABASE,MY-CLONED-DB(T001)
 2900 nnnnn (where nnnnn is the new DBID number)
 -END

After making your changes to all the transactions, submit them to CA Datacom Datadictionary with the DDUPDATE utility to create the new definitions. Then, use the DDRTVCAT utility to activate the database by copying it to PRODuction status and updating the CXX. Note that the DDRTVCAT BASIS parameter is required and must reference the original database. The BASIS parameter allows DDRTVCAT to check your new definition against the original database for compatibility with the using product.

Finally, allocate and initialize the new database using the CA Datacom/DB DBUTLTY INIT function. See the CA Datacom/DB DBUTLTY Reference Guide for details on this function.

See the CA using product installation manual for information on jobs that perform these functions for the original databases. You can copy the JCL in those jobs to create the new database.

Important! You should make a full backup of your CA Datacom Datadictionary databases and CXX plus a backup of the update transactions before starting this procedure. See the job in the SAMPJCL library that can be used for this purpose.