CA Datacom/DB ignores a NEWRXX request unless an active Recovery File (LOGRCV YES) is specified in the MUF startup options.
Execution of a NEWRXX request does not cause a spill to be performed. If a spill is in progress at the time of the request, MUF completes the spill before requesting a new tape. Examine the system log to determine the exact time of the last spill. Use the time of the last spill as an estimate in determining which Recovery File tapes are needed to perform a forward or backward recovery at some time in the future.
The Recovery File being demounted contains log records up to the point of the last spill executed by the MUF. This does not necessarily mean that all tasks completed at the time of the spill were written on the Recovery File. For example, a long running job that is executing with transaction backout specified can prevent records from other completed tasks from being spilled.
MUF dynamically deallocates the current RXX DD and reallocates a new one. CA Datacom/DB closes and reopens the Recovery File (RXX). Operations is responsible for mounting a new tape.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|