Preliminary Concepts › Entities and Version Management › MARK STATUS Considerations

MARK STATUS Considerations

The MARK STATUS command changes the status of a definition from test to production or from production to history. The effects of these changes are entirely different.

A definition is marked from test to production when no further testing is necessary and the definition is ready for use in a production application. Production and History versions are subject to the following rules:

• For all definitions except for SQL dataviews: There can be only one production version of a definition at a time. You cannot edit or delete that version.
• You cannot delete definitions for SQL dataviews if they are resources of production programs.
• You cannot mark a production version of a definition that is named as a resource of a production program to history without first replacing it with a new production version.
• You can mark the production version of a definition that is not named as a resource of a production program directly to history.
• Marking another test version to production automatically retires any existing production version to history status. For example, if in the following list of versions, the fifth version's status is marked to production, the status of the fourth version automatically changes to history:

Note: Marking version 2 to production also marks version 4 to history.

If a subprogram or unmodeled dataview in production status is listed in the resource fill-in of a program in production status and a new version of the subprogram or dataview becomes the production version, the resource fill-in of the calling program is automatically changed to reflect the new production version. However, to provide an audit trail, the history version of the subprogram is still included in the program-to-program relationship for the calling program. You should consider this relationship when you execute the source transport utility. If you do not want to transport history versions, include the command SET EXPORT RESOURCE HISTORY NO in the transport command member.