How to use inline COPY with LOAD
You can create a full image copy data set (SHRLEVEL REFERENCE) during LOAD execution. The new copy is an inline copy.
About this task
The advantage to using an inline copy is that the table space is not left in COPY-pending status regardless of which LOG option was specified for the utility. Thus, data availability is increased.
Procedure
To create an inline copy:
Use the COPYDDN and RECOVERYDDN keywords.
You can specify LOAD REPLACE with COPYDDN or RECOVERYDDN or LOAD RESUME YES
SHRLEVEL NONE with COPYDDN or RECOVERYDDN. If you specify RESUME NO but not REPLACE, an error
message is issued and LOAD terminates.
You can specify up to two primary and two secondary copies. Inline copies are produced during
the RELOAD phase of LOAD processing.
You can specify LOAD REPLACE with COPYDDN or RECOVERYDDN or LOAD RESUME YES
SHRLEVEL NONE with COPYDDN or RECOVERYDDN. If you specify RESUME NO but not REPLACE, an error
message is issued and LOAD terminates.
The SYSCOPY record that is produced by an inline copy contains ICTYPE=F and SHRLEVEL=R. The value
of the STYPE column depends on how the image copy was produced:
- R if the image copy was produced by LOAD REPLACE LOG(YES)
- S if the image copy was produced by LOAD REPLACE LOG(NO)
Y if the image copy was produced by LOAD RESUME LOG(NO)
Z if the image copy was produced by LOAD RESUME LOG(YES)
- Data pages might be out of sequence and some might be repeated. If pages are repeated, the last one is always the correct copy.
- Space map pages are out of sequence and might be repeated.
- If the compression dictionary is rebuilt with LOAD, the set of dictionary pages occurs twice in the data set, with the second set being the correct one.
The total number of duplicate pages is small, with a negligible effect on the required space for the data set.