Changes to Existing Features › Datadictionary Enhancements › 1000 ALTER Transaction

1000 ALTER Transaction

You can use the 1000 ALTER transaction to apply changes to the CA Datacom/DB CXX and to relevant attributes of certain entity-types without closing the database. The database is opened if the 1000 ALTER transaction finds that it is closed.

You can use the 1000 ALTER transaction for system-defined databases, such as DATA-DICT, DDD-DATABASE, and also for user-defined databases.

The 1000 ALTER transaction is only valid for the DATABASE and AREA entity-types. Processing of the 1000 ALTER only affects the CXX entry for the specified entity-occurrence in the header transaction.

The 1000 ALTER transaction is valid for [set the dad variable for your book].

When using 1000 ALTER, consider the following restrictions:

• The database must have been set or defaulted as ACCESS OPTIMIZE during the enabling of the MUF.
• The database must not be defined as VIRTUAL.
• The MUF must currently be a single instance of the MUF and not part of a MUFplex with two or more MUFs currently enabled. It is acceptable to have a Shadow MUF that is not enabled.
• The occurrence to be altered must have been previously cataloged and must match the identity information that is stored in the CXX.
• If you modify a database, the base must be FORMAT 2 in the CXX, indicating that a fallback to r11 is not likely to occur. Also, the SQL SECURITY data cannot be different from that currently in the CXX.
• If you modify a data area, the DATACOM NAME must match, and the area must be in URI format.

The DATABASE entity-type and AREA entity-type attributes are passed from Datadictionary to CA Datacom/DB for comparison to the CXX. Processing either does or does not take place depending on the results of that comparison.

Note: For more information, see the CA Datacom Datadictionary Batch Reference Guide.