This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 commonly have access path rebuilds occurring post the vary on of an IASP. We would like the capability to monitor the progress of the access path rebuilds from a batch job rather than just the screen.
We run a superannuation system on our IBMi. There are large batch processing windows and in order to keep the system available 24x7 for customers enquiries we use IASP's and flash copy technology to a HA (high availability) system for the duration of batch processing. This means that customers can continue to enquire on their superannuation balances 24x7.
Unfortunately, the flash copy we are forced to take is "dirty" because the application on the source production system cannot be shut down prior to the application being started on the target HA system. We do shut down as much as possible prior to the flash but there are services that have to stay available 24x7. This "dirty" flash results in access path rebuilds ranging anywhere from 10 minutes to 30 minutes depending on the level of activity on the source production system.
The switch to the HA system using the flash from the production system is controlled automatically by batch jobs on both the production and HA systems.
At the present time, the batch jobs have no way to detect when the access path rebuilds complete. This has become a problem when an access path rebuild conflicts with the application running as the application becomes unresponsive, thus causing customer complaints.
We have built 15 minute delays into the batch jobs and hope that these delays are sufficient but have no way to detect when an access path rebuild is complete and therefore still get issues on occasion.
Note:
We have done the following to minimise the impact of access path rebuilds;
1. Shutting down as many services as possible on the source system. This minimises activity when the flash copy occurs.
2. Used database file attribute RECOVER(*AFTIPL) on all database tables. This ensures that the rebuild is started at the soonest possible moment and minimise customer impacts.
3. We have increased the number of database server jobs which process access path rebuilds.
Despite these actions, we still have no supported way of detecting when access path rebuilds complete within a batch job.
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.
IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it.
IBM has received the requirement and is evaluating it. IBM will provide a response after evaluation is complete.
The CEAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed.
An IBM i Service might be a very nice solution.
Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.
For more information about CEAC, see http://www.comeur.org/i4a/pages/index.cfm?pageid=3285
Dawn May - CEAC Program Manager
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Db2 for i
Operating system - IBM i
Source - None
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Availability, Recovery
Operating system - IBM i
Source - None
If the index builds are asynchronous, you might try querying QRCYnnnnn/QADBERAP. In each IASP is a QADBERAP file.
In response to the question, "Would a message to indicate "Access Path Rebuild complete" satisfy the need?" Yes, where would the message be? As long it is something that can easily be monitored from a batch job then this is sufficient. The driver here is to detect when the access path rebuild process is finished rather then individual rebuilds, thus an overall completion message should suffice.
Would a message to indicate "Access Path Rebuild complete" satisfy the need?
The CAAC has reviewed this requirement and recommends that IBM view this as a “nice to have” low priority feature.
Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.
For more information about CAAC, see www.common.org/caac
For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/
Dawn May - CAAC Program Manager