Previous Topic: Defining Modeled Dataviews for Sequential FilesNext Topic: Defining Unmodeled Sequential File Dataviews

Creating Dataviews for Sequential Files › Defining Modeled Sequential Files › Recatalog and Recompile

Recatalog and Recompile

CA Ideal captures all information about a dataview, including field attributes, when the dataview is cataloged. This information is incorporated into the program when the program is compiled and actually becomes part of the program object module.

If you change the file model that affects the dataview (for example, a change in the element length) or make a change that affects the attributes of any field in the dataview (such as class, type, length, decimal positions, occurs, value, or the relative position of the field in any element), then you must:

  1. Enable the file structure and dataview.
  2. Catalog the new dataview in CA Ideal.
  3. Recompile all programs using that dataview.

You must enable the structure after performing any function that disables the structure (for example, COPY, ADD, DEFINE) or an attribute maintenance function that modifies an occurrence.

If you change attributes of a PROD status dataview (for example, UPDATE), you must restore the dataview to TEST to make the change. When the dataview is copied back to PROD status, a new version number is assigned. Follow the recatalog steps 1 to 3 above and update the resources of the programs that access the dataview.

When a dataview is copied in DDOL, both the old and new versions of the dataview are immediately reflected in the RESOURCE component of every program using the old version of the dataview. This is because the CA Ideal program resource panel is a dynamic presentation of all the recognized relationships for a program at the time of the display (or edit).

When you copy an entity‑occurrence in DDOL, all of its relationships (except ordered relationships) are automatically copied also. Thus, since the dataview is related to every program for which it is a resource by the PGM‑DVW‑USE relationship, copying the dataview also copies each of these relationships. As a result, both the new PROD version and the previous version are related to every program. The resource table of a TEST status program shows both PROD and HIST status dataviews. You must manually remove the HIST status dataview. (This is not a problem with a program in PROD status.)