IMS-managed ACBs
In the offline mode, you can use one of the following methods to determine the managed ACB environment.
- Specify CATALOG_ALIAS=NONE in the control cards associated with the PFPOPTS DD statement to run a job step in offline mode that bypasses IMS-managed ACBs. The IMS ACB library is used to obtain the required control blocks regardless of any existing IMS catalog information.
- Specify the high-level qualifier (SYSDSNHLQ) of the IMS catalog bootstrap data set (BSDS) and the IMS catalog directories are specified using the following:
A control card referenced by the PFPOPTS DD statement.
The PFPOPTS DD statement is first examined for the high-level qualifier (SYSDSNHLQ). If present, then the value specified for the SYSDSNHLQ keyword is used as the high-level qualifier for the IMS catalog BSDS and catalog directories.- An IMS catalog definition exit (DFS3CDX0).
The IMS catalog definition exit is checked for the catalog and the managed ACB environment. The catalog name is used to obtain the SYSDSNHLQ as the high-level qualifier for the IMS catalog BSDS and the catalog directories.
The SYSDSNHLQ is obtained from the following sources:- MDA member mapping the catalog BSDS in the format catalogAliasHLQ, where catalogAlias is derived from the catalog definition exit.
- Catalog database definitions in the RECON data sets.
- PROCLIB member (DFSDFXXX)
The PROCLIB member is checked for the catalog and the managed ACB environment. The catalog name is used to obtain the SYSDSNHLQ as the high-level qualifier for the IMS catalog BSDS and the catalog directories.
The SYSDSNHLQ is obtained from the following sources:- MDA member mapping the catalog BSDS in the format catalogAliasHLQ, where catalogAlias is derived from the PROCLIB member DFSDFXXX.
- Catalog database definitions in the RECON data sets.
- Entries in the RECONs
The RECONs are evaluated last. The SYSDSNHLQ is derived from the applicable IMS catalog information.
The following table describes how the staging or active directory is accessed in Fast Path Offline products:
Utility | ACBLIB environment | Directory to read the database | |
|---|---|---|---|
Default Directory | Alternate via keyword | ||
ANALYZE | IMSACB | ACTIVE |
|
INITIALIZE | IMSACB | ACTIVE | STAGING (using CATALOG_DIRECTORY) |
REORG | IMSACB | ACTIVE | STAGING (using CATALOG_DIRECTORY) |
UNLOAD | IMSACB | ACTIVE | Not applicable |
| NEWACB | STAGING | ACTIVE (if not in staging, no keyword) |
RELOAD | IMSACB | STAGING | ACTIVE (if not in staging, no keyword) |
CHANGE | IMSACB | STAGING | ACTIVE (if not in staging, no keyword) |
| OLDACB | ACTIVE | Not applicable |
BUILD | IMSACB | ACTIVE | STAGING (using CATALOG_DIRECTORY) |
XSCAN | IMSACB | ACTIVE | STAGING (using CATALOG_DIRECTORY) |
VERIFY | IMSACB | ACTIVE | STAGING (using CATALOG_DIRECTORY) |
COLLECT | IMSACB | ACTIVE |
|
DMAC_PRINT | IMSACB | ACTIVE |
|
EXTEND | IMSACB | ACTIVE | STAGING (using CATALOG_DIRECTORY) |
EXTRACT | IMSACB | ACTIVE |
|
PROCESS_AREA | IMSACB | ACTIVE | STAGING (using CATALOG_DIRECTORY) |
PFPSORT | IMSACB | ACTIVE | STAGING (using CATALOG_DIRECTORY) |
The FABEUR6 and FABEUR7 program extensions also support the IMS-managed ACB environment.
- When you specify the BSDSHLQ control statement, database (DMB) definitions are read directly from the IMS active or staging directory instead of from the ACBLIB data set.
- The BSDSDIR control statement controls which directory is used, with the active directory as the default.
- If you do not specify the BSDSHLQ control statement, the programs continue to operate in an ACBLIB-based environment, maintaining full backward compatibility.
For more information, see the FABEUR6 and FABEUR7 sections in Fast Path/EP products reference information.