Preliminary Concepts › Entities and Version Management › Status › Production

Production

When a version is created, edited, and tested, and is ready to use in an application, it is marked to production and becomes the production version. Only one version of a definition can be in production status at a time.

A production application must consist of components that are also in production status. This protects its integrity. Production applications run faster because CA Ideal does not need to verify at run time that all program components exist and are compiled. To convert programs to load module format, the application must be in production status.

For all entity types except modeled and SQL dataviews

You cannot edit or delete the production version. If a production version of a program is compiled, a compilation listing is produced; a new program object is not created.

For SQL dataviews

There can be only one version of a definition at a time ‑‑ version 1 in production status. The CA Ideal CATALOG command creates SQL dataviews. You cannot delete them if they are resources of production programs. You cannot edit them.

History

History versions of a definition are former production versions of that definition.

For all entity types except modeled and SQL dataviews

Marking a test version to production automatically retires the existing production version, if any, to history status.

For CA Datacom CBS dataviews and modeled sequential file dataviews

The maximum number of history status versions that can be saved is recorded in the dictionary (as the ENTY‑HIST‑VER attribute of the FILE entity in the DATA‑DICT database). When this number is exceeded, the oldest history versions are automatically deleted. You can modify the installed default of three history versions.