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.
We have assessed this requirement. We have no current plans for this to be implemented and so 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.
A customised version of the shutdown assist program DFHCESD could be utilised. A modified version of DFHCESD could be used that ignores the type of shutdown requested (perhaps based on some criteria).
Either of these options would be yet another site specific customization, which management and sysprogs are trying to get away from.
Even if I do get approval to implement either of the below options, how do I tie in either one into the shutdown menu that developers see in IDZ and CICS Explorer when right mouse clicking on a region? I don't think plugins permit replacing menu options and having two "shutdown" options will likely confuse developers. Furthermore, we don't have any CICS sysprogs that have any experience with creating or supporting an Eclipse plugin--and only one with substantive Java experience.
The function of allowing developers to do a shutdown, but not an immediate shutdown can be provided in a couple of ways on existing systems.
1) If you use SIT PARM CMDSEC=ASIS (which is the default).
Create a transaction which issues and EXEC CICS PERFORM SHUTDOWN.
Define the transaction with CMDSEC(NO).
Authorise this transaction to developers who you are happy with being able to shutdown their regions.
The commands will be audited with a DFHAP1900 message to say which user issued the request.
2) This is more complex and only necessary if you require SIT PARM CMDSEC=ALWAYS
Create a transaction A which issues a start to with USERID(U) to transaction B
Transaction B issues the EXEC CICS PERFORM SHUTDOWN
Developers have authority to run transaction A and DFHSTART surrogate authority to START a transaction with userid U.
Only userid U has access to run transaction B.
Userid U has command security to issue PEFORM SHUTDOWN.
Userid U should have no access to any other transactions.
Because the DFHAP1900 audit message will have userid U, transaction A should also issue it own audit message so that it is clear who issued the request.
Please let us know if this solves the problem.