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 Not under consideration
Workspace CICS Transaction Server for z/OS
Categories Runtime
Created by Guest
Created on Jun 6, 2012

RELATED IDEAS

CICS - ICSF callable Interface to use transaction owner's userid instead of CICS region userid

We need urgently an interface to propagate the transaction user as the checked userid in CSFSERV and CSFKEYS classes .
In our environment RACF access control is used for RACF classes CSFSERV and CSFKEYS for permitting technical userids to associated KEYLABELS and ICSF callable services.
The associated transaction that makes the ICSF-Calls runs under a specific technical user and we need the authorisation of this technical user against ICSF, the security context must be of the signed on user invoking the transaction issuing the ICSF call.
At the moment CICS uses the CICS region userid.

Idea priority Urgent
  • Guest
    Reply
    |     May 6, 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
    |     Aug 29, 2015

    Juergen,
    apologies for not back to you earlier.
    We have been working with ICSF and RACF to trying to get a solution in this release, but unfortunately this has proved more complex than first thought.
    We are still working with ICSF and RACF to try and identify a solution. This is something we would still like to do, but won't make the next release.

  • Guest
    Reply
    |     Aug 7, 2015

    Hello,
    this requirement is meantime opened for a long time, but nothing happens. Do you have an idea, when you are able to implement this RFE? It is still important for us, because we don't have a praciticable workaround.
    Best regards,
    Juergen

  • Guest
    Reply
    |     Jun 11, 2012

    Hi Colin, that's the problem. We are able to restrict a transaction to technical userids but we cannot restrict the ICSF-function-call itself. Which means, every transaction (program) running in that cics-region can use ICSF and the associated KEYLABELS, because cics uses the region userid for authorisation, not the transaction userid.
    Kind regards, Juergen

  • Guest
    Reply
    |     Jun 8, 2012

    Juergen, thank you for the RFE. You say that you need to restrict the function to specific "technical userids" associated with the transaction. Is there any reason why you are unable to just restrict who can run the transaction which invokes the ICSF calls.

    Colin Penfold

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.