C O N C E P T S & F A C I L I T I E S G U I D E

FDRPAS &FDRERASE

1

t a b l e o f c o n t e n t s

Introduction ................................................................................................................................................... 3

PART ONE. General Overview ................................................................................................ 5

FDRPAS—Non-Disruptive Movement of Disk Volumes ................................................................................. 6

FDRERASE—Quick Erasure of Disk Volumes .............................................................................................. 7

FDRCRYPT—Encrypted Backups ................................................................................................................. 8

PART TWO. FDRPAS ............................................................................................................. 9

Introduction .................................................................................................................................................. 10

The Many Uses of FDRPAS ........................................................................................................................ 10

The Basic SWAP Process (Single System Environment) ............................................................................ 12

FDRPAS SWAP Process—More Details ..................................................................................................... 14

After the SWAP Has Completed .................................................................................................................. 15

The Monitor Tasks (Multi-System Environment ........................................................................................... 16

System Determination .................................................................................................................................. 19

Initiating FDRPAS SWAPs—With Batch Jobs ............................................................................................. 19

Initiating FDRPAS SWAPs—Using PASPROC ............................................................................................ 23

FDRPAS ISPF Interface ............................................................................................................................... 23

FDRPAS SWAPBUILDIX Utility ................................................................................................................... 25

Point-In-Time Backups with FDRPAS .......................................................................................................... 26

Volume Consolidation with FDRPAS ........................................................................................................... 28

Summary ...................................................................................................................................................... 29

FDRPAS & FDRERASE

2

t a b l e o f c o n t e n t s

PART THREE. FDRERASE ................................................................................................... 31

Introduction .................................................................................................................................................. 32

Erase Standards .......................................................................................................................................... 32

Introducing FDRERASE ............................................................................................................................... 32

Erasing Data with FDRERASE .................................................................................................................... 32

What Levels of Erasure Does FDRERASE Offer? ....................................................................................... 33

Other Features of FDRERASE .................................................................................................................... 34

DASD Vendor Considerations ...................................................................................................................... 34

Protecting Against Accidental Erasure with FDRERASE ............................................................................. 35

Additional Considerations ............................................................................................................................ 36

FDRERASE in Batch—JCL Examples ......................................................................................................... 37

Sample Output and Performance ................................................................................................................ 39

Using the FDRERASE ISPF Interface ......................................................................................................... 40

Initiating FDRERASE tasks with the ISPF Interface .................................................................................... 41

Suspending, Terminating and Resuming FDRERASE tasks ....................................................................... 41

Displaying FDRERASE History Records ..................................................................................................... 42

Summary ...................................................................................................................................................... 42

PART FOUR. APPENDIX ..................................................................................................... 43

FDRPAS Case Study ................................................................................................................................... 44

FDRPAS—More Customer Quotes .............................................................................................................. 44

FDRERASE User Experiences .................................................................................................................... 45

FDRPAS & FDRERASE

33

PRODUCT OVERVIEW 1PART For more than 30 years, Innovation Data Processing has been producing high-quality Storage Management Software. Over the years, its products have evolved into today’s ultra high-speed, safe, reliable storage management solutions for z/OS, LAN and Open Systems Data.

It all started with the FDR Storage Management Family, of which over 5000 licenses have now been sold worldwide. The FDR Family is the complete Storage Management System for z/OS.

FDR has become the industry standard for fast, reliable backups of z/OS data.

ABR adds a layer of automation to the standard functions of FDR, providing advanced backup facilities like Incremental Backup, Application Backup and Archiving.

FDRCRYPT is an extra cost option to the FDR Family that provides encryption services for all FDR and ABR backups (as well as sequential output data sets created by an IDCAMS REPRO) protecting these backups against unauthorized access by anyone who does not possess the proper encryption keys.

COMPAKTOR and FDRREORG further enhance the suite by adding intelligent and powerful reorganization processes, for whole DASD volumes and for PDS, VSAM and IAM data sets.

FDREPORT provides extensive customized DASD Management Reporting to suit many needs and purposes.

FDRDRP is an extension of ABR that can reduce full-volume recovery time by up to 80%.

FDRINSTANT enables FDR/ABR to take near 24x7 backups of offl ine volumes, created by the latest DASD Subsystem features like StorageTek SnapShot Copy, EMC TimeFinder, Hitachi ShadowImage and IBM FlashCopy. FDRINSTANT also enhances the performance of other utilities in the FDR Family, such as FDRCOPY.

FDRPAS (FDR Plug and Swap) allows for the non-disruptive movement of z/OS disk volumes from one disk device to another. When new disk subsystems are installed, active online disk volumes can be swapped to drives in the new subsystem without disrupting normal operations or requiring a re-IPL. This allows a 24 x 7 installation with no window for major re-confi gurations and hardware changes to install and activate new hardware.

FDRERASE V5.4 L50 is an EAL2+ certifi ed product that can be licensed as an option to FDRPAS (or separately) which can quickly erase many disk volumes in parallel, allowing you to erase your data in the minimum elapsed time. FDRPAS and FDRERASE are separately licensed components of the FDR Family.

THE FDR/UPSTREAM Family of Products builds on the strengths of the FDR Storage Management Family providing a fast, safe and reliable solution to backing up Open Systems data from fi le servers and workstations, across a network connection to disk or tape on the z/OS host. If the Open Systems data is resident on an EMC Symmetrix/DMX with Enterprise Storage Platform (ESP), the FDRSOS and FDR/UPSTREAM/SOS products provide additional performance enhancements to the backup and restore process by utilizing high-speed mainframe channels.

INTRODUCTION

44

PRODUCT OVERVIEW 1PARTUPSTREAM Reservoir is designed for those users who wish to take advantage of the many strengths provided by FDR/UPSTREAM, but would prefer to use an Open Systems environment (e.g. Windows, AIX, Linux, Sun Solaris) for hosting the backup management engine.

IAM is Innovation’s alternative to VSAM KSDS, ESDS and (as a cost option) AIX and RRDS fi les. It eliminates VSAM performance bottlenecks and reduces VSAM fi le sizes by more than 50%.

FATS/FATAR and FATSCOPY are a set of multi-purpose tape subsystem Media Integrity tools that allow for online tape certifi cation, verifi cation and erasure, as well as the ability to analyze and copy tapes.

Each of the Innovation products is described in a range of Concepts & Facilities Guides.

In this particular guide, we take a look at FDRPAS and FDRERASE.

PART ONE provides a quick overview of FDRPAS and FDRERASE, and also gives a brief mention of another Innovation security-related product: FDRCRYPT.

PART TWO describes how FDRPAS can be used to non-disruptively move z/OS DASD volumes from one disk device to another. It also gives a brief outline of how FDRPAS can be used alongside other Innovation tools to consolidate several smaller devices (e.g. 3390-3s or 3390-9s) onto a single larger device (e.g. 3390-27 or 3390-54).

PART THREE shows how you can use FDRERASE to quickly, easily and safely erase data from one or more z/OS disk volumes.

PART FOUR, the Appendix contains several real-world experiences of using FDRPAS and FDRERASE, as well as some brief 1-liner quotes from satisfied FDRPAS users.

Any comments or suggestions regarding this guide can be directed to: support@fdrinnovation.com

And don’t forget to visit our website for additional and up-to-date information on all Innovation products: www.innovationdp.fdr.com

© Copyright 2006 Innovation Data Processing

INTRODUCTION

5

PART ONEGeneral Overview

This section provides

a brief overview of

FDRPAS and FDRERASE.

6

PRODUCT OVERVIEW 1PARTFDRPAS—Non-Disruptive Movement of Disk Volumes FDRPAS is one of the newer members of the FDR Storage Management Family. It is available as a cost option and it provides the ability to perform non-disruptive movement of z/OS disk volumes from one disk device to another of the same or higher capacity (e.g. a 3390-3 to a 3390-3, or higher). If the target device is of a higher capacity than the source, FDRPAS will automatically update the z/OS VTOC and Indexed VTOC on the target to make the additional capacity available as free space.

FDRPAS can swap volumes that are active. Users and application programs can continue to safely allocate new data sets, or read, update and delete existing data sets on the volume(s) being moved, without any disruption to their own processing or to the FDRPAS swap process.

FDRPAS can move volumes within a single system image, or volumes attached to multiple systems or LPARs in a shared-DASD complex or sysplex, whether locally or remotely attached. Multiple volumes can be swapped concurrently.

FDRPAS supports a wide variety of disk devices from hardware vendors including IBM, EMC, StorageTek and Hitachi. It can swap disk volumes between disks of the same type from the same hardware vendor, or between disks supplied by different vendors.

In general, no special software or hardware modifi cations are required to run FDRPAS. However, before you start to use FDRPAS, please contact Innovation for the latest information on microcode requirements and PTFs.

As well as DASD volumes containing standard application data, FDRPAS can also swap the following types of volumes:

• The SYSRES (and other active “system” volumes)

• Volumes with open catalogs

• Volumes containing multi-volume data sets

• CICS, TSO, Database volumes

• SMS-Managed volumes and WORK volumes

• VM-Owned volumes (as long as the VM systems are shutdown during the swap process).

The only volumes that FDRPAS cannot move are those containing active local PAGE or SWAP data sets. However, you can defi ne new PAGE and SWAP data sets on new volumes, and then migrate the paging activity to them with the console PAGEDEL REPLACE or PAGEADD and PAGEDEL DELETE commands.

GENERAL OVERVIEW 1PART

6

77

PA

RT

Maintaining 24 x 7 AvailabilityThe demand for 24 x 7 availability has never been greater. System outages due to the implementation of new DASD hardware can no longer be tolerated. This problem is addressed by FDRPAS, which can move/migrate hundreds of volumes in a day.

By default, FDRPAS copies 15 tracks from the source to the target in each I/O. An FDRPAS SWAP will take about the same elapsed time as a normal full-volume disk-to-disk copy, unless there is a great deal of update activity on the volume being swapped. The average elapsed time for FDRPAS to copy a 3390-3 is just 3 to 5 minutes! This volume movement can be done during normal system operations, without interrupting other activity. The operating system, application jobs, online systems, and end-users are unaware that FDRPAS is swapping disks to new devices.

Performance and Effi ciencyAs well as working non-disruptively, the FDRPAS SWAP process is also highly effi cient. The SWAP is accomplished with minimal impact on the performance of applications using the volume(s) being swapped. As already mentioned, end-users and applications can continue to use the volume(s), unaware that the data movement is occurring or has completed.

FDRPAS will dynamically manage the copy process in response to system activity (e.g. copying inactive data sets before active ones, and, optionally, pacing the copy I/O), to minimize its effect on the system. If necessary, SWAPs can also be suspended and then resumed at a later time.

On average, a FDRPAS SWAP of a 3390-3 can be completed in 3 to 5 minutes.

Ease-Of-UseOne of the key features of FDRPAS is its ease-of-use. The initiation of a volume swap can be done with a simple batch job, or through a set of ISPF panels (see “Initiating FDRPAS Swaps” later in this guide). The SWAP process can be monitored as it progresses, and a history record of all previous SWAPs can be viewed at any time.

See PART TWO for more detailed information on FDRPAS.

FDRERASE—Quick Erasure Of Disk VolumesThere are many times when you may wish to insure that all corporate data has been erased from a set of z/OS disk volumes. For example:

• At the end of a disaster recovery (test or real).

• When de-commissioning a disk control unit (perhaps after migrating data off it with FDRPAS).

• When re-assigning disk volumes (i.e. to be sure that no residual data remains on the disks).

FDRERASE is a secure data erase utility for z/OS DASD, which can be licensed as an option to FDRPAS, or as a stand-alone product for use by any installation. FDRERASE meets all the above needs and more. It can quickly erase many disk volumes in parallel, allowing you to erase your data from a set of disks in the minimum elapsed time. On average, the ERASE function of FDRERASE can erase approximately 1.5Tb of data (per DASD controller) in 1 hour. So, two FDRERASE jobs running against two separate DASD controllers could erase approximately 3Tb in 1 hour.

GENERAL OVERVIEW 1

88

FDRERASE V5.4 L50 is the fi rst z/OS secure erase utility to complete Common Criteria Evaluation and Validation Scheme (CCEVS) evaluation and Common Criteria EAL2 Augmented validation, and has earned the right to display the international Common Criteria Recognition Arrangement (CCRA) certifi cation mark on August 5, 2005.

FDRERASE is designed to comply with current U.S. Government guidelines for erasing computer disks prior to disposal.

The ERASE function, which performs a single overwrite, meets Department Of Defense (DoD) standards for “Clearing & Overwriting” data, while the SECUREERASE function, which performs three overwrites of varying patterns, meets DoD standards for “Purging & Sanitizing” data.

FDRERASE also complies with the government National Computer Security Center (NCSC) guidelines for erasing computer disks. The ERASE function meets the NCSC defi nition for “clearing” a disk and the SECUREERASE function meets the NCSC defi nition for “purging” a disk.

See PART THREE for more detailed information on FDRERASE.

FDRCRYPT—Encrypted BackupsWhile FDRERASE can be employed to securely erase data from your z/OS DASD, careful attention should also be paid to the security of the data stored on your z/OS backups.

Protection of backup data is now required by many of today’s government, industry and corporate privacy and security laws and regulations, such as HIPAA, Sarbanes-Oxley, and DoD requirements, among others in the USA and other countries.

FDRCRYPT, which is a cost option to the FDR Storage Management Family, provides encryption services for all FDR and ABR backups, protecting those backups against unauthorized access by anyone who does not possess the proper encryption keys.

If you make regular use of IDCAMS either for backup purposes or for data interchange with other organisations, you may also be interested in the FDRCAMS option of FDRCRYPT, which can be used to encrypt sequential output data sets created by an IDCAMS REPRO.

FDRCRYPT and FDRCAMS are not covered in this Guide. However, you can get more information on both products from the separate “FDRCRYPT” Concepts & Facilities Guide.

GENERAL OVERVIEW P

AR

T 1

9

PART TWOFDRPAS

This section describes how

FDRPAS can be used to

non-disruptively move z/OS

DASD volumes from one

disk device to another.

1010

1PARTIntroductionAs described in the overview in Part ONE, FDRPAS can be employed to non-disruptively move one or more z/OS disk volumes from one disk device to another of the same or higher capacity.

The Many Uses Of FDRPASFDRPAS is a multi-purpose utility that can be used whenever data needs to be migrated from one z/OS DASD volume to another with the minimum of disruption. Outlined below are some of the primary uses of FDRPAS.

1. When Installing New DASD HardwareOne of FDRPAS’s primary uses is with the installation of new DASD hardware.

With current z/OS hardware and software, you can attach new disk subsystems and dynamically activate an updated I/O confi guration to make these subsystems immediately available. This allows you to get the new hardware installed and operational as quickly as possible, without having to carry out an IPL of the Operating System.

However, with your new DASD hardware in place, you then need a way to quickly and easily move your data from the old volumes across to the new ones. You could use standard volume dump/restores with FDR or ABR, but this would require a quiesce of activity on the volume(s) to be moved (for the duration of the whole move) to ensure that data is in a consistent state.

2. For General Data MovementAside from installing new hardware, data centers may also have a requirement to move data around from time-to-time, either within a single DASD subsystem, or across multiple subsystems. For data centers running 24 x 7 operations, and perhaps even installations with large maintenance windows, there simply isn’t suffi cient “off peak” time available to move what is often now terabytes of data.

FDRPASP

AR

T 2

The FDRPAS Solution

FDRPAS offers a far better solution to a standard dump/restore. It allows you to move the data from existing DASD volumes to the new hardware while those volumes are still in use. When FDRPAS completes the SWAP process, the data resides completely on the new volume and the original volume is no longer required.

(The full SWAP process is described later in this section).

The FDRPAS Solution

FDRPAS removes this problem by allowing you to non-disruptively move terabytes of data—even during normal business hours.

1111

1PART3. Moving Volumes Containing z/OS CatalogsIn most data centers it is sometimes necessary to move a single DASD volume across to another device. If that volume is inactive, the data movement can be done with an FDR or ABR dump/restore. However, if the volume contains open catalogs (or is active in any other way), the process is more complicated.

4. When Re-Locating A Data CenterOccasionally, entire data centers have to be moved to a new location, involving the relocation of all the data onto a new DASD subsystem. This would traditionally be achieved with a volume-level backup/restore of all DASD volumes.

5. For I/O Load BalancingOccasionally, the I/O load in one or more disk subsystems may be excessive, while other subsystems remain under utilized.

6. For Non-Disruptive backupAs described in a separate Innovation white paper entitled “Corporate Backup with FDRINSTANT”, today’s 24 x 7 data centers now need to take their daily backups without suffering a backup window running into several hours.

FDRPASP

AR

T 2

The FDRPAS Solution

FDRPAS can move an active volume without having to wait for all activity to be quiesced, or for open catalogs to be closed.

The FDRPAS Solution

FDRPAS can be used an alternative to the backup/restore process to relocate an entire data centre by duplicating all of the offline volumes in new disk subsystems at the new location. Contact Innovation for additional information on the procedures and considerations for re-locating an entire data center.

The FDRPAS Solution

FDRPAS can be used to rearrange disk volumes to distribute the I/O load and improve performance. This can be done as soon as it is required—day or night.

The FDRPAS Solution

FDRPAS can be used to create offline point-in-time copies of DASD volumes, which can be used by FDR in conjunction with FDRINSTANT to take ‘instant’ backups.

1212

1PARTThe Basic SWAP Process (Single System Environment)The following section describes the basic SWAP process employed by FDRPAS in a “single system” environment—i.e. where the volume to be swapped is only accessed by applications running in a single z/OS image.

First, a SWAP task is initiated using either a batch job or a PROC (started via an Operator Command, or with the ISPF panels—see later).

The SWAP task identifi es the online “Source” volume to be swapped and the offl ine “Target” address where the data will be moved to. Our diagram shows one volume being swapped, but up to 32 can be swapped in one FDRPAS job (you can run more jobs if more SWAPs are required).

FDRPAS then temporarily suspends I/O to the online Source volume while it inserts an ‘intercept’ to record the updates that are occurring, be it from end-user applications or from z/OS system processes. Once the intercept is in place, I/O to the source volume can be resumed.

FDRPAS P

AR

T 2

Start FDRPAS, Select Target Volume

Applications System

OfflineTargetDevice

OnlineSource

Volume

FDRPAS inserts intercept

Applications

I/O intercept to Monitor updates

System

OfflineTargetDevice

OnlineSource

Volume

1313

1PARTFDRPAS then starts copying the data from the Source to the offl ine Target volume. The Target remains offl ine for the duration of the copy process so that the data copied to it is protected until the SWAP is complete. All used tracks (for inactive data sets) and all allocated tracks (for active data sets) are copied, while FDRPAS simultaneously detects updates to the Source. Updated tracks are then re-copied if necessary.

At the end of the SWAP process, the Source and Target volumes are identical. All I/O activity to the Source is then quiesced momentarily while access is swapped across to the Target volume:

FDRPAS switches devices so that all I/O is directed to the new device. During this process, the new device is placed online, while the old device is varied offl ine and the label is modifi ed so that z/OS will no longer be able to vary it online (unless a RESTVOL is run).

When the z/OS system is re-IPLed, it will be the new device that automatically comes online.

FDRPASP

AR

T 2

FDRPAS copies data tracks

Applications

I/O intercept to Monitor updates

System

OfflineTargetDevice

OnlineSource

Volume

Copy used tracks for inactive data sets

The volumes are identical

Applications

Quiesce all I/O to volume

System

OnlineTargetDevice

OfflineSource

Volume

Call swap serviceto swap the volume

1414

1PARTFDRPAS SWAP Process—More DetailsSome key points to note about the FDRPAS SWAP process:

• Only the Source and Target devices are accessed during the FDRPAS SWAP process. No other volumes need to be accessed by FDRPAS, with the exception of a dynamic allocation to the SYSRES volume during the SWAP process.

• FDRPAS does not use any additional communication service (e.g. TCP/IP or VTAM).

• FDRPAS does not require a coupling facility, or a separate ‘control’ data set on a third disk volume.

• An FDRPAS copy process can be terminated at any time before the fi nal SWAP has completed, either through the ISPF panels, or with the z/OS STOP command. This can be done without affecting the original device or any applications using it. When you stop a SWAP task, all active SWAPs will be allowed to complete, but any pending SWAPs requested in that same task will not start (a message will be issued to identify the volumes that were bypassed).

• Protection against accidental cancellation of a FDRPAS task, such as a console CANCEL command, is provided. If an FDRPAS task is cancelled with cancel protection in effect, the CANCEL acts like a STOP command (see above), in that it will wait for any active SWAPs to complete before terminating. If a task needs to be cancelled immediately (despite active tasks), a second CANCEL can be issued.

• When the SWAP has completed, FDRPAS can, if desired, send an e-mail message to one or more recipients informing them of the successful (or unsuccessful) completion of the task. This feature is enabled via a simple ‘FDREMAIL’ DD statement in the executing JCL, which points to control statements defi ning the message content and the intended recipients (see example on page 21). This feature requires an Internet connection from the LPAR, and also a TCP/IP & SMTP server.

• FDRPAS can also send error messages to a TSO user, allowing that user to quickly discover problems with an ongoing FDRPAS SWAP operation.

FDRPASP

AR

T 2

1515

1PARTAfter the SWAP has completed...This section outlines several options for the handling of the Source volume(s), which will be offl ine to z/OS following the successful completion of the FDRPAS SWAP.

If You Are De-Commissioning The Source Volume(s)...Prior to unplugging and de-commissioning the offl ine source volumes, you can use FDRERASE (see PART THREE) to quickly and securely erase those disks so that no residual data is left on them.

If You are Re-Using The Source Volume(s)...If the source volumes are to be retained and re-used for different purposes, you should still consider using FDRERASE to erase the residual data from them. As explained in PART THREE, re-labelling a disk, or using a basic ICKDSF INIT will wipe out the VTOC, but these processes still leave the residual data records on the volume where they can be accessed by unauthorized users. Not a good idea if, for example, a volume containing production PAYROLL data is re-used for development or testing but the residual data is left on the disk for anyone to inspect.

If You Wish To Use FDRPAS For “Point-In-Time” BackupsAs mentioned earlier, FDRPAS can be employed in the process of taking non-disruptive, “point-in-time” backups. An FDRPAS SWAPDUMP command is used in place of the SWAP command shown in the previous examples. This invokes the same COPY process, but at the end of the process the original Source volume is retained and stays online, while it is the Target volume (now containing a copy of all the data) that is maintained in an offl ine state.

Innovation’s FDR and FDRINSTANT products can then be used to backup that offl ine duplicate. See “Point-In-Time backups” later for more details.

FDRPASP

AR

T 2Unplug & Remove Original

Applications System

OnlineTargetDevice

OfflineSource

Volume

1616

1PARTThe Monitor Tasks (Multi-System Environment)When multiple z/OS systems can access the DASD volume to be moved, there are some additional steps required, as the SWAP process must be coordinated on all system images. Any update activity during the SWAP must be monitored on all sharing systems, and the fi nal SWAP to the new device must be conducted simultaneously across all images.

The sequence is as follows:

First, an FDRPAS monitor task is started on all systems that have access to the Target device (even if they don’t have access to the Source volume). Each monitor task can monitor up to 64 potential Target devices, after which z/OS starts a separate address space for additional monitor tasks.

A disk device can connect to up to 128 systems, so FDRPAS supports up to 128 separate monitor tasks for a given SWAP operation.

An FDRPAS SWAP task is then initiated to specify the Source and Target volumes, as described earlier. The SWAP task can be started in any of the systems involved, but for best performance it should be run on the system with the highest level of update activity to the Source. In our diagram, the monitor task has been started on z/OS B, while the SWAP has been initiated on z/OS A.

FDRPASP

AR

T 2

Monitor task is started:

OnlineSource

Volume

OfflineTargetDevice

MonitorTask

z/OS B

Swap task is started:

OnlineSource

Volume

OfflineTargetDevice

MonitorTask

z/OS Bz/OS A

SwapTask

1717

1PARTAfter validating the SWAP request, the FDRPAS SWAP task running in z/OS A will indicate that the SWAP is pending.

On all the other system images (in our case, just z/OS B), the FDRPAS monitor tasks will recognize the pending SWAP and indicate that they are ready to participate.

When the required number of monitor tasks have acknowledged their participation (see “System Determination” later), the SWAP task will signal that the SWAP has begun. It will then install the I/O intercept on its image to monitor updates.

The monitor tasks on the other systems will then recognize that the SWAP has begun and install the I/O intercept on their images to monitor updates.

When all monitor tasks have indicated that the intercepts are installed, the SWAP task will begin copying tracks from the original device to the target device, as previously described for the single system SWAPs.

FDRPASP

AR

T 2

Monitor task joins in swap:

OnlineSource

Volume

OfflineTargetDevice

z/OS Bz/OS A

SwapTask

MonitorTask

Intercepts installed:

OnlineSource

Volume

OfflineTargetDevice

z/OS Bz/OS A

SwapTask

MonitorTask

Intercep

t

Intercep

t

1818

1PARTThe FDRPAS intercepts on each system will monitor all I/O operations to the Source volume and will note all tracks that have been updated. Updated tracks will be copied (or re-copied if necessary) to the Target device.

When the copy is complete, FDRPAS signals to all monitor tasks to quiesce I/O to the original device. The remaining tracks, if any, are then copied across to the Target while all other I/O is quiesced.

The SWAP task will then signal all monitor tasks to SWAP all system pointers on all system images so that all future I/O to the volume will be directed to the new device. As with the single-system SWAP described earlier, the original Source volume will be placed offl ine and the volume label modifi ed so that it cannot be accidentally brought online during a subsequent Re-IPL.

FDRPASP

AR

T 2Tracks copied:

OnlineSource

Volume

OfflineTargetDevice

z/OS Bz/OS A

SwapTask

MonitorTask

Intercep

t

Intercep

t

I/O quiesced:

OnlineSource

Volume

OfflineTargetDevice

z/OS Bz/OS A

SwapTask

MonitorTask

Qu

iesce

Qu

iesce

Volume Swapped:

OnlineTargetDevice

OfflineSource

Volume

z/OS Bz/OS A

SwapTask

MonitorTask

1919

1PARTSystem DeterminationIn a multi-system environment, one or more FDRPAS monitor tasks must be executed on every system image that has the source volume online; one of those monitor tasks must also monitor the target device if it is in the I/O confi guration of that system.

If some of the systems are excluded from the FDRPAS swap process, those systems will not be aware that FDRPAS has moved the volume to a new device, and FDRPAS will not be aware of any updates to the volume which occur on the excluded systems.

To protect against this situation, FDRPAS attempts to determine how many z/OS systems have access to the source volume. Depending on the disk hardware involved, FDRPAS may be able to automatically identify the number of systems accessing the source volume and then supply the CPU serial number of each of those systems. However, if the number of systems cannot be determined, or if certain systems need to be excluded from participating in the SWAP, manual input has to be provided to FDRPAS to control this process. Section 300.05 of the FDRPAS user guide has more detailed information on the recommended procedures for system determination.

Initiating FDRPAS SWAPs—With Batch JobsThe initiation of FDRPAS SWAPs is very straightforward. The most common way of starting off a SWAP is with a standard z/OS batch job. The following examples show just how simple the process can be. With just a few control statements, hundreds of DASD volumes (containing terabytes of data) can be swapped.

1. SINGLE-SYSTEM SWAPsIn the fi rst example, a single DASD volume, accessible by a single z/OS system image, will be swapped to a new device.

• The Source volume (DATA22) must not be accessible to any other system image.

• The Target device (at address 07C3) must be offl ine.

• The CHECKTARGET=YES parameter will ensure that the Target device is empty before starting the SWAP operation.

FDRPASP

AR

T 2

FDRPAS—Single System SWAP Example #1

//SWAP EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * SWAP TYPE=FULL,CHECKTARGET=YES MOUNT VOL=DATA22,SWAPUNIT=07C3

2020

1PARTIn this next example, several TSO volumes on adjacent z/OS addresses on a single system image will be swapped to new devices on adjacent addresses (1AA*) in the new disk subsystem. Again, the Source volumes must not be accessible by any other system image, and the Target devices must be offl ine.

All three volumes will be swapped concurrently.

#SYSTEMS=1 is specifi ed because the source volumes are on a control unit where FDRPAS could not automatically determine the number of systems with access to the volume (e.g. an IBM RVA).

2. SIMULATED SWAPsThe following example executes a simulated SWAP (with the SIMSWAP statement) to validate the parameters that will be used for the real SWAP.

For multi-system SWAPs (see next page), where FDRPAS can identify the attached systems, SIMSWAP can also display all of the systems that have access to the Source volumes specifi ed.

FDRPASP

AR

T 2

FDRPAS—Single System SWAP Example #2

//SWAP EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//FDRSUMM DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * SWAP TYPE=FULL,#SYSTEMS=1,MAXTASKS=3,CHECKTARGET=YES MOUNT VOL=TSO001,SWAPUNIT=1AA* MOUNT VOL=TSO002,SWAPUNIT=1AA* MOUNT VOL=TSO003,SWAPUNIT=1AA*

FDRPAS—Simulated Swap

//SIMSWAP EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=* SIMSWAPTYPE=FULL,MAXTASKS=3,CHECKTARGET=YES MOUNT VOL=DATA22,SWAPUNIT=07C3 MOUNT VOL=PROD12,SWAPUNIT=425C MOUNT VOL=TSO123,SWAPUNIT=A340

2121

3. MULTI-SYSTEM SWAPsIn this next example, a single volume that is accessible to multiple system images will be swapped to a new device.

The volume is in a 3990-6 or 2105 compatible disk subsystem, so FDRPAS will be able to determine the number of systems that have access to the volume. The target device must be offl ine on all systems. The additional FDREMAIL DD card (which can optionally point to a member in a PDS) allows an e-mail message to be sent after the completion of the SWAP.

Prior to running the above SWAP job, an FDRPAS monitor task must be started on each of the other sharing systems to monitor the offl ine target device.

Below is an example of the monitor job that would be run. FDRPAS will periodically check to see if a SWAP task has started on another z/OS system image which is using the device as a Target. If so, the monitor task will assist the SWAP task by monitoring this system image for updates to the original volume during the copy process, and by switching all I/O activity to the new device when the swap is complete.

The monitor task will automatically terminate once the swap to the target has completed.

FDRPAS—Multi-System SWAP Example #1

//SWAP EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//FDREMAIL DD *MAILSERVER 12.132.14.178FROM:<abc@mycmpny.com>TO <xyz@mycompany.com>SUBJECT: DATA22 SWAP COMPLETED//SYSIN DD * SWAP TYPE=FULL,CHECKTARGET=YES MOUNT VOL=DATA22,SWAPUNIT=07C3

FDRPAS—Monitor a single volume

//MONITOR EXEC PASPROC//SYSIN DD * MONITOR TYPE=SWAP MOUNT SWAPUNIT=07C3

PA

RT 2 FDRPAS

2222

Here is an extract of sample output from the above SWAP job. Notice that three systems (CPUA, CPUB and CPUC) were found to be accessing the volume:

FDR241 FDRPAS SUCCESSFULLY COMPLETED SWAP OF VOL=DATA22 TO UNIT=07C3 ON CPUB 16.31.54FDR241 FDRPAS SUCCESSFULLY COMPLETED SWAP OF VOL=DATA22 TO UNIT=07C3 ON CPUA 16.31.56FDR241 FDRPAS SUCCESSFULLY COMPLETED SWAP OF VOL=DATA22 TO UNIT=07C3 ON CPUC 16.31.56FDR007 ENDING TIME OF FULL VOL SWAP -- 16.31.56 -- UNIT=3390-3 ,IN=D#DATA22,OUTPUT=TAPE1 16.31.56FDR122 OPERATION STATISTICS FOR 3390 VOLUME..................DATA22 16.31.56FDR122 CYLINDERS ON VOLUME..............3,339 16.31.56FDR122 DATASETS PROCESSED.................234 16.31.56FDR122 BYTES READ FROM DASD.......237,893,477 16.31.56FDR122 DASD TRACKS SWAPPED..............4,986 16.31.56FDR122 UPDATED TRACKS RECOPIED..........2,639 16.31.56FDR122 DASD EXCPS.........................381 16.31.56FDR122 TARGET DASD EXCPS..................450 16.31.56FDR122 CPU TIME (SECONDS)...............0.522 16.31.56FDR122 ELAPSED TIME (MINUTES).............2.5 16.31.56FDR122 SWAP TIME..........................2.5 16.31.56FDR999 FDR SUCCESSFULLY COMPLETED 16.31.56

IMPORTANT

Before running SWAP operations with FDRPAS, you are strongly advised to review the checklist in section 300.01 of the FDRPAS manual.

You should also contact Innovation for the latest information on IBM APARs and PTFs that may need to be applied to your z/OS system before running FDRPAS.

PA

RT 2 FDRPAS

2323

Initiating FDRPAS SWAPs—Using PASPROCAs an alternative to running a batch job, FDRPAS SWAPs can also be initiated via the PASPROC cataloged procedure and the z/OS START (S) console command. These SWAPs will run as system started tasks instead of jobs. For more information on this method of initiating FDRPAS SWAPs, see section 310 of the FDRPAS manual.

FDRPAS ISPF InterfaceThe third and fi nal way of initiating FDRPAS SWAPs is via the FDRPAS ISPF interface, which allows for the initiation, monitoring and control of FDRPAS operations on the system to which your TSO session is logged on. Through the interface, you can:

• Initiate and monitor SWAP (and SWAPDUMP) tasks

• Suspend, resume, terminate tasks and amend pacing values

• Reply to FDRPAS console messages

• Display FDRPAS history records

This fi rst example shows the basic display showing a SWAP in progress. As you can see, the SWAP from unit address 0943 to 0941 is currently 11% completed.

If more than one active SWAP task is being displayed, these tasks can be fi ltered and sorted. Entering the SORT command displays a panel that allows sorting criteria for various fi elds on the display. Sorting on Status and Volume Serial can be especially useful when numerous SWAP tasks are running concurrently.

The above panel also allows you to limit the display to only SWAP tasks with a specifi c STATUS—e.g. ACTIVE or SWAPPED.

PA

RT 2 FDRPAS

2424

PA

RT

If required, a more detailed display of a SWAP can be obtained:

FDRPAS retains history records of all the SWAPs it has completed. The following display has extracted some of that information. This type of history report can also be produced by running a report in batch.

2 FDRPAS

2525

PA

RT

FDRPAS SWAPBUILDIX UtilityIndependent of SWAP operations, FDRPAS also includes a utility function called SWAPBUILDIX that allows you to build an indexed VTOC (VTOCIX) or rebuild a disabled VTOCIX on a shared DASD volume while it is online to multiple systems. The SWAPBUILDIX function uses FDRPAS communication and co-ordination techniques to allow the VTOCIX to be built while remaining online to all sharing systems.

In the example shown below, the disabled VTOCIX will be rebuilt on the volume labelled DATA23. Because the volume is attached to a 3990-6 control unit (or compatible disk subsystem), FDRPAS can determine the number of systems which have access to this volume.

Prior to running this job, you must start FDRPAS monitor tasks (see below) on each of the indicated systems to monitor the offl ine device specifi ed by SWAPUNIT=.

The monitor device must be offl ine on all systems.

The following JCL example shows the monitoring of offl ine device 07C3 for the above SWAPBUILDIX operation.

FDRPAS will periodically check this device to see if a FDRPAS SWAPBUILDIX task has started on another system. If so, the monitor task will wait for the VTOCIX to be rebuilt and then update the VTOCIX information on this system. Since this type of monitor task will continue to look for SWAPBUILDIX operations until terminated, you will probably want to use the DURATION= operand to automatically terminate it when it has been idle for a number of minutes. Alternately, you can cancel it when you are done.

FDRPAS—SWAPBUILDIX Example

//BUILDIX EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=* SWAPBUILDIX TYPE=FULL MOUNT VOL=DATA23,SWAPUNIT=07C3

FDRPAS—Monitor SWAPBUILDIX Example

//MONITOR EXEC PASPROC//SYSSIN DD * MONITOR TYPE=SWAP,DURATION=10 MOUNT SWAPUNIT=07C3

2 FDRPAS

2626

PA

RT

Point-In-Time Backups with FDRPASAs mentioned earlier, FDRPAS (in conjunction with FDR and FDRINSTANT) can optionally be used to create non-disruptive, point-in-time backups of disk volumes.

• The FDRPAS SWAPDUMP command is used to start constantly-updated images of one or more disk volumes, at some time before the backups are required.

• A single command to FDRPAS (CONFIRMSPLIT) is then used to terminate the SWAPDUMP operation and create offl ine point-in-time images of those volumes.

• FDR and FDRINSTANT (separate features of the FDR DASD Management Family) can then be used to backup those offl ine images.

The diagram below summarizes the operation of point-in-time backups using the combination of FDRPAS, FDR and FDRINSTANT.

An offl ine duplicate of ZOS001 has been created using the FDRPAS SWAPDUMP command. Then, while end users (or CICS, TSO, DB2, etc) continue to use the original online volume, the offl ine duplicate is backed up to tape with a standard FDR full-volume backup, driven by FDRINSTANT:

Note: FDR and FDRINSTANT are fully described in a separate Concepts & Facilities guide.

z/OS HOSTStandard volume,

online to z/OS.

Offline duplicate, created by:

FDRPAS SWAPDUMP

FDRWITH

FDRINSTANT

End-Users, CICS,TSO, DB2, etc

ZOS001

ZOS001

Backup

2 FDRPAS

2727

PA

RT

Point-In-Time Backups with FDRPAS (continued)The job below is an example of the point-in-time backup process with FDRPAS and FDR/FDRINSTANT.

In this example, a volume accessible by a single system image will be copied to an offl ine device. As soon as FDRPAS fi nishes synchronizing the volumes, the target device will become a frozen image of the source volume. The second step then uses FDR and FDRINSTANT to backup that point-in-time image.

In the example below—this time using the PASPROC cataloged procedure via a z/OS START (S) command on the console—several volumes which are accessible to 3 system images will be copied to offl ine devices. Prior to running this job, an FDRPAS monitor task must be started on each of the systems to monitor the target devices.

Notes:

“CO=” and “SU=” are abbreviations for CONFIRMSPLIT= and SWAPUNIT=, to reduce the length of the console input.

CONFIRMSPLIT=YES causes FDRPAS to wait for confi rmation before freezing the point-in-time image. This can be done using the FDRPAS ISPF panels, or by using a MONITOR TYPE=CONFIRMSPLIT batch job.

CONFIRMSPLIT=YES does not involve a WTOR to the console operator. Once the SWAPDUMP operations have been confi rmed, FDRINSTANT can then be used to backup those frozen images to tape.

FDRPAS—Point-In-Time backup Example #1

//SWAPDUMP EXEC PGM=FDRPAS,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrpas.loadlib//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD * SWAPDUMP TYPE=FULL MOUNT VOL=DATA22,SWAPUNIT=07C3//BACKUP EXEC PGM=FDR,REGION=0M,COND=(0,NE,SWAPDUMP)//SYSPRINT DD SYSOUT=*//DISK1 DD DSN=FDR.USE.UNIT07C3,UNIT=SYSALLDA,// VOL=SER=DATA22,DISP=OLD//TAPE1 DD DSN=BACKUP.VDATA22,UNIT=TAPE,DISP=(,CATLG)//SYSIN DD * DUMP TYPE=FDR

FDRPAS—PASPROC Monitor Example

S PASPROC.PROD01,PARM='SWAPDUMP TYPE=FULL,CO=YES/MOUNT VOL=PROD01,SU=1B32'S PASPROC.PROD02,PARM='SWAPDUMP TYPE=FULL,CO=YES/MOUNT VOL=PROD02,SU=1B34'S PASPROC.PROD03,PARM='SWAPDUMP TYPE=FULL,CO=YES/MOUNT VOL=PROD03,SU=1B37'

FDRPAS 2

2828

Volume Consolidation with FDRPASAs described already in this section, FDRPAS can be used to:

• Non-disruptively move an entire volume to a target disk of the same size (e.g. a 3390-9 to another 3390-9). Or…

• Non-disruptively move an entire volume to a target disk of a larger size (e.g. a 3390-9 to a 3390-27). The extra cylinders on the larger disk become available as free space after the migration has completed.

FDRPAS can also assist with the consolidation of multiple smaller volumes to a single larger volume (e.g. three 3390-9s to a single 3390-27). FDRPAS will be used to migrate the fi rst of the three 3390-9s to the bottom third of the 3390-27, but the data on the remaining two 3390-9s will have to be moved at the data set level.

Data sets can only be moved while they are unallocated (not in use) because the catalog, VTOC and VVDS must be updated to refl ect the new location of each data set. So, any applications using those data sets must be quiesced or shut down during the move.

Normally a data set move can take some time, depending on the number of data sets and the number of tracks that need to be moved. Applications which use the affected data sets will have to remain quiesced or shutdown for the duration of the move, and this can lead to quite a considerable disruption to normal services.

However, as well as being used to move the entire fi rst volume, FDRPAS can also be used in concert with FDRCOPY and FDRINSTANT to reduce to a minimum the disruption caused when moving the second and third volumes as well –

• After using FDRPAS to migrate the fi rst 3390-9 to the bottom third of the target 3390-27…

• You can use FDRPAS again to migrate the other two 3390-9s onto two temporary “holding” 3390-9s (or larger) within the target DASD subsystem.

• You will then quiesce or shut down any applications which are using the data sets on the two temporary “holding” volumes.

• Using FDRCOPY, you can then move the data sets from the temporary “holding” volumes across to the target volume. If present and enabled in the target subsystem, FDRCOPY (using FDRINSTANT) will automatically use IBM FlashCopy, EMC SNAP or StorageTek SnapShot Copy to copy the data sets. In those instances, the elapsed time of the copy will be only the time required to allocate and catalog all the output data sets—possibly just a matter of a few minutes, and signifi cantly less than the time to do a normal disk-to-disk copy.

• Once all the data sets have been moved from the “holding” volumes to the target 3390-27 with FDRCOPY, you can then restart the applications.

If you are planning a DASD migration in the near future, and if that migration will involve the consolidation of smaller volumes onto larger volumes, please contact Innovation for more details on how FDRPAS, FDRCOPY and FDRINSTANT could be used to minimise the disruption.

PA

RT 2 FDRPAS

2929

PA

RT

SummaryIn today’s data centers, where 24 x 7 operations are now often a need rather than a luxury, the ability to move data around the DASD subsystem with the minimum of disruption has become a priority for most DASD Administrators.

Whether it is a single DASD volume being moved to alleviate I/O bottlenecks, or perhaps a full range of devices being migrated across to newly installed hardware, the DASD Administrator needs to get the job done quickly and effectively, and with the minimum of disruption to his end-users and their application systems.

FDRPAS provides DASD Administrators with a simple yet effective tool for non-disruptively moving data around the DASD subsystem. If required, a single batch job can be used to move anything from one volume to many terabytes of data. The whole process can be monitored through the ISPF panels and the completion of each volume swap can be recorded and viewed in the FDRPAS history logs.

FDRPAS can also be used (in conjunction with other Innovation tools) to help with volume consolidation projects, where smaller capacity volumes (e.g. 3390-3s or 3390-9s) are to be consolidated onto larger volumes (e.g. 3390-27 or 3390-54).

See the Appendix for some case studies on FDRPAS.

2 FDRPAS

3030

FDRPASP

AR

T 2

This Page Intentionally Left Blank

31

PART THREEFDRERASE

This section describes how you can

use FDRERASE quickly, easily and

safely to erase data from one or more

z/OS disk volumes.

3232

1PARTIntroductionYour corporate data is a valuable resource that often includes information that you do not want to share with anyone outside your company, and sometimes not even with others within your company. You almost certainly have some z/OS data that must be kept secure, either due to government regulations or other legislative requirements, such as HIPAA, Sarbanes-Oxley, and DoD requirements, among others in the USA and other countries.

For these reasons, you will have security procedures in place that limit access to your z/OS data in your data center, and which may also control access to that data when it is sent out of the data center. However, in many cases, little attention is paid to residual data that is left on disks after data sets are deleted or moved to other locations. Deleting a data set from disk does not erase the data from the disk tracks; it just deletes the VTOC pointers to the tracks containing that data.

Because of time constraints, a minimal INIT with ICKDSF is sometimes employed to erase data from disk. Although this wipes out the z/OS VTOC, it still leaves the data records on the volume where they can be accessed by unauthorized users.

Erase StandardsThe National Computer Security Center (NCSC), a division of the US NSA (National Security Agency) has documented DoD (Department of Defense) guidelines for erasing computer disks. These defi nitions are found in document NCSC-TG-025 A Guide to Understanding Data Remanence in Automated Information Systems, also called the “Green Book”. You can fi nd copies of this document online by searching the Internet for “NCSC-TG-025”.

Introducing FDRERASEFDRERASE V5.4 L50 is an EAL2+ certifi ed product that can be licensed as an option to FDRPAS (or separately) which can quickly erase many disk volumes in parallel, allowing you to erase your data in the minimum elapsed time. FDRPAS and FDRERASE are separately licensed components of the FDR Family.

Erasing Data With FDRERASEFDRERASE can quickly, yet securely erase disk volumes to NCSC Clearing/Purging standards.

This is useful for:

• Disaster Recovery testing—FDRERASE can be used at your disaster site to erase your corporate data from the disks before you leave.

• After a FDRPAS swap—FDRERASE can erase your corporate data from the old source disks before you disconnect them from the disk subsystem and sell them off, return them to the manufacturer, or destroy them.

• FDRERASE can also be used any time that you need to erase data from disks, such as when you are reusing disks for new purposes.

FDRERASEP

AR

T 3

33

PA

RT 3 FDRERASE

What Levels of Erasure Does FDRERASE Offer?FDRERASE offers three levels of data erasure. All of these levels will make your data unreadable through the disk subsystem when using the disks as z/OS CKD disks, but in some cases the data may still be recoverable if the hard drives are removed from the subsystem and accessed as native SCSI/FIBRE disks (see “DASD Vendor Considerations” later).

1. QUICKERASEQUICKERASE is the fastest method of erasing data, using hardware CKD commands to erase all records from all tracks of the selected disk devices. There are several such commands that are used, depending on the manufacturer and emulation mode of the disk subsystem, but they have the same effect: all records are erased from the tracks and the tracks appear to be empty (no records).

QUICKERASE is a non-certifi ed solution, best suited for erasing disks that will be re-used internally (i.e. where security risks are relatively low).

2. ERASEBy default, ERASE will overwrite every track on the selected disk devices with a single track-length record consisting of binary zeros, obliterating all data records which previously existed on the track. You can optionally request that every track be overwritten multiple times (ERASEPASS=n) and you can optionally specify the value to be used in each byte of the overwriting record (ERASEPATTERN=), varying it from pass to pass.

ERASE is often adequate for erasing disks which will be sold, scrapped, or returned to the manufacturer, since it makes it diffi cult to recover the original data, even if the hard drives are removed, and especially if multiple passes and patterns are used.

FDRERASE’s default ERASE function, which is CCRA certifi ed, meets the NCSC defi nition of “clearing” the disk.

3. SECUREERASESECUREERASE overwrites each track 3 times, with varying patterns. This can be used for your most sensitive data, to insure that it is unlikely to be recoverable from the internal hard drives. SECUREERASE is essentially an ERASE operation, except that ERASEPASS=3 is forced and special patterns are used. The fi rst pattern will be a random value (other than 00, 01, FE and FF), the second pass will use the complement of the fi rst pattern, and the third pattern will be a new random value (different from the fi rst two).

SECUREERASE can be used on your most sensitive data to make it very unlikely that the data could be recovered if the hard drives were removed.

FDRERASE’s SECUREERASE, which is CCRA certifi ed, meets the NCSC defi nition of “purging” the disk.

33

Other Features Of FDRERASEFDRERASE also offers two additional “erasing” features—EMPTYVTOC and SIMERASE—neither of which actually delete any data, but which can be of use in certain situations.

EMPTYVTOCEMPTYVTOC does not erase any data from disks, nor does it uncatalog any data sets. It simply reinitializes a disk with an empty VTOC. If present, the VTOCIX will be rebuilt. After the EMPTYVTOC has run, the emptied VTOC and the re-built VTOCIX will have the same size and location as the originals. This is a very quick way of initializing an empty volume (perhaps after a successful FDRPAS SWAP), but should not be used as a method of erasing disks.

SIMERASESIMERASE also does not erase any data, but it validates your FDRERASE control statements to confi rm which disk devices will be erased by a “real” QUICKERASE, ERASE or SECUREERASE. Innovation recommends that you always use SIMERASE to validate your FDRERASE control statements before running the process for real.

DASD Vendor ConsiderationsAll modern disk subsystems use internal FBA (Fixed Block Architecture) disks to emulate the CKD (count-key-data) disks used by z/OS systems. Every disk vendor has a different scheme for storing the emulated CKD data onto the FBA disks, but in most of them there is a fi xed FBA location for each emulated CKD track.

FDRERASE is able to overwrite the emulated CKD tracks to make the original data unavailable. However, there are some considerations:

• The FBA disks are usually off-the-shelf disks that can be removed from the CKD disk subsystem and attached to another system as an FBA disk. Depending on how the disk vendor has written your CKD data, it may be possible to recover your data directly from the FBA disks.

• Most modern disk subsystems are reconfi gurable, meaning that the mapping of the emulated CKD disk volumes onto the FBA disks can be changed. If this mapping is changed, some of your old data may reside in areas of the FBA disks that are no longer in use. This data may be recoverable if the FBA disks are removed from the subsystem.

• Most modern disk subsystems use “hot spares” for the FBA disks. If a FBA disk fails, the subsystem is able to assign an unused hot spare FBA disk to replace the failed disk, and recreate the data that was on the failed disk. Usually the failed disk will be replaced and returned to the vendor for diagnosis and repair. However, your data may still be on that failed disk, and may be recoverable. FDRERASE cannot access the failed FBA disk and cannot erase data from it. You may need to speak with the disk vendor to insure that your data is secure.

Additional vendor-specifi c details are documented in the FDRERASE manual.

FDRERASEP

AR

T 3

34

Protecting Against Accidental Erasure with FDRERASEAlthough FDRERASE has checks to help insure that only appropriate disks are erased, these checks can be circumvented. So, please note:

• Only you can positively identify the disks which can be safely erased.

• You should do the same sort of checks for FDRERASE that you would do before initializing a disk with ICKDSF.

FDRERASE offers the following mechanisms to help protect against accidental erasure of your data:

FDRERASE DefaultsBy default, FDRERASE operates on only offl ine disks, which are either FDRPAS source disks, or which contain no data sets (i.e. nothing in the VTOC). However, these defaults can be overridden to tell FDRERASE to:

• Erase any offl ine disk, even if there are data sets in the VTOC (CHECKTARGET=NO)

• Select online volumes and vary them offl ine for erasing (ONLINE=VARYOFF)

These overrides are usually only appropriate at a disaster site to vary your volumes offl ine and erase them before leaving. Care should always be taken when overriding FDRERASE’s default options.

Always use SIMERASE fi rst to validate that your FDRERASE control statements select the right disks to be erased.

Your z/OS Security SystemSince erasing disks offers the capability of accidentally destroying a great deal of valid data, you will want to control who can execute FDRERASE. You can use your z/OS Security System to limit access to the program library containing FDRERASE or the program name FDRERASE.

• If FDRERASE has been installed in a separate load library, you can use your security system to limit access to that library and use a STEPLIB to access the library. Whenever FDRERASE is executed it will check for authority to this security resource:

CLASS=FACILITY ENTITY=FDRERASE.ERASE

• If you have defi ned that FACILITY class resource, then only users who have at least READ authority to the resource will be able to execute FDRERASE. If you have not defi ned the resource, then all users will be able to erase disks.

• Two additional resources are required if the CHECKTARGET=NO or ONLINE=VARYOFF overrides are to be used:

CLASS=FACILITY ENTITY=FDRERASE.ERASEALL

CLASS=FACILITY ENTITY=FDRERASE.ONLINE.VARYOFF

FDRERASEP

AR

T 3

35

3636

Additional ConsiderationsRunning FDRERASE in Multi-system EnvironmentsExcept on most EMC subsystems, FDRERASE cannot tell if a disk may be online to another system. Even the ONLINE=VARYOFF operand (which varies online disks offl ine for erasing) only operates on the current system. It is your responsibility to insure that the disks are offl ine on all systems.

The following console command can quickly tell if a range of disks are offl ine; execute this on each system before using FDRERASE:

D U,,,uuuu,nn

If your systems are in a sysplex, the following console command will execute this on every system:

ROUTE *ALL,DS D U,,,uuuu,nn

Special Notes For FDRPAS UsersWith the default of CHECKTARGET=YES, FDRERASE will erase disk devices which were the source volumes of a successful FDRPAS swap, or the target volumes of a successful FDRPAS SWAPDUMP.

Do not specify CHECKTARGET=NO if only FDRPAS disks are to be erased. FDRERASE and FDRPAS both check to be sure that the disk is not already being used by the other program, so you can’t accidentally erase a disk which is being swapped, or initiate a swap to a disk that is being erased.

If you plan to erase disks from a subsystem using FDRERASE, while at the same time swapping other volumes in the same subsystem with FDRPAS, be aware that the FDRERASE I/Os may increase the FDRPAS swap elapsed time. We recommend that you only erase a few volumes at a time (MAXTASKS=n) in this case.

If the old disk subsystem will be sold or returned to the vendor, you should run an ERASE or SECUREERASE to insure that your corporate data is gone. If it will be reused within your corporation, then QUICKERASE is usually appropriate.

Warning: when swapping volumes with FDRPAS, the source disks serve as a backup in case of problems with the new hardware. Do not begin erasing data from the old disks until you are sure that the new ones are operating without problems.

Erasing Data From z/OS TapeFDRERASE can not be used to erase data from z/OS tape. However, a separate Innovation product called FATS can be used for this purpose. See the separate “FATS/FATAR” Concepts and Facilities Guide for more details.

FDRERASEP

AR

T 3

3737

PA

RT

FDRERASE in Batch—JCL ExamplesExample 1: Using SIMERASE to validate control statementsThis example shows SIMERASE being used to validate control statements. It will also list the offl ine disk volumes that would be erased if once the SIMERASE is changed to one of the other FDRERASE options.

Example 2: Using ERASE to erase a range of disks after a Disaster Recovery testWhen leaving a DR site, you will want to erase all the data that you restored. In this example, which uses the default ERASE function, several ranges of volumes will be varied offl ine (if necessary) and then erased. Your DR site requires that you re-label and vary online the disks, so VARYON=AFTER and CHANGEVOL= have been used. The volumes will be varied online and re-labeled with SG plus the 4-digit hex unit address (e.g., SG323A). An empty VTOC will be built starting on relative track 1 (cylinder 0 track 1) for 44 tracks (3 cylinders). If the volume had a VTOCIX, it will be rebuilt after the VTOC (cylinder 3 track 0 for 3 tracks).

3 FDRERASE

//FDRERASE EXEC PGM=FDRERASE,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrerase.loadlib//SYSPRINT DD SYSOUT=*//FDRSUMM DD SYSOUT=*//SYSIN DD * SIMERASE TYPE=FULL MOUNT ERASEUNIT=(3A*,3B*,4*)

//FDRERASE EXEC PGM=FDRERASE,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrerase.loadlib//SYSPRINT DD SYSOUT=*//FDRSUMM DD SYSOUT=*//SYSIN DD * ERASE TYPE=FULL,CHECKTARGET=NO,MAXTASKS=64,ONLINE=VARYOFF,VARYON=AFTER MOUNT ERASEUNIT=(3*,4*,5*),CHANGEVOL=SG&UUU,VTOCLOC=1,VTOCSIZE=44

3838

Example 3: Using SECUREERASE to erase disks that will be de-commissionedFollowing a successful FDRPAS SWAP, some disks in the old subsystem, which is now going to be de-commissioned, contain old copies of extremely sensitive data. An FDRERASE SECUREERASE will be used to purge all data from those disks. Each track will be overwritten 3 times with random patterns. All these disks must be offl ine (which is how FDRPAS leaves them). The default of CHECKTARGET=YES will verify that each disk device is a FDRPAS source disk before erasing it.

Example 4: Using EMPTYVTOC on selected volumesFDRERASE, with the EMPTYVTOC function, provides a quick and convenient way of emptying the VTOC on these disks, as an alternative to initializing them one-at-a-time with ICKDSF. Note that this will not uncatalog any data sets that were in the VTOCs. Again, CHANGEVOL= and VARYON=AFTER will cause the volumes to be relabelled and remounted after emptying the VTOC.

Stopping and Modifying FDRERASE jobsWhile an FDRERASE job is running, you can stop it prematurely (before all disks are erased) or modify the number of ERASE tasks (MAXTASKS) dynamically with console commands. To stop FDRERASE, issue the STOP (P) command with the name of the FDRERASE job:

P jobname

FDRERASE will terminate as soon as all disks currently being erased have terminated; no new disks will be started. To dynamically modify the value of MAXTASKS= (the number of concurrent ERASE tasks), issue the MODIFY (F) command:

F jobname,MAXTASKS=nn

//FDRERASE EXEC PGM=FDRERASE,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrerase.loadlib//SYSPRINT DD SYSOUT=*//FDRSUMM DD SYSOUT=*//SYSIN DD * EMPTYVTOC TYPE=FULL,VARYON=AFTER MOUNT ERASEUNIT=21C*,CHANGEVOL=XX****

FDRERASEP

AR

T 3

//FDRERASE EXEC PGM=FDRERASE,REGION=0M//STEPLIB DD DISP=SHR,DSN=fdrerase.loadlib//SYSPRINT DD SYSOUT=*//FDRSUMM DD SYSOUT=*//SYSIN DD * SECUREERASE TYPE=FULL MOUNT ERASEUNIT=(07C5,07D2,07D3,07DA, 07E5,07F4)

Warning: when swapping volumes with FDRPAS, the source disks serve as a backup in case of problems with the new hardware. Do not begin erasing data from the old disks until you are sure that the new ones are operating without problems

3939

PA

RT

Sample Output and PerformanceSample Output #1: ERASEWhen the overwriting record used by FDRERASE is all binary zeros, the ERASE function is quite fast, as very little data must be sent down the channel for each track, allowing many disks to be erased in parallel. In the following example, the ERASE of a 3390-3 volume took just 2.8 minutes, overwriting each track once. The defaults of 1 pass with a data record of all zeros were used. The blank volser (VOL=) indicates that the disk did not have a volume label prior to the ERASE.

Sample Output #2: SECUREERASESECUREERASE will be slower than ERASE since it always writes a non-zero record, multiple times, to every track. It also waits at the end of each pass to be sure that the data is hardened (written) to disk before continuing; this may take some seconds. In the following example, the SECUREERASE of a 3390-3 volume took 7.7 minutes, overwriting each track 3 times. The FDR272 messages show the 3 passes and the data pattern used for each one. Because of the 3 passes, the DASD TRACKS ERASED in the FDR122 message is 3 times the number of tracks on the volume.

See the Appendix for more examples of FDRERASE performance.

FDRERASE 3

FDR001 FDR ERASE VOLUMES - FDRERASE - INNOVATION DATA PROCESSING FDR303 CARD IMAGE -- ERASE TYPE=FULL,ALREADYERASED=PROCESS FDR303 CARD IMAGE -- MOUNT ERASEUNIT=21C5 12.35.49 FDR235 FDRERASE WILL ERASE THE FOLLOWING 1 UNITS: 12.35.49 FDR235 21C3 12.35.49 FDR270 DEVICE IS ALREADY ERASED UNIT=21C5 VOL= OVERRIDDEN 12.35.49 FDR272 ERASE STARTED PASS 1 PATTERN=00 12.35.49 FDR273 ERASE HARDENED DATA TO UNIT=21C5 IN 2 SECS 12.38.34 FDR272 ERASE ENDED PASS 1 12.38.34 FDR241 FDRERASE SUCCESSFULLY COMPLETED ERASE OF VOL= ON UNIT=21C5 12.38.34 FDR122 OPERATION STATISTICS FOR 3390 VOLUME.................. 21C5 12.38.34 FDR122 CYLINDERS ON VOLUME..............3,339 12.38.34 FDR122 DATASETS PROCESSED...................0 12.38.34 FDR122 BYTES READ FROM DASD.................0 12.38.34 FDR122 DASD TRACKS ERASED..............50,085 12.38.34 FDR122 UPDATED TRACKS RECOPIED..............0 12.38.34 FDR122 DASD EXCPS.......................3,345 12.38.34 FDR122 TARGET DASD EXCPS....................0 12.38.34 FDR122 CPU TIME (SECONDS)...............0.254 12.38.34 FDR122 ELAPSED TIME (MINUTES).............2.8 12.38.34 FDR122 ERASE TIME.........................2.8 12.38.34 FDR999 FDR SUCCESSFULLY COMPLETED 12.38.34

FDR001 FDR ERASE VOLUMES - FDRERASE - INNOVATION DATA PROCESSING FDR303 CARD IMAGE -- SECUREERASE TYPE=FULL,ALREADYERASED=PROCESS FDR303 CARD IMAGE -- MOUNT ERASEUNIT=21C3 12.38.34 FDR235 FDRERASE WILL ERASE THE FOLLOWING 1 UNITS: 12.38.34 FDR235 21C3 12.38.34 FDR270 DEVICE IS ALREADY ERASED UNIT=21C3 VOL=SH21C3 OVERRIDDEN 12.38.34 FDR272 ERASE STARTED PASS 1 PATTERN=FA 12.38.34 FDR273 ERASE HARDENED DATA TO UNIT=21C3 IN 2 SECS 12.41.05 FDR272 ERASE ENDED PASS 1 12.41.05 FDR272 ERASE STARTED PASS 2 PATTERN=05 12.41.05 FDR273 ERASE HARDENED DATA TO UNIT=21C3 IN 2 SECS 12.43.36 FDR272 ERASE ENDED PASS 2 12.43.36 FDR272 ERASE STARTED PASS 3 PATTERN=4B 12.43.36 FDR273 ERASE HARDENED DATA TO UNIT=21C3 IN 2 SECS 12.46.16 FDR272 ERASE ENDED PASS 3 12.46.16 FDR241 FDRERASE SUCCESSFULLY COMPLETED ERASE OF VOL=SH21C3 ON UNIT=21C3 12.46.16 FDR122 OPERATION STATISTICS FOR 3390 VOLUME..................SH21C3 12.46.16 FDR122 CYLINDERS ON VOLUME..............3,339 12.46.16 FDR122 DATASETS PROCESSED...................0 12.46.16 FDR122 BYTES READ FROM DASD.................0 12.46.16 FDR122 DASD TRACKS ERASED.............150,255 12.46.16 FDR122 UPDATED TRACKS RECOPIED..............0 12.46.16 FDR122 DASD EXCPS......................10,027 12.46.16 FDR122 TARGET DASD EXCPS....................0 12.46.16 FDR122 CPU TIME (SECONDS)...............3.820 12.46.16 FDR122 ELAPSED TIME (MINUTES).............7.7 12.46.16 FDR122 ERASE TIME.........................7.7 12.46.16 FDR999 FDR SUCCESSFULLY COMPLETED 12.46.16

4040

PA

RT

Using the FDRERASE ISPF InterfaceThe FDRERASE ISPF interface allows you to initiate, monitor and control FDRERASE operations on the system to which your TSO session is logged on. You can:

• Submit FDRERASE jobs

• Monitor active FDRERASE tasks

• Suspend and resume active FDRERASE tasks

• Terminate active FDRERASE tasks

• Display FDRERASE history

The FDRERASE panel (see below) is displayed via option ‘E’ from the main FDR/ABR Primary Option menu option. Pressing ENTER checks to see if there are any FDRERASE tasks in progress on this system. If active tasks are found, they are automatically displayed.

The status of ACTIVE indicates that the erase is in progress; the text following it indicates the type of erase (QUICK, ERASE, or SECURE). The status can also show ERASED, ERROR (if the erase failed), SUSPEND, or INACTIVE (no erase was ever started for the volume).

Other fi elds show the percent complete, pass number, elapsed time and description of the device.

Whenever you press ENTER, the information displayed will be updated. Alternately, you can overtype the number after REFRESH with a value. The screen will be updated automatically, every 2 seconds, until this value counts down to zero; the 2 second refresh interval can be changed on a separate FDRERASE “options” panel.

Additional devices can be added to the display by the volume serial, unit address, SMS storage group, SSID (subsystem ID), or control unit serial number. If a complete volume serial or unit address is entered, only that disk will be displayed. If an SMS storage group, SSID, or serial number is entered, all disks matching that value will be displayed. The SSID or serial number is a convenient way to display all volumes in an unused disk subsystem so that you can erase all or some of them.

An asterisk (*) is the only supported wild card character for the selection of multiple volumes, units, storage groups, or control units. If it appears in the middle of a selection string it represents exactly one character. If it appears at the end, it represents one or more characters. ISPF line commands (in the “Command” column) are supported for inserting and deleting entries in the display. For example, enter ‘D’ to delete a volume from the display, or ‘I’ to insert a blank entry.

FDRERASE 3

--------------------------------- FDRERASE ------------------- Row 1 to 2 of 2 COMMAND ===> SCROLL ===> PAGE Active QUick ERase SEcure SIm EMpty ABort SUspend REsume OPtions HIstory SOrt Refresh 0 Command Unit Volume Elapsed Control SMS Addr Serial Cmp Pass Time Unit Storage Mask Mask % # Status MM:SS SSID Serial# Group Cyls ------- ---- ------ --- --- -------------- ------- ---- ------- -------- ----- 21C0 12 1/1 ACTIVE QUICK 0:25 0311 10017 21C3 33 1/1 ACTIVE QUICK 0:19 0311 3339

4141

PA

RT

Initiating FDRERASE tasks with the ISPF InterfaceTo initiate an ERASE, display one or more inactive disk devices and then enter the appropriate command, either in the “Command” column or at the command line at the top of the screen:

• SIM (SIMERASE)

• QUICK (QUICKERASE)

• ERASE (ERASE)

• SECURE (SECURERASE)

• EMPTY (EMPTYVTOC)

This will create one or more batch jobs to erase the selected disks. You will have the option to browse or edit the generated jobstream, or submit it immediately. We recommend that you always issue a SIM to create the JCL as a SIMERASE, submit it, then re-submit with the appropriate command once you have validated that the correct target disks have been selected.

Suspending, Terminating and Resuming FDRERASE tasksYou can also use the FDRERASE ISPF interface to:

• Temporarily suspend an FDRERASE task (SUSPEND)

• Terminate an FDRERASE task (ABORT)

• Resume an FDRERASE task (RESUME)

For example, enter the SUSPEND command (or just SU) in the “Command” column next to the active erase to be suspended. The status will change to SUSPEND. To resume, enter the RESUME command (or just RE) next to any suspended swap.

3 FDRERASE

--------------------------------- FDRERASE ------------------- Row 1 to 9 of 9 COMMAND ===> SCROLL ===> PAGE Active QUick ERase SEcure SIm EMpty ABort SUspend REsume OPtions HIstory SOrt Refresh 0 Command Unit Volume Elapsed Control SMS Addr Serial Cmp Pass Time Unit Storage Mask Mask % # Status MM:SS SSID Serial# Group Cyls ------- ---- ------ --- --- -------------- ------- ---- ------- -------- -----erase 21CD INACTIVE 0311 3390 1113 quick 21CC INACTIVE 0311 3390 1113

Command Unit Volume Elapsed Control SMS Addr Serial Cmp Pass Time Unit Storage Mask Mask % # Status MM:SS SSID Serial# Group Cyls ------- ---- ------ --- --- -------------- ------- ---- ------- -------- -----suspend 21C0 12 1/1 ACTIVE QUICK 0:19 0310 10017resume 21C3 12 1/1 SUSPEND QUICK 0:15 0313 10017abort 21C5 33 1/1 ACTIVE QUICK 0:19 0315 10017

4242

PA

RT

Displaying FDRERASE History RecordsIf you enter the HISTORY command (or just HI) on the command line of the FDRERASE panel, you can display FDRERASE history records, as shown below, for all volumes which have been successfully erased on this system since the last IPL.

SummaryFDRERASE provides an excellent combination of speed, fl exibility and reliability when erasing corporate data from your z/OS disks.

With FDRERASE, you can choose the level of erasure that is appropriate to your needs. You can be sure that the selected erase process will run as quickly as possible, whilst at the same time ensure that your data is erased to the required standard.

The choice of either batch or ISPF initiation offers you the fl exibility to use FDRERASE whenever and however it is required—regardless of whether you are erasing a single disk or a whole DASD subsystem.

See the Appendix for a case study on FDRERASE.

3 FDRERASE

--------------------------------- FDRERASE - History --------- Row 1 to 3 of 3 COMMAND ===> SCROLL ===> PAGE HIstory SOrt Command Unit Volume Elapsed Control SMS Addr Serial Cmp Pass Time Unit Storage Mask Mask % # Status MM:SS SSID Serial# Group Cyls ------- ---- ------ --- --- -------------- ------- ---- ------- -------- ----- 21C3 ERASED QUICK 1:55 311 3339 21C0 ERASED QUICK 4:12 311 10017

43

PART FOURAPPENDIX

Hundreds of successful DASD migrations worldwide have been completed using FDRPAS.

This section contains a few recent case studies.

Also included is a separate case study on FDRERASE.

4444

FDRPAS Case StudyWe provide a wide range of Technical Support for the IBM zSeries™ software infrastructure, including large-scale Data Migration. One of our recent projects for a client involved a data migration onto a new DASD Subsystem using FDRPAS. The migration was of 416 3390-3s.

This move was completed over a single weekend. Here is our “diary” of the three days:

FridayMet with the client for a review meeting. We then installed FDRPAS, ran the LICENSEprogram, and tested a MONITOR job. At the end of the day the customer gave us TSOuser IDs, passwords, temporary badges, a desk/cubicle...and said “see you on Monday!”

SaturdayOnly 2 LPARs were active (CICS regions), so we submitted batch MONITOR jobs on bothLPARs and then submitted the batch SWAP jobs from another production LPAR. Each jobran with MAXTASKS=10, and we submitted 3 FDRPAS SWAP jobs at a time, allowing atotal of 30 SWAPs to run concurrently.

We moved 236 of the 416 volumes in around 8 hours.

SundayWe used the same approach as Saturday to move the remaining volumes, which includedthose containing JES2 Checkpoint, SPOOL vols, RES packs, CICS loggers, etc

We moved the remaining 180 volumes in 5 hours

FDRPAS—More Customer Quotes“Installation of FDRPAS was very easy and fast, and we were able to run the fi rst tests after less than 1 hour...”

“The actual migrations ran so fast that we couldn’t believe they were working until we checked the output volumes..!”

“Our only complaint about FDRPAS was that it ran too fast for us to monitor what it was doing!”

“FDRPAS was very easy to install and to use—even in our confi guration consisting of 10’s of LPARs...”

“We would highly recommend FDRPAS and are now thinking of using it on a regular basis for day-to-day DASD I/O balancing...”

PA

RT 4 APPENDIX

4545

PA

RT 4 APPENDIX

FDRERASE User Experiences

“ We’ve just confi gured a 3.3Tb DS8000 and yesterday we ran FDRERASE (ERASE) against the entire box, which took just 2 hours and 4 minutes to complete. Afterwards, we ran FDRERASE EMPTYVTOC to create new VTOCs on the volumes and vary them all online...and that took just 2 minutes!”

“ At the end of our DR test last week, we used FDRERASE (ERASE) to erase 41Tb of data, which had been restored to 3390-27s (on IBM 2105 DASD). The entire process took just over 5 hours...”

C O N C E P T S & F A C I L I T I E S G U I D E

September 2006

Corporate HeadquartersInnovation Plaza275 Paterson Avenue, Little Falls, New Jersey 07424-1658Tel: (973) 890-7300 Fax: (973) 890-7147support@fdrinnovation.com sales@fdrinnovation.com

www.innovationdp.fdr.com

European Offi ces

FRANCE GERMANY NETHERLANDS UNITED KINGDOM (& Nordic Countries)_____________________ _____________________ _____________________ _____________________191, avenue Aristide Briand Orleansstraße 4a Brouwerstraat 8 Clarendon House94230 Cachan 81669 München 1315 BP Almere 125 Shenley Road Borehamwood, Herts WD6 1AG Tel: (33) 1 49 69 94 02 Tel: 089-489 0210 Tel: 036-534 1660 Tel: 0208 905 1266Fax: (33) 1 49 69 90 98 Fax: 089-489 1355 Fax: 036-533 7308 Fax: 0208 905 1428frsales@fdrinnovation.com desales@fdrinnovation.com nlsales@fdrinnovation.com uksales@fdrinnovation.comfrsupport@fdrinnovation.com desupport@fdrinnovation.com nlsupport@fdrinnovation.com uksupport@fdrinnovation.com