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.

Add a new idea Subscribe
Status Delivered
Workspace CICS Transaction Server for z/OS
Categories Runtime
Created by Guest
Created on Sep 5, 2013

RELATED IDEAS

variables in LIBRARY definitions

When using Application Bundles, with Program, Transactions, and LIBRARY(s) in CICS TS 5.1, I am going to run into a problem where the application is CICS release dependent, and needs a release # variable appended to the dsname, like we are allowed to do in JOURNAL models.

I understand most application code may not be CICS release dependent. However for ISVs that may want to deliver their customers App.Bundle manifests for their software products, a release dependent load library is very likely!

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 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
    |     Jan 25, 2021

    This RFE is 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 SYSIDor 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

  • Guest
    Reply
    |     Apr 7, 2020

    This is a candidate for a future release

  • Guest
    Reply
    |     Jul 19, 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
    |     Jan 6, 2014

    I have had a similar request for a variable to cover Application version.

  • Guest
    Reply
    |     Oct 7, 2013

    As we currently support CICS TS 3.1, 3.2, 4.1., 4.2, 5.1, and now the beta. we are talking about 6 release bundles. I realize currently the older releases don't even support bundle yet, but what happens in the future,
    do you really think it is a good practice for a vendor to ship 6 separate application bundles? and the only thing that is different is the LIBRARY DSName! Seems like a recipe for trouble, for example forgetting to go back and rebuild an older CICS application bundle for a new ISV release. This may be a little easier to deal with if the CICS explorer was able to build a new release bundle from and old bundle, and allow you to change the LIBRARY DSName before binding it

  • Guest
    Reply
    |     Oct 4, 2013

    We recognise the need for vendor products or any application that is using an API/SPI that is not guaranteed to be backwards compatible e.g. user exit to have release-specific code. However, the symbol substitution design you propose is problematic for a couple of reasons:
    1. It's difficult/impossible to tell ahead of time what will be installed into the runtime, a situation we are trying to improve with cloud
    2. It only covers PROGRAM resources

    An approach we have discussed is configuring an Application, Binding or Platform to install certain CICS bundles only into a particular release of CICS. That way you could have mybundle.510, mybundle.520, ... or whatever naming convention you like and a deployment rule would decide where it went. The downside is multiple CICS bundles, each defining a separate LIBRARY in your example, but the advantage is each CICS bundle only contains resources for a specific release and could contain things other than PROGRAM or LIBRARY e.g. URIMAP. This allows you to exploit new capability more easily.

    Thoughts?

  • Guest
    Reply
    |     Oct 4, 2013

    We recognise the need for vendor products or any application that is using an API/SPI that is not guaranteed to be backwards compatible e.g. user exit to have release-specific code. However, the symbol substitution design you propose is problematic for a couple of reasons:
    1. It's difficult/impossible to tell ahead of time what will be installed into the runtime, a situation we are trying to improve with cloud
    2. It only covers PROGRAM resources

    An approach we have discussed is configuring an Application, Binding or Platform to install certain CICS bundles only into a particular release of CICS. That way you could have mybundle.510, mybundle.520, ... or whatever naming convention you like and a deployment rule would decide where it went. The downside is multiple CICS bundles, each defining a separate LIBRARY in your example, but the advantage is each CICS bundle only contains resources for a specific release and could contain things other than PROGRAM or LIBRARY e.g. URIMAP. This allows you to exploit new capability more easily.

    Thoughts?

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.