Modifying Schema Entities › Record Modifications › Adding and Dropping Database Procedures

Adding and Dropping Database Procedures

What components are affected

If you implement a new database procedure, or change the name of an existing procedure, it will affect the schema and one or more subschemas. It may also require that you restructure the database, if the purpose of the procedure is to alter the physical data (for example, record compression). All subschemas and access modules that reference the record are also affected by procedure changes.

Steps to make the change

To add, modify, or delete database procedures that have no effect on the data, follow the procedure described in 33.2, "Modifications to an Unloaded Database".

Considerations

• If a new database procedure does affect the data, write and compile the new procedure and then use the RESTRUCTURE utility statement to change the existing data by specifying the new procedure in a NUPROCS macro.

  If database procedures are already associated with the record, they may need to be removed from the schema and subschema before executing RESTRUCTURE. The existing procedures, if invoked, will be called after all NUPROCS procedures have been called. If, for example, the new procedure compresses the data in the record, the existing procedures may not work properly. To overcome this problem, either execute RESTRUCTURE using a subschema derived from an intermediate schema in which all procedures normally called before the new procedure have been removed from the record or unload and reload the data to add the new procedure.

• You can add or remove procedures that affect the data by unloading and reloading it. To do this, create a new schema and subschema containing the revised procedure calls. Unload the data using the old subschema and reload it using the new subschema.
• To change a database procedure for an area, all calls must be respecified.