QUERY OLR

Hi Rick,
Thank you for your interest in keeping IMS a vital and successful product. Software development has continuously evolved during IMS's lifetime, and so has IMS itself. We have kept pace with, adopted, and implemented many industry standard best practices within our organization, including Continuous Delivery, Design Thinking, and Agile.

When choosing new features to add from the list of requirements in our backlog, we assess which will bring the most value to as many clients as possible and prioritize those.

At this time, after reviewing this request for enhancement and assessing its potential value, we have decided to reject it. The reason we are rejecting RFE 39585 is because this is a low priority item and we have not had many clients ask for this enhancement. We would rather invest in high priority items that bring the most value to many clients.

We appreciate your input to IMS, and we hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of IMS.

Thank you.
Sincerely,
Deepak Kohli - deepakk@us.ibm.com

Hi Rick,

Is this correct? Ignore the fact that 10 partitions would be OLR'd concurrently not just 2 as in my example.

For example, a PCJK database is being altered. HALDB master DBOHIDK5 with 4 partitions POHIDKA - POHIDKD.

Without this enhancement the user does the following
TSO SPOC input:
QRY OLREORG NAME(*) STATUS(ALTER) SHOW(ALL)

TSO SPOC output:
Response for: QRY OLREORG NAME(*) STATUS(ALTER) SHOW(ALL)
Partition MbrName CC LclStat Rate Bytes-Moved Segs-Moved Roots-Moved Option StartTime
-------------------------------------------------------------------------------------------------------------------
POHIDKA IMS1 0 ALTINPRG DEL,_NOREL
POHIDKB IMS1 0 ALTINPRG DEL,_NOREL
POHIDKC IMS1 0 ALTINQUE DEL,_NOREL
POHIDKD IMS1 0 ALTDONE DEL,_NOREL


With this enhancement the user does the following
TSO SPOC input:
QRY OLREORG NAME(DBOHIDK5) STATUS(ALTER) SHOW(ALL)

TSO SPOC output:
Response for: QRY OLREORG NAME(*) STATUS(ALTER) SHOW(ALL)
Partition MbrName CC LclStat Rate Bytes-Moved Segs-Moved Roots-Moved Option StartTime
-------------------------------------------------------------------------------------------------------------------
POHIDKA IMS1 0 ALTINPRG DEL,_NOREL
POHIDKB IMS1 0 ALTINPRG DEL,_NOREL
POHIDKC IMS1 0 ALTINQUE DEL,_NOREL
POHIDKD IMS1 0 ALTDONE DEL,_NOREL

Since the HALDB ALTER is started using the master name, I would like to submit a QUERY command to see the status of how many of the individual partition OLRs are done and how many in progress. Since the master name was used, the names of the individual partition OLRs is not known without looking at the the RECON to find the names. There is not command which can be used to get those names easily, so the use of the MASTER name in th e QUERY OLR is required now.

Previously with OLR you used the partition name, so you know the name from the command issued. this is not true when the master name is used to start the ALTER.

Hello Rick,

I need additional information from you on this RFE.

Provide more information on possible customers that would use this function.

Provide an expanded business justification. It would be best if you explained the pain points that you think a customer would experience without this function and how the enhancement would resolve those pain points.

Expand the use case to be more detailed so that we have enough information if/when this RFE is implemented. Personally I understand the RFE now because we have talked about it a few days ago but in a few months it may not be as clear. You should be as detailed as possible so that if/when we begin to design the solution, the function that the gets implemented resolves the issue you are reporting.

Thank you,
Jeff Fontaine
IMS Database Development