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 Not under consideration
Categories Runtime
Created by Guest
Created on Aug 23, 2012

BAS target/related regions can not currently overlap

When deploying a dynamic resource with BAS, and specify both a Target Scope (for Remote installs) and a Related Scope (for local installs), CPSM does not allow any overlap, where the same CICS region is a member of the Target Scope and Related Scope. The customer's desired resolution is that when a region is in both the Target Scope and Related Scope, that the Related Scope would take priority, and CPSM would remove it from the Target Scope list of regions prior to doing the install.

While a customer may manually define additional groups so that no overlap exists, it diminishes the usefulness of BAS, in that for large shops it can take more effort to administer the CICS groups by BAS than it does by leaving the resources defined by CICS RDO in the CSD.

This restriction doesn't make sense from the user's perspective. For small shops with small numbers of regions, it isn't that big a deal to go and define more CICS groups to get around the restriction. But then, how many small shops are actually using BAS? It's the large shops that take advantage of it? In large CICSPlexes, having to define more CICS groups to code around this makes administration of resources more labor intensive, not less.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server