Appendix F1 -- Titan Restore Procedures

# General Information

## Reading an Internally Labeled Tape

If you need to read an internally labeled tape before proceeding, the
dataset \$CDS1.MISC.CNTL on the SunGard floor system has a member,
TAPELABL, which uses IEBGENER to copy the labels from a tape to sysout
using BLP (Bypass Label Processing).

## Using Visara to Access SunGard DR System Console

Any PC having a tn3270 application such as QWS can be used to access the
SunGard disaster recovery LPARs during a disaster recovery test or an
actual disaster.

The following procedure to set up the session applies when the LPAR is
running the SunGard floor system, NIH DR System 4, or NIH DR System 9.

Set up a tn3270 session as follows:

> Hostname = drvisara.cit.nih.gov
>
> Terminal type = IBM-3278-2
>
> Port = 23
>
> Lu name = sunXcon or sunXalt

Where X is the number of the desired SunGard LPAR.

**Note**: Normally, this will only work from inside NIHnet (including
VPN commections to NIHnet).

## Scratch Tapes

The scratch tapes are 040800 through 040999.

# Information About Backups

All disks except for those used by DB2 are backed up by the Storage
Administrators. After all of the backup jobs have completed, a list
indicating the disk volser, the data set name on tape, the data set
sequence number, and the tape volser is produced. This list is written
to tape E00001 with the data set name NIH.STGADMIN.DRMAIL and is also
emailed to the Public Distribution List CIT DCSS DRlistings. Similar
information for the DB2 backup tapes is written to tape E00002 with the
data set name ZDB2DB2.DB2.DISKSAVE.DRTAPE. Each tape has information for
each dump cycle with the most recent cycle appearing first.

If a copy of the appropriate email is not available at the disaster
site, you can print the list with the following JCL:

//JDALIST JOB (),'LIST DISASTER TAPES',

// MSGCLASS=H,NOTIFY=\$JDA

//\* LIST FIRST DATA SET ON TAPES E00001 AND E00002

> //\*
>
> //STEP1 EXEC PGM=IEBGENER
>
> //SYSUT1 DD DSN=NIH.STGADMIN.DRMAIL,
>
> // LABEL=(1,SL),
>
> // UNIT=R9840,
>
> // VOL=SER=E00001,
>
> // DISP=(OLD,KEEP)
>
> //SYSUT2 DD SYSOUT=\*
>
> //SYSPRINT DD SYSOUT=\*
>
> //SYSIN DD DUMMY
>
> //\*
>
> //STEP2 EXEC PGM=IEBGENER
>
> //SYSUT1 DD DSN=ZDB2DB2.DB2.DISKSAVE.DRTAPE,
>
> // LABEL=(1,SL),
>
> // UNIT=R9840,
>
> // VOL=SER=E00002,
>
> // DISP=(OLD,KEEP)
>
> //SYSUT2 DD SYSOUT=\*
>
> //SYSPRINT DD SYSOUT=\*
>
> //SYSIN DD DUMMY

In the event of an actual disaster, we would eject tapes E00001 and
E00002 and send them to the disaster site with the other tapes. However,
if we were to do this for a test, then the weekend jobs attempting to
write the new dump information to these tapes would fail because the
tapes are not in our silo. To avoid this situation, we have assigned
tapes DR0001 and DR0002 with retention periods of 9999 days (which is
the maximum value allowed). After the dumps have been created for a
particular disaster test, the Storage Administrators should copy tape
E00001 to DR0001 and tape E00002 to DR0002. Tapes DR0001 and DR0002
should then be ejected and sent to the disaster site with the other
tapes. The JCL that can be used to create these copies is found in
NIH.STGADMIN.DIST.WORK.CNTL(COPYTAPE):

> //JDACOPY JOB (),'COPY DR TAPES',MSGCLASS=H,NOTIFY=\$JDA
>
> //\*
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //\* JOB TO COPY TAPES WITH DUMP INFORMATION (E00001 AND E00002) TO \*
>
> //\* TAPES (E00101 AND E00102) THAT CAN THEN BE EJECTED FOR A DISASTER
> \*
>
> //\* RECOVERY TEST \*
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //\*
>
> //COPY1 EXEC PGM=IEBGENER
>
> //SYSPRINT DD SYSOUT=\*
>
> //\*
>
> //SYSUT1 DD DSN=NIH.STGADMIN.DRMAIL,DISP=SHR
>
> //\*
>
> //SYSUT2 DD DSN=NIH.STGADMIN.DRMCOPY,
>
> // UNIT=R9840,
>
> // LABEL=(1,SL),RETPD=9999,
>
> // VOL=SER=(E00101),
>
> // DISP=(OLD,KEEP)
>
> //\*
>
> //SYSIN DD DUMMY
>
> //\*
>
> //COPY2 EXEC PGM=IEBGENER
>
> //SYSPRINT DD SYSOUT=\*
>
> //\*
>
> //SYSUT1 DD DSN=ZDB2DB2.DB2.DISKSAVE.DRTAPE,DISP=SHR
>
> //\*
>
> //SYSUT2 DD DSN=ZDB2DB2.DB2.DISKSAVE.DRCOPY,
>
> // UNIT=R9840,
>
> // LABEL=(1,SL),RETPD=9999,
>
> // VOL=SER=(E00102),
>
> // DISP=(OLD,KEEP)
>
> //\*
>
> //SYSIN DD DUMMY

Note that the data set names on tapes E00101 and E00102 is slightly
different (NIH.STGADMIN.DRMCOPY and ZDB2DB2.DB2.DISKSAVE.DRCOPY) than
those on tapes E00001 and E00002. Consequently, if you need to list the
data from either tape, adjust your JCL accordingly.

The data sets on all four tapes (E00001, E00002, DR0001, and DR0002) are
cataloged.

# Load FDRABR Software

FDRABR (Fast Dump Restore/Automatic Backup and Restore) is used to back
up and restore Titan volumes for disaster recovery purposes. FDRABR is
not installed on the hot site system; FDRABR must be installed before
proceeding with restoring the Titan volumes.

Several useful listings are created with every set of Titan backups:

-   DRLIST1 and DRLIST2 -- lists the dumps by volume name with the tape
    data set name and the tape volume containing the backup. These lists
    are automatically emailed to all members of the CITDCSSDRLISTINGS
    and CITDCSSAUTO groups each Saturday after backups have completed.

-   STGSVOLS or STGDVOLS -- lists the contents of each backup tape.

-   STGEJECT -- lists the backup tapes required to restore the system at
    the hot site. This list is also emailed to all members of the
    CITDCSSDRLISTINGS and CITDCSSAUTO groups.

-   STGATLST -- lists all tapes in the offsite ATL.

1)  Determine which LPAR is assigned to System 4 from the
    SunGard-supplied Web-based mainframe test plan in the table under
    the heading, LPAR Setup. Confirm the SunGard floor system is up and
    available to us.

2)  Logon to the floor system with the user ID **SG01** (logon range is
    SG01 through SG20).

3)  **[Copy the FDRABR software from tape to disk using the 9840 tape
    drives in Wood Dale.]{.underline}** Create the JCL to do this by
    modifying one of the existing IEBCOPY jobs contained in SRS.JCL.CNTL
    (on the SunGard floor system) to match the following JCL:

...... //SG01A JOB 'IEBCOPY-3490-TAPE',CLASS=A,

...... // TIME=10,NOTIFY=SG01,MSGCLASS=D

...... //COPY1 EXEC PGM=IEBCOPY,REGION=0K

...... //SYSPRINT DD SYSOUT=\*

...... //IN1 DD DSN=NIH.STGADMIN.DISTBKUP.STARTUP.**GXXXXV00**,

> ...... // VOL=SER=**E00XXX**,LABEL=(3,SL),
>
> ...... // UNIT=**CART9840**,DISP=(OLD,KEEP,KEEP)
>
> ...... //OUT1 DD DSN=SG01.STARTUP.CNTL,
>
> ...... // UNIT=3390,VOL=SER=**2A0CAT**,
>
> ...... // DISP=(NEW,CATLG,DELETE),SPACE=(TRK,(25,1,10),
>
> ...... // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160,DSORG=PO)
>
> ...... //SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1),RLSE)
>
> ...... //SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(5,1),RLSE)
>
> ...... //SYSIN DD \*
>
> ...... COPY OUTDD=OUT1,INDD=IN1
>
> ...... /\*
>
> ...... //
>
> where Gxxxxv00 is the most current startup volume (see STGSVOLS or
> STGDVOLS output),

E00xxx is the tape volume (see DRLIST1 output),

STGAMIN4 output is available in NIH.STGADMIN.PROD.JCL

**Note:** Check either STGSVOLS or STGDVOLS in the SHOWVOL section near
the end of the listing. Look for NIH.STGADMIN.DISTBKUP.STARTUP(0). The
GDG name will be shown along with the 9840 tape volume, file sequence
number, and creation date.

Save the JCL, and submit the job, noting the time and job number. Verify
the job completes successfully (Condition Code 0000).

> Job Number \_\_\_\_\_\_\_\_\_, Time Submitted \_\_\_\_\_\_\_\_\_\_,
> Cond Codes \_\_\_\_\_\_\_\_\_\_
>
> This IEBCOPY job creates the SG01.STARTUP.CNTL partitioned data set on
> VOL=SER=2A0CAT containing the following members:

+--------------+-------------------------------------------------------+
| #README      | Information                                           |
+--------------+-------------------------------------------------------+
| ABRSTART     | loads the FDR/ABR libraries at SunGard                |
|              |                                                       |
|              | closes the FDRABR (openexit) at SunGard               |
|              |                                                       |
|              | imports and assigns alias name (FDRABR.#) at SunGard  |
+--------------+-------------------------------------------------------+
| DRPEXTRA     | FDR (DRP) parm member extra for adhoc volumes         |
+--------------+-------------------------------------------------------+
| DRPJCL1      | FDR (DRP) production JCL for FDRDRP restores          |
+--------------+-------------------------------------------------------+
| DRPPARM1     | FDR (DRP) parm for system volumes                     |
+--------------+-------------------------------------------------------+
| DRPPARM2     | FDR (DRP) parm for Titan LIB volumes                  |
+--------------+-------------------------------------------------------+
| DRPPARM3     | FDR(DRP) parm for Titan database volumes              |
+--------------+-------------------------------------------------------+
| DRPPARM4     | FDR(DRP) parm for additional Titan volumes            |
+--------------+-------------------------------------------------------+
| EXTRAIEB     | Extra single IEBCOPY JCL                              |
+--------------+-------------------------------------------------------+
| INIQUICK     | used to initialize volumes                            |
+--------------+-------------------------------------------------------+
| INITVVDS     | used to initialize VVDs on volumes                    |
+--------------+-------------------------------------------------------+
| OLDIDCAM     | old JCL (import ABR catalog to SunGard catalog)       |
+--------------+-------------------------------------------------------+
| OLDZAPOP     | old JCL (disable ABR open exit routine)               |
+--------------+-------------------------------------------------------+
| RESTORE1     | restores ABRSYS and TMS001 volumes (control dataset,  |
|              | ABR catalog, and tape management data sets required   |
|              | by FDRABR).                                           |
+--------------+-------------------------------------------------------+
| SCRSM1       | old JCL (restores the SCRSM1 volume)                  |
+--------------+-------------------------------------------------------+
| SUNCICS      | used to load CICS volumes                             |
+--------------+-------------------------------------------------------+
| \*\*END\*\*  |                                                       |
+--------------+-------------------------------------------------------+

1)  **[Load the FDRABR software using the SunGard floor
    system.]{.underline}** Edit the **ABRSTART** member by replacing the
    dot (**.**) placeholders (in bold and underlined) with the
    appropriate digits, save the changes, and submit the job, noting the
    time and job number.

