Preliminary Concepts › Entities and Version Management › Status

Status

Each version is assigned to a category that is based on the stage it reached in the production process. This category is called the status of the version. A version can be in test status, production status, or history status. Except for dataview entity types, you can change the status of a version with the MARK STATUS command.

The following is a list of status types and the rules that apply to each.

Test

All entity types except modeled and SQL dataviews-When a version is created in CA Ideal by the CREATE or DUPLICATE command, the version is in test status. You can modify a version as long as it remains in test status. There can be many versions in test status at a time. If you edit a dataview, you must recatalog it before you can use it.

CA Datacom/DB CBS dataviews and sequential file dataviews modeled in the dictionary-Test versions are created and maintained in the dictionary. There can be up to 999 test versions at a time.

For SQL-Only one version is assigned; version 1 in production status.

Production

When a version was created, edited, and tested, and is ready for 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 serves to protect its integrity.

• 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 object program 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 can delete them unless 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/DB CBS dataviews and sequential file dataviews modeled in the dictionary-The maximum number of history status versions that you can save 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.