Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 Future consideration
Created by Guest
Created on Sep 2, 2016

Parmgen enhancement for OMEGAMON XE z/OS 5.3, XE CICS 5.3, PE for DB2 5.3, MQ 7.3 etc.

RFE for Parmgen OMEGAMON XE z/OS 5.3, XE CICS 5.3, PE for DB2 5.3, MQ 7.3 etc.:

We have several user modified members in different libs which we always have to take care not to overwrite them by parmgen.
Most customized members are in RKANPARU or RKD2PAR, but we also have members in RKANCMDU, RKANMACU, UKANWENU.

To avoid overwrite, runtime Libs should stay unchanged and all modified members shoud be stored in an own Userlib (some UKAN* libs already exist This logic is not consistently implemented for all products.
To satisfy our company standards we urgently need a special HLQ for all kind of user customizable libs, p.e. UKANPARU, UKD2PAR, UKANCMDU, UKANMACU, UKANWENU
These libs we need in shared version for definitions which are same for all lpars and for each lpar.
So we need a user specific lib for all kinds of libs which may contain user modifications (parms, panels, commands etc.)

our request:
- freely selectable Parmgen HLQ (p.e. RTE_UHILEV) -> very important!
- freely selectable Parmgen volume (p.e RTE_UHILEV_VOLUME)
- for shared libs
- for lpar specific libs
- generated into STC and JOB jcl by parmgen -> very important!

Idea priority High
  • Guest
    Reply
    |
    Jan 10, 2019

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - Tivoli Management Services on z/OS
    Component - Product functionality
    Source - Other

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - OMEGAMON for z/OS
    Component - Installation
    Source -

  • Guest
    Reply
    |
    Dec 7, 2016

    Yes, you understood correctly:
    RTE_HILEV_UKAN and
    RTE_X_HILEV_SHARING_UKAN
    or perhaps (may be that's closer to your curent WCONFIG logic):
    RTE_U_HILEV
    RTE_U_HILEV_SHARING

    As you explained, these libs will contain user modified runtime modules which currently are stored in RKANPARU, RKANCMDU, RKANMODU, RKANSAMU, RKANSQLU, RKD2PAR
    And the most important is that these UKAN*U libs are not changed by parmgen.

    Regards
    Andrea Strixner

  • Guest
    Reply
    |
    Dec 5, 2016

    Thank you for the submission - we are currently evaluating it but need to some more information to fully understand the scenario.
    For example, are you wanting PARMGEN to support a new RTE_HILEV_UKAN parm. that then allocates an empty set of user libraries, and let you as a client populate it with just runtime members that are purely your copies?