INFILE

You can specify the INFILE option to use a copy or a data set other than the Db2 table space data set as the source of the input data. When you are unloading from multiple table spaces, the INFILE option applies to all table spaces.

This option is valid only when DIRECT YES is in effect.

The following table lists the alternative sources of input data that you can use, and tells you which INFILE option to use for each input type:

Alternative sources of BMC AMI Unload input

Input type	INFILE option
Full (including Inline Image copies) or incremental image copy data sets	IMAGECOPY INLINE COPY
Cabinet copies created by BMC AMI Copy, the BMC Recovery Management for Db2 solution, or the BMC AMI Recovery for Db2 solution	IMAGECOPY
DSN1COPY sequential data sets	ddname

Restrictions

The following additional restrictions apply to the INFILE option:

• (PTF BQU3237 applied) You must specify +SVRMODETAPE(I) when specifying a JCL-allocated, INFILE ddname using tape and unloading to an OUTPUT statement using tape.
• You cannot specify FILTERPART YES when unloading from image copies. 
• BMC AMI Unload does not unload from LOB or XML copy data sets. However, you can unload from a copy of the base table if you do not select any LOB or XML columns.
• You cannot use a DDLIN data set for copy file input.
• You cannot use a concatenation of image copies for different tablespaces when specifying INFILE ddname.
  
• You cannot use the following types of copy input:
  
  • Encrypted copies created by BMC AMI Copy
  • Instant Snapshot copies created by BMC AMI Copy
  • VSAM linear data sets
  • VSAM FlashCopy image copies
  • Online consistent copies created by the BMC Recovery Management for Db2 or BMC Recovery for Db2 solutions
• BMC AMI Unload does not support unloading from PBR2 inline copies which contain more than one partition. 

Additional considerations

The following additional considerations apply to the INFILE option:

• Unpredictable results might occur if the data sets do not match the options that you specify:
  • If the input data set is an inline image copy, specify the INLINE YES option. If INLINE YES or the default, INLINE NO, does not match the type of input data set, rows might be omitted from the output.
  • If the input data set is an incremental image copy, specify the INCREMENTAL option.
  • If you are unloading all partitions of a partitioned table space, ensure that the data set includes a full image copy of all of the partitions.
  • If you are unloading a specific partition, ensure that the input provides the specified partition with the full image copy data set either by including a DSNUM ALL copy, or a partlevel copy of the partition(s) specified in the UNLOAD command.
• When you specify INFILE to unload any of the following types of copy data sets, all selected rows must be at the current version (as defined in SYSIBM.SYSTABLES):
  • An incremental image copy
  • Any image copy created with the SYSTEMPAGES NO copy option

IMAGECOPY

Specify INFILE IMAGECOPY to have BMC AMI Unload use the specified full or incremental image copy data set that is in the SYSIBM.SYSCOPY table or the BMCXCOPY table; BMCXCOPY applies only if you are unloading a cabinet copy.

For information that applies to all INFILE options, see Restrictions and Additional considerations.

Partitioned table spaces (PTF BQU2139 applied)

If the table space is partitioned, BMC AMI Unload uses one of the following copy types:

• (BMC.DB2.SPE2304) Partition range image copies (duplicate SYSCOPY entries where DSNUM is not equal to 0). Each partition of the table must exist in one of the image copy files.
• (BMC.DB2.SPE2304) Individual partition image copies (unique SYSCOPY entries where DSNUM is not equal to 0) There must be an individual copy for each partition in the table.
• If there is not one copy for each partition that you unload, the first image copy that fulfills your specifications and that contains all partitions (DSNUM is equal to 0) will be used.
• (BMC.DB2.SPE2304) Inline copies produced using Reorg ICLIMIT are also considered. 

Partitioned table spaces (PTF BQU2139 not applied)

Non-partitioned table spaces

BMC AMI Unload can unload multi-data-set, non-partitioned table spaces only from a single image copy that contains all of the individual data sets. You cannot unload non-partitioned table spaces from separate image copy data sets where DSNUM is not equal to 0.

Operands

