Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
Unloading from other sources
Unloading from a copy of a table space (an image copy, incremental copy, or a DSN1COPY) is similar to unloading from a table space.
Specifying which copy to unload—using the UNLOAD command
To unload from a copy, use the INFILE option.
Specifying which copy to unload—using the UNLD command
To invoke this feature, add one of the following options to your unload statement:
COPYDDN | If you use COPYDDN, you must change the JCL to add the DD name supplied with the COPYDDN keyword. Either ensure that the DD in the JCL points to the input data set, or specify the OUTPUT-command-for-BMC-AMI-Unload to provide the data set name. |
|---|---|
COPYDSN | If you do not want to change your JCL, use the COPYDSN keyword and supply the full data set name. Quotation marks around the data set name are optional. |
SYSCOPY | Use the SYSCOPY keyword to unload from the last posted copy in the Db2 catalog, or to specify that you want the last FULL or INCREMENTAL copy. |
Considerations when unloading from a copy
The attributes of the input data set that describe an image copy or DSN1COPY must be RECFM=F, or RECFM=FB and LRECL=4096. The input data set is assumed to contain valid Db2 page layouts.
When unloading from an image copy, BMC AMI Unload counts, but does not use, control pages (that is, header pages and space map pages). Therefore, provided that the input data set contains valid Db2 pages, they can be in any order.
When unloading from an image copy, you can unload either from a single partition or all partitions. You cannot specify multiple partitions from which to unload.