> //SG01A JOB (),\'FDR-LIBRARY\',CLASS=A,TIME=15,
>
> // MSGCLASS=D,NOTIFY=SG01
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //\* JCL FOR USE FOR DISASTER RECOVERY - ALL STEPS MUST COMPLETE \*
>
> //\* ASSUMPTIONS: GENERIC FOR 9840 CARTRIDGE = CART9840 \*
>
> //\* SYS MASTER CATALOG VOLID IS 2A0CAT \*
>
> //\* STEP1 RESTORES FDRABR SOFTWARE TO DR DASD \*
>
> //\* COPY INDD=((IN1,R)),OUTDD=OUT1 TO REPLACE MEMBERS \*
>
> //\* COPY INDD=IN1,OUTDD=OUT1 \*
>
> //\* STEP2 DISABLES FDRABR OPENEXIT ROUTINE \*
>
> //\* STEP3 IMPORTS THE ABR USERCAT TO DR MASTERCAT (CATALOG.V2A0CAT)
> \*
>
> //\* STEP4 CONNECTS ALIASES REQUIRED FOR DR \*
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //\* STEP 1: CHANGE IN1 GENERATION (####) AND INPUT TAPE (TTTTTT) \*
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //STEP1 EXEC PGM=IEBCOPY,REGION=0K
>
> //SYSPRINT DD SYSOUT=\*
>
> //IN1 DD DSN=PCC.OFFSITE.FDRLIB2.G0**[\...]{.underline}**V00,
>
> // UNIT=CART9840,VOL=SER=E00**[\...]{.underline}**,
>
> // LABEL=(1,SL),DISP=(OLD,KEEP,KEEP)
>
> //OUT1 DD DSN=SUN1.FDRABR.LOADLIB,UNIT=3390,VOL=SER=2A0CAT,
>
> // SPACE=(TRK,(425,15,50)),DISP=SHR
>
> //SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(3,3))
>
> //SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(3,3))
>
> //SYSIN DD \*
>
> COPY INDD=((IN1,R)),OUTDD=OUT1
>
> /\*
>
> //STEP2 EXEC PGM=FDRZAPOP,REGION=6144K
>
> //STEPLIB DD DSN=SUN1.FDRABR.LOADLIB,UNIT=3390,VOL=SER=2A0CAT,DISP=SHR
>
> //SYSPRINT DD SYSOUT=\*
>
> //SYSLIB DD DSN=SUN1.FDRABR.LOADLIB,UNIT=3390,VOL=SER=2A0CAT,DISP=SHR
>
> //SYSIN DD \*
>
> ZAP DISABLE=OPENEXIT
>
> /\*
>
> //STEP3 EXEC PGM=IDCAMS,REGION=0K
>
> //SYSPRINT DD SYSOUT=\*
>
> //SYSIN DD \*
>
> IMPORT CONNECT -
>
> OBJECTS( -
>
> (VSAM.VPCCX.CATALOG.ABRBASE -
>
> VOLUME(ABRSYS) -
>
> DEVICETYPE(3390))) -
>
> CATALOG(CATALOG.V2A0CAT)
>
> /\*
>
> //STEP4 EXEC PGM=IDCAMS,REGION=0K
>
> //SYSPRINT DD SYSOUT=\*
>
> //SYSIN DD \*
>
> DEFINE ALIAS (NAME(FDRABR) RELATE(VSAM.VPCCX.CATALOG.ABRBASE))
>
> DEFINE ALIAS (NAME(#) RELATE(VSAM.VPCCX.CATALOG.ABRBASE))
>
> /\*
>
> //
>
> Job Number \_\_\_\_\_\_\_\_\_, Time Submitted \_\_\_\_\_\_\_\_\_\_,
> Cond-Codes \_\_\_\_\_\_\_\_\_\_
>
> **Note:** Step 1 information can be found in DRLIST1.
>
> When this job is completed, the FDRABR software has been loaded, the
> open exit for FDR has been turned off, and the aliases (FDRABR and #)
> have been imported and attached to the SunGard catalog. Now ready to
> start loading the two volumes needed by FDRABR(DRP) disaster software

2)  **[Load the two (2) critical volumes needed by
    FDRABR.]{.underline}** Edit the **RESTORE1** member to restore
    ABRSYS and TMS001. **JCL changes are necessary by replacing the dot
    (.) placeholders (in bold and underlined) with the appropriate
    digits.** See the comments at the beginning of the JCL regarding the
    changes.

> Use DRLIST2 to find the following information for ABRSYS and TMS001:

-   Dataset names

-   Tape label information

-   Volume serial number of the 9840 backup tape

> //SG01ABR JOB (),\'CRITICAL-RESTORES\',CLASS=A,TIME=60,
>
> // NOTIFY=SG01,MSGCLASS=D
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //\* DR JCL TO RESTORE THE FIRST TWO CRITICAL VOLUMES: \*
>
> //\* ABRSYS (ABR CATALOGS) AND TMS001 (TMS CATALOGS) \*
>
> //\* ASSUMES: MCAT IS 2A0CAT; 9840 GENERIC DEVICE IS CART9840 \*
>
> //\* CHANGES REQUIRED (SEE DRLIST1 AND DRLIST2 OR TAPE E00001): \*
>
> //\* VERIFY CATALOG NAME=2A0CAT \*
>
> //\* CHANGE \'DISK1\' TO TARGET DASD ADDRESS \*
>
> //\* CHANGE \'TAPE1\' TO BACKUP (SOURCE) TAPE VOLUME NUMBER \*
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //ABRSYS EXEC PGM=FDRABR,REGION=4M
>
> //STEPLIB DD DSN=SUN1.FDRABR.LOADLIB,UNIT=3390,VOL=SER=2A0CAT,DISP=SHR
>
> //SYSPRINT DD SYSOUT=\*
>
> //SYSPRIN1 DD SYSOUT=\*
>
> //DISK1 DD UNIT=3390,VOL=SER=SG**[\....]{.underline}**,DISP=OLD
>
> //TAPE1 DD DSN=FDRABR.VABRSYS.C20**[\...]{.underline}**00,
>
> // UNIT=CART9840,VOL=SER=E00**[\...]{.underline}**,
>
> // LABEL=(1,SL),DISP=(OLD,KEEP,KEEP)
>
> //SYSIN DD \*
>
> RESTORE TYPE=FDR,CONFMESS=NO,CPYVOLID=YES,VOLRESET=YES
>
> SELECT VOL=ABRSYS,NVOL=SG**[\....]{.underline}**,TAPEDD=1
>
> /\*
>
> //TMS001 EXEC PGM=FDRABR,REGION=4M
>
> //STEPLIB DD DSN=SUN1.FDRABR.LOADLIB,UNIT=3390,VOL=SER=2A0CAT,DISP=SHR
>
> //SYSPRINT DD SYSOUT=\*
>
> //SYSPRIN1 DD SYSOUT=\*
>
> //DISK1 DD UNIT=3390,VOL=SER=SG**[\....]{.underline}**,DISP=OLD
>
> //TAPE1 DD DSN=FDRABR.VTMS001.C20**[\...]{.underline}**00,
>
> // UNIT=CART9840,VOL=SER=E00**[\...]{.underline}**,
>
> // LABEL=(2,SL),DISP=(OLD,KEEP,KEEP)
>
> //SYSIN DD \*
>
> RESTORE TYPE=FDR,CONFMESS=NO,CPYVOLID=YES,VOLRESET=YES
>
> SELECT VOL=TMS001,NVOL=SG70A1,TAPEDD=1
>
> /\*
>
> //
>
> //
>
> //\* \.....IF VOLUME IS (SMS) VOLUME USE BELOW CONTROL STATEMENT\.....
>
> RESTORE TYPE=FDR,CONFMESS=NO,CPYVOLID=YES,VOLRESET=YES,SMSPROT=NONE
>
> Submit the job.
>
> Job Number \_\_\_\_\_\_\_\_\_, Time Submitted \_\_\_\_\_\_\_\_\_\_,
> Cond-Codes \_\_\_\_\_\_\_\_\_\_

Verify the job completes successfully (Cond-Code 0000). The ABRSYS and
TMS001 volumes are now loaded.

**When all preceding steps have [successfully]{.underline} completed,
the volumes needed to IPL the system can be loaded. Fix any failures or
start over.**

# Restore System Volumes

The JCL for restoring the system volumes has been loaded with the FDRABR
software. The FDR(DRP) component of FDRABR is used to restore the
volumes. FDRDRP optimizes full volume recovery from ABR volume backups
and eliminates the need for coding extensive restore JCL. Necessary
information for performing the restores is retrieved from two sources,
the ABR catalog and information from the tape management system that
works with the FDRDRP software.

Make sure the STGSVOLS report and the SunGard DASD address chart are
handy. The SunGard DASD address chart lists the disk addresses and
indicates where each volume will be restored. The chart is prepared
based on information provided in the SunGard-supplied Web-based
mainframe test plan in the input box under the heading, Special DASD.

The following volumes are restored to IPL the system:

+-------------+-------+-------+-------+------------------------------+
| **Volume**  | **    | *     | *     | **Notes**                    |
|             | TSO** | *user | *Star |                              |
|             |       | cat** | ted** |                              |
|             | *     |       |       |                              |
|             | *Sess |       | **Ta  |                              |
|             | ion** |       | sks** |                              |
+=============+=======+=======+=======+==============================+
| ABRSYS      | Y     | .v    |       | Already loaded during the    |
|             |       | pccx. |       | load of FDRABR               |
+-------------+-------+-------+-------+------------------------------+
| TMS001      |       |       |       | Used with ABRSYS for DRP     |
|             |       |       |       | software                     |
+-------------+-------+-------+-------+------------------------------+
| BOOKS1      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| CICS00,     |       |       |       | Required to bring up CICS    |
| CICS01,     |       |       |       | regions. CICS00, CICS01,     |
| CICS03,     |       |       |       | CICS14, CICS15 restored by   |
| CICS06,     |       |       |       | FDR(DRP); CICS03, CICS06,    |
| CICS10,     |       |       |       | CICS10, CICS11 restored by   |
| CISC11,     |       |       |       | FDR/SUNCICS job.             |
| CICS14,     |       |       |       |                              |
| CICS15      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| DISR01,     |       |       |       | Disaster Recovery volumes    |
| DIST00,     |       |       |       | containing customer files,   |
| DIST01,     |       |       |       | including profiles           |
| DIST02      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| HBL101      |       |       |       | NHLBI Information System     |
+-------------+-------+-------+-------+------------------------------+
| JESCKA,     |       |       | JES2  |                              |
| JESCKB      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| JESSP1,     |       |       | JES2  |                              |
| JESSP2,     |       |       |       |                              |
| JESSRC      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| LIB001      | Y     |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| LIB002      | Y     | .     |       |                              |
|             |       | pub5. |       |                              |
+-------------+-------+-------+-------+------------------------------+
| LIB003      | Y     |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| LIB016      | Y     |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| LIB017      |       | .pcc. |       |                              |
+-------------+-------+-------+-------+------------------------------+
| LIB018      | Y     |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| LIB019      | Y     |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| MCATS4      |       | maste |       |                              |
|             |       | r-cat |       |                              |
+-------------+-------+-------+-------+------------------------------+
| MSTATS      |       |       |       | Contains multiple libraries  |
|             |       |       |       | for software products (e.g., |
|             |       |       |       | SAS, IRS, MARK IV)           |
+-------------+-------+-------+-------+------------------------------+
| MCATS9      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| NIHLBA      |       | u     |       | Should be at pre-determined  |
|             |       | serca |       | UCB address since the        |
|             |       | t.nih |       | address determines the IPL   |
|             |       |       |       | parameters                   |
+-------------+-------+-------+-------+------------------------------+
| NIHLBB      |       |       |       | Should be at pre-determined  |
|             |       |       |       | UCB address since the        |
|             |       |       |       | address determines the IPL   |
|             |       |       |       | parameters                   |
+-------------+-------+-------+-------+------------------------------+
| NIHLBC      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| NIHLBD      | tmgr  |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| NIHLBE      | s     |       |       |                              |
|             | hadow |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| NIHLBF      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| NIHLB1      | Y     |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| NIHLB2      | Y     |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| NIHLB3      | Y     |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| NIHLB4      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| NIHLB5      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| NIHLB6      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| OPSLG1,     |       |       |       |                              |
| OPSLG2      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| OPSLOG      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| PAGE01      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| PPCC12      |       | .     |       |                              |
|             |       | pub6. |       |                              |
+-------------+-------+-------+-------+------------------------------+
| PPCC13      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| RACFV1,     |       |       | RACF  |                              |
| RACFV2      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| SHR001,     |       |       |       |                              |
| SHR002,     |       |       |       |                              |
| SHR003      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| SMR001      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| SYSOPS      |       |       |       | Automated operations         |
|             |       |       |       | software                     |
+-------------+-------+-------+-------+------------------------------+
| SYS4R1      | Y     |       |       | Should be at pre-determined  |
|             |       |       |       | UCB address since the        |
|             |       |       |       | address determines the IPL   |
|             |       |       |       | parameters for system 4      |
+-------------+-------+-------+-------+------------------------------+
| SYS4R2      | Y     |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| SYS4R3      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| SYS9R1      |       |       |       | Should be at pre-determined  |
|             |       |       |       | UCB address since the        |
|             |       |       |       | address determines the IPL   |
|             |       |       |       | parameters for system 9      |
+-------------+-------+-------+-------+------------------------------+
| SYS9R2      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| SYS9R3      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCATAG      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCATHP      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCATQZ      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCAT01      |       | .u    |       |                              |
|             |       | cat01 |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCAT02      |       | .u    |       |                              |
|             |       | cat02 |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCAT03      |       | .u    |       |                              |
|             |       | cat03 |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCAT04      |       | .u    |       |                              |
|             |       | cat04 |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCAT05      |       | .u    |       |                              |
|             |       | cat05 |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCAT06      |       | .u    |       |                              |
|             |       | cat06 |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCAT07      |       | .u    |       |                              |
|             |       | cat07 |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCAT08      |       | .u    |       |                              |
|             |       | cat08 |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCAT09      |       | .u    |       |                              |
|             |       | cat09 |       |                              |
+-------------+-------+-------+-------+------------------------------+
| UCAT10      |       | .u    |       |                              |
|             |       | cat10 |       |                              |
+-------------+-------+-------+-------+------------------------------+
| WYL100      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| DB2P01,     |       |       |       | DB2 SMS volumes, initialized |
| DB2P02,     |       |       |       | only                         |
|             |       |       |       |                              |
| DB2P03,     |       |       |       |                              |
| DB2P04      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| DB2PS1,     |       |       |       | DB2 Non-SMS system volumes,  |
| DB2PS2,     |       |       |       | initialized only             |
| SYS         |       |       |       |                              |
| DB2,SSYDPR, |       |       |       |                              |
|             |       |       |       |                              |
| OSS         |       |       |       |                              |
| DB2,MASDB2, |       |       |       |                              |
| STGDB2      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| HSM101-71   |       |       | S     | HSM ML1 volumes              |
|             |       |       | yshsm |                              |
| HSMBC1      |       |       |       | HSM Control volumes          |
|             |       |       |       |                              |
| HSMBC2      |       |       |       |                              |
|             |       |       |       |                              |
| HSMJRL      |       |       |       |                              |
|             |       |       |       |                              |
| HSMMCD      |       |       |       |                              |
|             |       |       |       |                              |
| HSMOCD      |       |       |       |                              |
|             |       |       |       |                              |
| HSMPRM      |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| DSP101-189  |       |       |       | SMS Managed Public volumes   |
|             |       |       |       |                              |
| DSL101-259  |       |       |       |                              |
|             |       |       |       |                              |
| DSO010-107  |       |       |       |                              |
+-------------+-------+-------+-------+------------------------------+
| SCR999      |       |       |       | Non-SMS volume, initialized  |
|             |       |       |       | only. Must be at UCB address |
|             |       |       |       | GENed as MSS, PUB, SYSDA,    |
|             |       |       |       | SYSSQ, SYSTS, and TMP.       |
+-------------+-------+-------+-------+------------------------------+

The following database volumes are restored with the system volumes:

  ----------- -----------------------------------------------------------
  M204:       M20401, M20402, M20403, M20404, M20405, M20406,
              M20407,M20408, M20409, M20410

  IMS:        IMS001, IMS002, IMS003, IMS004
  ----------- -----------------------------------------------------------

The following user volumes are restored with the system volumes:

  ----------- -----------------------------------------------------------
  NIH:        ODA103, ODA104, ODA105, ODA106 (Administrative Database)

  NIH:        OFM101, OFM102 (Central Accounting System)

  NIH:        DRG001, DRG002, DRG003, DRG004, DRG005, DRG006 (IMPAC and
              CRISP)

  PSC:        ESC101, ESC102, ESC103, ESC104, ESC105, ESC106 (DHHS
              Civilian Payroll System)

  PSC:        FAF104 (Payment Management System)
  ----------- -----------------------------------------------------------

# Load DASD Using FDR(DRP) Software

1)  Using ISPF EDIT (2):

> EDIT NIH.STGADMIN.DIST.STARTUP.CNTL
>
> Command ===\>
>
> Name Prompt Size Created
>
> \_\_\_\_\_\_\_\_\_\_DRPJCL
>
> \_\_\_\_\_\_\_\_\_\_DRPJCLC
>
> \_\_\_\_\_\_\_\_\_ DRPPARMA \*Edited 3 2005/07/20
>
> \_\_\_\_\_\_\_\_\_\_DRPPARMB 54 2006/05/05
>
> \_\_\_\_\_\_\_\_\_\_DRPPARMC 135 2006/05/05
>
> \_\_\_\_\_\_\_\_\_\_DRPPARMD 68 2006/05/05
>
> \_\_\_\_\_\_\_\_\_\_DRPPARME 80 2006/05/05
>
> \_\_\_\_\_\_\_\_\_\_DRPPARMF 72 2006/05/05

a)  Submit member **DRPJCL** (sample JCL below).

