IDR - Install Data Record

Enhanced Definition

An Install Data Record (IDR) is a component of a Program Temporary Fix (PTF) or Authorized Program Analysis Report (APAR) fix that contains specific instructions for the System Modification Program/Extended (SMP/E). It directs SMP/E on how to apply the associated software modification to the z/OS system libraries, ensuring proper integration and functionality of the fix.

Key Characteristics

- SMP/E Instructions: Contains SMP/E control statements (e.g., COPY, DELETE, LINKEDIT, MACRO) that dictate the actions SMP/E must perform.
- Fix Integration: Essential for integrating PTFs and APARs into the z/OS software environment, modifying target and distribution libraries as required.
- Sequential Data: Typically provided as a sequential dataset or a member within a partitioned dataset (PDS or PDSE) that SMP/E reads.
- SYSMOD Component: It is an integral part of a SYSMOD (System Modification), which is the package containing the actual code changes and the IDR instructions.
- Automated Processing: Designed for automated processing by SMP/E during the APPLY and ACCEPT phases of software maintenance.
- Version Control: Ensures that specific versions of modules or macros are correctly updated or replaced according to the fix's requirements.

Use Cases

- Applying PTFs: The primary use case, where an IDR guides SMP/E to install routine maintenance and bug fixes for IBM or vendor products.
- Implementing APAR Fixes: Used to apply emergency or critical fixes (APARs) to resolve software defects that may impact system stability or data integrity.
- Module Replacement/Update: Directs SMP/E to replace existing load modules, source members, or macros with updated versions provided in the fix.
- Library Link-Editing: Contains instructions for LINKEDITing modules into target libraries, ensuring correct entry points and external references.
- System Customization Updates: While not directly for user customization, IDRs can update system components that are critical for supporting various system customizations.

Related Concepts

The IDR is intrinsically linked to SMP/E, serving as the instruction set that SMP/E interprets and executes to perform software maintenance. It is a fundamental component of a PTF or APAR SYSMOD, providing the necessary metadata and actions for the actual code changes to be correctly applied to the z/OS target and distribution libraries. Without an IDR, SMP/E would not know how to integrate the new or modified software components into the system.

Best Practices:

Review SMP/E Output: Always thoroughly review the SMP/E job output, particularly messages related to IDR processing, to ensure successful application and identify any warnings or errors.
Test in Staging Environments: Apply PTFs and APARs containing IDRs in a non-production or test CSI (Consolidated Software Inventory) and target environment first to validate changes before production deployment.
Understand IDR Actions: For critical system components, understand the specific actions (COPY, DELETE, LINKEDIT) the IDR is instructing SMP/E to perform to anticipate potential impacts.
Maintain CSI Integrity: Ensure the SMP/E CSI datasets are regularly backed up and maintained, as IDR processing relies heavily on the CSI for tracking software levels.
Backup Target Libraries: Before applying any SYSMODs with IDRs, ensure that the affected target and distribution libraries are backed up to facilitate recovery in case of an issue.