FULL	(default) BMC AMI Unload unloads from a full image copy. BMC AMI Unload unloads from the most recent full image copy found in the SYSIBM.SYSCOPY table or the BMCXCOPY table; BMCXCOPY applies only if you are unloading a cabinet copy. To unload from a full image copy before the most recent one, specify a negative integer to count the specified number of full image copies back from the most recent one.
INCREMENTAL	BMC AMI Unload unloads from an incremental image copy. When unloading from an incremental image copy, BMC AMI Unload reads all rows in the incremental image copy (not only the rows that changed) and unloads those that match the SELECT statement criteria. BMC AMI Unload unloads the most recent incremental image copy found in the SYSIBM.SYSCOPY table or the BMCXCOPY table; BMCXCOPY applies only if you are unloading a cabinet copy. (PTF BQU2139 applied) To unload from an incremental image copy before the most recent one, specify a negative integer to count the specified number of incremental image copies back from the most recent one. BMC AMI Unload cannot use the INFILE option to unload an incremental image copy that does not contain dictionary pages and does contain compressed data.
0	(PTF BQU2139 applied) (default) This option tells BMC AMI Unload that the specified file is the most recent image copy
–integer	(PTF BQU2139 applied) This option tells BMC AMI Unload to count the specified number of image copies back from the most recent one

ddname

Use this option to specify a ddname or ddname prefix when unloading from a DSN1COPY sequential data set or a specific full or incremental image copy.

If you specify INFILE ddname, BMC AMI Unload unloads all rows from the specified data set that match your SELECT statement criteria.

Additional restrictions and considerations

In addition to the general restrictions and considerations on the INFILE option, the following restrictions and considerations apply to INFILE ddname:

• The following Db2 catalog information must match the copy that you are unloading:
  • The OBIDs of the tables that you specify, unless you specify the OBID for the table by using the OBID option
  • The table definitionsHowever, if you added more columns to a table since the copy was made and you are unloading those columns, the new columns contain their default values.
• Concatenating multiple image copy data sets, particularly when mixing copy data sets from tape with copy data sets from DASD, produces unpredictable results.
• Using multiple SELECT statements for different tables with concatenated image copy data sets (using INFILE ddname) can cause failures or might unload the wrong data.
  
• When unloading an image copy on a Db2 subsystem other than the one on which the copy was created, the following information applies:
  • For a range-partitioned table space, BMC AMI Unload unloads only the number of partitions that are defined on the target subsystem.
  • For a partition-by-growth table space, BMC AMI Unload unloads only the number of partitions that exist on the target subsystem.

Operands

FULL	(Default) Tells BMC AMI Unload that the specified file is a full image copy or a DSN1COPY data set
INLINE	(SPE2005) BMC AMI Unload INFILE ddname FULL now supports unloading from an INLINE image copy using INFILE ddname FULL INLINE YES. YES Tells BMC AMI Unload to read the image copy mentioned in the JCL's ddname DD statement as an INLINE image copy NO (Default) Tells BMC AMI Unload to read the image copy mentioned in the JCL's ddname DD statement as a full image copy Warning Important NO is the default only if you omit the INLINE keyword. However, if you do specify INLINE, you must also specify YES or NO. Otherwise, BMC AMI Unload fails with a syntax error.
INCREMENTAL	Tells BMC AMI Unload that the specified file is an incremental image copy If INFILE ddname specifies an incremental image copy, you must use this option or BMC AMI Unload assumes that FULL (the default) applies and unpredictable results might occur. When using an incremental image copy, BMC AMI Unload reads all rows in that image copy, not only the rows that changed. INFILE ddname INCREMENTAL does not support INLINE YES. Warning Important BMC AMI Unload cannot use the INFILE option to unload an incremental image copy that does not contain dictionary pages and does contain compressed data.
INFILEPFX	(SPE2005)  Tells  BMC AMI Unload  to scan for numbered ddnames (for example, ddn01, ddn02, ddn03, and so on) for a partitioned-by-range (PBR) table spaceBMC AMI Unload then reads these numbered ddnames instead of reading a single INFILE ddname. The numeric suffix can contain an arbitrary number of leading zeros for example, ddn0006, ddn7, or ddn008. The number of these ddnames corresponds to the number of selected partitions in the PBR table space.