b)  Submit member **DRPJCLC**

> Job Number \_\_\_\_\_\_\_\_\_, Time Submitted \_\_\_\_\_\_\_\_\_\_,
> Cond-Codes \_\_\_\_\_\_\_\_\_\_
>
> Sample JCL:
>
> //SG01DRP1 JOB \'TITAN RESTORE\',CLASS=A,TIME=900,
>
> // NOTIFY=SG01,MSGCLASS=D
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //\* FOLLOWING STEP ALLOWS DB2 TO BE RESTORED ALONGSIDE SUN BACKUPS \*
>
> //\* USE THIS JOB \*ONLY\* ON SUNGARD FLOOR SYSTEM \*
>
> //\* RESTORE (PGM=FDRDRP) (V53. LEVEL59) USING 9840 TAPE DRIVES \*
>
> //\* ASSUMES: CATALOG VOLSER IS Z14CAT, NO OTHER CHANGES NEEDED \*
>
> //\* 11/15/04 DOB INCREASED REGION FROM 64M TO 0M \*
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //STEP1 EXEC PGM=FDRDRP,REGION=0M
>
> //STEPLIB DD DSN=SUN1.FDRABR.LOADLIB,UNIT=3390,VOL=SER=Z14CAT,DISP=SHR
>
> //SYSPRINT DD SYSOUT=\*
>
> //SYSPRIN1 DD SYSOUT=\*
>
> //SYSIN DD DSN=SG01.STARTUP.CNTL(DRPPARMA),DISP=SHR
>
> /\*
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //\* USE THIS JOB \*ONLY\* ON SUNGARD FLOOR SYSTEM \*
>
> //\* RESTORE (PGM=FDRDRP) (V53. LEVEL59) USING 9840 TAPE DRIVES \*
>
> //\* ASSUMES: CATALOG VOLSER IS Z14CAT, NO OTHER CHANGES NEEDED \*
>
> //\* 11/15/04 DOB INCREASED REGION FROM 64M TO 0M \*
>
> //\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
>
> //STEP2 EXEC PGM=FDRDRP,REGION=0M
>
> //STEPLIB DD DSN=SUN1.FDRABR.LOADLIB,UNIT=3390,VOL=SER=Z14CAT,DISP=SHR
>
> //SYSPRINT DD SYSOUT=\*
>
> //SYSPRIN1 DD SYSOUT=\*
>
> //SYSIN DD DSN=SG01.STARTUP.CNTL(DRPPARMB),DISP=SHR
>
> /\*
>
> //
>
> //\* SUBMIT MEMBER DRPJCLC NEXT

**NOTE: While the FDR(DRP) restore jobs are executing, you can restore
the CICS volumes and initialize the public volumes while you are
waiting.**

2)  **[When the restore jobs have completed, enter the following command
    to verify that all required volumes (see previous table) have been
    restored and are on-line.:]{.underline}**

> D U

# Restore CICS Database Volumes

The FDR component of FDRABR is used to restore the database volumes of
CICS.

Make sure the STGSVOLS report and the SunGard DASD address chart are
handy.

The following CICS database volumes are to be restored: CICS03, CICS06,
CICS10, CICS11

1)  Using ISPF (3.4) DSLIST:

> EDIT **NIH.STGADMIN.DIST.STARTUP.CNTL** on ABRSYS
>
> Name Size Created Changed ID
>
> \_\_\_\_\_\_\_\_\_SUNCICS 53 2001/10/08 2003/12/01 \$RYM

2)  Select and edit member **SUNCICS**; and change if necessary: data
    set names, volume serial numbers, and unit addresses. Each Step will
    restore the CICS volume associated with it.

> Submit the job, noting the times and job numbers. Verify job
> successfully complete (Cond-Code 0000).

Job Number \_\_\_\_\_\_\_\_\_, Time Submitted \_\_\_\_\_\_\_\_\_\_,
Cond-Codes \_\_\_\_\_\_\_\_\_\_\_

If any of the jobs failed, they must be re-run after making appropriate
adjustments before proceeding to the initialization of public volumes.

# Initialize Volumes

Empty volumes will be initialized for DB2 and general public work space
for DR testing.

1)  Using ISPF (3.4) DSLIST:

> EDIT **NIH.STGADMIN.DIST.STARTUP.CNTL** on ABRSYS
>
> Members you will need:
>
> **Name Size Created Changed ID**
>
> \_\_\_\_INIQUICK 99 2001/02/15 2002/03/12 \$RYM
>
> \_\_\_\_INITVVDS 65 2001/02/15 2002/03/12 \$RYM

Edit the **INIQUICK** member, sample JCL:

//SG01INI JOB (),\'FDR-LIBRARY\',CLASS=A,TIME=15,

// MSGCLASS=D,NOTIFY=SG01

.

.

//\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

//\* NON-SMS VOLUME(S) \*

//\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

//NSMS1 EXEC PGM=ICKDSF,REGION=6144K

//SYSPRINT DD SYSOUT=\*

//SYSIN DD \*

INIT UNITADDRESS(**4450**) VERIFY(**SG4450**) VOLID(**SCR999**) -

DEVTYPE(3390) INDEX(10,00,15) VTOC(11,00,60) -

MAP NOCHECK NOVALIDATE

/\*

.

.

.

.

> Verify **all** of the INIT statements have correct UNITADDRESS,
> VERIFY, and VOLID parameters; the other parms will not change.

2)  Before submitting the job, go to the Titan console and use the VARY
    command to take each of the volumes off-line, e.g.:

> VARY 4480,OFFLINE (continue until all volumes have been taken offline)

3)  Submit the job, and respond to each system prompt with:

> nnU where nn = the number of the prompt
>
> Wait for the job to successfully complete (Cond-Code 0000).
>
> Job Number \_\_\_\_\_\_\_\_\_, Time Submitted \_\_\_\_\_\_\_\_\_\_,
> Cond-Codes \_\_\_\_\_\_\_\_\_\_

4)  Go to the Titan console to use the VARY command to put each of the
    volumes on-line, e.g.:

> VARY 380,ONLINE (continue until all of the nineteen have been placed
> back online)

5)  Use the MOUNT command to mount all of the volumes, e.g.:

