|
|
|
DataManager only lets you edit definitions stored in the DEVELOPMENT version. Before you can customize your IRDs or ORDs, you must copy them to create a new DEVELOPMENT version. DataManager lets you choose which set of Output Record Definitions to copy when making a new DEVELOPMENT version of record definitions for editing. No matter which ORD version you choose (TEST or PROD), DataManager automatically copies your REAL IRD definitions to the DEVELOPMENT version, too.
Copying is a vital step in DataManager maintenance. Whenever you want to make changes to the definitions currently in production, the first step involved is a copy.
Every COPY job copies REAL IRDs and one version of committed ORDs into the DEVELOPMENT version. This job selects records for editing.
The COPY control statement identifies which version to copy and how to prevent duplicate records. Options specify whether new or existing records take precedence.
►►─ COPY ─ DM ─┬─ REFRESH ─┬──────────────────────────────────────────────────►◄ ├─ TEST ────┤ └─ PROD ────┘
where:
Specifies which set of committed definitions to copy to the DEVELOPMENT version.
Deletes all definitions in the DEVELOPMENT version before copying the requested committed versions (REAL and TEST|PROD) to the DEVELOPMENT version.
Caution: The COPY option can destroy the correspondence between input and output records. Therefore, be very careful when writing COPY control statements.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |