Migrations Between Control, Test, and Production

#### Search Results

Search

# Migrations Between Control, Test, and Production

This document covers the following topics:

- Migrations to Test or Production

- Migrations to Production

- Migrations to Test

## Migrations to Test or Production

Cataloged objects can be migrated to a test or production status from Control status, a test status, or a production status. If support for dynamic source variables is required in the execution environment, saved copy code, programs and maps are migrated as well. Foreign objects, whether saved or cataloged, can also be migrated as part of the object list.

Rules, views/DDMs (except VSAM views which are required at execution time), local data areas, and parameter data areas are ignored unless Applymod 8 is active in your environment to force the migration of views and data areas during migration processing.

Migrations to test or production result in an object status entry being created for each object migrated. The migration may be processed in batch or online.

## Migrations to Production

The production status is controlled by PAA; thus, there is more processing required for verification and consistency checking of the migration because PAA audit information and superseded backups will also be created.

## Migrations to Test

Only the Copy option is possible for migrations to test from production or Control; a copy of the objects must remain in Control and production. Both the Copy and Move options are possible for migrations to a test status from another test status.

### On this page

- Migrations to Test or Production
- Migrations to Production
- Migrations to Test