> M 4480,VOL=(SL,DSL101)

6)  Use the D U to verify the volumes are mounted, e.g.:

> D U,,,4480,1 This will display the volume and where it is mounted.

# IPL the System

IPL System 4 first, then System 9. The following instructions, with
differences noted, apply to IPL'ing both LPARs.

**\*\*\*\* IMPORTANT REMINDERS \*\*\*\***

**Whenever any disk volumes are restored to one LPAR after both LPARs
have been IPL'ed, the restored disk volumes MUST be varied offline and
online on the other LPAR. If this is not done, any attempts to access
the disk volumes on the other LPAR [will fail]{.underline}.**

**If you need to re-IPL the system, shut the system down per the
instructions below under *Shut Down the System*.**

**To logon from one of the Herndon PCs after the system has been IPL'ed,
use the following command:**

> **LOG APPLID(TSO*n*) where n is the system number (i.e., 4 or 9)**

**To retrieve Operator commands from the Herndon PCs that have been
designated as the Titan Operator consoles, use the numeric keypad minus
(-) key (located at the upper right corner of the numeric keypad).**

1)  Verify the load address and the load parameter.

  -----------------------------------------------------------------------
  **[SYS4:]{.underline}** The load address must be the UCB address of the
  disk SYS4R1 and the format of the load parameter must be aaaa4DM where
  aaaa is the UCB address of the disk containing the IPLPARM and IODF
  data sets which reside on NIHLBB.

  **[SYS 9:]{.underline}** The load address must be the UCB address of
  the disk SYS9R1 and the format of the load parameter must be aaaa9DM
  where aaaa is the UCB address of the disk containing the IPLPARM and
  IODF data sets which reside on NIHLBB.
  -----------------------------------------------------------------------

The addresses for these 3 volumes will always be:

> SYS4R1 - xx02
>
> SYS9R1 - xx03
>
> NIHLBB - xx04

The 'xx' value will depend on the range of addresses assigned by
SunGard. For example, if the address range is 78xx through 78yy, then
the respective addresses for these volumes would be:

> SYS4R1 -- 7802
>
> SYS9R1 -- 7803
>
> NIHLBB -- 7804

The load address and load parms would then be:

> SYS4 - Load address = 7802
>
> Load parm = 78044DM
>
> SYS9 - Load Address = 7803
>
> Load parm = 78049DM

Provide the load address and the load parameter to the SunGard
personnel.

2)  The Operators will initiate the load.

3)  The Master Console screen displays blue colored messages. Prompts
    pertaining to DASD volumes may appear. Respond accordingly.

4)  The date and time on the console should be correct. If not, contact
    the SunGard personnel.

5)  The Master Console screen should begin displaying green colored
    messages. You should see the following message regarding the sysplex
    environment:

> IXC418I SYSTEM SYSX IS NOW ACTIVE IN SYSPLEX TITAN
>
> The operating system will issue start commands for a number of Started
> Tasks (STCs).

6)  After OPSMAIN4/OPMSMAIN9 initializes, it will issue the following
    WTOR, requesting directions pertaining to the activation of System
    State Manager (SSM):

> nn SSMBEGIN ENTER DESIRED STATEMAN STARTUP OPTION (1-5) AND/OR MODE
> (A/P/I):

During the first IPL, place STATEMAN into PASSIVE mode. This will enable
you to start the desired STCs and respond to WTORs without any
interference from Automation. Issue the following response to place
STATEMAN into PASSIVE mode:

> R nn,1P
>
> [**Note:** **Since OPSMVS is started with PASSIVE mode, all tasks will
> be started manually.**]{.underline}

7)  If the automatic rule fails, then issue the following commands:

> OPSAOF disable TOD
>
> OPSAOF disable MSG.\$HASP400
>
> OPSAOF disable MSG.\$HASP426
>
> OPSAOF disable MSG.IST051A
>
> OPSAOF disable CMD.\$S
>
> OPSAOF disable STD.EZZ4324I.
>
> OPSAOF disable STD.EZZ0403I.
>
> OPSAOF disable MSG.EZZ4324I.
>
> OPSAOF disable STD.SHADTOD
>
> OPSAOF disable STD.SHADTOD1
>
> OPSAOF enable STD.DR.
>
> OPSAOF Resetauto MSG.\$HASP400
>
> OPSAOF Resetauto MSG.\$HASP426
>
> OPSAOF Resetauto MSG.IST051A
>
> OPSAOF Resetauto TOD

8)  Start JES2.

The first time the system is IPL'ed, JES2 will have to be started
manually because JES2 will have to be COLD started. All subsequent IPLs
(such as bringing up System 9) will require a warm start.

Issue the following command:

  ------------------------------------ ----------------------------------
  **[SYS4:]{.underline}** S            **[SYS9:]{.underline}** S
  JES2,DEV=DR,PARM=COLD                JES2,DEV=DR

  ------------------------------------ ----------------------------------

The following non-highlighted message will appear on the console:

> \$HASP400 ENTER REQUEST JES2 READY
>
> After this message appears, issue the command to activate JES2: \$S

The following printers are assigned to the Titan JES2 at the disaster
site:

  ------------------------------------------------------------------------
  ***Printer Model*** ***Location***         ***Printer     ***Unit
                                             Number***      Address***
  ------------------- ---------------------- -------------- --------------
  3900                Reference test plan    PRT30          Reference test
                                                            plan

  4245                Reference test plan    PRT11          Reference test
                                                            plan

  4245                Reference test plan    PRT12          Reference test
                                                            plan
  ------------------------------------------------------------------------

Set the Unit Address for PRT30 by issuing the command:

> \$TPRT30,UNIT=cuu
>
> where cuu is the unit address obtained from the SunGard web-based test
> plan

9)  If this is the initial manual IPL and JES2 is being cold started,
    issue the following command to also cold start ThruPut Manager:

+-----------------------------------------------------------------------+
| **[SYS4:]{.underline}** S TM,CF=COLD,CMF=COLD,VIF=COLD                |
|                                                                       |
| Reply \'nnY\' to the following messages.                              |
|                                                                       |
| > DTM6007A IS A CONTROL FILE COLD START AUTHORIZED? REPLY \'Y\' OR    |
| > \'N\'                                                               |
| >                                                                     |
| > DTM0805A IS A VIF COLD START AUTHORIZED? REPLY \'Y\' OR \'N\'       |
| >                                                                     |
| > DTM7152A IS A DCS CMF FILE COLD START AUTHORIZED? REPLY \'Y\' OR    |
| > \'N\'                                                               |
|                                                                       |
| The following messages will appear on the console:                    |
|                                                                       |
| > DTM0023I TMSS INITIALIZATION COMPLETE                               |
| >                                                                     |
| > DTM6422I JLS RECONCILE COMPLETE                                     |
| >                                                                     |
| > DTM7153I THE DCS CMF FILE IS BEING FORMATTED                        |
| >                                                                     |
| > DTM7154I THE DCS CMF FILE HAS BEEN FORMATTED (7200 BLOCKS, 600      |
| > TRACKS)                                                             |
| >                                                                     |
| > DTM2224I THRUPUT MANAGER VERSION 5 RELEASE 2.2 PTF TMT5212          |
|                                                                       |
| After these messages appear, enter the following commands on the      |
| System 4 console:                                                     |
|                                                                       |
| > %TM BATCH NIH.TMGRPROD.DRFOUR.COMMAND                               |
| >                                                                     |
| > %JAL EVENT ON DISASTER                                              |
|                                                                       |
| **Note 1:** The first command defines a group of AGENT names and      |
| activates the agents on SYS4.                                         |
|                                                                       |
| **Note 2 (Important):** The second command turns on a Thruput Manager |
| 'Event' named DISASTER. When the DISASTER event is turned on, all     |
| jobs submitted by CA-7 are placed in 'Operator Hold' and are          |
| [not]{.underline} executed. Jobs that are held by this facility can   |
| be released with the Thruput Manager command:                         |
|                                                                       |
| > %JSS RELEASE '*JOBNAME*'                                            |
| >                                                                     |
| > or                                                                  |
| >                                                                     |
| > %JSS RELEASE *JES2 Job Number*                                      |
|                                                                       |
| If all jobs submitted from CA-7 are to be executed, issue the         |
| following command:                                                    |
|                                                                       |
| > %JAL EVENT OFF DISASTER                                             |
|                                                                       |
| To view the status of Thruput Manager events, issue the following     |
| command:                                                              |
|                                                                       |
| > %JAL EVENT DISPLAY                                                  |
+-----------------------------------------------------------------------+
| **[SYS9:]{.underline}** S TM                                          |
|                                                                       |
| The following message will appear on the console:                     |
|                                                                       |
| > DTM2224I THRUPUT MANAGER VERSION 5 RELEASE 2.2 PTF TMT5212          |
|                                                                       |
| After this message appears, enter the following commands on system 9  |
| console:                                                              |
|                                                                       |
| > %TM BATCH NIH.TMGRPROD.DRNINE.COMMAND                               |
| >                                                                     |
| > %JAL EVENT ON DISASTER                                              |
|                                                                       |
| **Note 1:** The first command defines a group of AGENT names and      |
| activates the agents on SYS9.                                         |
|                                                                       |
| **Note 2 (Important):** The second command turns on a Thruput Manager |
| 'Event' named DISASTER. When the DISASTER event is turned on, all     |
| jobs submitted by CA-7 are placed in 'Operator Hold' and are          |
| [not]{.underline} executed. Jobs that are held by this facility can   |
| be released with the Thruput Manager command:                         |
|                                                                       |
| > %JSS RELEASE '*JOBNAME*'                                            |
| >                                                                     |
| > or                                                                  |
| >                                                                     |
| > %JSS RELEASE *JES2 Job Number*                                      |
|                                                                       |
| If all jobs submitted from CA-7 are to be executed, issue the         |
| following command:                                                    |
|                                                                       |
| > %JAL EVENT OFF DISASTER                                             |
|                                                                       |
| To view the status of Thruput Manager events, issue the following     |
| command:                                                              |
|                                                                       |
| > %JAL EVENT DISPLAY                                                  |
+-----------------------------------------------------------------------+

> All subsequent TM restarts on SYS4 and SYS9 will require a warm start
> using the following command:
>
> S TM

10) Manually start the following tasks.

> Issue the commands to start MIM and MIA (that allow shared DASD and
> tapes):

+-----------------------------------------------------------------------+
| **[SYS4:]{.underline}**                                               |
|                                                                       |
| > S SYSMIM,FORMAT=BOTH,MEMBER=MIMINTDR                                |
| >                                                                     |
| > S SYSMIA,FORMAT=CF,MEMBER=MIAINTDR                                  |
+-----------------------------------------------------------------------+
| **[SYS9:]{.underline}**                                               |
|                                                                       |
| > S SYSMIM,FORMAT=CKPT,MEMBER=MIMINTDR                                |
| >                                                                     |
| > S SYSMIA,MEMBER=MIAINTDR                                            |
+-----------------------------------------------------------------------+

> Issue the following commands:

