Logger DSN missing at DR site

Document ID : KB000121521
Last Modified Date : 26/11/2018
Show Technical Document Details
We conducted a Disaster Recovery test using Duplex tapes and copies of BSDS etc. 
All went very well.

One small niggle. I presume every time it wrote a record out to the log, certainly quite regularly, we saw message 

Your manual refers me to the IBM IXGWRITE which says 
RC=4 - processed successfuly with a warning 
REASON=407 suggests there is a block missing between this block and the one previously returned. 

We delete all the logger log data sets before starting up VTAPE 
I don't think we need the data in these logs if we invoked DR. 
Is there a way tell it to ignore this, or to do some sort of cold Start. 
Or do we need these logs backing up at same time as BSDS? 
There are 2 options to deal with this problem: 
1) deactivate the Logger into the VTPARMS when you do a DR 
2) restore the active Logger data set backup at the same time of the BSDS. 

Here is what IBM redbook says: 
DASD-only log stream recovery Like a CF-Structure based log stream, a DASD-only log stream can be affected by a system or System Logger failure. However, because DASD-only log streams are always duplexed to DASD, it is not necessary to go through the same recovery process that is required for CF-Structure based log streams, where System Logger attempts to move the log data to a non-volatile medium as quickly as possible. Also, because DASD-only log streams can only be accessed by one system at a time, the concept of peer recovery does not apply. Recovery for a DASD-only log stream only takes place when an application reconnects to the log stream. As part of connect processing, System Logger reads log data from the staging data set (associated with the last connection to the log stream) into the local buffers of the current connecting system. This allows the application to control recovery, by selecting which system they wish to have reconnect to the log stream and when. Note that for another system to connect to the log stream and perform recovery, the staging data sets must reside on devices accessible by both systems. 

Here is the link of this documentation: 
So it is important for MVS LOGGER address space to read the latest data written into the active logger for Vtape to pursue writting into it on DR restart.