SMP/E Interactions and Delivering ISPF Software Updates

SMP/E (System Modification Program/Extended) is IBM's tool for installing, updating, and maintaining system software on z/OS mainframes. ISPF software updates are delivered and installed through SMP/E, which manages the complex process of updating ISPF system libraries while maintaining system integrity. This tutorial covers SMP/E concepts, ISPF update delivery procedures, maintenance processes, and best practices for system administrators.

Understanding SMP/E is essential for system administrators responsible for maintaining ISPF. SMP/E ensures proper installation of ISPF updates, tracks what's installed, manages dependencies, and provides rollback capabilities. While SMP/E operations are typically performed by system administrators, understanding the process helps users understand how ISPF updates are delivered and what to expect during maintenance windows.

Understanding SMP/E

SMP/E is IBM's standard tool for software maintenance on z/OS. It provides structured processes for receiving, installing, and managing software updates while maintaining system stability and tracking changes.

What is SMP/E?

SMP/E (System Modification Program/Extended) is:

• Installation Tool: Manages installation of system software and updates
• Change Tracker: Tracks what software is installed and what changes have been made
• Dependency Manager: Handles prerequisites and dependencies between software components
• Conflict Resolver: Identifies and helps resolve conflicts between updates and customizations
• Rollback Mechanism: Provides capabilities to back out changes if needed

SMP/E is used for all IBM system software maintenance, including ISPF, z/OS components, and other system software. It provides a standardized, controlled way to update system software while minimizing risk.

SMP/E Zones

SMP/E organizes software into zones, which are logical groupings of datasets:

• DLIB (Distribution Library): Contains received PTF data before installation. PTFs are received into DLIB zones, where they're stored until ready for installation.
• TARGET: Contains active system software. When PTFs are applied, they're installed into TARGET zones, where the system actually uses them. ISPF runs from TARGET zones.
• DISTLIB (Distribution Library): Contains distribution libraries used during installation. DISTLIB zones provide source material for installation processes.

Zone structure allows SMP/E to manage the installation process safely. Updates are received into DLIB, applied to TARGET (where they become active), and can be accepted (made permanent) or backed out if needed.

PTFs and APARs

Software updates are delivered as:

• PTF (Program Temporary Fix): Fixes for specific problems or enhancements. PTFs are the primary delivery mechanism for ISPF updates.
• APAR (Authorized Program Analysis Report): Problem reports that may result in PTFs. APARs document problems and their resolutions.
• PE (Program Enhancement): New features or significant enhancements delivered through SMP/E.
• HOLDDATA: Information about known problems, restrictions, or special handling requirements.

ISPF updates are typically delivered as PTFs, which fix specific issues or provide enhancements. Multiple PTFs may be bundled together in a maintenance package for easier installation.

SMP/E Process for ISPF Updates

The SMP/E process for installing ISPF updates follows a structured sequence: receive, apply, accept. Each step serves a specific purpose and provides opportunities for verification.

Step 1: RECEIVE

The RECEIVE step processes PTF data into SMP/E format:

• Input: PTF data from tape, electronic distribution, or other sources
• Processing: SMP/E reads and processes PTF data, extracting installation information
• Output: PTF data stored in DLIB zones, ready for installation
• Verification: SMP/E validates PTF format and basic integrity

RECEIVE doesn't install anything; it prepares PTF data for installation. This allows you to receive updates in advance and install them during maintenance windows.

Example RECEIVE command:

1
2
SET BDY(GLOBAL) .
RECEIVE SYSMODS(ISPFPTF01 ISPFPTF02) .

This receives specified PTFs into the DLIB zone, making them available for installation.

Step 2: APPLY

The APPLY step installs PTFs into TARGET zones:

• Input: PTFs from DLIB zones
• Processing: SMP/E installs PTF changes into TARGET libraries
• Output: Updated TARGET libraries with PTF changes installed
• Verification: SMP/E checks prerequisites, resolves conflicts, and validates installation

APPLY makes changes active in TARGET zones. ISPF will use the updated libraries after APPLY completes successfully. Changes can still be backed out until ACCEPT is performed.

Example APPLY command:

