On 10/29/2015 10:52 AM, CRPence wrote:
On 29-Oct-2015 12:35 -0500, Jerry Draper wrote:
In a recent DR simulation we restored some libraries with lots
of DDM files.
The target system of the DDM files was NOT on the network as
this was a simulation.
The restore operation of each file failed after a timeout of 315
There are many, many DDM files so at 12/hour we weren't getting
There are no break messages so you only find out after wondering
why the restore is taking so long.
How can this be managed so we can restore the files and NOT
validate the remote system?
What is the actual information from a spooled joblog? Just a SWAG,
that [the messaging in the joblog will reveal that] the timeout is
nothing to do with contacting a remote system, and instead is a
functional issue with the *DBXREF.
Working theory on this one is that it is a LIC incompatibility
The DR machine was IPLed from an iBASE DVD at refresh level B and
then the system was "restored" from a tape with refresh level M.
We will test this on 12/10/15. I'll let you know.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.