EXPORT command

The EXPORT command creates a sequential file that contains BMCXCOPY and SYSCOPY table information about all selected table spaces, and optionally their indexes. The file also contains Db2 catalog information. The file created when you use the EXPORT command is used by the BMC AMI Recover MIGRATE and IMPORT command to move data from one or more table spaces to another.

If the migration file is going to be used with IMPORT, all the objects named in the EXPORT command must have a valid full image copy registered in SYSIBM.SYSCOPY or BMCXCOPY. If you want to run EXPORT on the target system to create a migration file to use with BMC AMI Recover MIGRATE on the source system, no image copy is required on the target system. If no copy exists, the following informational message is issued:

Incremental image copies are not supported.

For more information, see Creating-a-migration-file-for-the-Copy-Migration-feature.

The following figure shows the syntax for the EXPORT command with defaults underscored.

When you use the EXPORT command in the SYSIN data set, the following rules apply:

• The first option you specify must be TABLESPACE, RMGROUP, OBJECTSET, or APPLICATION.

  You cannot specify EXPORT INDEXSPACE or EXPORT INDEX syntax. Indexes are only included when you specify INDEXES YES.

• The table space name, RMGROUP name, OBJECTSET name, or APPLICATION is required (explicitly or by wildcard).
• You can specify the other options in any order.
• An asterisk in column 1 in the SYSIN data set specifies that the line is a comment that will not be echoed in the SYSPRINT output. A double hyphen (--) coded in column 1 through 70 also makes the rest of the line a comment.
• You can specify the start RBA value of the image copy to be copied using either ATRBA or ATLOGPOINT. (These keywords are synonymous.) However, BMC AMI Copy normally uses the latest copy (LASTCOPY).