1
2
3
SET BDY(GLOBAL) .
APPLY CHECK SYSMODS(ISPFPTF01) .
APPLY SYSMODS(ISPFPTF01) .

APPLY CHECK validates installation without making changes. APPLY without CHECK performs the actual installation. Using CHECK first is recommended to identify problems before making changes.

Step 3: ACCEPT

The ACCEPT step makes PTF changes permanent:

• Input: Applied PTFs in TARGET zones
• Processing: SMP/E marks PTFs as accepted, making them permanent
• Output: PTFs marked as accepted, changes are permanent
• Implication: Accepted PTFs cannot be easily backed out

ACCEPT should be performed after verifying that applied PTFs work correctly. Once accepted, backing out changes requires more complex procedures. Typically, ACCEPT is performed after a verification period.

Example ACCEPT command:

1
2
SET BDY(GLOBAL) .
ACCEPT SYSMODS(ISPFPTF01) .

This accepts the specified PTF, making its changes permanent.

ISPF-Specific Considerations

ISPF updates have specific considerations that differ from other system software. Understanding these helps ensure successful ISPF maintenance.

ISPF Library Updates

ISPF updates typically modify ISPF system libraries:

• Panel Libraries (ISR@PENU): Updated panels for new features or fixes
• Message Libraries (ISR@MSGS): Updated messages, error text, or help information
• Skeleton Libraries (ISR@SKEL): Updated skeleton templates
• Executable Modules: Updated ISPF program modules
• Table Libraries: Updated table definitions

SMP/E manages updating these libraries while ISPF may be in use. Understanding which libraries are affected helps plan maintenance and verify updates.

ISPF Version Compatibility

ISPF updates must be compatible with:

• z/OS Version: ISPF version must be compatible with z/OS level
• Prerequisite PTFs: Some ISPF PTFs require other PTFs to be installed first
• Customizations: User customizations (USERMODs) must be compatible with updates
• Dependencies: ISPF may depend on other system components that also need updates

SMP/E checks prerequisites and dependencies, but understanding compatibility helps plan maintenance and avoid problems.

Customization Management

ISPF customizations require special attention during updates:

• USERMOD Tracking: Document all customizations to system libraries
• Conflict Resolution: SMP/E identifies conflicts between PTFs and USERMODs
• Reapplication: Customizations may need reapplication after system updates
• User Libraries: Consider using user libraries instead of modifying system libraries

Best practice is to use user libraries for customizations when possible, avoiding modification of system libraries that SMP/E manages.

Maintenance Procedures

Proper maintenance procedures ensure ISPF updates are installed correctly and safely. Following structured procedures minimizes risk and ensures successful updates.

Pre-Installation Planning

Before installing ISPF updates:

• Review PTF Information: Understand what the PTF fixes or enhances
• Check Prerequisites: Verify all prerequisite PTFs are installed
• Review HOLDDATA: Check for restrictions or special handling requirements
• Plan Maintenance Window: Schedule installation during appropriate maintenance window
• Backup System Libraries: Create backups of ISPF libraries before updates
• Document Current State: Document current ISPF configuration and customizations

Proper planning prevents problems and ensures smooth installation.

Installation Process

During installation:

• Receive PTFs: Use SMP/E RECEIVE to process PTF data
• Verify Receipt: Check SMP/E reports for successful receipt
• Apply Check: Use APPLY CHECK to validate installation without making changes
• Review Check Results: Verify no errors or conflicts in check results
• Apply PTFs: Use APPLY to install PTFs into TARGET zones
• Verify Installation: Check SMP/E reports and verify ISPF libraries are updated

Following this process ensures updates are installed correctly and provides opportunities to catch problems early.

Post-Installation Verification

After installation:

• Test ISPF Functionality: Test key ISPF features to ensure they work correctly
• Verify Library Updates: Check that ISPF libraries contain updated members
• Review SMP/E Reports: Check for warnings or errors in SMP/E reports
• Monitor for Issues: Monitor system for problems related to ISPF updates
• Document Installation: Document what was installed and when

Verification ensures updates work correctly and helps identify any issues that need attention.

Acceptance Process

After verification period:

