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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
We would like to suggest an enhancement for the way ACFREP (AOFRSRPY) replies to WTORs.
Currently, the PIPE named ISSUECMD executes the reply command via CORRCMD and then locates the message IEE600I and save to a stem named resp. This works gracefully, however, the last stage is "LOGTO NETLOG", which causes the message IEE600I to be registered in NetView's log but cannot be processed by any other AT entry.
This way, users who have alerts based on WTORs (in addition to them) are not able to suppress these alerts when the WTORs are answered, unless the DOM action and Actiondl functions are used. Having the message IEE600I would simplify this process.
The suggestion for analysis and possible implementation is to use the stage EXPOSE, instead of LOGTO NETLOG, which will cause the message to be registered in the NetView's log and also be exposed for processing by further AT entries. Since the ACFREP program internally calls AOFRSA0E in order to process the reply response, and is also defined to SA z/OS AT INGMSGSA based on message IEE600I, this internal call could be removed in order to avoid duplicities in execution of AOFRSA0E.
We understand this code is available for a long time with no problems, and we also understand a deep impact analysis must be performed, but we would like to suggest this as an enhancement to SA z/OS (possibly via APAR for the available and supported releases, or for the next releases that have not yet been GA).
Below is an example, from Netlog, of how processing of message IEE600I works with LOGTO NETLOG or EXPOSE:
LOGTO NETLOG:
PIPE LITERAL /IEE600I REPLY TO 001 IS/ | LOGTO NETLOG
IEE600I REPLY TO 001 IS
EXPOSE:
PIPE LITERAL /IEE600I REPLY TO 001 IS/ | EXPOSE
CNM493I INGMSGSA : 03260039 : AOFRSA0E
IEE600I REPLY TO 001 IS
Idea priority | Medium |
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - zSeries Software
Product - Tivoli System Automation for z/OS (SA z/OS)
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Automation
Product - Tivoli System Automation for z/OS (SA z/OS)
Hello Ayrton,
thank you for this RFE. We discussed it today in our requirements meeting.
It is will be a candidate for a future release.
Best Regards,
Raimund Thielker
SA z/OS Development