Restrictions for the Image Copy function

Certain restrictions apply to using the Image Copy function with the FABJMAIN program.

The following restrictions are common restrictions for IMS HP Image Copy functions:
  • The FABJMAIN program can process only one IMS HP Image Copy function in one job-step execution.
  • A HALDB requires that DBRC is active; otherwise a copy request is rejected.
  • HSAM, GSAM, and MSDB databases are not supported.
  • DD names that start with prefixes FABJ, ICE$, and HKT have special meaning to IMS HP Image Copy. Do not use DD statements with these prefixes except for the DD statements that are listed in DD statements for creating image copies.

Subtopics:

Restrictions for the Image Copy function

  • The Image Copy function supports the following environments only:
    • Batch image copy
    • Concurrent image copy
  • The Image Copy function does not support the functions that are provided by the following IMS utilities:
    • Online image copy
    • HSSP image copy
    • Image copy 2
    • Restart function under UCF
  • The maximum number of full-function database data sets that can be processed in a job step is 2000.
  • The maximum number of DEDB area data sets that can be processed in a job step is 2048.
  • The total number of database data sets that can be processed in a job step is equal to or fewer than 2048.
  • The same data set group, DBDS, or area cannot be processed in the same job step, which means, you cannot specify the same data set group, DBDS, or area in multiple ICEIN statements, such as IC and AIC, in the same job step.

    When you process shared secondary index databases, be aware that you can specify only one secondary index for each shared secondary index database in a job step. For example, as shown in the following figure, if a shared secondary index database has two secondary indexes with database names INDEX0 and INDEX1, you can specify only INDEX0 or INDEX1. 

    //ICEIN DD *
  AIC   DBD=INDEX0,DDN=SIDXDD30   <- If you specify INDEX0,
* AIC   DBD=INDEX1,DDN=SIDXDD30   <- you cannot specify INDEX1 
*                                    because INDEX0 and INDEX1 are physically same database.
/*
  • A compressed image copy data set cannot be used with IMS Database Recovery utility as an input data set. Use either the Recovery function of IMS HP Image Copy or the IMS Database Recovery Facility.

Restrictions for the Advanced Image Copy Services

  • You cannot specify both OFFLDTYPE=F and OFFLDTYPE=S in a same job step.
  • You cannot specify both OFFLDTYPE=F and ICOUT=(,%STACK) in a same job step.
  • You cannot specify both ICOUT=(,*) and ICOUT=(,%STACK) in a same job step.
  • If the input database is a multi-volume OSAM database, you must not use separate IEFBR14 utility step for each volume. If you use separate IEFBR14 step for each volume, extents that have the same identifier (volume 1) are created. Advanced Image Copy Services requires that you allocate your multi-volume data sets by using the standard DFSMS methods.
    If your input database data set is allocated by using separate IEFBR14 utility step for each volume, IMS HP Image Copy issues the following message and ends with a return code of 08.
    FABJ0163E FORMAT OF INPUT DBDS IS NOT SUITABLE FOR DFSMSDSS ADVANCED

Restrictions for parallel processing

  • Parallel image copy processing is invoked only by the FABJMAIN program.
  • Both batch image copy and concurrent image copy cannot be specified in one job step.
  • Parallel processing and sequential processing cannot coexist in one group.

Restrictions for single-step HASH Check (for full-function databases)

  • For full-function databases, the Pointer to Segment Check function is not supported. Only the HASH Check option of the HD Pointer Checker is supported.
  • All the restrictions that apply to stand-alone HD Pointer Checker HASH Check option jobs also apply to the HD Pointer Checker HASH Check processes that are invoked through the HASH Check option of the Image Copy function.
  • The maximum number of databases that can be processed at a time is 2500.
  • HASH Check cannot detect the following pointer-type errors:
    • Physical parent pointers that are not at the beginning or end of their twin chain
    • Direct address pointers in a HISAM database that chain the logical records from a primary to an overflow data set or the logical records in the overflow data set.
  • For HALDBs, the HASH Check option has the following restrictions:
    • It can validate only physical pointers. It cannot validate logical relationships.
    • It does not provide the ability to analyze a PSINDEX database or a PHIDAM primary index database.
    • It cannot detect the following pointer-type errors:
      • Logical parent pointers and paired logical child pointers that reside in an Extended Pointer Set (EPS)
      • Indirect pointers that reside in the Indirect List Data Set (ILDS)
  • In an image copy job, the maximum number of tasks for a HASH Check is 99.

Restrictions for multiple-step HASH Check (for full-function databases)

  • In an IMS-managed ACBs environment, multiple-step HASH Check for full-function databases is not supported.
  • For full-function databases, the Pointer to Segment Check function is not supported. Only the HASH Check option of the HD Pointer Checker is supported.
  • All the restrictions that apply to stand-alone HD Pointer Checker HASH Check option jobs also apply to the HD Pointer Checker HASH Check processes that are invoked through the HASH Check option of the Image Copy function.
  • Multiple-step HASH Check is not supported for parallel image copy processing.
  • The maximum number of databases that can be processed at a time is 2500.
  • The HASH Check option cannot detect the following pointer-type errors:
    • Physical parent pointers that are not at the beginning or end of their twin chain
    • Direct address pointers in a HISAM database that chain the logical records from a primary to an overflow data set or the logical records in the overflow data set.
  • In HALDB, the HASH Check option has the following restrictions:
    • It can validate physical pointers only. It cannot validate logical relationships.
    • It does not provide the ability to analyze a PSINDEX database or a PHIDAM primary index database.
    • It cannot detect the following pointer-type errors:
      • Logical parent pointers and paired logical child pointers that reside in an Extended Pointer Set (EPS)
      • Indirect pointers that reside in the Indirect List Data Set (ILDS)
  • Secondary index databases cannot be checked.

Restrictions for DEDB HASH Check

  • The Pointer to Segment Check function is not supported. Only the HASH Check option of the DEDB Pointer Checker is supported.
  • All restrictions that apply to stand-alone DEDB Pointer Checker HASH Check option jobs also apply to the DEDB Pointer Checker HASH Check option that is enabled in Image Copy function jobs.