IBM Data Platform Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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 ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
Thank you for submitting this Db2 Log Analysis Tool for z/OS enhancement request.
After giving the request a comprehensive review, we have determined that we cannot include it as a candidate in an upcoming product deliverable because the request has a high implementation cost with a low relative value for the full base of customers. Consequently, we will not be implementing this request.
Read further for more information and suggested work around.
We appreciate your input to the Db2 Log Analysis Tool for z/OS development team. We also hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of Db2 Log Analysis Tool for z/OS.
Sincerely,
Db2 Log Analysis Tool for z/OS Team
Reasoning:
The customer should switch to FlashCopy image copies (FCIC) if possible in lieu of Concurrent Copy Image Copy.
FCIC created with COPY SHRLEVEL CHANGE FLASHCOPY CONSISTENT will allow application updates throughout the COPY process (objects are in UTRW state) then logs will be applied or backed out directly on the FCIC to back out any uncommitted changes, making it consistent.
Evidence indicates that there are few customers using concurrent image copies making a large effort in this area cost-prohibitive.
Workaround:
The affected tablespace can be supported by converting the CONCURRENT copy back into normal format using DFDSS services (separately priced feature), and that image copy can then be used using Expert Options, though the tablespace must be isolated for the run (use the single tablespace filter only).
Run a ADRDSSU RESTORE with RENAMEU options to restore the VSAM saved inside the concurrent IC:
//RESTORE1 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//INFILE DD DISP=SHR,DSN=RSTEST.IC.IDS2.DEPLOYME.P00000.J0SBFK8Cß dataset name of concurrent IC
//SYSIN DD *
RESTORE INDDNAME(INFILE) -
DATASET(INCLUDE(**)) -
RENAMEU(TS5941) - rename the HLQ from the Db2 HLQ to something else to avoid overwriting the live Db2 VSAM !!!
ADMINISTRATOR
Output:
ADR489I (001)-TDLOG(02), CLUSTER TS5941.DSNDBC.TS5941.DEPLOYME.J0001.A001 WAS RESTORED
CATALOG CATALOG.RSPLEX03.TSO.CAT1
COMPONENT TS5941.DSNDBD.TS5941.DEPLOYME.J0001.A001 notice the TS5941 HLQ instead of the normal Db2 HLQ “IDS2”
Launch ALA, make sure you’re in Classic mode, then use option 0 - make sure you’re using Two Phase mode.
Then use option 1 – general report to run a general report only (no detailed report yet). This scans the log and extracts the log records.
Then use option 2 – details report and enable Expert mode
On the Expert mode panel I’ve entered the LSRN of the concurrent IC + dataset type T + the restored dataset
Now ALA will use the restored concurrent IC as the starting point and then do log-forward to obtain the details about the change (and produce reports, SQL REDO/UNDO, etc.)
In the ALA output can see it is forced into log forward and that the restored CCIC is being used
LF MODE SET BY- USER
…
ALAA156I: TS5941.DSNDBC.TS5941.DEPLOYME.J0001.A001