Use the RESTORE function to replicate a structure or substructure that is in PROD or HIST status to a TEST status. Only use this function with structures and substructures that are in PROD status or HIST status.
You can use the RESTORE function against DATABASE, AREA, TABLE, and DATAVIEW structures and substructures. KEY and ELEMENT substructures must be restored by restoring the entire TABLE substructure.
Important! We recommend that you restore the structure or substructure from PROD status immediately before you change it to avoid any loss of information.
When you submit a RESTORE function, the DDD-SYNCH attribute value is set to N for all tables in the structure. If a subsequent COPY to PROD status is issued at the database level, all tables are DDD-SYNCH=N instead of just the modified table(s). This results in all plans associated with the tables being flagged invalid. All plans must then be rebound, either manually or automatically when next referenced. To eliminate unnecessary rebinds, copy only the modified tables back to PROD status. Only the plan using these tables requires rebind.
How It Works
You can use the date/time stamp (ASOF) to construct a TEST version of what your PROD or HIST status version looked like on that day. Using the date/time stamp, you can determine which structures and substructures were in PROD status at a given time and re-create the structure or substructure in the specified TEST status. If you want to restore a HIST version to PROD, first restore it to TEST and then copy it to PROD status.
Note: If your time value includes seconds, round up to the nearest minute.
When you restore a TEST structure or substructure, the existing structure or substructure is entirely replaced by the structure or substructure from which it is being restored. Any occurrences or relationships are deleted or added as necessary to make the restored structure or substructure the same as the one from which it is being restored.
Required Definitions
If you are restoring a TABLE substructure, the parent entity-occurrence definition must exist in the same version to which you are restoring the occurrence. For example, if you are restoring a TABLE substructure to T001 status, the DATABASE and AREA entity-occurrence definitions for that TABLE must exist in T001 status for the RESTORE to be successful.
From History Status
When you restore a structure or substructure from HIST status, CA Datacom Datadictionary cannot complete the process if any of the related occurrences have been deleted due to exceeding the maximum number of allowed HIST versions. CA Datacom Datadictionary returns an error message if the structure is incomplete due to deleted occurrences of this type.
Relationships
If the structure contains relationships with occurrences outside the structure, the relationships may not be restored with the structure or substructure. The copy-rule specified for the relationship determines whether the relationship is restored. For more information and details about relationship copy-rules, see the CA Datacom Datadictionary User Guide.
Constraints
When a structure that has constraints related to it is restored, all constraints are copied. Subsequent maintenance of these tables through SQL cause CA Datacom Datadictionary to change the CONSTRAINT attribute to A for all TEST or HIST versions of these tables. If you later attempt to copy one of these versions (or a structure containing one of these versions) to PROD status, CA Datacom Datadictionary prevents the copy, issues an error message, and identifies the table which has been altered. For more information and instructions, see Maintaining Tables with Related Constraints.
How to Use
Use one of the following procedures to perform this function:
When you select the RESTORE function on the Structure Functions Menu or enter an incomplete RESTORE command, you receive a prompter panel similar to the following example:
=> => => 1-DDOL000196A - CMPP - PLEASE COMPLETE REQUIRED INFORMATION FOR COMMAND ------------------------------------------------------------------------------- DATACOM/DB Structure Maintenance TRCF RESTORE DATABASE ________________________________ to STATUS ____ RES BAS (name) STAT (stat) FROM STATUS ____ AS OF ____________ STAT (stat) (YYYYMMDDhhmm) with PASSWORD using OVERRIDE PSWD (pswd) OVRD (ovrd) PF1=HELP PF2=END PF3=CLARIFY PF4=PROCESS PF5=MENU PF6=STATUS PF7=SCB PF8=SCF PF9=APPLY PF10=PATH PF11=NEXT PF12=INPUT
The following list describes each field, the valid entries and the default (if one exists). Fields that require an entry are highlighted on your terminal. Fields which are not highlighted indicate that an entry is optional.
(Required) Specify the name of the root or base occurrence of the structure or substructure you are restoring.
The entity-occurrence name definition must exist in the same version to which you are restoring the substructure.
1- to 32-character occurrence name
(No default)
(Required) Specify the status of the occurrence to which you are restoring.
T001—T999
(No default)
(Required) Specify the status of the occurrence from which you are restoring.
PROD or 001—999
H000—H997 (000-997 is the generation number)
ASOF (if you want to use the AS OF option)
(No default)
(Optional) If you enter ASOF in the status field, specify the date/time stamp to display the version of the structure that was in PROD status at that date and time. You can specify the full date and time or a partial date, such as 199001 for the year and month or 19900131 for the year, month, and day.
Note: If your time value includes seconds, round up to the nearest minute.
1 to 12 digits
(No default)
Only required if this occurrence has protection against unauthorized maintenance with a password assignment. Supply the password for this occurrence.
1- to 4-character password
(No default)
Only required if this occurrence is restricted from unauthorized maintenance or retrieval with a lock level assignment. Supply the override code.
1- to 4-character override code
(No default)
Press PF9 (APPLY) after completing your entries. If there are no errors, you receive a message confirming the success of the function.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|