Input data sets
DDNAME | Contents | Used for these functions |
|---|---|---|
ACBLIB | Application control blocks (ACBs) built during ACBGEN process | Actions on ACBs |
ACBLIB2 | Application control blocks built during ACBGEN to use for comparison (cannot be specified on GLBL control statement) | Comparison of a control block to an ACB |
DBDLIB | Assembled database definitions (DBDs) | Actions on DBDs |
DBDLIB2 | Assembled database definitions (DBDs) to use for comparison (cannot be specified on GLBL control statement) | Comparison of a control block to a DBD |
DBILABEL | Database Integrity labels (optional KSDS) | Actions on labels |
DBISYSIN | Database Integrity control statements that define the tasks you want Database Integrity to perform and the options to use when doing the tasks. The ddname of the data set can be either DBISYSIN or PLUSIN. The control statement data set can be a sequential data set or a member of a PDS, or it can be in stream. The logical record length must be 80 bytes. Coding-Database-Integrity-control-statements describes the Database Integrity control statements in detail. | All |
DFSMDA | IMS dynamic allocation members | DBD audit |
DFSRESLB | IMS load modules | DBD audit, actions on MFS formats, actions on labels |
INFILE | Labels to import | Label import |
MFSLIB | Message descriptions and device formats | Actions on MFS formats |
MODBLKS | IMS online control blocks | DBD audit |
PSBLIB | Assembled program specification blocks (PSBs) | Actions on PSBs |
PSBLIB2 | Assembled program specification blocks (PSBs) to use for comparison (cannot be specified on GLBL control statement) | Comparison of a control block to a PSB |
RECONn | DBRC recovery control data sets | DBD audit, actions on labels |
You can specify the data set name of each library by coding one or more of the following:
- A separate DD statement
- A keyword value on the GLBL control statement
- A keyword value on a function control statement
If you use the DD statement or GLBL statement, you only have to specify a particular type of library once. If you use the function control statements, you must code the keyword on every function control statement.
Each job step can employ more than one method to specify the libraries. If a particular type of library is specified with multiple methods, the GLBL statement overrides the DD statement, and the function control statement overrides both the DD statement and GLBL statement. Therefore, you can define the usual libraries you work with in a standard JCL procedure, and use the GLBL or function specification if you need to work with a different library.