EXPORT syntax option description

This section describes each of the options you can specify with the EXPORT command.



Related topic

EXPORT-command

APPLICATION creatorName

APPLICATION creatorName can be used to specify the object for migration. When this type of object is specified with a creator name of SAPR3, all table spaces that have CREATOR=SAPR3 are copied.

APPLICATION can be mixed with TABLESPACE specifications within the same EXPORT command.

Important

Only the table spaces are used from an APPLICATION. Any index spaces that appear in the group are ignored. Use INDEXES YES to include the table space indexes.

ATLOGPOINT


Important

Use ATLOGPOINT in a data sharing environment; use ATRBA in a non-data-sharing environment.

The ATLOGPOINT option specifies the image copy to export. The copy must be registered in the SYSIBM.SYSCOPY table or BMCXCOPY. The default is the most recent primary image copy. BMC AMI Copy will only EXPORT one image copy per object. If there are multiple image copies available at a given log point, preference will be given in the following order: LP, LB, RB, RP.

Important

BMC AMI Copy will export SHRLEVEL REFERENCE or SHRLEVEL CHANGE image copies. Using a SHRLEVEL CHANGE image copy with the BMC AMI Recover IMPORT command might produce inconsistent results.

Values of ATLOGPOINT

Value

Description

ATLOGPOINT LASTFULLCOPY

When you want to migrate the most recent full image copy (ICTYPE F) of the named space, use ATLOGPOINT LASTFULLCOPY. Care must be taken when using this option with INDEXES YES. If the image copies for the table space and indexes are not at the same log point, the IMPORT might produce inconsistent results.

ATLOGPOINT X’hexStartLRSN’

Use ATLOGPOINT X’hexStartLRSN’ to specify the start RBA of the image copy that you want to migrate. If you use this option with INDEXES YES and the index image copies do not have the same log point as the table space image copy, the index image copies will not be exported.

ATRBA


Important

Use ATRBA in a non-data-sharing environment; use ATLOGPOINT in a data sharing environment.

The ATRBA option specifies the image copy to export. The copy must be registered in the SYSIBM.SYSCOPY table or BMCXCOPY. The default is the most recent primary image copy. BMC AMI Copy exports only one image copy per object. If there are multiple image copies available at a given log point, preference is given in the following order: LP, LB, RB, RP.

Important

BMC AMI Copy will export SHRLEVEL REFERENCE or SHRLEVEL CHANGE image copies. Using a SHRLEVEL CHANGE image copy with the BMC AMI Recover IMPORT command might produce inconsistent results.

Values of ATRBA

Value

Description

ATRBA LASTFULLCOPY

When you want to migrate the most recently registered full image copy (ICTYPE F) of the named space, use ATRBA LASTFULLCOPY. Care must be taken when using this option with INDEXES YES. If the image copies for the table space and indexes are not at the same log point, the IMPORT might produce inconsistent results.

ATRBA X’hexStartRBA’

Use ATRBA X’hexStartRBA’ to specify the start RBA value of the image copy that you want to migrate. If you use this option with INDEXES YES and the index image copies do not have the same log point as the table space image copy, the index image copies will not be exported.

AUX

The AUX option allows BMC AMI Copy to migrate auxiliary, history, and archive objects without having to explicitly specify these objects.

AUX ALL is automatically generated for EXPORT commands. This includes XML and LOB spaces.

For a description of the AUX option and its parameters, see AUX.

CLONE

The CLONE option indicates that EXPORT is to process only image copies that are for clone tables.

The base table space and its clone can not be processed in the same BMC AMI Copy command.

COLSTATS

You can use the COLSTATS option to carry forward existing RUNSTATS column statistics from a migration file and to apply these column statistics during a BMC AMI Recover IMPORT. To import statistics, you must have specified STATS YES COLSTATS YES in the BMC AMI Copy EXPORT command.
Column statistics from SYSCOLSTATS, SYSCOLDIST, SYSCOLDISTSTATS, and SYSCOLUMNS are included in the migration file.

Value

Description

YES

Specifying YES includes the RUNSTATS column statistics information from the source system in the migration file.

NO

(Default) Specifying NO indicates that the RUNSTATS column statistics information is not included in the migration file.

Important

You can specify the COLSTATS option only if the STATS YES command is requested.

DSNAME dataSetName

Use the DSNAME option when you dynamically allocate the migration file data set and want to override the default name. The value of dataSetName becomes the new default migration file data set name.

You can construct dataSetName using any of the symbolic variables listed under COPYDSN.

This option is usually used with wildcard selection of data sets. 

For more information, see Using-symbolic-variables and Stacking-copies-on-tape.

EXCLUDE

Use the EXCLUDE option after a wildcard space specification to exclude one or more spaces from migration that would otherwise be included. You can use wildcards % and * or specific names to specify the exclusions.

