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 Oct 29, 2014

CICS configuration elements that need USS paths should allow use of symbols

All CICS configuration elements, whether housed in CSD, CPSM, or USS files, that require or permit the specification of a USS path value should permit the use of symbols in that value. For example, on the CONFIGFILE parameter of a PIPELINE definition:
&USSHOME/&APPLID/<remainder of path>
or
&USSHOME/Config_&APPLID..VariousStuff/<remainder of path>
Should be permitted and have the current values of the symbols substituted when the resource is installed into the region.
Allowable symbols should include:
* Any system symbol ("built in" or defined via IEASYMxx)
* Any JCL symbol (// SET <name>=<value>)
* Various configuration elements from the SIT, such as USSHOME, APPLID, SYSIDNT, etc. including applicable CICS version and release (i.e. TS510, TS520, etc.)

Idea priority High
  • Guest
    Reply
    |
    Jun 17, 2022
    Support for this is also provided in CICS TS 6.1 which is generally available from 17th June 2022.

    For more information see https://www.ibm.com/docs/en/cics-ts/6.1?topic=whats-new
  • Guest
    Reply
    |
    Apr 5, 2022
    Support for this is also partially provided in CICS TS 6.1 which is announced today April 5th and will GA June 17th 2022.

    See Announcement letter https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS222-092/index.html&request_locale=en
  • Guest
    Reply
    |
    Feb 22, 2021

    This RFE is partially satisfied by the resource overrides feature provided by PH30590 on CICS TS 5.6

    This feature enables a system programmer to tailor the resources for a specific CICS environment, and provides the following advantages:

    • You can take a set of CICS definitions from development through to a production environment without change. Any resource attributes can be overridden to support each environment as required.
    • In addition, you can use system-specific symbols such as the SYSID or APPLID to override attribute values dynamically when a resource is installed.
    • You can apply standards by ensuring that certain attribute values are always turned on or off, or set to a specific value.

    For more information see https://www.ibm.com/support/knowledgecenter/SSGMCP_5.6.0/configuring/resources/resource-definition-overrides.html

    Not available via PH30590 on 5.6 is the ability to support system symbols for USSCONFIG, SYSPLEX, JOBNAME etc, which is an extension being considered in a future release.

  • Guest
    Reply
    |
    Jan 19, 2021

    This RFE is being reopened. It is a candidate for a future release

  • Guest
    Reply
    |
    Dec 14, 2016

    Whilst this requirement is valid, based on our current plans and priorities, it is not likely that this could be implemented in the next 12 months, or in the next CICS TS release. Correspondingly this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • 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

  • Guest
    Reply
    |
    Sep 11, 2015

    This is a candidate for a future release