IPRT - Install Product Runtime

Enhanced Definition

IPRT, or Install Product Runtime, refers to the phase within the IBM System Modification Program/Extended (SMP/E) process where a software product's executable code, load modules, and runtime libraries are installed into the target z/OS system's operational datasets. This process makes the product available for execution and use by applications and users.

Key Characteristics

- SMP/E Driven: IPRT is fundamentally an SMP/E APPLY process, which moves modules and data from SMP/E's Global, Target, and Distribution Zones into the actual runtime libraries.
- Target Libraries: It populates the TARGET libraries (e.g., SYS1.LINKLIB, product.LOADLIB, product.SASC.LOAD) that are directly used by the z/OS operating system and applications at runtime.
- Runtime Environment Creation: This step effectively builds or updates the operational environment for the software product, making its functions accessible.
- Distinct from Distribution: IPRT applies changes from the DLIBs (Distribution Libraries), which hold the master copy of the product, to the TLIBs (Target Libraries), which are the actual runtime libraries.
- JCL Execution: The process typically involves submitting JCL jobs generated or provided by SMP/E, which execute the GIMAPPLY utility.
- Prerequisite for Customization: Once the runtime is installed, product-specific customization (e.g., configuration, parameter libraries, security setup) can begin.

Use Cases

- New Product Installation: Installing a new IBM or vendor software product onto a z/OS system for the first time.
- Applying Maintenance: Incorporating Program Temporary Fixes (PTFs), Authorized Program Analysis Reports (APARs), or Recommended Service Upgrades (RSUs) to an existing product to fix defects or add minor enhancements.
- Version Upgrades: Upgrading a product to a new major or minor version, which often involves significant changes to the runtime environment.
- System Recovery: Re-establishing a product's runtime environment after a system failure or during a disaster recovery scenario.
- Cloning Environments: Creating a new test or development environment by applying a product's maintenance levels to a fresh set of target libraries.

Related Concepts

IPRT is a critical step in the overall SMP/E lifecycle, following the RECEIVE (acquiring maintenance) and APPLY CHECK (validating maintenance) phases. It directly interacts with Target Libraries and Distribution Libraries, moving code from the latter to the former. The successful completion of IPRT is a prerequisite for product customization and system IPL (Initial Program Load) if the product is integral to the operating system or its subsystems. It is managed by System Programmers who use JCL to invoke SMP/E utilities.

Best Practices:

Perform APPLY CHECK First: Always run APPLY CHECK before APPLY to identify potential conflicts, missing requisites, or errors without modifying the target libraries.
Backup Target Libraries: Before performing an IPRT, ensure that all relevant TARGET libraries are backed up to allow for easy rollback in case of issues.
Review SMP/E Output: Meticulously review the SMP/E job output for any return codes greater than 0, warning messages, or error messages, as these can indicate partial success or potential problems.
Schedule During Low Activity: For critical products or system-wide changes, schedule IPRT during a planned maintenance window or period of low system activity to minimize impact.
Follow Product Documentation: Adhere strictly to the product's installation and maintenance guide, as specific products may have unique requirements or post-IPRT steps.