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 Delivered
Categories Runtime
Created by Guest
Created on Sep 20, 2018

Ability to specify GROUPLIST name as part of the GROUP Migration process

As part of the process used to migrate resources from one configuration to another we need the ability to specify the GROUPLIST and add the resources to the GROUPLIST. The GROUPLIST can be specified manually as part of creating the change package or derived from the CICS configuration name or the CSD file name. The third qualifier in the dataset name matches the CICS configuration name.
The GROUPLIST methodology that is employed at our site is as follows
GRPLIST=(IBMLIST,SZsysid,applid,sysidLIST)
Where
• IBMLIST contains all of the IBM groups this grouplist will not be managed by CCM
• SZsysid (sysid is the sysid of the region) this grouplist will not be managed by CCM
o contains third party software groups
o CICS connections
• applid contains the application definitions for PPT, PCT, FCT, and DCT, this grouplist will be managed by CCM.
o CICS region applid the format is stanCICS where
 s is the application state identifier
 t is the type of region
 a is the primary application that resides in the region
 n is a sequence number for cloned regions starting with 0. Cloned regions use the same grouplist and share the same CSD file. Example we have 6 cloned regions called PR20CICS to PR25CICS and they all share the same CSD file and all of the regions have PR20CICS in the GRPLST sitparm
• sysidLIST contains any definitions that are undue to the region such as the CICS log and Shunt will not be managed by CCM

Idea priority High
  • Guest
    Reply
    |
    May 5, 2020

    Please note that this was delivered in Feb 2019 via PTF UI61271 as APAR PH04511.
    The GROUP creation exit point (CCVXRGP) was provided, thereby allowing newly created Groups to be processed by the exit.
    Samples were provided to added the new Group to the appropriate CSD List in the Target Configurations.

  • Guest
    Reply
    |
    Nov 22, 2018

    Yes, this is something we would like to do. The status of the RFE is being moved into Planned for a future release. Please note the following.


    IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.