DYNA-STEP

The architecture of DYNA-STEP centers around three main components: the DYNA-STEP load module, the configuration dataset, and the ISPF interface. The load module is the core component, intercepting program load requests within the z/OS environment. It consults the configuration dataset to determine which libraries to allocate.

The configuration dataset is a critical component, containing rules for library allocation based on program names, user IDs, or other criteria. This dataset is typically a partitioned dataset (PDS) or a partitioned extended dataset (PDSE) and is managed using standard z/OS utilities. The ISPF interface provides a user-friendly way to interact with DYNA-STEP, allowing administrators to view and manage the configuration.

Communication between these components is primarily internal to the z/OS system, using standard z/OS system services. DYNA-STEP does not use external APIs or protocols. The product integrates with the z/OS security infrastructure, leveraging RACF, ACF2, or Top Secret for access control.

The load module is loaded into the LPA (Link Pack Area) or the SVA (System Virtual Area) to ensure it is available to all TSO/ISPF sessions. The configuration dataset should be secured to prevent unauthorized modifications. Monitoring is achieved through logging, which records library allocations and any errors.

The configuration dataset is the central point for managing library allocations, and its structure and content are crucial for the proper functioning of DYNA-STEP. The product's design emphasizes efficiency and minimal impact on system performance.