Hints and tips for DBRC

This topic provides task-oriented instructions for frequently-used procedures, including the following topics.

Changing the RECON data sets to output time stamps in local time of origin
If the listing of the RECON data set does not list the offset value for time stamps, the record might have been created when the offset value was different from the current offset value. Using DBRC commands to change or delete such a record will result in a record-not-found condition because the current offset is applied if it is not included in the time stamp parameter of the command.
Locating the last SLDS stop time in the RECON data set
Use the following procedure to find the last SLDS stop time in the RECON data set using the GENJCL.USER command. This procedure can be used while IMS is still running and can also be used if the PRISLD is already closed.
Adjusting GENMAX when it is reached or it is too high
Prior to image copy utility execution, verification exit processing may determine that one of the following situations is true when image copy data sets are being reused. In such cases, the GENMAX value is either too high or too low. In either case, a command must be issued to correct the problem.
Adjusting GRPMAX when it is reached or it is too high
Before execution of the Change Accumulation utility, DBRC might determine that the change accumulation data sets are being reused and that the GRPMAX value must be changed. A command must be issued to correct this problem.
Closing an open online PRILOG record
During time stamp recoveries, when DBRC reports that there are open allocations that are not needed for the recovery, it might be easier to close the open PRILOG record rather than deleting the individual allocations. Use the NOTIFY.PRILOG command to close the open PRILOG record.
Working with subsystem records (SSYS)
If authorization for a database fails and you list the database and all the subsystem records in the RECON data set, you might wonder how the subsystem names (SSIDs) were created.
Removing authorization inconsistency between the SSYS from DB/AREA records
To change database authorization or if authorization fails, a LIST.DB command shows that the DB or area is authorized to a nonexistent subsystem and backout is not required.
Restarting the change accumulation process for logs
Change accumulation erroneously stops processing logs and the source of the problem is traced to an OLDS left in the ARC STARTED state. An IPL of z/OS® is done on the CPU where the archive job was run and the status of the OLDS remains in this state.
Restarting the change accumulation work when it states nothing to process
Change accumulation has issued a message stating that it found no logs to process. A review of the listing reveals that there are many logs that need to be processed.
Moving log data sets
DBRC records information about IMS logs in the RECON data set. This information includes the log data set name (DSN), its starting and ending times, and the volume serial (VOLSER).
Cataloging data sets
You can indicate whether image copy, change accumulation, and log data sets are cataloged or SMS managed by using the CATDS or NOCATDS keywords on the CHANGE.RECON or INIT.RECON command.
Performing multiple cold starts in a test environment
Many times in a test environment, you may want to cold start IMS. In order to cold start IMS the last OLDS must be closed.
Reducing potential RECON data set enqueue problems
The following list describes some scenarios that can cause the RECON data set enqueue problems and contain suggestions for avoiding these problems.

Parent topic: DBRC administration