Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Functionality already exists
Workspace z/OS
Categories Core Infrastructure
Created by Guest
Created on Sep 12, 2025

Adding a capability to Reflect RSU Level or Maintenance(APAR Level)

Hello Team, 

Greetings ! As z/OS SysProgs it is often difficult to keep track of maintenance level at which z/OS LPARs are. I was going over IBM Z community discussion and observed one locally developed solution to address this issue. It was done by updating CVTVERID field to update maintenance level and output can be displayed in SDSF SYMBOLS panel or IEA008I message during IPL. 

Can this be addressed as APAR to provide the solution to all customers. 

Idea priority Medium
  • Guest
    Sep 30, 2025
    We understand the request for a simple ?maintenance level? value associated with each physical copy (clone) of z/OS. However, IBM has actively avoided general ?maintenance level? labels because there is no such thing as one ?level? that accurately describes the maintenance for an entire z/OS system. For example, consider PTFs assigned a particular RSU are installed, like RSU2506 for example. That RSU level is a collection of many, many PTFs. If a customer attempts to install all RSU2506 PTFs, many will be installed, but some inevitably will not, for various reasons, unresolved PEs being the most common culprit. So, if one, or many, of the PTFs assigned RSU2506 are not installed, should that maintenance level be called ?RSU2506?? The point is, it is very subjective how to label a system?s maintenance level, which is why IBM assigns labels to PTFs, but not to whole z/OS systems. Each customer, based on their methods and procedures for installing PTFs must decide on maintenance level labels that are meaningful for them. Customer-specific USERMODs to update CVTVERID are plentiful upon an online search such that a customer can tailor what "maintenance level" means to them.
    Additionally, you can already query the RSU SOURCEID today, across any software installed on the system, if there was a need to know the highest RSU identifier. More information on this command can be found here: https://www.ibm.com/docs/en/zos/3.2.0?topic=commands-report-sourceid-command
  • Guest
    Sep 26, 2025

    Hi
    You will see the value in the SDSF SYS panel in CVTVERID column. There are two ways to achieve this. Either the 'proper' way and update the value with a USERMOD or directly with the AMASPZAP (depending on access levels).

    Using AMASPZAP

    //PUTCLEAR  EXEC PGM=AMASPZAP                        
    //SYSLIB    DD   DSN=SYS1.NUCLEUS,DISP=SHR,UNIT=3390,VOL=SER=<your-SYSRES>
    //SYSPRINT  DD   SYSOUT=*                                            
    //SYSIN     DD   *                                                   
      NAME IEANUC01 IEAVCVT                                              
      REP  000028 <your-RSU-level>                                              
    //*

     

    Using USERMOD

    //UMOD      EXEC PGM=GIMSMP,COND=(04,LT)
    //SMPCSI    DD DISP=SHR,DSN=<your-smpe-csi>
    //SMPHOLD   DD DUMMY                    
    //SMPCNTL   DD *                        
      SET BDY(GLOBAL) .                     
       RECEIVE S(UMOD001) .                 
      SET BDY(<your-target-zone>).                     
       APPLY S(UMOD001) .                   
       LIST SYSMOD(UMOD001) .               
    /*                                      
    //*                                     
    //SMPPTFIN DD * DATA,DLM=$$             
    ++ USERMOD (UMOD001) .                  
    ++ VER (Z038) FMID(&FMID.).             
    ++ ZAP(IEAVCVT) DISTLIB(AOSC5) .        
     NAME IEANUC01 IEAVCVT                  
     VER 28 4040404040404040 CHECK OFFSETS  
     REP 28 <your-RSU-level> INSERT RSU LEVEL
     IDRDATA UMOD001                        
    //*

     

    So it does not need an APAR as you have to 'dynamically' fill field.

    I hope that helps you getting that setup in your environment.