+-----------------------------------------------------------------------+
| **[SYS4:]{.underline}**                                               |
|                                                                       |
| > S SLAMRUN                                                           |
| >                                                                     |
| > S TCPIP                                                             |
| >                                                                     |
| > S TN3270                                                            |
| >                                                                     |
| > S TCAS                                                              |
| >                                                                     |
| > S EMSPROC                                                           |
| >                                                                     |
| > S SYSVPSP                                                           |
| >                                                                     |
| > S SMR                                                               |
| >                                                                     |
| > S SRVVPSP                                                           |
| >                                                                     |
| > S DRSVPI                                                            |
| >                                                                     |
| > S GSSA                                                              |
| >                                                                     |
| > S BBVTAS.ZZUZPZO,SUF=P3                                             |
| >                                                                     |
| > S BABCAS                                                            |
| >                                                                     |
| > S MVSPAS                                                            |
| >                                                                     |
| > S ENF                                                               |
| >                                                                     |
| > S NDMP                                                              |
| >                                                                     |
| > The Storage Group will start HSM                                    |
|                                                                       |
| **Note 1:** After CCITCP and CCITCPGW are started, please inform TC   |
| Chen, so he can check their status.                                   |
|                                                                       |
| **Note 2:** If SMPTP does not come up because it is looking for data  |
| sets on public volumes, uncatalog all NIH.TCPIP.SMTP.\* data sets and |
| reissue the start command.                                            |
|                                                                       |
| > S SMTP                                                              |
+-----------------------------------------------------------------------+
| **[SYS9:]{.underline}**                                               |
|                                                                       |
| > S SLAMRUN                                                           |
| >                                                                     |
| > S TCPIP                                                             |
| >                                                                     |
| > S TN3270                                                            |
| >                                                                     |
| > S TCAS                                                              |
| >                                                                     |
| > S BABCAS                                                            |
| >                                                                     |
| > S SMR                                                               |
| >                                                                     |
| > S MVSPAS                                                            |
| >                                                                     |
| > The Storage Group will start HSM                                    |
+-----------------------------------------------------------------------+

11) Issue the following command to start the NJE connection to
    production Titan (for tests only):

> \$SN,A=NIHJES2
>
> **NOTE:** Make sure JES2 and Enterprise Extender are up and running
> before issuing this command.

12) **After both SYS4 and SYS9 are up, verify that all tape drives are
    online to both LPARs so that batch jobs won't hang or get
    cancelled.**

13) After all the above tasks have been started, CICS and M204 can be
    started. Notify appropriate staff to start these subsystems.

> For the December 2 - 4, 2007 test, notify:
>
> Ed Ryan at 301-496-1452 (CICS)
>
> Hoyt Carelock at 301-435-5488 (M204)

14) DB2 and Oracle client

```{=html}
<!-- -->
```
a)  Call either Ed Ryan at 301-496-1452, Angela Bennett at 301-435-5491,
    or Charles Green at 301-402-8523 to start DB2.

b)  If, prior to the backups that have been restored for the disaster
    recovery test, NIH.SHADOW.TITNSLK.SDBP.NIH.EXEC(SDBPIN00) had not
    been updated with the "emergency license code" for Shadow Direct,
    update the NIH.SHADOW.TITNSILK.SDBP.NIH.EXEC(SDBPIN00) to replace
    the LICENSECODE with the "emergency license code" obtained prior to
    the test.

c)  Verify that SYS9 is available.

d)  Start DSNP and the Oracle client on Titan by submitting the
    following job:

> ZDB2DB2.CA7.DSNP.JCL(DB2PWSTR)
>
> **Note:** This job issues an OPS message to Restart DSNP, and its
> related Oracle and Shadow jobs. At DR it will use the temporary
> license for Shadow Direct, so SDBP will remain UP. However, at DR,
> Shadow Web Server - SWSP - will fail because there is no license. This
> is as planned since we do NOT want SHADSWSP executing at DR.

e)  Perform a quick test of DSNP

f)  Verify that SWSP is DOWN.

    15. IMS **(SYS4 ONLY)** -- **<During> DR tests, IMS is brought up
        manually via a COLD start.** [Since the IMS testing at the DR
        site does not involve accessing DB2, there is no need for DB2 to
        be started prior to staring IMS. If there are any problems
        starting IMS, please call Pete Nordyke at 301-402-1246, Clyde
        Colmes at 301-496-6244, or Ed Ryan at 301-496-1452.]{.underline}

> **[To bring up IMS during a DR test, always issue a COLD start as
> follows:]{.underline}**

a)  Run batch job from IMSVS.V9R1.TITAN.P.SRCLIB(RCONREST)

b)  S IMS9DR

c)  When IMS puts out a WTOR \"nn DFS810A IMS READY\",

> Enter: REPLY nn,/NRESTART CHECKPOINT 0 FORMAT ALL

d)  When you see "nn DFS996I \*IMS READY\* PROD" on the console log,

> Enter: REPLY nn,/START TRAN IMS\* JAH\* IXX\*

e)  When you see \"nn DFS996I \*IMS READY\* PROD\" on the console log,

> Enter: REPLY nn,/START REG IMS9PMP8

f)  When you see \"nn DFS996I \*IMS READY\* PROD\" on the console log,

> Enter: REPLY nn,/START DC

g)  When you see \"nn DFS996I \*IMS READY\* PROD\" on console log,

> Enter: REPLY nn,/START LINE 3 PTERM ALL

h)  When you see \"nn DFS996I \*IMS READY\* PROD\" on console log,

> Enter: REPLY nn,/START LINE 2 PTERM ALL

i)  S IMS9PRDR,MBR=JESCMDS1

> **[APPC must be disabled at the DR site]{.underline}**.
>
> In order to avoid a repeat of the July, 2006 problem whereby some IMS
> users who signed on at NIH got the DR site instead (or vice versa),
> APPC must be disabled at the DR site.
>
> The IMS proc for DR has been modified so that IMS at the DR site comes
> up with APPC disabled. To verify this:

-   Logon to IMS at the DR site.

-   Verify that you are connected at the DR site.

-   Display APPC status via the /DIS APPC command.

-   If APPC is enabled at DR, disable it with the /STOP APPC command.

> An alternative is:

-   Verify that IMS started OK at the DR site.

-   Bring IMS down at the DR site.

-   The next morning, after IMS has been started at NIH, restart IMS at
    the DR site.

-   Logon to IMS at the DR site.

-   Verify that you are connected at the DR site.

-   Display APPC status via the /DIS APPC command.

-   If APPC is enabled at the DR site, disable it with the /STOP APPC
    command.

**[The procedures for an IMS warm start are included here for
documentation purposes only:]{.underline}**

a)  S IMS9DR

b)  When IMS puts out a WTOR \"nn DFS810A IMS READY\",

> Enter: REPLY nn,/NRESTART

c)  When IMS puts out a WTOR \"nn DFS996I \*IMS READY\* PROD\" then,

> Enter: START IMSVTAM

d)  You will see "nn DFS996I \*IMS READY\* PROD" on the console log,

> Enter: REPLY nn,/START TRAN IMS\* JAH\* IXX\*

e)  You will see \"nn DFS996I \*IMS READY\* PROD\" on the console log,

> Enter: REPLY nn,/START REG IMS9PMP8

f)  You will see \"nn DFS996I \*IMS READY\* PROD\" on the console log,

> Enter: REPLY nn,/START DC

g)  When you see \"nn DFS996I \*IMS READY\* PROD\" on the console log,

> Enter: REPLY nn,/START LINE 3 PTERM ALL

h)  When you see \"nn DFS996I \*IMS READY\* PROD\" on the console log,

> Enter: REPLY nn,/START LINE 2 PTERM ALL

i)  S IMS9PRDR,MBR=JESCMDS1

# SYSHSM

All volumes necessary for production SYSHSM have now been restored and
all Disaster Tape volumes have been transported to the Disaster site.

Do the following to bring up SYSHSM at the DR site.

1)  Edit Syshsm.parmlib(arccmd04):

> Insert the following: SETSYS DISASTERMODE
>
> Change setsys DUPLEX to NO for both Backup and Migration
>
> Add the Hold All to the end of arccmd04

2)  Start SYSHSM

3)  Verify that Initialization completed successfully; correct any
    errors.

4)  Once Initialization is complete, issue: TSO HSEND RELEASE TAPEREPL

5)  Issue: TSO HSEND TAPEREPL ALL DAVOLUMES

6)  Issue: TSO HSEND RELEASE RECALL

7)  Test Recall of a dataset on ML2. If the subsequent tape mount calls
    for a H2\* volume, then Syshsm is functional.

8)  Issue: TSO HSEND RELEASE ALL

9)  Issue: TSO HSEND HOLD BACKUP MIGRATION (For DR Test only)

In the event of a real Disaster all H2\* should be available. It will be
necessary to reconcile the H2 tapes currently in use with those H2 tapes
available as HSM scratch tapes.

Issue TSO HSEND LIST TTOC ODS(\'\$DOB.TTOC.ALL.JAN21A\') DSI from the
TSO command line of from ISPF 6.

Edit the Output dataset. Sort the data by cols 2-7. Any tape number not
listed needs to be added to HSM via the Addvol command as either a
Backup or Migration tape as needed.

See DFSMShsm Storage Administration Reference for details. It is
available on Bookmanager.

# Workload Manager (WLM)

Once the system is IPL'ed and TSO is available, the standard Titan
Workload Manager policy (TTANSTD) can be installed into the WLM DR
couple datasets and activated. Until that is done, an IBM default policy
will be in effect and not conducive to our system environment as
activity picks up.

Do the following to install TITANSTD:

1)  Logon to TSO and go into the ISPF command screen (6).

2)  Enter: EX 'SYS1.SBLSCLI0(IWMARIN0)'

3)  Select "Read Saved Definition", from NIH.WLM.SYS4DR.PDS

4)  Select "Install" from the "Utilities" bar at the top.

5)  Select "Activate" from the "Utilities" bar at the top.

> (An alternative would be the console command: V WLM,POLICY=TITANSTD)

6)  Select "Exit" from the "File" bar at the top.

You can double-check for our policy TITANSTD activation using the
console command:

> D WLM,SYSTEM=SYS4

**Note:** This is SYSPLEX-wide, and will also be in effect on SYS9 if it
is up -- or when it does come up.

# Manual START Commands

In case you need to manually start various tasks, Section 9 of the Titan
System Programmers Handbook should have most of the information you need
to do this.

To see how OPS/MVS would normally bring up a started task, begin by
looking at the data set SYS1.SYSn.PROCLIB(OPSMAINn) where \"n\" is the
system in question. Then look at the data sets allocated to the SYSEXEC
ddname. Look for member names beginning with the string \"START...\".
Then look for the text \"issue\" and you will generally be close to the
command that OPS/MVS would issue. To see how OPS/MVS would stop the
task, look at the member names beginning with \"STOP...\".

# Shutdown Procedures

## Shut Down the System

1)  Before shutting down the system, DB2 needs to be terminated as
    follows:

> Call the DB2 support person to submit the following job for stopping
> DSNP and the Oracle client on Titan.
>
> ZDB2DB2.CA7.DSNP.JCL(DB2PWSTP)
>
> **Note:** Initiator must be available before executing the job.

2)  Issue the following command on the console for the system you are
    shutting down:

> SHUTDOWN ENTIRE SYSTEM NOW

3)  Reply "U" to "accept", then "N" to "shutdown now" in response to
    SSMSHUT request from OPS System State Manager.

4)  Reply "5" to SSMBEGIN start option to select the "Use current
    desired state and no schedule" option.

5)  After started tasks are terminated, if the other system is still up,
    issue

> VARY XCF,SYSn,OFFLINE
>
> where n = 4 or 9, the number of the system you are shutting down. This
> removes the system from the Sysplex.

6)  Reply "SYSNAME=SYSn" (where n = 4 or 9) to message IXC371D "Confirm
    request to vary system offline".

7)  Reply "DOWN" to message IXC102A "XCF is waiting for system SYSn
    deactivation" on the other system.

## Shut Down IMS

Use the following procedure in TSO Option \'S.OPS\' (AutoOps):

1)  Issue the following operator command to get the number of the
    Outstanding IMS message:

> /D R,L
>
> The following example is the response from the July 2005 test:
>
> 20JUL 15:13:10 D R,L
>
> 20JUL 15:13:10 IEE112I 15.13.10 PENDING REQUESTS 742
>
> 20JUL 15:13:10 RM=7 IM=0 CEM=0 EM=0 RU=0 IR=0 NOAMRF
>
> 20JUL 15:13:10 ID:R/K T TIME JOB ID MESSAGE TEXT
>
> 20JUL 15:13:10 **97** R 15.11.38 04S17361 \*97 DFS996I \*IMS READY\*
> TEST

2)  Issue the following operator command to display active the IMS
    regions:

