IBM Z Hardware and Operating Systems Ideas Portal
This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.
I understand the reasoning behind a decision to stop using exits. Not only does someone need to write the exit but then it has to be maintained. That said, the lack of the ability to write to the joblog to inform why the job was failed is a BIG deficiency in the implementation.
I would vote for adding the capability to the JES policy implementation.
We are currently migrating from JES3 and we wrote an AUTHJOB policy that checks Resource rules for account code and execution class utilization. The checks work fine using the AuthorityCheck function but the SendMessage action is not messaging the application end user in the JESMSGLG. Big miss and show stopper :-((
I think this should be a HIGH priority. If a job is canceled by a policy, I can´t expect the user to scroll through the SYSLOG looking for the reason. A user might not even have access to the SYSLOG. I should have the option that the message be also (or exclusively) sent to the JOB LOG.