Learn more about the key features of IBM DL/I VSE
Allocation of DL/I resources above 16 MB
When running in a CICS/DLI online environment, the following DL/I resources can be allocated above the 16 MB line of storage: PSBs, HD data buffers, DL/I action modules, and DL/I user exit routines. Moving HD buffers above the 16 MB line will also allow for keeping more data in storage with possibly faster access to DL/I data.
DL/I GETVIS storage in separate subpools
GETVIS storage allocated for different types of DL/I resources is assigned to different sub-pools. This includes: PSBs loaded during CICS/DLI initialization, PSB copies for the single transactions, buffer pool for HD databases, action modules, user exit routines, and queuing elements of the Program Isolation function. The amount of storage that is held by the different subpools can be viewed by their respective subpool-IDs.
More than one Multiple Partition Support (MPS) System
The DL/I Master Partition Controller for the DL/I MPS function can be activated in more than one CICS/DLI online partition at the same time. This way an MPS batch job can connect to any active CICS/DLI online system and process databases defined there. The option to dynamically select regular batch or MPS batch execution (DLZCTRL) has been adapted to the Multiple MPS environment.
More than four GB for HD databases
The data component of DL/I HD (HDAM/HIDAM) databases can be allocated on more than one VSAM ESDS dataset. Up to 16 datasets can be defined. The enhancement is transparent to user applications. The split into multiple datasets is realized through adaptions in the DBD definition and a reorganization or new initial load of the database.
Using DL/I partitioning, database records can be stored in different sections called partitions, where each partition owns the same number of data sets. This increases the maximum storage capacity of a database and allows to overcome the 4 GB limit for a single segment type. The function is transparent to user applications. Partitioning is realized through adaptations in the DBD definition and a reorganization or new initial load of the database.