Launch Express for ISPF

The architecture of Launch Express for ISPF centers around three primary components: the LE Manager, the Allocation Module, and the Deallocation Module. The LE Manager acts as the central control point, overseeing the allocation and deallocation processes. The Allocation Module intercepts library requests made by ISPF applications and dynamically allocates the required datasets.

This module uses configuration files to determine which libraries are needed for each application. The Deallocation Module is responsible for releasing the allocated libraries when the application terminates. Communication between these components is primarily internal to the z/OS environment, utilizing system services and control blocks.

There are no external APIs or network protocols involved in the core functionality. Configuration files are used to define the libraries required for each ISPF application. These files specify the datasets to be allocated and the conditions under which they should be allocated.

The system integrates with the z/OS security system, such as RACF, for access control. All actions are logged, providing an audit trail. Compared to manual library management, Launch Express reduces the risk of errors and simplifies the deployment process.

For example, the Allocation Module uses the configuration files to determine which datasets to allocate when an ISPF application is started, ensuring that the correct libraries are available.