• Wait for Verification Period: Allow time to verify updates work correctly in production
• Review Any Issues: Address any problems discovered during verification
• Accept PTFs: Use SMP/E ACCEPT to make updates permanent
• Update Documentation: Update system documentation with accepted PTFs

Acceptance makes updates permanent. Only accept after thorough verification.

Troubleshooting SMP/E Issues

Understanding common SMP/E issues and how to resolve them helps ensure successful ISPF maintenance.

Common Issues

Common SMP/E issues include:

• Missing Prerequisites: Required PTFs not installed before applying dependent PTFs
• Conflicts: PTFs conflict with existing USERMODs or other PTFs
• Space Problems: Insufficient space in target libraries for updates
• Access Problems: Insufficient authority to update target libraries
• Format Errors: PTF data format problems or corruption

Understanding these issues helps diagnose and resolve problems quickly.

Resolution Strategies

Resolution strategies include:

• Install Prerequisites: Install missing prerequisite PTFs before applying dependent PTFs
• Resolve Conflicts: Work with IBM support or remove conflicting USERMODs
• Free Space: Free space in target libraries or increase allocation
• Verify Authority: Ensure proper authority to update target libraries
• Re-receive PTFs: Re-receive PTF data if format problems are suspected

SMP/E provides detailed error messages and reports that help identify specific problems and resolution steps.

Best Practices

Following best practices ensures successful ISPF maintenance and minimizes risk:

• Test in Non-Production First: Test ISPF updates in test or development environments before production
• Use APPLY CHECK: Always use APPLY CHECK before APPLY to identify problems early
• Maintain Backups: Keep backups of ISPF libraries before updates
• Document Everything: Document all maintenance activities, issues, and resolutions
• Plan Maintenance Windows: Schedule updates during appropriate maintenance windows
• Verify After Installation: Always verify ISPF functionality after updates
• Wait Before ACCEPT: Allow verification period before accepting PTFs
• Use User Libraries: Prefer user libraries over modifying system libraries for customizations
• Stay Current: Keep ISPF reasonably current with available updates
• Review HOLDDATA: Always review HOLDDATA for restrictions or special requirements

Explain Like I'm 5: SMP/E and ISPF Updates

Think of SMP/E like a careful librarian who updates books in a library:

• SMP/E is like a librarian who carefully updates books in the library. When new versions of books (ISPF updates) arrive, the librarian doesn't just replace them immediately - they follow a careful process!
• RECEIVE is like the librarian receiving new books and putting them in a special receiving area (DLIB zone). The books aren't on the shelves yet, but they're ready to be put out!
• APPLY is like the librarian putting the new books on the shelves (TARGET zone) where people can use them. But the old books are kept nearby just in case something goes wrong and we need to put them back!
• ACCEPT is like the librarian deciding the new books are good and making the change permanent. After ACCEPT, the old books are removed, and the new books stay on the shelves!
• PTFs are like updated pages or chapters that fix problems or add new features to the books. Each PTF is a specific update that makes the books better!
• Zones are like different areas of the library - the receiving area (DLIB), the shelves people use (TARGET), and storage areas (DISTLIB). Each area has a specific purpose!

So SMP/E is like a careful librarian who makes sure ISPF updates are installed safely, with backups and testing, so everything keeps working correctly!

Practice Exercises

These exercises are for system administrators with SMP/E access:

Exercise 1: Review SMP/E Status

Objective: Understand current SMP/E status for ISPF.

Steps:

• Use SMP/E LIST commands to review installed ISPF PTFs
• Identify ISPF-related zones and their contents
• Review SMP/E reports for ISPF maintenance history
• Document current ISPF PTF level

Exercise 2: Simulate PTF Receipt

Objective: Practice receiving PTF data (in test environment).

Steps:

• Obtain test PTF data (if available in your environment)
• Use SMP/E RECEIVE to process PTF data
• Review SMP/E reports for successful receipt
• Verify PTF data is in DLIB zones

Exercise 3: Review ISPF Library Contents

Objective: Understand ISPF library structure after updates.

Steps:

• Use ISPF Library Utility to browse ISPF system libraries
• Identify library members and their purposes
• Compare library contents with SMP/E installation records
• Document library structure for reference

Related Concepts