> 97/dis a
>
> The following example is the response from the July 2005 test:
>
> R 97,/DIS A
>
> IEE600I REPLY TO 97 IS;/DIS A
>
> DFS000I REGID JOBNAME TYPE TRAN/STEP PROGRAM STATUS
>
> DFS000I 2 IMS7TMP1 TPE WAITING
>
> DFS000I 1 IMS7TMP5 TPE WAITING
>
> DFS000I JMPRGN JMP NONE
>
> DFS000I JBPRGN JBP NONE
>
> DFS000I BATCHREG BMP NONE
>
> DFS000I DBTRGN DBT NONE
>
> DFS000I IMS7TRC DBRC
>
> DFS000I IMS7TSAS DLS
>
> DFS000I VTAM ACB OPEN -LOGONS ENABLED
>
> DFS000I IMSLU=NIH.APPCIMST APPC STATUS=ENABLED TIM
>
> DFS000I OTMA GROUP=N/A STATUS=NOTACTIVE
>
> DFS000I APPLID=IMSTEST GRSNAME= STATUS=DISABLED
>
> DFS000I LINE ACTIVE-IN - 1 ACTIV-OUT - 0
>
> DFS000I NODE ACTIVE-IN - 0 ACTIV-OUT - 0

3)  Issue the following command to stop an IMS region:

> /mm/STOP REGION n (where mm is the new outstanding message id and n is
> the region ID)
>
> The following example is from the July 2005 test.
>
> R 98,/STOP REGION 2
>
> IEE600I REPLY TO 98 IS;/STOP REGION 2
>
> DFS058I 15:13:44 STOP COMMAND IN PROGRESS
>
> DFS058I 15:13:44 STOP COMMAND IN PROGRESS TEST
>
> 99 DFS996I \*IMS READY\* TEST
>
> DFS552I MESSAGE REGION IMS7TMP1 STOPPED ID=00002 TIME=1513 TEST
>
> DFS552I MESSAGE REGION IMS7TMP1 STOPPED ID=00002 TIME=1513

# Other Vendor Software

The following products have licensing restrictions that require special
procedures to enable them to run at the hot site:

+-----------------+----------------------------------------------------+
| > ***Co         | Connect:Direct requires a new license key. Contact |
| nnect:Direct*** |                                                    |
|                 | <https://support.st                                |
|                 | erlingcommerce.com/forms/connect_key_request.aspx> |
|                 |                                                    |
|                 |   or call customer support at  1-800-292-0104 to   |
|                 | obtain a license key to update the data set APDSN  |
|                 | with the hot site cpu ID. The DCSS customer ID is  |
|                 | 11653.                                             |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+
| > ***IOF***     | IOF requires an authorization patch. Contact Patty |
|                 | Robbins (patty.robbins@ triangle-systems.com) and  |
|                 | Christine Cargnoni (Christine.cargnoni@fisc.com)   |
|                 | to obtain the patch. When making the request be    |
|                 | prepared to provide the following information:     |
|                 |                                                    |
|                 | -   Starting day of test and length (3 days)       |
|                 |                                                    |
|                 | -   Current IOF release level: 7.G.0               |
|                 |                                                    |
|                 | -   Processor type being emulated at the hot site: |
|                 |     9672-RB6                                       |
|                 |                                                    |
|                 | -   Product license and issuer: 085 0693, Federal  |
|                 |     Data Corporation                               |
|                 |                                                    |
|                 | -   CPU ID and machine type: obtained from the     |
|                 |     SunGard web-based test plan                    |
|                 |                                                    |
|                 | The following is an example of the patch that will |
|                 | be received:                                       |
|                 |                                                    |
|                 | > REP 00 10C9,0F57,B68C,B165 - good thru 07 Nov    |
|                 | > 2001, Wednesday                                  |
|                 |                                                    |
|                 | 1)  Member A40EXPIR in                             |
|                 |     NIH.IOF.PROD.IOFT7GO.OPTIONS must be updated   |
|                 |     with the new zap codes; examples of the format |
|                 |     are in the member.                             |
|                 |                                                    |
|                 | 2)  Execute member M40EXPIR in                     |
|                 |     NIH.IOF.PROD.IOFT7G0.INSTALL.                  |
|                 |                                                    |
|                 | 3)  If condition code 0 is returned, do an LLA     |
|                 |     Refresh                                        |
|                 |                                                    |
|                 | > (F LLA,REFRESH) to activate the new              |
|                 | > authorization code.                              |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+
| > ***MAX***     | MAX software requires temporary enabling codes     |
|                 | (good for 10 days). Contact the vendor at          |
|                 | 1-888-376-6629 or 301-985-1558, or by email,       |
|                 | info@maxsoftware.com to request the authorization  |
|                 | zaps. Indicate the request is for NIH (CIT) for    |
|                 | testing at SunGard on the specified test dates and |
|                 | provide the SunGard CPU serial number and          |
|                 | processor type/model number (obtained from the     |
|                 | SunGard web-based test plan).                      |
|                 |                                                    |
|                 | 1)  Make sure the DR passwords are in the MAXAUTH  |
|                 |     member in the NIH.MXRX320.JCL library.         |
|                 |                                                    |
|                 | 2)  Submit ASMAUTHS from the NIH.MXRX320.JCL       |
|                 |     library to create the MAXAUTH load module.     |
|                 |                                                    |
|                 | 3)  If the jobs are run after the system has been  |
|                 |     IPL'ed, do an LLA Refresh; otherwise, wait for |
|                 |     an IPL.                                        |
|                 |                                                    |
|                 | 4)  Verify the Max functions (Max View, Max Edit,  |
|                 |     Max PDF, Max Utility) are accessible without   |
|                 |     an authorization error message. Submit a batch |
|                 |     job executing pgm=maxbat to ensure that it     |
|                 |     executes without error.                        |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+
| > ***MIA***     | These products require an authorization key.       |
| >               | Contact Computer Associates (CA) at 1-800-338-6720 |
| > ***MIM***     | to request the authorization key. Provide the site |
| >               | ID: 193082 and the CPU ID and model number of the  |
| > ***OPSMVS***  | SunGard system (obtained from the SunGard          |
| >               | web-based test plan). The EKG key received from CA |
| > ***SMR***     | is put into the KEYS member of PPOPTION.           |
| >               |                                                    |
| > ***TMS***     |                                                    |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+
| > ***Model      | Contact Liz Klass of CCA at 703-506-2107 to obtain |
| > 204***        | the cpuzap for the disaster recovery site. You     |
|                 | will need to provide the CPU ID and the operating  |
|                 | system level (obtained from the SunGard web-based  |
|                 | test plan). Create a new copy of                   |
|                 | NIH.M204.RACF.PGMS.DISASTER and apply the zap to   |
|                 | the new copy (the dataset is on M20402) as         |
|                 | follows.                                           |
|                 |                                                    |
|                 | Prior to the test, on the home production system:  |
|                 |                                                    |
|                 | 1)  Logon to TSO and copy the NIH.M204.RACF.PGMS   |
|                 |     to another dataset -                           |
|                 |     NIH.M204.RACF.PGMS.DISASTER.                   |
|                 |                                                    |
|                 | 2)  Use SPF 3.3 to copy ONLINE, IFAM1, IFAM4 and   |
|                 |     Batch204 modules into the                      |
|                 |     NIH.M204.RACF.PGMS.DISASTER library.           |
|                 |                                                    |
|                 | 3)  Upload the CCA zap to the dataset              |
|                 |     \$DBS.HOTSITE.ZAP.                             |
|                 |                                                    |
|                 | 4)  Run the job NIH.M204.V510.FIXES.DATA(ZAPUCPU)  |
|                 |     to zap/update ONLINE, IFAM1, IFAM4 and         |
|                 |     Batch204 modules, which are stored in the      |
|                 |     NIH.M204.RACF.PGMS.DISASTER library. This zap  |
|                 |     verifies and then replaces the CPU name info   |
|                 |     with 0000\'s; thus removing the present NIH    |
|                 |     site information.                              |
|                 |                                                    |
|                 | 5)  Run the job NIH.M204.V510.FIXES.DATA(ZAP510)   |
|                 |     to zap/update ONLINE, IFAM1, IFAM4 and         |
|                 |     Batch204 modules, which are stored in the      |
|                 |     NIH.M204.RACF.PGMS.DISASTER library. This zap  |
|                 |     verifies and then replaces the 0000\'s with    |
|                 |     the hot site cpu information.                  |
|                 |                                                    |
|                 | At the hot site:                                   |
|                 |                                                    |
|                 | 1)  Logon to TSO SPF.                              |
|                 |                                                    |
|                 | 2)  Use SPF 3.3 to copy the ONLINE, IFAM1, IFAM4   |
|                 |     and Batch204 modules from the                  |
|                 |     NIH.M204.RACF.PGMS.DISASTER library to the     |
|                 |     NIH.M204.RACF.PGMS library.                    |
|                 |                                                    |
|                 | 3)  Start M204PROD by entering the following at    |
|                 |     the console:                                   |
|                 |                                                    |
|                 | > /S M204R                                         |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+
| >               | Quick-Ref requires a key to run at the DR site.    |
| ***Quick-Ref*** | Contact Chicago-Soft at 733-282-4777 or by email:  |
|                 | <zap@chicago-soft.com> to obtain the keys. You     |
|                 | will need to provide the following information:    |
|                 | the key is for the US National Institutes of       |
|                 | Health, LA #9011495, the date of the test, and the |
|                 | CPU ID.                                            |
|                 |                                                    |
|                 | Run the job NIH.QUICKREF.R640.JCL (QWIEXPDT) to    |
|                 | apply the zap to member QWIKREF1 in the current    |
|                 | Quick-Ref linklib.                                 |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+
| > ***SAS***     | To prepare SAS PROCs for use in a DR situation,    |
|                 | comment out the two DD cards containing DSN=SYSDB2 |
|                 | in each of the following two PROCs:                |
|                 | ZABCRUN.PROCLIB (SAS) and ZABCRUN.PROCLIB          |
|                 | (SAS609). The SAS PROCLIB resides on MSTATS.       |
|                 |                                                    |
|                 | Contact Mr. Ray Danner at (301)496-6037 or Ms.     |
|                 | Cindy Harper at (919)677-8000 to obtain a SETINIT  |
|                 | job. Execute the SETINIT job after modifying the   |
|                 | SAS PROCs. This will suppress printing of the SAS  |
|                 | warning messages.                                  |
|                 |                                                    |
|                 | It is not necessary to obtain the SETINIT job for  |
|                 | hot site testing, but SAS should be notified after |
|                 | the test.                                          |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+
| > ***Shadow***  | Shadow requires a temporary "emergency license     |
|                 | code". Contact Neon Systems by email:              |
|                 | support@neonsys.com.                               |
+-----------------+----------------------------------------------------+
|                 |                                                    |
+-----------------+----------------------------------------------------+
| > ***Superset   | Superset Utilities require authorization codes.    |
| > Utilities***  | Contact Applied Software (Ron Turner) at           |
|                 | 215-297-9441, Fax 215-297-9498, or by email:       |
|                 | ron@appliedsoftware.com to request the             |
|                 | authorization codes. Provide the dates, CPU serial |
|                 | number, and model number of the SunGard system     |
|                 | (obtained from the SunGard web-based test plan).   |
|                 |                                                    |
|                 | Assuming module AS0000PW is already prepared with  |
|                 | the authorization codes, you can use the following |
|                 | shortcut procedure from the floor system prior to  |
|                 | the first IPL:                                     |
|                 |                                                    |
|                 | Use ISPR 3.3 "Move/Copy Utility" to REPLACE module |
|                 | AS0000PW:                                          |
|                 |                                                    |
|                 | > From: 'NIH.SUPERSET.DR.LOAD', Volume ABRSYS      |
|                 | >                                                  |
|                 | > To: 'SYS1.SUPERSET.LOAD', Volume NIHLBB          |
|                 |                                                    |
|                 | Be sure to specify "/" to allow "Replace           |
|                 | like-named member"'                                |
|                 |                                                    |
|                 | If you did not use the pre-IPL procedure above, do |
|                 | the following:                                     |
|                 |                                                    |
|                 | The two members in NIH.SUPERSET.DR.CNTL for        |
|                 | updating the authorization module are: ASMPSWDX    |
|                 | and PCCPSWDC. Make sure PCCPSWDC has the current   |
|                 | authorization codes. Edit member ASMPSWDX to make  |
|                 | sure "//SYSLMOD" points to library                 |
|                 | SYS.SUPERSET.LOAD submit the job.                  |
|                 |                                                    |
|                 | After the batch job completes, optionally browse   |
|                 | SYS1.SUPERSET.LOAD(AS0000PW) to verify the current |
|                 | disaster site codes are in place.                  |
|                 |                                                    |
|                 | From the console:                                  |
|                 |                                                    |
|                 | > F LLA,REFRESH                                    |
+-----------------+----------------------------------------------------+

