Overview

Affect on Applications Associated with the Subschema

Changes you make to a subschema impact application programs associated with that subschema. In general, when you add, modify, or delete a subschema entity and regenerate the subschema, follow the appropriate procedure in the following table:

If a program...	You should...
Is associated with the subschema but does not need to access the new entity (area, record, or set)	Not have to recompile the program
Is associated with the subschema and needs access to a new entity or has access to a modified entity	Alter the program as needed Recompile the program

Regenerating the Subschema

Before you can use the subschema, you must regenerate it as described in Chapter 15, “Subschema Statements".

If you want to use the subschema before the system is recycled, you must issue a DCMT VARY PROGRAM .. NEW COPY command. This statement causes the regenerated subschema to be loaded into the program pool the next time it is requested.

Identifying Programs Associated with a Subschema

If your site updates the dictionary every time a program is compiled, the dictionary will contain the necessary information to identify the programs associated with a modified subschema.

If this information is stored in the dictionary, you can run IDMSRPTS Program Cross-Reference Listing report. For each program associated with a subschema, the report lists:

Name
Version number
Date last compiled
Number of times compiled
Language

Note: For more information about IDMSRPTS, see the CA IDMS Utilities Guide.

If your site does not update the dictionary when a program is compiled, such information must be maintained manually.