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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
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
Securing access to this new query interface via SAF would be fine. Might that alleviate some of the security concerns? The overall objective of the request is to afford CPSM API users the ability to learn about the environment they're running in while requiring little or no "advance knowledge" of it.
This requirement has been re-evaluated. Looking at current plans, it is not likely that this would be implemented in the next two CICS TS releases, so correspondingly this requirement is being rejected. You have an opportunity to resubmit in eighteen months time if you wish it to be considered then. There are a number of technical and security problems here that would need to be resolved before we could complete a solution for this and still wouldn't provide the complete capability.
Have you tried doing the CONNECT, without specifying a CONTEXT or SCOPE? You should be able to request CMAS related views without specifying the request CONTEXT and SCOPE at all. This has the added benefit that you are not bypassing security.
The Infocenter states the following about the CONNECT command:
"If you do not specify the CONTEXT option, the default context for the thread is the CMAS to which the thread is connected."
Have a look at the following resource tables:
CPLXCMAS - CMAS in CICSplex definitions
CMASPLEX - CICSplexes managed by CMAS
CMASLIST - CMASs known to local CMAS
CMAS - CMAS detail (this one contains the CPSMVER field which has the CICS TS release).
You should be able to get the CMASLIST records back without specifying a context. This will give you a list of all defined CMAS. From there do EXEC CPSM GET OBJECT(CMAS) CONTEXT() for each CMASLIST record in the previous request. This should give you everything you need.