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.
having time spent suspended waiting for resource 'RZCBNOTI' or other sub pools will help analyze prolong response time situations. We have a case where se se only have a suspend time but no other timing in the SMF110 accounting record which make it very hard to identify the problem.
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 wait in RZCBNOTI implies request streams, RZ is used for a context switch. A services request arrives in CICS, a task is started to process it; that task figures out the target transaction/userid that's needed for the application processing work, and a new task is triggered with those credentials (and potentially routed to another region) using RZ; while the new task is running the old one will be blocked with a waiting state of RZCBNOTI. The flow of control for the external web request isn't blocked however, it'll be chugging along nicely in another task. The important work will be happening in the second task, the first is merely waiting for it to complete. The RZ wait has existed since TS V2.1 (it was first used for EJB) but is now used for Web Services.
The RZCBNOTI wait shouldn't be misconstrued to be of direct importance - that first task will wait in the RZCBNOTI suspend for the entire elapsed time in which the application is running (and potentially rather longer than that if there are remote transactions to coordinate).