Operational Considerations

Before running CA IDMS Extractor, consider these operational factors:

All CA IDMS conventions regarding locking of the source and target databases are used. To ensure accurate extraction of data from the source database while CA IDMS Extractor is executing, you may want to prevent other jobs from updating the source database.
You may either load a new database (that is, a database that was just formatted) or update an existing database. If you update an existing database, unexpected problems may arise if an attempt is made to store or connect a duplicate record unless the store or connect is prevented by a DUPLICATES NOT ALLOWED clause.
The target subschema must reside in a dictionary load area. The Database Load Component of CA IDMS Extractor requires all user-defined and non-system owned integrated index sets have a set CONNECT option of MANUAL and a set ORDER of NEXT or SORTED. Further, if a SORTED set allows duplicates, and the source database was created with duplicates FIRST, the target database must be created with DUPLICATES LAST. To assist in complying with these requirements, a transient (temporary) subschema is created from the specified target so that you do not have to create a special target schema/subschema for CA IDMS Extractor use. The transient subschema is added to the target dictionary, used by the Database Load Component, and subsequently deleted from the target dictionary. Optionally, the transient subschema may be linked into a load library that is defined as a STEPLIB for the Database Load Component.