Resetting log RBA

LP: R+/CHANGE ACCUM 10.1.00

Details: One of our V9 DB2 subsystems is approaching the maximum RBA and we have plans to reset it soon. We will bring a new member into the data sharing group and shut down the threatened one for a week. After that, we will reset the Log RBA for member 1 and shut down member 3. Is there anything we need to prepare/change on Change Accum?
Thank you.



Issue Summary: Resetting log RBA

 

Legacy ID:KA383645

RESET LOG RBA and logmaster.

For Log Master, if you have ONGOING processes then you will need to run your ONGOING processes just prior to bringing down the DB2 system where they are going to reset the RBA's. They will need to make sure there are no OPEN URIDS at that time by queiscing or stopping the objects being processed before running the last ongoing processes. Then AFTER the DB2 systems has its RBA's reset, they will need to change the FROM DATE/TIME in all of their ONGOING jobs to a point AFTER the RBA RESET and also include the RESET PURGE keywords in each ongoing processes first run. Then remove the RESET PURGE keyword after the initial run.

Example

ONGOING Handle 10 RESET PURGE


The RESET PURGE keywords causes Log Master to ignore the REPOS entries for the ongoing processes starting point and instead use the FROM DATE/TIME specified in the JCL as they cannot process any log records prior to the RESET.
 

1. R+/CHANGE ACCUM