Products requiring keys to run at the DR site and responsibilities:

+---------------------+---------------+---------------+---------------+
| **vendor**          | **product**   | **Key         | **            |
|                     |               | required for  | responsible** |
|                     |               | DR test?**    |               |
+---------------------+---------------+---------------+---------------+
| Applied Software,   | Superset      | yes           | S Filbert     |
| Inc                 | utilities     |               |               |
+---------------------+---------------+---------------+---------------+
| BMC Software        | CMF Monitor   |               | B Long        |
+---------------------+---------------+---------------+---------------+
|                     | Loadplus      |               | E Ryan        |
+---------------------+---------------+---------------+---------------+
|                     | Mainview      |               | B Long        |
+---------------------+---------------+---------------+---------------+
|                     | Re            |               | B Long        |
|                     | solve/Sysprog |               |               |
+---------------------+---------------+---------------+---------------+
| Chicago Soft        | Quick-Ref     | yes           | B Bauer       |
+---------------------+---------------+---------------+---------------+
| Computer Associates | CA1           |               | D O'Brien     |
+---------------------+---------------+---------------+---------------+
|                     | CA7           |               | TC Chen       |
+---------------------+---------------+---------------+---------------+
|                     | CA11          |               | TC / J        |
|                     |               |               | Dussault      |
+---------------------+---------------+---------------+---------------+
|                     | Common        |               | TC / J        |
|                     | Service       |               | Dussault      |
+---------------------+---------------+---------------+---------------+
|                     | MIA/MIM       |               | B Bauer       |
+---------------------+---------------+---------------+---------------+
|                     | OPSMVS        |               | TC / J        |
|                     |               |               | Dussault      |
+---------------------+---------------+---------------+---------------+
|                     | SMR           | yes           | TC / J        |
|                     |               |               | Dussault      |
+---------------------+---------------+---------------+---------------+
|                     | TMS           | yes           | TC / J        |
|                     |               |               | Dussault      |
+---------------------+---------------+---------------+---------------+
| Computer Corp. of   | Model 204     | yes           | H Carelock    |
| America             |               |               |               |
+---------------------+---------------+---------------+---------------+
| DataDirect          | Shadow        | yes           | E Ryan        |
| Technologies        | z/Direct      |               |               |
+---------------------+---------------+---------------+---------------+
|                     | Shadow        |               | E Ryan        |
|                     |               |               |               |
|                     | z/            |               |               |
|                     | EnterpriseWeb |               |               |
|                     | Server        |               |               |
+---------------------+---------------+---------------+---------------+
| Fisher Int'l Sys.,  | IOF           | yes           | B Long        |
| Inc.                |               |               |               |
+---------------------+---------------+---------------+---------------+
| Max Software        | MAX           | yes           | C Green       |
+---------------------+---------------+---------------+---------------+
| SAS Institute       | SAS           | yes           | A Bennett     |
+---------------------+---------------+---------------+---------------+
| Software            | PDSFast       |               | B Long        |
| Engineering of      |               |               |               |
| America             |               |               |               |
+---------------------+---------------+---------------+---------------+
| Sterling Commerce   | C             | yes           | B Bauer       |
|                     | onnect:Direct |               |               |
|                     |               |               | G Tran        |
+---------------------+---------------+---------------+---------------+

# Dump Disaster Volumes

After the completion of disaster recovery testing, the disaster volumes,
DIST00, DIST01, and DIST002 are dumped to 9840 scratch tapes to be
returned to NIH.

The NIH.STGADMIN.DIST.WORK.CNTL(DISTDUMP) dataset contains the JCL to
perform the dumps. The only changes to the JCL that may be necessary
might be the volume serial numbers of the volumes being dumped and the
tape device parameters.

Submit this job (after any necessary edits), noting the job number and
time, and verify successful completion (Cond-Code 0000).

# Dump Console Log Volumes

As long as SMR has been running during the test, the current day\'s
console logs will be in data sets named NIH.CA.SYSLOG.CURRssss where
\"ssss\" is the SMFid of the system (e.g., 4090). The log for the
previous day will be in the data set named NIH.CA.SYSLOG.SMRyyjjj where
\"yy\" is the last 2 digits of the year and \"jjj\" is the Julian date.
You should verify that these data sets are on NIHLB4 and SMR001
respectively. If not, modify the JCL below as necessary.

After the completion of disaster recovery testing, the volumes NIHLB4
and SMR001 containing the console logs are dumped to 3490 scratch tapes
to be returned to NIH.

The NIH.STGADMIN.DIST.WORK.CNTL(DUMPLOGS) dataset contains the JCL to
perform the dumps. The only changes to the JCL that may be necessary are
the volume serial numbers of the volumes being dumped and the tape
device parameters.

Submit this job (after any necessary edits) and verify successful
completion (Cond-Code 0000). Also make a note of the scratch tapes that
were written so that you can copy these tapes once the \"scratch\" tapes
come back to NIH. You must use DFDSS to copy these tapes (for sample
JCL, see \$JDA.DISASTER.CNTL(COPYDUMP)).

# Miscellaneous

The following is useful information.

## SMF

From time to time it may be necessary to clear the SMF datasets on the
DR z/OS operating system. The following procedure can be used to manage
the SMF data.

1)  On the Operator\'s console issue the \'D SMF\' command. This
    displays the status of the SYS1.MAN1, SYS1.MAN2, and SYS1.MAN3
    datasets.

2)  If any of the MAN files shows a status of \'DUMP REQUIRED\' the job
    SMFCLEAR can be submitted from dataset NIH.DISASTER.JCL. Be sure to
    specify the MAN file you wish to clear (1,2, or 3) on the EXEC card.
    This job will clear all records from the SMF MAN file and reset it
    back to 0% full.\"

## CICS

1)  Since the environment at the DR site is new and the log streams will
    be defined for this new environment, the CICS startup should be
    INITIAL. The easiest way to achieve this is by adding the following
    to the SIT override data set, i.e., adding to
    NIH.CICSTS22.PROD.R1CICS22.SYSIN(DFH\$SIPT) :

START=INITIAL, X

2)  Since TMON for CICS is not started at the DR site, CICS will not
    start at the DR site unless the TMON programs that it executes
    during its initialization at NIH are removed from the initialization
    at the DR site. The easiest way to achieve this is by adding the
    following to the SIT override data set, i.e.,
    NIH.CICSTS22.PROD.R1CICS22.SYSIN(DFH\$SIPT) :

PLTPI=NO, X

3)  UNCATLOG, DELETE and DEFINE the logstreams for CICS:

> Verify that you are logged in at the DR site (System 4).
>
> Verify the names of the CICS log data sets referenced in
> NIH.CICSTS22.PROD.R1CICS22.LIBRARY(LGRUNCAT).
>
> **Note:** The generation qualifier in the data set names referenced in
> LRGUNCAT change from one DR test to the next.
>
> Modify LGRUNCAT based on the log datasets that are cataloged at the DR
> site.
>
> **Note:** Prior to submitting the LGRUNCAT JCL, you may want to recall
> any datasets that you will uncatalog that are currently migrated. If
> you don't, it may take a long time for the LGRUNCAT job to execute as
> recalls of migrated datasets at the DR site seem to be longer than
> normal.
>
> **Note:** To execute LGRUNCAT you need ALTER access to:
>
> PRF.CP1.PPCSPROD.USRJRNLS.\*\*
>
> OFM.HAS.FDMSPROD.USRJRNLS.\*\*
>
> OFM.HAS.PCAPROD.USRJRNLS.\*\*
>
> **Note:** ZDB2EOR has the required access authority.
>
> Remove the comments from the job card, and execute LGRUNCAT.
>
> **Note:** A cond code = 8 may be alright; just verify that the log
> files are uncataloged.
>
> From OPSLOG, display the logstreams by issuing:
>
> /d logger,logstream
>
> As an alternative, the logstreams can be displayed from the IOF LOG
> with the following command:
>
> #d logger,logstream
>
> Modify NIH.CICSTS22.PROD.R1CICS22.LIBRARY(LGRDELET) based on the CICS
> logstreams that do not exist at the DR site. Many, if not all, of the
> logstreams may not initially exist at the DR site. Remove any CICS
> logstreams that do not exist at DR because their presence in the JCL
> will cause the submission to receive a Cond Code = 0012. If none of
> the CICS logstreams initially exist at the DR site, there should be no
> need to execute LGRDELET.
>
> Remove the comments from the job card, and execute LGRDELET.
>
> **Note:** To execute LGRDELET, you need READ access to: MVSADMIN.LOGR
> cl(facility). ZDB2EOR has the required access authority.
>
> Remove the comments from the job card, and execute
> NIH.CICSTS13.PROD.R1CCIS22.LIBRARY(LGRDEFIN).

4)  If CICS06 and CICS11 have not yet been restored, comment out the DTM
    loadlib from the RPL. (CCIS11 contains the file and CICS06 contains
    the catalog).

5)  Bring up the region by issuing the following command:

> /S CICS22R1

6)  Verify that the user files are allocated to CICS.

7)  If the user files are not allocated, you may need to execute the
    following transactions:

> AARM
>
> ADMC
>
> APCA

8)  Modify the record in NIH.CICSTS22.SITEFILE to a \'2\'.

9)  Test the Site transaction.

10) Issue the following command:

> CECI EXEC CICS LINK PROG(\'DUMPTBLE\')

11) Notify the staff at the DR site that CICSPROD is up.

## TESTING THE Oracle Client

1)  Log on to DRTITAN2.NIH.GOV (System 9).

2)  Verify the contents of the SQLNET and Oracle TNSNAMES files.

> **Note:** There is a current project in CIT to discontinue support of
> Oracle Names. Until this project is completed:

-   Verify that any customer testing at the DR site who has already
    transitioned to using their own SQLNET and TNSNAMES files, modifies
    the entries in their TNSNAMES file to point to the databases at the
    DR site.

-   Continue with the following steps if there are DR customers who are
    testing and have not yet transitioned to their own SQLNET and
    TNSNAMES files.

> The ORASQL, ORALDR, and ORACB2 procs in the NIH.ORACLE.PROCLIB each
> contain the following DD cards:
>
> //sqlnet dd dsn=nih.sqlnet.ora,disp=shr
>
> //tnsnames dd dsn=nih.oracle.tnsnames,disp=shr
>
> At the NIH, the directory path in NIH.SQLNET.ORA looks first at
> TNSNAMES and then at ONAMES. On Titan, NIH.ORACLE.TNSNAMES has no
> entries, so unless the JCL overrides the TNSNAMES DD statement in the
> proc by specifying a different TNSNAMES data set that contains
> entries, the connection at the NIH is made using ONAMES. The ONAMES
> entries point to the NIH computer systems.
>
> **Note:** AFPSP, John Biggie's application, uses NIH.SQLNET.ORA.ASO
> instead of NIH.SQLNET.ORA, but the process is the same.
>
> During disaster recovery, the users' connections should not be to the
> NIH machines. The connections should be to the machines set up at the
> disaster recovery site. The connections to REPOSPRD that are made to
> test the members of NIH.ORACLE.PROCLIB are made to the database back
> at NIH.
>
> The connection information needed at the DR site is contained in
> NIH.SQLNET.ORA.DRSITE, NIHSQLNET.ORA.ASO.DRSITE, and
> NIH.ORACLE.TNSNAMES.DRSITE. The job, DB2PWSTR, starts ORAONSP at the
> disaster recovery site. The job includes steps that copy
> NIH.SQLNET.ORA.DRSITE, NIHSQLNET.ORA.ASO.DRSITE, and
> NIH.ORACLE.TNSNAMES.DRSITE to NIH.SQLNET.ORA, NIH.SQLNET.ORA.ASO, and
> NIH.ORACLE.TNSNAMES, respectively. When NIH.SQLNET.ORA,
> NIH.SQLNET.ORA.ASO, and NIH.ORACLE.TNSNAMES are referenced at the DR
> site, they contain the connection information needed for the test; not
> the connection information used at NIH.