The excluded spaces must be in the form of a list following the EXCLUDE keyword. Each item in the list must be in the form databaseName.s paceName and you must separate the individual items by commas. Optionally, you can enclose the list in parentheses. For more information, see  Excluding-specified-spaces-from-a-wildcard-specification.

EXPORTDDN exportOutputDescriptor

Use the EXPORTDDN option to specify the OUTPUT command descriptor name that has the EXPOUT YES option.

INDEXES

The INDEXES option allows you to specify that you want BMC AMI Copy to export the indexes associated with the table space(s) given by the object list of the EXPORT command. The default is INDEXES NO indicating that no indexes are to be exported.

Important

The use of INDEX is synonymous with INDEXES for this option.

Values of INDEXES

Value

Description

INDEXES NO

(Default) Specifying INDEXES NO tells BMC AMI Copy to exclude indexes from the migration file.

INDEXES YES

Specifying INDEXES YES tells BMC AMI Copy to export all indexes for the table space(s) specified by the object list. INDEXES YES implies grouping the indexes with the table space when ATRBA/ATLOGPOINT is specified with a log point. When ATRBA/ATLOGPOINT LASTFULLCOPY is specified, grouping is not applied.

Important

If the table space includes a clone table, BMC AMI Copy suppresses the INDEXES YES option. BMC AMI Recover rebuilds the indexes when the table space is imported.

Important

For optimal results with EXPORT and IMPORT, make sure that the image copies for both table spaces and index spaces are consistent. If the table space and image space copies are not registered at the same RBA, you might receive the following informational message indicating that the copies might not be consistent:

BMC180132I databaseName.spaceName(part) MAY NOT BE CONSISTENT (X’rba’, X’rba’)

This message suggests only possible inconsistencies due to registration RBAs but does not confirm them.

If a table has multiple indexes, you must register all image copies for the index spaces at the same RBA to include them in the migration file. The expected RBA is set by the first exported index. For any other index image copies not registered at that first RBA, the image copy information is not included in the migration file although the migration file will still include the other catalog data for the indexes. 

To include the missing index image copies in the migration file, you must make index image copies with a common RBA and then rerun EXPORT to rebuild the migration file.    

OBJECTSET objectSetName

Use OBJECTSET objectSetName to specify the table spaces that are included in a BMC AMI Recovery Manager object set that you want to migrate. The BMC AMI Recovery Manager object set is identified by objectSetName.

Important

EXPORT OBJECTSET is synonymous with EXPORT TABLESPACE OBJECTSET.

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager object sets, see the BMC AMI Recovery Manager for Db2 documentation.

Important

Only the table spaces are used from a BMC AMI Recovery Manager OBJECTSET. Any index spaces that appear in the object set are ignored. Use INDEXES YES to include the table space indexes.

ON ERROR ICEXISTS

The ON ERROR ICEXISTS option allows you to specify what action BMC AMI Copy is to take for EXPORT when a valid source copy does not exist.

Values of ON ERROR ICEXISTS

Value

Description

ON ERROR ICEXISTS END

ON ERROR ICEXISTS END, the default, indicates BMC AMI Copy is to terminate processing.

ON ERROR ICEXISTS SKIP

ON ERROR ICEXISTS SKIP directs BMC AMI Copy to issue the message BMC30143I CONTINUING DUE TO ON ERROR ICEXISTS OPTION, skip the space, and continue processing the other spaces specified in SYSIN.

If you are migrating multiple spaces and copies do not exist for all spaces and you specified ON ERROR ICEXISTS SKIP, BMC AMI Copy issues an error message, but continues on to the next command, if there are any.

ON ERROR NOTSUPPORTED

The ON ERROR NOTSUPPORTED option allows you to specify what action BMC AMI Copy is to take if a space or partition is an unsupported type in BMC AMI Copy. The following table lists the types not supported by BMC AMI Copy and the error messages that BMC AMI Copy issues:


ON ERROR NOTSUPPORTED condition

BMC AMI Copy message issued

Space has a page size or piece size that is not supported.

BMC30575E PAGESIZE = pageSizeValue IS NOT SUPPORTED

Values of ON ERROR NOTSUPPORTED

Value

Description

ON ERROR NOTSUPPORTED SKIP

ON ERROR NOTSUPPORTED SKIP causes BMC AMI Copy to issue a message, skip over the space, and continue processing other spaces specified in SYSIN.

ON ERROR NOTSUPPORTED END

(Default) ON ERROR NOSUPPORTED END indicates BMC AMI Copy is to terminate processing with an RC=12 if an unsupported type is encountered.

REUSE

The REUSE option allows you to specify the allocation disposition of the migration file.

Values of REUSE

Value

Description

REUSE NO

(Default) REUSE NO causes the migration file to be allocated with DISP=NEW.

REUSE YES

