Purpose of Delayed OVA

The intent of Delayed OVA is to provide a mechanism whereby you can run an OVA session after a TDMF session is complete. A Delayed OVA job is the equivalent of a single system TDMF session that can be controlled by using the TDMF TSO or Batch Monitors.

The requirements for a Delayed OVA session are the following.

The Communications data set (COMMDS) from the original session.
All PIT target volumes remain offline.
Running the GTDDOVA program.

You can run a Delayed OVA batch job on any system that was a participant of the original session. When you start the Delayed OVA batch job, the TDMF I/O Monitor (GTDIMON) is called. The COMMDS of the original session are scanned and all completed PIT pairings become eligible for the OVA job. OVA need not be specified in the original session to be eligible for Delayed OVA. The OVA batch job might be run immediately after the Delayed OVA job is started. You can also use the TDMF TSO Monitor for these sessions, except the displayed information for the offline target volume is the device address and not the volume serial number.

Volume and group initialization proceeds as if a regular TDMF session were running. The GTDDOVA program reads the Communication data set and generates REPLICATE statements that contain a source volume serial number and its PIT target device address. If the Delayed OVA job is running on what was an Agent system in the original migration, the target volumes must be available to TDMF at the time of the migration. To prevent corruption of the Point-In-Time copy data resident on the offline target volumes, do not vary online to any system in the complex until all the OVA backup jobs are done.

When the Communication data set is scanned, a temporary COMMDS data set is created for the Delayed OVA job. This temporary COMMDS can be pre-allocated with a DDNAME of DOVACOM, if preferred, in which case the data set must be large enough for a single system migration.

The Delayed OVA job remains active for 15 minutes or until an OVA job is submitted. You have no limit to the number of runs of Delayed OVA if the Communications data set and the offline target volumes are available.

An example of the screen displays for a Delayed OVA session as seen from the TDMF TSO Monitor follows.

Figure 1. Delayed OVA session display

                         Sessions Monitor                  Row 1 to 6 of 6
Command ===>                                              Scroll ===> CSR_
--------------------------------------------------------------------------
TDMF Master V5.9.0 Session Active.
ComDataSet : SYS03321.T021016.RA000.SWH10DVA.R0105353
       Source  Migration   Percent Complete --------->
Group  VolSer   Phase      ..10...20...30...40...50...60...70...80...90..100
       PROD92  Waiting OVA
       PROD94  Waiting OVA

F1=Help      F2=Split     F3=Exit      F5=Rfind     F7=Back      F8=Forward
F9=Swap     F10=Status   F12=Cancel

The example shows a Delayed OVA session. The COMMDS has a temporary name. Any OVA session can now be started within 15 minutes of starting the Delayed OVA session. OVA in the JCL was not specified in the original TDMF session; only the Point-In-Time option was selected.

If F10 is pressed, the status of the job is shown.

Figure 2. Delayed OVA session status

                          Session Status                   Row 1 to 2 of 2
Command ===>                                              Scroll ===> CSR_
System: Master               TDMF                   Version: 5.9.0
ComDataSet : SYS03321.T021016.RA000.SWH10DVA.R0105353          Sessions 01
Number of volumes migrating : 02        Number of concurrent volumes  : 02
Number of volumes  complete : 00        Number of  volumes   waiting  : 00
Requested   Volume Device  Group     --- Migration --- - Error Info - Sync
 Action     Serial Number  Name      Status      Type  System Message Goal
   __       PROD92  22FB           Waiting OVA   DOVA
                    22F5
   __       PROD94  22F8           Waiting OVA   DOVA
                    22F6
F1=Help      F2=Split     F3=Exit      F4=Next      F5=Rfind     F6=Options
F7=Back      F8=Forward   F9=Swap     F10=Monitor  F11=ActionTg F12=Cancel

Select F6 to display the options for this session. OVA is yes.

Figure 3. Delayed OVA session options

                           Session Status                  Row 1 to 2 of 2
Command ===>                                              Scroll ===> CSR_
System: Master               TDMF                   Version: 5.9.0
ComDataSet SYS03321.T021016.RA000.SWH10DVA.R0105353            Sessions 01
Number of volumes migrating : 02        Number of concurrent volumes  : 02
Number of volumes  complete : 00        Number of  volumes   waiting  : 00
Requested   Volume Device  Group     --- Migration --- - Error Info - Sync
 Action     Serial Number  Name      Status      Type  System Message Goal
   __       PROD92         ActCopy = N PACING = N AUTOOPER = N TIME =LOCAL
                           CONFIRM = N PURGE  = N TERMGRP  = N COMPARE = N
                           OVA     = Y PPIT   = N FASTCOPY = N nonPPRC = N
   __       PROD94         ActCopy = N PACING = N AUTOOPER = N TIME =LOCAL
                           CONFIRM = N PURGE  = N TERMGRP  = N COMPARE = N
                           OVA     = Y PPIT   = N FASTCOPY = N nonPPRC = N

As with any OVA session, you can end it by using the session status window and entering H. Confirmation for the termination is then requested.

Figure 4. Halt OVA registrations confirmation window

                     Volume Confirmation Screen            Row 1 to 2 of 2
Command ===>                                              Scroll ===> CSR_
ComDataSet:  . . . . : SYS03321.T021016.RA000.SWH10DVA.R0105353
Confirmation required to Halt OVA registrations.
Volume Serial No.  . : PROD92
Confirm? (YES/NO): . . ___
 F1=Help    F2=Split   F3=Exit    F9=Swap   F12=Cancel