3)  Verify the absence of numbering in NIH.ORACLE.TNSNAMES,
    NIH.SQLNET.ORA.ASO, and NIH.SQLNET.ORA. To do this, edit
    NIH.ORACLE.TNSNAMES, NIH.SQLNET.ORA.ASO, and NIH.SQLNET.ORA and
    press PF11. If there are numbers on right, go to the command line
    and enter the UNNUM command.

4)  Verify that the TMX11826I message references the IP address at the
    DR site.

5)  Verify the TCP/IP connections. From TSO enter:

> PING DREOS.CIT.NIH.GOV

6)  The following are problems from previous tests with resolution. They
    are included here in case they occur during current testing; this
    may help hasten the resolution.

+-----------------------------------+-----------------------------------+
| **Problem**                       | **Solution**                      |
+-----------------------------------+-----------------------------------+
| The job just waited on the        | The ORACLE JES2 agent needed to   |
| execution queue                   | be activated                      |
+-----------------------------------+-----------------------------------+
| The TNSNAMES and ORACLE NAMES     | The UNNUM command needed to be    |
| files had numbers on and          | issued on the files               |
| extraneous data in the right most |                                   |
| columns of the data sets          |                                   |
+-----------------------------------+-----------------------------------+
| Job submission errors stating:    | The resolution was to UNCATALOG   |
|                                   | the ZDB2INI.SYS4...CNTL data set  |
| > Temporary control card data set |                                   |
| > cannot be allocated             |                                   |
| >                                 |                                   |
| > DAIR RC = 12 dec, DARC = 970C   |                                   |
| > hex                             |                                   |
+-----------------------------------+-----------------------------------+

7)  Test the Oracle procs

> If space on EOS is limited at the DR site (this is usually the case),
> NIH.ORACLE.TNSNAMES.DRSITE will have an entry for REPOSPRD which
> connects to REPOSPRD at the NIH. If so, the password for the test of
> REPOSPRD must match the password on EOS at NIH.
>
> Prior to testing verify that:

-   The directory path in NIH.SQLNET.ORA does not include ONAMES,

-   The directory path in NIH.SQLNET.ORA.ASO does not include ONAMES,
    and

-   the DR entries are included in NIH.ORACLE.TNSNAMES.

> **Test ORASQL and ORALDR**

a)  Submit the following JCL:

> ZDB2INI.ORA.TJS.REPOSPRD.JCL(SQLPLUS)

b)  If the SELECT succeeded (the tjs_table1 exists), execute the
    following:

> ZDB2INI.ORA.TJS.REPOSPRD.JCL(DELROWS)
>
> ZDB2INI.ORA.TJS.REPOSPRD.JCL(SQLLOAD)
>
> ZDB2INI.ORA.TJS.REPOSPRD.JCL(SQLPLUS)

c)  If the SELECT failed (the tjs_table1 does not exist), execute the
    following:

> ZDB2INI.ORA.TJS.REPOSPRD.JCL(CREATETB)
>
> ZDB2INI.ORA.TJS.REPOSPRD.JCL(SQLLOAD)
>
> ZDB2INI.ORA.TJS.REPOSPRD.JCL(SQLPLUS)
>
> **Test ORACB2**

a)  Submit the following JCL:

> ZDB2INI.ORA.TJS.REPOSPRD.JCL(COBOLCL)

b)  Add //TNSNAMES DD NIH.ORACLE.TNSNAMES,DSP=SHR to
    ZDB2INI.ORA.TJS.REPOSPRD.JCL(COBOLGO)

c)  Enter: EXECUTE 'ZDB2INI.ORA.TJS.REPOSPRD.JCL(COBOLGO)'

```{=html}
<!-- -->
```
8)  Verify the connection to AFPSP at the DR site:

```{=html}
<!-- -->
```
a)  On the Database Development Main Menu, enter: O

b)  You will be prompted for the fully qualified TNSNAMES file.

> Enter: NIH.ORACLE.TNSNAMES

c)  You will be prompted for the Oracle Connect String.

> Enter: REPOSPRD.WORLD

d)  You will be prompted for your Oracle userid.

> Enter: ZDB2INI

e)  You will be asked to confirm the TNSNAMES file, connect string, and
    userid.

> Press Enter to confirm or enter NO to repeat the prompt cycle.

f)  After confirming the information, you will be prompted for the
    password.

> Enter the password.

g)  The SQL prompt is displayed.

> Enter: HOST TNSPING AFPSP.WORLD

h)  If AFPSP has been restored at DR, the host will be identified as
    DREOS.CIT.NIH.GOV.

```{=html}
<!-- -->
```
9)  Using the ORAMON userid, test the connection to AFPSP at the DR
    site.

> Verify the password in ZDB2INI.ORA.TJS.REPOSPRD.PARMLIB(AFPSP).
>
> Submit ZDB2INI.ORA.TJS.REPOSPRD.JCL(AFPSP).

10) Call the disaster recovery site to report that all is okay.

## TESTING DB2

The DB2 disaster recovery testing plan is in
ZDB2DB2.DR.DB2.CNTL(TESTING).

## FDR/ABR Model

Procedures to place an FDR/ABR Model on a volume. Either edit and submit
the batch job in NIH.STGADMIN.DIST.WORK.JCL(INIMODEL) or do the
following.

1)  On the Command line of the main ISPF panel, select option **C**,
    Products, and hit the enter key.

2)  On the Command line enter **A.I.8** and hit the Enter key. The
    following panel will be displayed. If the dataset name indicated in
    bold is not the one displayed, type it in. Hit the Enter key.

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

ABR DISK VOLUME PROCESSING OPTIONS MUST BE SET PRIOR TO ABR EXECUTION.

SETTING THE ABR PROCESSING OPTIONS DOES NOT AFFECT NORMAL USE OF THE
VOLUME.

FDR PROGRAM LIBRARY DATA SET:

DATA SET NAME ===\> **\'SYS1.FDRABR.PROD5359.LINKLIB\'**

VOLUME SERIAL ===\>

SYSOUT CLASS ===\> \*

JOB STATEMENT INFORMATION:

===\>//STGMODEL JOB (ZZXZ,112,E),\'COLLINS,NOTIFY=\$RYM

===\>//\*ROUTE OUTPUT HOLD

===\>//\*

===\>//\*

PLEASE PRESS THE \"ENTER\" KEY TO DISPLAY THE TABLE

\-\-\-\-\-\-\-\-\--COPYRIGHT 1987, 2000 \-\-- INNOVATION DATA
PROCESSING, INC.\-\-\-\-\-\--

3)  The panel to create the ABR Model will be displayed. Enter DASD
    volser under the Volume Serial Number column (as indicated in bold)
    and hit the enter key.

\-\-\-\-\-\-\--FDR INSTALLATION \-- SET ABR VOLUME PROCESSING OPTIO Row
1 to 1 of 1,

COMMAND ===\> SCROLL ===\> PAGE

SUBMIT - SUBMIT FDRABRM BATCH JOB EDIT - EDIT FDRABRM BATCH JOB

REFRESH- REFRESH ABR VOLUME INFO FIND - FIND THE SPECIFIED STRING

\-\-\--CURRENT BACKUP\-\-\-\--

VOLUME GEN CYC EXPDT AC MOD MAX GEN RETPD ARCHIVE STORCLAS FORCE

SERIAL DATE EXPD2 MAX AC RETP2 SCRATCH ARCHI

CMD NUMBER OLDBKUP ARCLOW

\-\-- \-\-\-\-\-- \-\-- \-\-- \-\-\-\-\-\-\-- \-- \-\-- \-\-\-\-\-\--
\-\-\-\-- \-\-\-\-\-\-- \-\-\-\-\-\-\-- \-\-\-\--

**DDDXXX**

\-\-- \-\-\-\-\-- \-\-- \-\-- \-\-\-\-\-\-\-- \-- \-\-- \-\-\-\-\-\--
\-\-\-\-- \-\-\-\-\-\-- \-\-\-\-\-\-\-- \-\-\-\--

PLEASE ENTER THE VOLUME SERIAL NUMBERS TO DISPLAY/SET ABR PROCESSING
OPTIONS

4)  The values set for volume DSL101 will be displayed:

\-\-\-\-\-\-\--FDR INSTALLATION \-- SET ABR VOLUME PROCESSING OPTIO Row
1 to 1 of 1,

COMMAND ===\> SCROLL ===\> PAGE

SUBMIT - SUBMIT FDRABRM BATCH JOB EDIT - EDIT FDRABRM BATCH JOB

REFRESH- REFRESH ABR VOLUME INFO FIND - FIND THE SPECIFIED STRING

\-\-\--CURRENT BACKUP\-\-\-\--

VOLUME GEN CYC EXPDT AC MOD MAX GEN RETPD ARCHIVE STORCLAS FORCE

SERIAL DATE EXPD2 MAX AC RETP2 SCRATCH ARCHI

CMD NUMBER OLDBKUP ARCLOW

\-\-- \-\-\-\-\-- \-\-- \-\-- \-\-\-\-\-\-\-- \-- \-\-- \-\-\-\-\-\--
\-\-\-\-- \-\-\-\-\-\-- \-\-\-\-\-\-\-- \-\-\-\--

**DDDXXX** xxx xx xx xxx xx xxx

xx xx xxx xx

xx xx xxx xx

\-\-- \-\-\-\-\-- \-\-- \-\-- \-\-\-\-\-\-\-- \-- \-\-- \-\-\-\-\-\--
\-\-\-\-- \-\-\-\-\-\-- \-\-\-\-\-\-\-- \-\-\-\--

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Bottom of
data \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

Either accept the values or change as appropriate.

5)  At the COMMAND ===\> prompt, enter: SUBMIT, followed by the Enter
    key. This will submit the batch job for the selected ABR model.

6)  Either use IOF to display the batch job to verify the ABR model has
    been created or:

Using IPSP (3.4) DSLIST:

> \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

Data Set List Utility

Option ===\>

Blank Display data set list P Print data set list

V Display VTOC information PV Print VTOC information

> \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

Enter one or both of the following parameters:

> Dsname Level: **FDRABR.\***
>
> Volume Serial: **DDDXXX**

Hit the Enter key; the following will be displayed:

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

DSLIST - Data Sets on volume DSL101 Row 1 of 1

Command ===\> Scroll ===\> PAGE

Command - Enter \"/\" to select action Message Volume

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

FDRABR.VDDDXXX DDDXXX

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

# SunGard Esoterics

  ----------------------------------- -----------------------------------
  ***Device Type***                   ***Esoteric***

  3380 and 3390                       SYSDA, DISK, SYSSQ

  3420                                TAPE

  3480                                CART and TAPEC

  3490                                CART3490 and CARTE

  MetroCenter 3420                    METRO20

  MetroCenter 3480                    METRO

  MetroCenter 3490                    METRO90

  3480 and 3490                       ALLCART

  3590 - All Models                   CART3590, MAGSTAR

  3590B                               CART359B

  3590E                               CART359E

  3590H                               CART359H

  9840 - All Models                   CART9840, STK9840

  9840C                               STK9840C

  9940B                               STK9940, CART9940

  3494-B18 / 3490E                    VTS

  3494-B18 / 3590E                    ATL

  STK VSM                             VSM
  ----------------------------------- -----------------------------------