REUSE YES causes the migration file to be allocated as DISP=OLD. If the migration file exists, the contents of the file will be replaced. If the migration file does not exist, the file will be allocated as DISP=NEW.

OPTION MAXTASKS 1,1                      
OUTPUT OUT                               
UNIT 3390                                
EXPOUT YES                               
DSNAME RWC.COPY.EXP.HARDCODE.NAME        

             EXPORT TABLESPACE ACPDB40.*
                EXPORTDDN (OUT)          
                REUSE YES

RMGROUP creator.groupName RMGROUPTS creator.groupName

RMGROUP can be used in place of TABLESPACE in any EXPORT command. Use RMGROUP to specify the table spaces that are included in a BMC AMI Recovery Manager object set that you want to migrate.

Important

EXPORT RMGROUPTS, EXPORT RMGROUP, and EXPORT TABLESPACE OBJECTSET are synonymous.

RMGROUP is followed by the two-part BMC AMI Recovery Manager creator.objectSetName. A maximum of 8 characters can be used for a creator, while objectSetName can be a maximum of 18 characters. creator follows the rules for short SQL identifiers. objectSetName follows the rules for long SQL identifiers. Each part, creator and objectSetName , can be delimited by double or single quotation marks. The symbols $, #, and @ are valid and can be used as the first character for a creator.

BMC AMI Copy does not allow wildcards to be specified with RMGROUP and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager object sets, see the BMC AMI Recovery Manager for Db2 documentation.

Important

Only the table spaces are used from a BMC AMI Recovery Manager object set. Any index spaces that appear in the object set are ignored. Use INDEXES YES to include the table space indexes.

STATS

The STATS option allows you to carry forward existing RUNSTATS in a migration file. These RUNSTATS might then be optionally applied during an BMC AMI Recover IMPORT using the migration file.

Specifying YES includes SYSINDEXSTATS, SYSLOBSTATS, and SYSTABSTATS in the migration file. Real-time statistics are included in a migration, regardless of the STATS specification.


Value

Description

YES

STATS YES tells BMC AMI Copy to carry forward any existing RUNSTATS in the migration file.

NO

(Default) STATS NO tells BMC AMI Copy not to carry forward existing RUNSTATS in the migration file.

TABLESPACE databaseName.spaceName

Use the TABLESPACE option to specify the spaces that you want to migrate.

The space specification is a list that can contain both explicit space names and wildcard patterns with the individual items in the list separated by commas.

Each explicit space name in the space list must be in the form databaseName.spaceName where:

  • databaseName is the name of the database containing the space. If you do not provide a database name, BMC AMI Copy uses the default DSNDB04.
  • spaceName is the name of the space containing the partitions or data sets to be migrated.

You can enclose databaseName.spaceName in double quotation marks or single quotation marks. This allows the use of special characters, such as $, #, or /, in your object names.

When you use a wildcard pattern to specify multiple spaces, you can include the wildcard characters * (asterisk) and % (percent) to provide matching on one or more characters. Using-wildcard-characters-in-the-object-name-specification tells you how wildcards are used and how BMC AMI Copy orders the results of wildcard expansions.

TABLESPACE OBJECTSET objectSetName

Use TABLESPACE OBJECTSET objectSetName to specify the table spaces that are included in a BMC AMI Recovery Manager object set that you want to migrate. The BMC AMI Recovery Manager object set is identified by objectSetName. objectSetName identifies the BMC AMI Recovery Manager object set that contains the table spaces.

Important

EXPORT TABLESPACE OBJECTSET is synonymous with EXPORT OBJECTSET, EXPORT RMGROUP, and EXPORT RMGROUPTS.

BMC AMI Copy does not allow wildcards to be specified with OBJECTSET and will issue messages regarding an invalid group name if wildcards are used.

BMC AMI Copy accesses the BMC Common Db2 repository and the Db2 catalog to retrieve the table spaces that are defined for the group.

For more information about BMC AMI Recovery Manager object sets, see the BMC AMI Recovery Manager for Db2 documentation.

Important

Only the table spaces are used from a BMC AMI Recovery Manager OBJECTSET. Any index spaces that appear in the object set are ignored. Use INDEXES YES to include the table space indexes.

TAGSET tagName

Use the TAGSET option to include table spaces tagged with a tag name in the COPY command. All table spaces with the specified tag are selected for EXPORT processing. Use EXCLUDE to omit unwanted table spaces.

TAPEVOLS

The TAPEVOLS option requests that EXPORT capture volser and file sequence number for image copies on tape and include them in the migration file. TAPEVOLS allows BMC AMI Recover to import from the image copies when they are not cataloged on the target system.

Values of TAPEVOLS

Description

NO

(Default) BMC AMI Copy does not include volser and file sequence number in the migration file.

YES

BMC AMI Copy includes volser and file sequence number in the migration file.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*