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).
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.
The current implementation for processing a VARY-OFFLINE-command is to request the "SYSIEFSD Q4" enqueue exclusively and cancel this request after 5 seconds if it could not be obtained.
If due to some error or during allocation recovery some shared holder of this enqueue got stuck, each and every allocation has to wait for 5 seconds behind this exclusive request.
While this is a valid design when setting a device offline which is currently online (with "alerting" messages after 5 seconds!) this design can severely impact performance without any alert if the command was issued for an offline devices because the command is then processed after 5 seconds.This performance impact is especially severe if hundreds of such commands had been issued.
Suggested improvement:
A design with much less impact would be to check the device status first and if it is already offline, you can do your "blocking of other requestors" by requesting Q4 exclusively while checking the device status with a very short timer. If you find the device is online, then you could go ahead as currently implemented. This would eliminate the extreme delays we had been suffering from.
Idea priority | High |
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 - z Systems Software
Product - z/OS
Component - BCP_Consoles
Operating system - IBM z/OS
Source - None
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - z Systems Software
Product - z/OS
Component - BCP_General
Operating system - IBM z/OS
Source - None
Creating a new RFE based on Community RFE #88184 in product z/OS.