DB2 Server for VSE. Operations Guide / Handbooks (2004-2007)

database minidisks in write (W) mode. If a minidisk needs to be accessed, it will

be accessed as filemode B, C, D, or E. These filemodes should be available before

invoking RESTORE.

Files

The Data Restore RESTORE requires some input and output files:

For VM only:

v SYSIN file - the file contains the command to be processed.

v SYSPRINT file - Data Restore feature creates a report that lists the SYSIN

values, messages and results.

For VM and VSE:

v ARCHIV - Data Restore archive file to be restored

If the archive file processed has been generated by the BACKUP

INCREMENTAL function, a FULL archive will be accessed to complete

processing. You will be prompted to mount the right FULL archive).

v FULLARC - Data Restore FULL archive file necessary to complete the RESTORE,

if the ARCHIV file is an INCREMENTAL BACKUP.

Note: If the FULLARC file is used, the DEVICE2 parameter on the OPTIONS

statement, should specify TAPE or DASD.

Example

Figure 5 shows a sample of the JCL to use Data Restore RESTORE.

* $$ JOB JNM=DRFRESTR,CLASS=0,DISP=D

* $$ LST CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)

* $$ PUN CLASS=A,DISP=D,PRI=3,DEST=(*,VSESQADM)

// JOB DRFRESTR

RESTORE DATABASE WITH DRF from tape

// LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)

// EXEC PROC=SQLVSE02

// EXEC PROC=XTS9DLBL

// TLBL

ARCHIV

// ASSGN

SYS006,181

// MTC

REW,SYS006

/* PAUSE for monitor

// EXEC XTS91001,SIZE=AUTO

CONTROL DBNAME=SQLVSE02

RESTORE

* $$ EOJ

Figure 5. JCL File for Data Restore RESTORE

Figure 6 on page 31 shows a sample of the EXEC to use Data Restore RESTORE.

Data Restore Guide

/* */

/* FILEDEF FOR INPUT FROM TAPE */

’FILEDEF ARCHIV TAP1 SL (RECFM VB BLOCK 32760’

’FILEDEF SYSIN

DISK RESTORE SYSIN A’

’FILEDEF SYSPRINT DISK RESTORE SYSPRINT A’

’XTS91001’

Exit rc

Figure 6. EXEC File for Data Restore RESTORE from Data Restore BACKUP (RESTORE

EXEC)

Figure 7 shows a sample of the EXEC to use Data Restore RESTORE.

OPTIONS DEVICE=TAPE CONFIRM=NO

CONTROL BASE=ELDB2A

RESTORE

Figure 7. SYSIN File for Data Restore RESTORE from Data Restore BACKUP (RESTORE

SYSIN)

Summary

Compatibilities

Data Restore BACKUP uses a different format than DB2 ARCHIVE. Therefore, a

Data Restore archive cannot be used for a DB2 restore.

However, you can change a DB2 archive to a Data Restore archive format using the

Data Restore TRANSLATE command; the only difference is that after TRANSLATE

the work files need to be kept separately for a future Data Restore RELOAD with

forward recovery, whereas this information is already at the beginning of a Data

Restore archive file after BACKUP.

Table 1 gives you an overview of the compatibilities among the methods that can

be used to archive and recover your DB2 database.

Table

1. Compatibilities - Archive and Recovery

... can be Input to:

Data

Data Restore Data Restore

Restore

Equivalent

Output from ...

DB2 RESTORE TRANSLATE DESCRIBE RELOAD RESTORE user restore

DB2 archive

Translated DB2 archive

Data Restore UNLOAD

Data Restore BACKUP

Any user archive

Possibilities

The DESCRIBE function of the Data Restore feature lists the contents of a Data

Restore BACKUP or UNLOAD file to determine which tables can be reloaded.

For the difference between filtered log recovery and APPLYLOG with forward log

recovery to a certain point in time, see “Log Recovery” on page 26.

Chapter 3. Archive and Recovery

The following table gives you an overview of the methods and their possibilities to

archive your DB2 database.

Table 2. Possibilities to Archive

Database Manager

Data Restore

Function

User archive

ARCHIVE

UNLOAD

Unit

table

storage pool

database

Status database

online

offline

Restore

last archive

any archive

Recover log

apply all

to log file border

to a point in time

filtered log

Data Restore Guide

Chapter 4. Installing Data Restore

This chapter describes the steps required to install Data Restore.

Supported Environments

v DB2 Server for VSE & VM Version 7 Release 3

v All VSE/ESA and VM/ESA releases supported by DB2 Server for VSE & VM

Most of the Data Restore functions work on physical pages. When the database

manager is in a VM environment, Data Restore processes all functions in VM, even

if VSE Guest Sharing is used. When the database manager is in a VSE

environment, Data Restore processes all commands in VSE.

The only exception to this is the RELOAD function, which uses DB2 Server for

VSE & VM functions to recreate tables and insert rows before recreating the

physical database pages. If you have VSE Guest Sharing, Data Restore can process

the RELOAD command in either environment.

You can execute the RELOAD process in single or multiple user mode.

Complete the Preinstallation Checklist

Before beginning, ensure that you have completed the following:

__ 1. Read Chapter 1, “How to Recover from Failures” on page 3.

__ 2. Installed DB2 Server for VSE & VM Version 7 Release 3 with at least one

Version 7 Release 3 database available. This database is required to verify

the installation of Data Restore.

__ 3. Decided whether you are installing in a VM, VSE, or VSE Guest Sharing

environment.

__ 4. Provided enough space on DASD as shown in Figure 8 or Figure 9.

3375 :

16 CYLINDERS

3380 :

10 CYLINDERS

3390 :

9 CYLINDERS

9345 :

10 CYLINDERS

FBA

10000 BLOCKS

Figure 8. Minidisk Space Calculation for Data Restore VM Installation

3375 :

5 CYLINDERS

3380 :

4 CYLINDERS

3390 :

3 CYLINDERS

9345 :

4 CYLINDERS

FBA

2932 BLOCKS

Figure 9. Sublibrary Space Calculation for Data Restore VSE Installation

Note: If you are installing in a VSE Guest Sharing environment, obtain the

total DASD requirement by adding the VM and VSE requirements.

__ 5. Checked with your IBM Support Center or used either Information/Access

or IBMLink (ServiceLink) to see whether there is any additional Preventive

Service Planning (PSP) information that you should be aware of.

__ 6. Ensured that the userid SQLDBA is defined in your database with DBA

authority.

__ 7. Ensured that you have three public dbspaces available, having 6400, 1024,

and 128 pages respectively.

__ 8. Verified that the server is running and that ISQL is available.

__ 9. Ensured that a tape drive is available to be attached to load Data Restore.

Section

1. Installing Under VM

The procedure for installing this feature in a VM environment has three steps. You

must do these steps in order.

1. Define the requirements for VM resources.

2. Define the requirements for the database manager resources.

3. Run the supplied EXECs to complete the installation.

Step 1. Define the VM Resources

This step is mandatory.

1. Define a new VM userid for Data Restore and ensure that it can access all of

the application servers. The minimum virtual storage size for this machine is 8

MB.

2. Allocate a minidisk of the required size (see Figure 10) to this userid. Format

the minidisk (using the CMS FORMAT command) with a block size of 4 KB.

3375 :

16 CYLINDERS

3380 :

10 CYLINDERS

3390 :

9 CYLINDERS

9345 :

10 CYLINDERS

FBA

10000 BLOCKS

Figure 10. Minidisk Space Calculation for Data Restore VM Installation

3. If you are using an external security manager like RACF, make sure that this

machine is authorized to access the minidisks of the application server

(including the directory, log, and dbextent disks) in both read and write mode.

(See “Security and Authorizing Access to the Server Minidisks (VM Only)” on

page 65 for more information).

4. Verify that your machine can link to the application server’s 195 (production)

minidisk.

Step

2. Define the Database Manager Resources

This step is mandatory.

In this step, you define the database manager resources so that you can run Data

Restore.

You need three public dbspaces:

6400-page dbspace which is defined for Data Restore’s internal use

1024-page dbspace which is defined for Data Restore’s internal use

Data Restore Guide

128-page dbspace which is used to force a checkpoint to maintain data integrity

if you use the UNLOAD function while the database is running.

Note: This dbspace is not acquired during installation.

Using ISQL, enter the following commands:

(1) ---> SQLINIT DBNAME(dbname)

(2) ---> ISQL

(3) ---> CONNECT SQLDBA IDENTIFIED BY XXXXXXXX

(4) ---> ACQUIRE PUBLIC DBSPACE NAMED DATARFTR (PAGES=6400,PCTFREE=0,STORPOOL=n)

(5) ---> ACQUIRE PUBLIC DBSPACE NAMED DATARFT2 (PAGES=1024,PCTFREE=0,PCTINDEX=10,

STORPOOL=n)

(6) ---> EXIT

Figure 11. Acquiring the Required Dbspaces

Note: With the STORPOOL parameter, you may select either a recoverable or a

nonrecoverable storage pool. Use a nonrecoverable storage pool, if possible.

Statement 1

Initializes a connection to the database with the appropriate

parameters.

Statement 2

Invokes the Interactive SQL environment.

Statement 3

Signs on to the application server with DBA authority. (Replace

XXXXXXXX with the connect password for SQLDBA.)

Statement 4

Acquires a required public dbspace.

Statement 5

Acquires a required public dbspace.

Statement 6

Exits the ISQL environment.

You are now ready to complete the Data Restore installation.

Step

3. Complete the VM Installation Process

This process consists of four mandatory steps and two optional steps.

Step 3.1 Load Data Restore from Tape

This step is mandatory.

Log on to the Data Restore userid and execute the commands in Figure 12.

(1) ---> ACCESS cuu1 A

(2) ---> ATTACH cuu2 to * as 181

(3) ---> VMFPLC2 REW

(4) ---> VMFPLC2 LOAD

(5) ---> SQLINIT DBNAME(dbname)

Figure 12. Loading the Installation Files

Statement 1

Accesses the minidisk cuu1 that was defined in step 1 (the

minidisk must already be formatted).

Statement 2

Attaches tape drive cuu2 as 181 and mounts the Data Restore tape

on this drive.

Statement 3

Rewinds the tape on drive 181.

Chapter 4. Installing Data Restore

Statement 4

Loads the contents of the tape.

Statement 5

Runs the SQLINIT EXEC with the appropriate parameters to

connect to the correct database.

Step 3.2 Create the Database Environment

This step is mandatory.

Run the following EXEC:

XTS9CRE

Figure 13. Creating the Database Environment

This EXEC creates the required database environment; for example, tables used

internally by the product.

When prompted, enter the appropriate SQL CONNECT statement to connect to the

database as user SQLDBA, or, if the VM userid has DBA authority, press the enter

key.

Step 3.3 Load the Data Restore Packages

This step is mandatory.

Run the following EXEC:

XTS9PREP

Figure 14. Loading the Data Restore Packages

This EXEC loads the Data Restore packages into the database.

When prompted, enter the appropriate SQL CONNECT statement to connect to the

database as user SQLDBA, or, if the VM userid has DBA authority, press the enter

key.

Step 3.4 Create the Data Restore Modules

This step is mandatory.

Run the following EXEC:

XTS9GMOD

Figure 15. Creating the Data Restore Modules

This EXEC creates the Data Restore executable modules XTS91001, and XTS91002.

These modules are used to invoke various functions such as BACKUP, for example.

Data Restore is now installed in one application server. You may want to take a

backup of your database at this point.

Step 3.5 Install in Additional Application Servers

This step is optional.

If you want to install Data Restore in additional application servers on the same

VM system, repeat the following steps:

Data Restore Guide

“Step 2. Define the Database Manager Resources” on page 34.

“Step 3.2 Create the Database Environment” on page 36 which acquires the

required dbspaces.

“Step 3.3 Load the Data Restore Packages” on page 36 which creates the

database environment.

Step 3.6 Define Default Values for Data Restore Parameters

This step is optional.

While using Data Restore, you can pass parameters in the SYSIN file. Instead of

passing these parameters, you can modify and assemble the LMBRPARM program

to specify default values for them.

v Edit the XTS9PARM ASSEMBLE program to customize the parameters shown in

Figure 16, specifying the appropriate value in the LMBRPARM macro.

Notes:

1. Do not change the source for the LMBRPARM macro definition. Change

statement 2 only.

2. To specify more than one parameter, separate each parameter with a comma.

Assembler continuation rules apply.

(1) --->

MACRO

(1) --->

LMBRPARM &NOTA=E,&CASE=M,&DEVICE=TAPE,

(1) --->

&COMMIT=0,&MSGCLAS=1,&MSGDEV=3,

(1) --->

&DBAPW=SQLDBAPW,&BASE=SQL/DS V3R5,&LANG=S01,&CONFIRM=YES

LCLB

&BIT1,&BIT2;

CL11’&PWD’

&BIT1

SETB

(’&DEVICE’ EQ ’TAPE’)

&BIT2

SETB

(’&DEVICE’ EQ ’DASD’)

AL1(&BIT1+&BIT2*2)

&BIT1

SETB

(’&NOTA’(1,1) EQ ’E’)

AL1(&BIT1)

&BIT1

SETB

(’&CASE’(1,1) EQ ’M’)

&BIT2

SETB

(’&CASE’(1,1) EQ ’U’)

AL1(&BIT1+&BIT2*2)

AL4(&COMMIT)

AL1(&MSGCLAS)

AL1(&MSGDEV)

CL8’&DBAPW’

CL8’&BASE’

CL4’&LANG’

CL1’&CONFIRM’

MEND

LMBRPARM CSECT

* in order to customize your default table

** modify the following statement specifying all required parameters

(2) --->

LMBRPARM LANG=S001,BASE=dbname

END

LMBRPARM

Figure 16. XTS9PARM ASSEMBLE Program (Catalog Default Values)

Statement 1

Defines the macro.

Statement 2

Specify your default value for any parameter defined in the

LMBRPARM MACRO (statement 1). The defaults entered here

override the installation defaults.

Refer to “OPTIONS and CONTROL Statements” on page 167 which explains the

OPTIONS parameters on the LMBRPARM macro.

Chapter 4. Installing Data Restore

v Assemble the modified program containing your default values and re-execute

“Step 3.4 Create the Data Restore Modules” on page 36.

Starting Data Restore in a VM Environment

The CMS minidisk on which Data Restore is installed should be linked and

accessed.

Note: Link the minidisk with an address different from the minidisk of the

application server to avoid LINK errors during operation.

You can use a REXX EXEC like the one in Figure 17 to execute the Data Restore

functions.

/**/

’FILEDEF ARCHIV TAP1 SL 1 (RECFM VB BLOCK 32760’

’FILEDEF SYSPRINT DISK BACKUP SYSPRINT A’

’FILEDEF SYSIN DISK BACKUP SYSIN A’

’XTS91001’

Figure 17. Example EXEC to Execute Data Restore Functions

The SYSIN specifies which function to process. In Figure 17, the SYSIN file starts

Data Restore to execute a BACKUP command in a VM environment.

Section

2. Installing Under VSE

The procedure for installing Data Restore under VSE has three steps. You must do

these steps in order.

v Define the library to be installed.

v Restore the Data Restore distribution library.

v Run the supplied jobs to complete the installation.

Before using this chapter to install Data Restore in a VSE environment, refer to the

installation manual for your VSE system for an overview of how to install optional

programs.

Placement of Data Restore Distribution Libraries

When you use VSE/Interactive Interface (VSE/II), the job stream generated installs

Data Restore in the VSE library PRD2.RCVvrm Although you can override this

library, do not. All of the jobs described in this manual assume that the target

library is PRD2.RCVvrm. If you decide to install Data Restore in a different library,

you must change any LIBDEF statements that refer to PRD2.RCVvrm.

Machine-Readable Material

IBM distributes the machine-readable product on magnetic tape (reel or cartridge,

non-stack). The format of the tape for VSE is:

File 1

Data Restore Copyright Records

File 2

Data Restore History File

File 3

Data Restore Product File

File 4

Tape Mark

File 5

Tape Mark

Data Restore Guide

This tape is meant to be processed by the VSE maintain system history program

(MSHP) or VSE/II. You need the following information to restore the Data Restore

library:

v The tape label for Data Restore is DB2VSE.RCV.7.1.0

v The library for the product is PRD2

v The sublibrary for the feature is RCVvrm

Ensure that you have a distribution tape in the correct format for your VSE system.

To verify this tape, scan it by running the example JCL shown in Figure 18.

Figure 19 shows a report from the scan job.

The scan report also shows the space requirements for different DASD types. You

need this information if you have to define the library as described in “Step

Define the Library to be Installed” on page 40.

//JOB SCAN TAPE

* *********************************************************************

* PLEASE MOUNT DB2.RCV.7.1.0 DISTRIBUTION TAPE ON A TAPE DRIVE

* AND ASSIGN SYS006 TO THAT TAPE DRIVE.

* THEN PRESS THE ENTER KEY WHEN READY ...

* **********************************************************************

// PAUSE

PLEASE ASSIGN SYS006 NOW ...

// MTC REW,SYS006

// EXEC LIBR

RESTORE * TAPE=SYS006 SCAN=YES

Figure 18. Scanning the Data Restore Feature Version 7.1.0 Distribution Library

RESTORE * TAPE=SYS006 SCAN=YES

L0591 BACKUP FILE ID = ’DB2VSE.RCV.7.1.0’

L123I HISTORY FILE FOUND ON TAPE

L091I SUBLIBRARY XSOFT.RCV710 FOUND ON INPUT TAPE

APPROXIMATE SPACE REQUIREMENT : 1093 LIBRARY BLOCKS

3375 :

59 TRACKS

4 CYLINDERS 11 TRACKS

3380 :

48 TRACKS

3 CYLINDERS

3 TRACKS

3390 :

45 TRACKS

3 CYLINDERS

0 TRACKS

9345 :

53 TRACKS

3 CYLINDERS

8 TRACKS

FBA

2932 BLOCKS

L113I RETURN CODE OF RESTORE IS 0

Figure 19. Report from the Scan Job

IBM-Supplied Installation Aids

To help you install Data Restore on a VSE system, sample job control members are

included on the Data Restore distribution tape. They are distributed as Z-type

source members in the Data Restore sublibrary. Load these members as part of

preparing for installation, as described in “Step 2. Restore the Data Restore

Distribution Library” on page 42.

Depending on how you choose to install Data Restore, you may have to change

some of the job control members before submitting them for execution. These

Chapter 4. Installing Data Restore

members and the changes needed are discussed in the following installation steps.

You can punch these members out of the Data Restore sublibrary into VSE/ICCF

or card decks for editing and re-submission, or, because most of them are short,

you can type them in yourself.

Step

1. Define the Library to be Installed

This step is optional.

If the PRD2 library already exists and there is enough space in the library to

contain the Data Restore feature, skip the rest of this step and go to “Step 2.

Restore the Data Restore Distribution Library” on page 42.

If you want to install Data Restore in a library created in a VSE/VSAM space, you

must:

1. Define the VSAM cluster for the VSE library using the VSAM utility IDCAMS.

2. Prepare DLBL statements for the library.

3. Define the VSE library and sublibrary using the library utility program LIBR.

If you want to install Data Restore in a library created in a non-VSE/VSAM space,

you must:

1. Prepare DLBL and EXTENT statements for the library.

2. Define the VSE library and sublibrary using the library utility program LIBR.

Note: The IBM-supplied installation procedures and examples assume that Data

Restore is installed in library PRD2, sublibrary RCVvrm If you install it

elsewhere, make sure you change the job control statements as needed in all

subsequent procedures and examples.

Step 1.1 Define a Library in VSE/VSAM Space

Refer to your VSAM manual for library cluster definitions. Figure 20 shows a job

that can be used to define a VSE/VSAM library cluster.

// JOB DEFINE VSE LIBRARY

// EXEC IDCAMS,SIZE=AUTO

DEFINE CLUSTER

(1) --->

(NAME(VSE.PRD2.LIBRARY)

(2) --->

VOLUMES(volidn)

NONINDEXED

RECORDFORMAT(NOCIFORMAT)

SHR(3)

(3) --->

CYL(primary secondary)

(4) --->

DATA(NAME(VSE.PRD2.LIBRARY.DATA)))

(4) --->

CATALOG(VSAM.MASTER.CATALOG)

Figure 20. Defining a VSE/VSAM Library Cluster

Statement 1

Use the cluster name VSE.PRD2.LIBRARY. If you change it here,

also change it as shown in Figure 21 on page 41.

Statement 2

Replace volidn with the appropriate volume identification

information.

Statement 3

Use Figure 9 on page 33 to determine the minimum primary and

secondary VSAM space allocations (add 25% free space to allow

for maintenance).

Data Restore Guide

Statement 4

The data name VSE.PRD2.LIBRARY.DATA and the catalog name

VSAM.MASTER.CATALOG are provided as examples. Modify

them to conform to your installation’s standards.

Step 1.2 Prepare the Library DLBL Statements

To define the file names of the library that will contain the Data Restore feature,

prepare DLBL and EXTENT statements for the library, based on the type

(VSE/VSAM or non-VSE/VSAM). One of the job streams shown in Figure 21

stores the applicable statements into the system standard subarea of the label

information area. You should also add the applicable statements to the existing

standard label loading procedure used in the automated system initialization (ASI)

process.

// JOB ADDSTDL FOR VSE LIBRARY IN VSE/VSAM SPACE

// OPTIONS STDLABEL=ADD

(1) ---> // DLBL PRD2,’VSE.PRD2.LIBRARY’,,VSAM,CAT=IJSYSCT,DISP=(OLD,KEEP)

// JOB ADDSTDL FOR VSE LIBRARY IN NON-VSE/VSAM SPACE

// OPTION STDLABEL=ADD

(1) ---> // DLBL PRD2,’VSE.PRD2.LIBRARY’

(2) ---> // EXTENT volidn,1,0,xxx,yyy

Figure 21. Adding the Data Restore Library Information in the Standard Subarea

Statement 1

If you change PRD2 to a different value, make the same change in

all the JCL provided.

Statement 2

Provide the volume identification (volidn) and extent information

(xxx,yyy) in tracks. Refer to the system control statements manual

for your VSE operating system for information on how to code

these values.

Step 1.3 Define the Library and Sublibrary

Use the job shown in Figure 22 to define a new VSE library and sublibrary (either

BAM or VSAM). For more information about library definitions, refer to the

system control statements manual for your VSE system.

// JOB DEFINE LIBRARY & SUBLIBRARY

// EXEC LIBR

ON $RC>4 GOTO ENDJOB

(1) ---> DEFINE LIB=PRD2

DEFINE SUBLIB=PRD2.RCVvrm R=Y

/. ENDJOB

Figure 22. Defining a New Library and Sublibrary for Data Restore

Statement 1

If the library PRD2 already exists, omit the DEFINE LIB statement.

Chapter 4. Installing Data Restore

Step 2. Restore the Data Restore Distribution Library

This step is mandatory.

You can restore the Data Restore distribution library in one of two ways:

v Use the VSE/Interactive Interface, Product Installation Dialog in VSE/ESA. If

you use this method, you need to know that Data Restore is shipped on a

non-stacked V2 format tape. For details on using this method, refer to the

installation manual for your VSE system.

v Create the job control statements member shown in Figure 23 to restore the

distribution library, mount the distribution tape, and run your modified job.

// JOB INSvrRCV

INSTALL DB2 RECOVERY FEATURE

// MTC REW,cuu

*-- REWIND TAPE

// ASSGN SYS002,cuu1

*--AUXILIARY HISTORY FILE

// ASSGN SYS005,UA

*--NO RESTORE TO DOSRES

// ASSGN SYS006,cuu

*--DISTRIBUTION TAPE

// OPTION CATAL

// EXEC MSHP

(1) ---> INSTALL PRODUCT FROM TAPE ID=’DB2VSE.RCV.7.1.0’- *--ACTUAL TAPE ID

(2) ---> PROD IN=PRD2.RCVvrm *--IDENTIFICATION OF LIBRARIES

DEFINE HISTORY AUX EXTENT=xxx:yyy

// MTC RUN,cuu

Figure 23. Job INSvrRCV (Using MSHP to Install Data Restore in VSE)

Before execution, modify the above statements as follows:

cuu

Replace with the address of the tape drive.

cuu1

Replace with the address of the disk drive on which the auxiliary

history file resides.

PRD2.RCVvrm

Replace with the library and sublibrary names you are using.

xxx

Replace with the starting address of the auxiliary history file (in

tracks or blocks).

yyy

Replace with the size of the auxiliary history file (in tracks or

blocks).

Notes:

1. You may receive messages from MSHP. These messages are normal and can be

ignored. For more details about the MSHP control statements, refer to the

messages and codes manual for your VSE operating system.

2. The remaining installation steps do not require the distribution tape.

Step

3. Install Data Restore

To install Data Restore, do the following mandatory steps. You must do them in

order.

Note: Mandatory steps are marked with an asterisk (*). Optional steps are marked

with a circle (Resource Adapter Change transaction (CIRC)).

Step 3.1 * Acquire the required dbspaces.

Step 3.2 * Create the required tables.

Data Restore Guide

Step 3.3 * Reload the Data Restore packages.

Step 3.4 * Link-edit the Data Restore PRDI.

Step 3.5 * Define the VSAM files required for Data Restore.

Step 3.6 Resource Adapter Change transaction (CIRC) Define default values for

Data Restore parameters.

Note: If a procedure within any of the steps does not execute successfully, correct

the problem and rerun the entire step before continuing.

Technique used for installation:

All of the job control members used in the install process are in the Data Restore

sublibrary cataloged as Z-type members. You can use the job shown in Figure 24 as

an example of the JCL required to punch out the job control members.

// JOB PUNCH Z TYPE

* ***************************************************

* PURPOSE : JOB STREAM TO PUNCH OUT MEMBER XXXXXXXX.Z

* ***************************************************

// EXEC LIBR,PARM=’MSHP’

ACCESS SUBLIB=PRD2.RCVvrm

PUNCH XXXXXXXX.Z

Figure 24. Example of JCL Required to Punch Out Z-TYPE Members

You may have to modify several job control statements before execution as

specified in the following steps.

Step 3.1 Acquire the Required Dbspaces

This step is mandatory.

You need three public dbspaces:

6400-page dbspace which is defined for Data Restore’s internal use

1024-page dbspace which is defined for Data Restore’s internal use

128-page dbspace which is used to force a checkpoint to maintain data integrity

if you use the UNLOAD function while the database is running.

Note: This dbspace is not acquired during installation.

To acquire the dbspaces needed by Data Restore, run the job control member

XTS9ACQ as shown in Figure 25 on page 44. This job should end with a DB2

Server for VSE & VM return code of 0. Ensure that the job is run successfully

before continuing.

Chapter 4. Installing Data Restore

(1) ---> ..* $$ JOB JNM=XTS9ACQ,CLASS=0

// JOB XTS9ACQ

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* XTS9ACQ : Data Restore FEATURE

: ACQUIRING DBSPACES

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

(2) ---> // LIBDEF *,SEARCH=PRD2.DB2vrm

(3) ---> // EXEC ARIDBS,SIZE=AUTO,PARM=’DBNAME(dbname)’

(4) ---> CONNECT SQLDBA IDENTIFIED BY XXXXXXXX;

(5) ---> ACQUIRE PUBLIC DBSPACE NAMED DATARFTR(PAGES=6400,PCTFREE=0,STORPOOL=xx);

(5) ---> ACQUIRE PUBLIC DBSPACE NAMED DATARFT2(PAGES=1024,PCTFREE=0,STORPOOL=xx,

PCTINDEX=10);

..* $$ EOJ

Figure 25. Job XTS9ACQ (Acquiring Dbspaces)

Statement 1

Alter the POWER statement to run the job in an appropriate class.

Statement 2

Specifies the DB2 R710 library.

Statement 3

Runs program ARIDBS (the database services utility) to acquire the

required dbspaces. Replace dbname with the appropriate database

name or remove the PARM= specification if you are accessing the

default database.

Statement 4

Specify the connect password for userid SQLDBA. SQLDBA must

be defined with DBA authority.

Statement 5

Acquires the required public dbspaces.

Note: With the STORPOOL parameter, you may select either a recoverable or a

nonrecoverable storage pool. Define the dbspaces in a nonrecoverable

storage pool, if possible.

Step 3.2 Create the Required Tables

This step is mandatory.

To create the Data Restore tables, run the job control member XTS9CRE shown in

Table 4. Punch the member; if the user retypes it, errors may occur. The job should

end with an SQLCODE of 0. Ensure the job is run successfully. If not, review the

report created, correct the cause of the error, and rerun the job.

Table 4. Job XTS9CRE (Create Environment)

(1) ---> ..* $$ JOB JNM=XTS9CRE,CLASS=0

// JOB XTS9CRE

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* XTS9CRE : Data Restore FEATURE

: CREATE DATA BASE MANAGER ENVIRONMENT

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* XTS9CRE : Data Restore FEATURE

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

(2) ---> // LIBDEF *,SEARCH=PRD2.DB2vrm

(3) ---> // EXEC ARIDBS,SIZE=AUTO,PARM=’DBNAME(dbname)’

(4) ---> CONNECT SQLDBA IDENTIFIED BY XXXXXXXX;

CREATE TABLE IXLNGVAR (DBNO SMALLINT NOT NULL,PAGENO INTEGER NOT NULL

Data Restore Guide

Table 4. Job XTS9CRE (Create Environment) (continued)

,RECNO INTEGER NOT NULL) IN DATARFT2;

COMMIT WORK;

..* $$ EOJ

Statement 1

Alter the POWER statement to run the job in an appropriate class.

Statement 2

Specifies the DB2 Server for VSE & VM R710 library.

Statement 3

Runs program ARIDBS (the database services utility) to acquire the

required dbspaces. Replace dbname with the appropriate database

name or remove the PARM= specification if you are accessing the

default database.

Statement 4

Specify the connect password for userid SQLDBA. SQLDBA must

be defined with DBA authority.

Step 3.3 Reload the Data Restore Packages

This step is mandatory.

To reload the Data Restore packages, run the job control member XTS9PREP shown

in Figure 26. You must punch the job to run it. It cannot be retyped. Update the

database name and password before you run the job.

The job should end with an SQLCODE of 0. Ensure the job is run successfully. If

not, review the report created, correct the cause of the error, and rerun the job.

Note: If the job is run more than once in a database, an error may occur on the

revoke command. This error can be ignored.

(1) ---> ..* $$ JOB JNM=XTS9PREP,CLASS=0

// JOB XTS9PREP

// LIBDEF *,SEARCH=PRD2.DB2vrm

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* XTS9PREP: Data Restore FEATURE

: RELOAD PACKAGES

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

(2) ---> // EXEC ARIDBS,SIZE=AUTO,PARM=’DBNAME(dbname)’

(3) ---> CONNECT SQLDBA IDENTIFIED BY XXXXXXXX;

(4) ---> RELOAD PROGRAM(SQLDBA.LMBRP029) INFILE(SYSIPT) REPLACE;

(6) ---> GRANT RUN ON LMBRP064 TO PUBLIC;

GRANT RUN ON XTS91002 TO PUBLIC;

SET ERRORMODE CONTINUE;

(7) ---> REVOKE CONNECT FROM DATARFTR;

COMMIT WORK;

..* $$ EOJ

Figure 26. Job XTS9PREP (Reload Packages)

Statement 1

Alter the POWER statement to run the job in an appropriate class.

Chapter 4. Installing Data Restore

Statement 2

Runs program ARIDBS (the database services utility) to acquire the

required dbspaces. Replace dbname with the appropriate database

name or remove the PARM= specification if you are accessing the

default database.

Statement 3

Specify the connect password for userid SQLDBA. SQLDBA must

be defined with DBA authority.

Statement 4

Reloads the programs.

Statement 5

The package to be reloaded (only one example is provided).

Statement 6

Grants authorization to run the programs.

Statement 7

Revokes connect authority from the userid DATARFTR.

Step 3.4 Link-edit the Data Restore PRDI

This step is mandatory.

To link-edit XTSOPRDI, run the job control member XTS9PRDI shown in Figure

27.

This job should end with a return code of 0.

(1) ---> ..* $$ JOB JNM=XTS9PRDI,CLASS=0

// JOB XTS9PRDI

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* XTS9PRDI: Data Restore FEATURE

: LINK EDIT XTSOPRDI

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

(2) ---> // LIBDEF PHASE,CATALOG=PRD2.RCVvrm

/ rcv sublibrary

(3) ---> // LIBDEF OBJ,SEARCH=PRD2.DB2vrm

/ sql/ds sublibrary

// OPTION CATAL

(4) ---> PHASE XTSOPRDI,*

(5) ---> INCLUDE ARIPRDID

(6) ---> // EXEC LNKEDT,PARM=’RMODE=24’

..* $$ EOJ

Figure 27. Job XTS9PRDI (Link-edit XTSOPRDI)

Statement 1

Alter the POWER statement to run the job in an appropriate class.

Statement 2

Catalogs the phase into the Data Restore library.

Statement 3

Specifies the DB2 Server for VSE library.

Statement 4

The executable phase is XTSOPRDI.

Statement 5

Includes ARIPRDID to be link-edited.

Statement 6

Executes the Linkage Editor.

Step 3.5 Define the VSAM Files for Data Restore

This step is mandatory.

To define the required VSAM files, run the job control member XTS9DEF shown in

Figure 28 on page 47.

The job ends with a return code of 8 on first execution because the DELETE

CLUSTER command is processed for clusters that do not yet exist.

Data Restore Guide

(1) ---> ..* $$ JOB JNM=XTS9DEF,CLASS=0

// JOB XTS9DEF

* * * * * * * * * * * * * * * * * * * * * * *

* XTS9DEF : Data Restore FEATURE

: DEFINE VSAM FILES

* * * * * * * * * * * * * * * * * * * * * * *

(2) ---> // DLBL IJSYSUC,’vsesp.user.catalog’,,VSAM

(3) ---> // EXEC IDCAMS,SIZE=AUTO

(4) ---> DELETE DIRWORK PURGE CLUSTER

(5) ---> DEFINE CLUSTER(NAME(DIRWORK) CYL(06)-

(6) --->

VOLUME(vvvvvv) CISZ(512) REUSE-

RECSZ(505 505) SHR(2) NIXD)

DELETE LMBRWRK PURGE CLUSTER

(7) ---> DEFINE CLUSTER(NAME(LMBRWRK) CYL(05)-

(6) --->

VOLUME(vvvvvv) CISZ(4096) REUSE-

RECSZ(4089 4089) SHR(2) NIXD)

DELETE LMBRLG1

PURGE CLUSTER

(8) ---> DEFINE CLUSTER(NAME(LMBRLG1) CYL(01)-

(6) --->

VOLUME(vvvvvv) REUSE-

RECSZ(4096 4096) SHR(2) NIXD)

DELETE LMBRLG2

PURGE CLUSTER

(9) ---> DEFINE CLUSTER(NAME(LMBRLG2) CYL(01)-

(6) --->

VOLUME(vvvvvv) REUSE-

RECSZ(4096 4096) SHR(2) NIXD)

DELETE LMBRLG3

PURGE CLUSTER

(10) ---> DEFINE CLUSTER(NAME(LMBRLG3) CYL(01)-

(6) --->

VOLUME(vvvvvv) REUSE-

RECSZ(4096 32750) SHR(2) NUMBERED)

..* $$ EOJ

Figure 28. Job XTS9DEF (Define VSAM Files)

Statement 1

Alter the POWER statement to run the job in an appropriate class.

Statement 2

Specifies the VSE/VSAM user catalog.

Statement 3

Executes IDCAMS to define the required clusters.

Statement 4

Deletes the cluster before redefining it.

Statement 5

Defines the DIRWORK cluster. Modify the CYL parameter to match

the size of the database directory disk (BDISK).

Statement 6

Replace vvvvvv with the appropriate volume identifier.

Statement 7

Defines the LMBRWRK cluster to contain all of the active pages for

the biggest dbspace to be reloaded with the RECOVERY=YES

parameter, or the biggest dbspace containing a LONG column.

Statement 8

Defines LMBRLG1 to contain all of the changes executed on the

database for tables to be reloaded with the RECOVERY=YES

parameter. The maximum of this cluster would be the size of the

log disk; however, this is rarely required.

Statement 9

Defines LMBRLG2 to contain 5 bytes per rollback LUW (logical

unit of work) in the log files during the RECOVERY process.

Statement 10

Defines LMBRLG3 to contain LONGVARCHAR columns for the

updated rows.

Note: You can specify a secondary allocation for all of the clusters.

Chapter 4. Installing Data Restore

Step 3.6 Define Default Values for Data Restore Parameters

This step is optional.

While using Data Restore, you can pass parameters in SYSIPT by using the

OPTIONS statement. Instead of passing these parameters, you can modify and

assemble the LMBRPARM program to specify default values for them.

To customize your parameter defaults, punch the XTS9PARM.Z member and

specify the appropriate values in the LMBRPARM macro as shown in Figure 29 on

page 49.

Notes:

1. Do not change the source for the LMBRPARM macro definition. Change

statement 5 only.

2. To specify more than one parameter, separate each parameter with a comma.

Assembler continuation rules apply.

Data Restore Guide

(1)

--->

..* $$ JOB JNM=XTS9PARM,CLASS=0

// JOB XTS9PARM

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* XTS9PARM: Data Restore FEATURE

: CATALOG DEFAULT VALUES

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

(2)

--->

// LIBDEF PHASE,CATALOG=PRD2.RCVvrm

(2)

--->

// LIBDEF *,SEARCH=PRD2.RCVvrm

// OPTION CATAL

(3)

---> PHASE LMBRPARM,*

// EXEC ASSEMBLY,SIZE=512K

(4)

--->

MACRO

LMBRPARM &NOTA=E,&CASE=M,&DEVICE=TAPE,

&COMMIT=0,&MSGCLAS=1,&MSGDEV=3,

&DBAPW=SQLDBAPW,&BASE=SQL/DS V3R5,&LANG=S001,&CONFIRM=YES

LCLB

&BIT1,&BIT2;

CL11’&PWD’

&BIT1

SETB

(’&DEVICE’ EQ ’TAPE’)

&BIT2

SETB

(’&DEVICE’ EQ ’DASD’)

AL1(&BIT1+&BIT2*2)

&BIT1

SETB

(’&NOTA’(1,1) EQ ’E’)

AL1(&BIT1)

&BIT1

SETB

(’&CASE’(1,1) EQ ’M’)

&BIT2

SETB

(’&CASE’(1,1) EQ ’U’)

AL1(&BIT1+&BIT2*2)

AL4(&COMMIT)

AL1(&MSGCLAS)

AL1(&MSGDEV)

CL8’&DBAPW’

CL8’&BASE’

CL4’&LANG’

CL1’&CONFIRM’

MEND

LMBRPARM CSECT

* in order to customize your default table

* modify the following statement specifying all required parameters

(5)

--->

LMBRPARM LANG=S001

END

LMBRPARM

// EXEC LNKEDT,PARM=’MSHP,RMODE=24’

..* $$ EOJ

Figure 29. Job XTS9PARM (Catalog Default Values)

Statement 1

Alter the POWER statement to run the job in an appropriate class.

Statement 2

Specifies the sublibrary for Data Restore.

Statement 3

Assembles and link-edits the LMBRPARM phase.

Statement 4

Defines the macro.

Statement 5

Specify your default values for any parameter defined in the

LMBRPARM macro (statement 4). The defaults entered here

override the installation defaults.

Refer to “OPTIONS and CONTROL Statements” on page 167, for additional

information on parameter values.

Chapter 4. Installing Data Restore

Starting Data Restore in a VSE Environment

You can execute a job by specifying the library in which Data Restore is installed,

unless it is defined in standard libraries. (You can create the jobs and store them in

standard libraries for later use.)

You can define a job like the one in Figure 30 to execute the Data Restore functions

in a VSE environment.

// JOB BACKUP

// LIBDEF *,SEARCH=(PRD2.DB2vrm,PRD2.RCVvrm)

// EXEC PROC=ARIS73DB

// TLBL ARCHIV,’ARCHIVE.DB2’

// ASSGN SYS006,180

// MTC REW,SYS006

// EXEC XTS91001,SIZE=AUTO

.. function to process

Figure 30. Example JCL to Execute Data Restore Functions

The SYSIN file specifies the command to process in the JCL after the EXEC

XTS91001 statement.

Section

3. Installing Under VSE Guest Sharing

The procedure for installing Data Restore in a VSE Guest Sharing environment has

five steps:

1. Define the requirements for VM resources.

2. Define the requirements for the database manager resources.

3. Run the supplied EXECs to complete the VM installation.

4. Define the requirements for VSE resources.

5. Run the supplied jobs to complete the VSE installation.

Note: In a VSE Guest Sharing environment, only RELOAD with RECOVERY=NO

can be executed from a VSE partition. No other Data Restore functions are

available since these functions need direct access (LINK and ACCESS) to the

database mini-disks. It is strongly recommended that Data Restore be

installed as a VM product in a VSE Guest Sharing environment.

Step 1. Define the VM Resources

This step is mandatory.

1. Define a new VM userid for Data Restore and ensure that it can access all of

the application servers. The minimum virtual storage size for this machine is 8

MB.

2. Allocate a minidisk of the required size (see Figure 31 on page 51) to this

userid. Format the minidisk (using the CMS FORMAT command) with a block

size of 4 KB.

Data Restore Guide

3375 :

16 CYLINDERS

3380 :

10 CYLINDERS

3390 :

9 CYLINDERS

9345 :

10 CYLINDERS

FBA

10000 BLOCKS

Figure 31. Minidisk Space Calculation for Data Restore VM Installation

3. If you are using an external security manager like RACF, make sure that this

machine is authorized to access the minidisks of the application server

(including the directory, log, and dbextent disks) in both read and write mode.

(See “Security and Authorizing Access to the Server Minidisks (VM Only)” on

page 65 for more information).

4. Verify that your machine can link to the application server’s 195 (production)

minidisk.

Step

2. Define the Database Manager Resources

This step is mandatory.

In this step, you define the resources in the database manager so that you can run

Data Restore.

You need three public dbspaces:

6400-page dbspace which is defined for Data Restore’s internal use

1024-page dbspace which is defined for Data Restore’s internal use

128-page dbspace which is used to force a checkpoint to maintain data integrity

if you use the UNLOAD function while the database is running.

Note: This dbspace is not acquired during installation.

Using ISQL, enter the following commands:

(1) ---> SQLINIT DBNAME(dbname)

(2) ---> ISQL

(3) ---> CONNECT SQLDBA IDENTIFIED BY XXXXXXXX

(4) ---> ACQUIRE PUBLIC DBSPACE NAMED DATARFTR (PAGES=6400,PCTFREE=0,STORPOOL=n)

(5) ---> ACQUIRE PUBLIC DBSPACE NAMED DATARFT2 (PAGES=1024,PCTFREE=0,PCTINDEX=10,

STORPOOL=n)

(6) ---> EXIT

Figure 32. Acquiring the Required Dbspaces.

Note: With the STORPOOL parameter, you may select either a recoverable or a

nonrecoverable storage pool. Use a nonrecoverable storage pool, if possible.

Statement 1

Initializes a connection to the database with the appropriate

parameters.

Statement 2

Invokes the Interactive SQL environment.

Statement 3

Signs on to the application server with DBA authority. (Replace

XXXXXXXX with the connect password for SQLDBA.)

Statement 4

Acquires a required public dbspace.

Statement 5

Acquires a required public dbspace.

Chapter 4. Installing Data Restore

Statement 6

Exits the ISQL environment.

You are now ready to complete the Data Restore installation on VM.

Step

3. Complete the VM Installation Process

This process consists of four mandatory steps and two optional steps.

Step 3.1 Load Data Restore from Tape

This step is mandatory.

Log on to the Data Restore userid and execute the commands in Figure 33.

(1) ---> ACCESS cuu1 A

(2) ---> ATTACH cuu2 to * as 181

(3) ---> VMFPLC2 REW

(4) ---> VMFPLC2 LOAD

(5) ---> SQLINIT DBNAME(dbname)

Figure 33. Loading the Installation Files

Statement 1

Accesses the minidisk cuu1 that was defined in step 1 (the

minidisk must already be formatted).

Statement 2

Attaches tape drive cuu2 as 181 and mounts the Data Restore tape

on this drive.

Statement 3

Rewinds the tape on drive 181.

Statement 4

Loads the contents of the tape.

Statement 5

Runs the SQLINIT EXEC with the appropriate parameters to

connect to the correct database.

Step 3.2 Create the Database Environment

This step is mandatory.

Run the following EXEC:

XTS9CRE

Figure 34. Creating the Database Environment

This EXEC creates the required database environment; for example, tables used

internally by the product.

When prompted, enter the appropriate SQL CONNECT statement to connect to the

database as user SQLDBA, or, if the VM userid has DBA authority, press the enter

key.

Step 3.3 Load the Data Restore Packages

This step is mandatory.

Run the following EXEC:

Data Restore Guide

XTS9PREP

Figure 35. Loading the Data Restore Packages

This EXEC loads the Data Restore packages into the database.

When prompted, enter the appropriate SQL CONNECT statement to connect to the

database as user SQLDBA, or, if the VM userid has DBA authority, press the enter

key.

Step 3.4 Create the Data Restore Modules

This step is mandatory.

Run the following EXEC:

XTS9GMOD

Figure 36. Creating the Data Restore Modules

This EXEC creates the Data Restore executable modules XTS91001, and XTS91002.

These modules are used to invoke various functions such as BACKUP, etc.

Data Restore is now installed in one application server. You may want to take a

backup of your database at this point.

Note: Refer to “Step 3.5 Install in Additional Application Servers” on page 36 if

you want to install Data Restore in additional application servers in the

same VM system.

Step 3.5 Define Default Values for Data Restore Parameters

This step is optional.

While using Data Restore, you can pass parameters in the SYSIN file. Instead of

passing these parameters, you can modify and assemble the LMBRPARM program

to specify default values for them.

v Edit the XTS9PARM ASSEMBLE program to customize the parameters shown in

Figure 37 on page 54, specifying the appropriate value in the LMBRPARM macro.

Notes:

1. Do not change the source for the LMBRPARM macro definition. Change

statement 2 only.

2. To specify more than one parameter, separate each parameter with a comma.

Assembler continuation rules apply.

Chapter 4. Installing Data Restore

(1) --->

MACRO

(1) --->

LMBRPARM &NOTA=E,&CASE=M,&PWD=A,&DEVICE=TAPE,

(1) --->

&COMMIT=0,&MSGCLAS=1,&MSGDEV=3,

(1) --->

&DBAPW=SQLDBAPW,&BASE=SQL/DS V3R5,&LANG=S001,&CONFIRM=YES

LCLB

&BIT1,&BIT2;

CL11’&PWD’

&BIT1

SETB

(’&DEVICE’ EQ ’TAPE’)

&BIT2

SETB

(’&DEVICE’ EQ ’DASD’)

AL1(&BIT1+&BIT2*2)

&BIT1

SETB

(’&NOTA’(1,1) EQ ’E’)

AL1(&BIT1)

&BIT1

SETB

(’&CASE’(1,1) EQ ’M’)

&BIT2

SETB

(’&CASE’(1,1) EQ ’U’)

AL1(&BIT1+&BIT2*2)

AL4(&COMMIT)

AL1(&MSGCLAS)

AL1(&MSGDEV)

CL8’&DBAPW’

CL8’&BASE’

CL4’&LANG’

CL1’&CONFIRM’

MEND

LMBRPARM CSECT

* in order to customize your default table

** modify the following statement specifying all required parameters

(2) --->

LMBRPARM LANG=S001

END

LMBRPARM

Figure 37. XTS9PARM ASSEMBLE Program (Catalog Default Values)

Statement 1

Defines the macro.

Statement 2

Specify your default value for any parameter defined in the

LMBRPARM MACRO (statement 1). The defaults entered here

override the installation defaults.

Refer to “OPTIONS and CONTROL Statements” on page 167 for more information

on parameter values.

v Assemble the modified program containing your default values and re-execute

“Step 3.4 Create the Data Restore Modules” on page 53.

Step

4. Define the VSE Resources

Refer to “Section 2. Installing Under VSE” on page 38 for initial considerations for

installing Data Restore on a VSE system.

Step 4.1 Define the Library to be Installed

This step is optional.

If the PRD2 library already exists, and there is enough space in the library to

contain the Data Restore feature, skip the rest of this step and go to “Step 4.5

Restore the Data Restore Distribution Library” on page 56.

If you want to install Data Restore in a library created in a VSE/VSAM space, you

must:

1. Define the VSAM cluster for the VSE library using the VSAM utility IDCAMS.

2. Prepare DLBL statements for the library.

3. Define the VSE library and sublibrary using the library utility program LIBR.

Data Restore Guide

If you want to install Data Restore in a library created in a non-VSE/VSAM space,

you must:

1. Prepare DLBL and EXTENT statements for the library.

2. Define the VSE library and sublibrary using the library utility program LIBR.

Note: The IBM-supplied installation procedures and examples assume that Data

Restore is installed in library PRD2, sublibrary RCVvrm. If you install it

elsewhere make sure you change the job control statements as needed in all

subsequent procedures and examples.

Step 4.2 Define a Library in VSE/VSAM Space

Refer to your VSAM manual for library cluster definitions. Figure 38 shows a job

that can be used to define a VSE/VSAM library cluster.

// JOB DEFINE VSE LIBRARY

// EXEC IDCAMS,SIZE=AUTO

DEFINE CLUSTER

(1) --->

(NAME(VSE.PRD2.LIBRARY)

(2) --->

VOLUMES(volidn)

NONINDEXED

RECORDFORMAT(NOCIFORMAT)

SHR(3)

(3) --->

CYL(primary secondary)

(4) --->

DATA(NAME(VSE.PRD2.LIBRARY.DATA)))

(4) --->

CATALOG(VSAM.MASTER.CATALOG)

Figure 38. Defining a VSE VSAM Library Cluster

Statement 1

Use the cluster name VSE.PRD2.LIBRARY. If you change it here,

also change it as shown in Figure 39 on page 56.

Statement 2

Replace volidn with the appropriate volume identification

information.

Statement 3

Use Figure 9 on page 33 to determine the minimum primary and

secondary VSAM space allocations (add 25% free space to allow

for maintenance).

Statement 4

The data name VSE.PRD2.LIBRARY.DATA and the catalog name

VSAM.MASTER.CATALOG are provided as examples. Modify

them to conform to your installation’s standards.

Step 4.3 Prepare the Library DLBL Statements

To define the file names of the library that will contain the Data Restore feature,

prepare DLBL and EXTENT statements for the library, based on the type

(VSE/VSAM or non-VSE/VSAM). One of the job streams shown in Figure 39 on

page 56 stores the applicable statements into the system standard subarea of the

label information area. You should also add the applicable statements to the

existing standard label loading procedure used in the automated system

initialization (ASI) process.

Chapter 4. Installing Data Restore

In the Standard Label Area

// JOB ADDSTDL FOR VSE LIBRARY IN VSE/VSAM SPACE

// OPTIONS STDLABEL=ADD

(1) ---> // DLBL PRD2,’VSE.PRD2.LIBRARY’,,VSAM,CAT=IJSYSCT,DISP=(OLD,KEEP)

// JOB ADDSTDL FOR VSE LIBRARY IN NON-VSE/VSAM SPACE

// OPTION STDLABEL=ADD

(1) ---> // DLBL PRD2,’VSE.PRD2.LIBRARY’

(2) ---> // EXTENT volidn,1,0,xxx,yyy

Figure 39. Adding the Data Restore Library Information in the Standard Subarea

Statement 1

If you change PRD2 to a different value, make the same change in

all the JCL provided.

Statement 2

Provide the volume identification (volidn) and extent information

(xxx,yyy) in tracks. Refer to the system control statements manual

for your VSE operating system for information on how to code

these values.

Step 4.4 Define the Library and Sublibrary

Use the job shown in Figure 40 to define a new VSE library and sublibrary (either

BAM or VSAM). For more information about library definitions, refer to the

control statements manual for your VSE system.

// JOB DEFINE LIBRARY & SUBLIBRARY

// EXEC LIBR

ON $RC>4 GOTO ENDJOB

(1) ---> DEFINE LIB=PRD2

DEFINE SUBLIB=PRD2.RCVvrm R=Y

/.ENDJOB

Figure 40. Defining a New Library and Sublibrary for Data Restore

Statement 1

If the library PRD2 already exists, omit the DEFINE LIB statement.

Step 4.5 Restore the Data Restore Distribution Library

This step is mandatory.

You can restore the Data Restore distribution library in one of two ways:

v Use the VSE/Interactive Interface, Product Installation Dialog in VSE/ESA. If

you use this method, you need to know that Data Restore is shipped on a

non-stacked V2 format tape. For details on using this method, refer to the

installation manual for your VSE system.

v Create the job control statements member shown in Figure 41 on page 57 to

restore the distribution library, mount the distribution tape, and run your

modified job.

Data Restore Guide

// JOB INSvrRCV

INSTALL Data Restore FEATURE

// MTC REW,cuu

*-- REWIND TAPE

// ASSGN SYS002,cuu1

*--AUXILIARY HISTORY FILE

// ASSGN SYS005,UA

*--NO RESTORE TO DOSRES

// ASSGN SYS006,cuu

*--DISTRIBUTION TAPE

// OPTION CATAL

// EXEC MSHP

INSTALL PRODUCT FROM TAPE ID=’DB2VSE.RCV.7.1.0’- *-ACTUAL TAPE ID

PROD IN=PRD2.RCVvrm *--IDENTIFICATION OF LIBRARIES

DEFINE HISTORY AUX EXTENT=xxx:yyy

// MTC RUN,cuu

Figure 41. Job INSvrRCV (Using MSHP to Install Data Restore in VSE)

Before execution, modify the above statements as follows:

cuu

Replace with the address of the tape drive.

cuu1

Replace with the address of the disk drive on which the auxiliary

history file resides.

PRD2.RCVvrm

Replace with the library and sublibrary names you are using.

xxx

Replace with the starting address of the auxiliary history file (in

tracks or blocks).

yyy

Replace with the size of the auxiliary history file (in tracks or

blocks).

Notes:

1. You may receive messages from MSHP. These messages are normal and can be

ignored. For more details about the MSHP control statements, refer to the

messages and codes manual for your VSE operating system.

2. The remaining installation steps do not require the distribution tape.

Step

5. Complete the VSE Installation Process

This process consists of two mandatory steps and one optional step. You must do

these steps in order.

v Link-edit the Data Restore PRDI.

v Define the VSAM files for Data Restore.

v Define default values for Data Restore parameters.

Step 5.1 Link-edit the Data Restore PRDI

This step is mandatory.

To link-edit XTSOPRDI, run the job control member XTS9PRDI shown in Figure 42

on page 58. This job should end with a return code of 0.

Chapter 4. Installing Data Restore

(1) ---> ..* $$ JOB JNM=XTS9PRDI,CLASS=0

// JOB XTS9PRDI

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* XTS9PRDI: Data Restore FEATURE

: LINK EDIT XTSOPRDI

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

(2) ---> // LIBDEF PHASE,CATALOG=PRD2.RCVvrm

/ rcv sublibrary

(3) ---> // LIBDEF OBJ,SEARCH=PRD2.DB2vrm

/ DB2 Server for VSE sublibrary

// OPTION CATAL

(4) ---> PHASE XTSOPRDI,*

(5) ---> INCLUDE ARIPRDID

(6) ---> // EXEC LNKEDT,PARM=’RMODE=24’

..* $$ EOJ

Figure 42. Job XTS9PRDI (Link-edit XTSOPRDI)

Statement 1

Alter the POWER statement to run the job in an appropriate class.

Statement 2

Catalogs the phase into the Data Restore library.

Statement 3

Specifies the DB2 Server for VSE & VM library.

Statement 4

The executable phase is XTSOPRDI.

Statement 5

Includes ARIPRDID to be link-edited.

Statement 6

Executes the Linkage Editor.

Step 5.2 Define the VSAM Files for Data Restore

This step is mandatory.

To define the required VSAM files, run the job control member XTS9DEF shown in

Figure 43 on page 59.

The job ends with a return code of 8 on first execution because the DELETE

CLUSTER command is processed for clusters that do not yet exist.

Data Restore Guide

(1) ---> ..* $$ JOB JNM=XTS9DEF,CLASS=0

// JOB XTS9DEF

* * * * * * * * * * * * * * * * * * * * * * *

* XTS9DEF : Data Restore FEATURE

: DEFINE VSAM FILES

* * * * * * * * * * * * * * * * * * * * * * *

(2) ---> // DLBL IJSYSUC,’vsesp.user.catalog’,,VSAM

(3) ---> // EXEC IDCAMS,SIZE=AUTO

(4) ---> DELETE DIRWORK PURGE CLUSTER

(5) ---> DEFINE CLUSTER(NAME(DIRWORK) CYL(06)-

(6) --->

VOLUME(vvvvvv) CISZ(512) REUSE-

RECSZ(505 505) SHR(2) NIXD)

DELETE LMBRWRK PURGE CLUSTER

(7) ---> DEFINE CLUSTER(NAME(LMBRWRK) CYL(05)-

(6) --->

VOLUME(vvvvvv) CISZ(4096) REUSE-

RECSZ(4089 4089) SHR(2) NIXD)

DELETE LMBRLG1

PURGE CLUSTER

(8) ---> DEFINE CLUSTER(NAME(LMBRLG1) CYL(01)-

(6) --->

VOLUME(vvvvvv) REUSE-

RECSZ(4096 4096) SHR(2) NIXD)

DELETE LMBRLG2

PURGE CLUSTER

(9) ---> DEFINE CLUSTER(NAME(LMBRLG2) CYL(01)-

(6) --->

VOLUME(vvvvvv) REUSE-

RECSZ(4096 4096) SHR(2) NIXD)

DELETE LMBRLG3

PURGE CLUSTER

(10) ---> DEFINE CLUSTER(NAME(LMBRLG3) CYL(01)-

(6) --->

VOLUME(vvvvvv) REUSE-

RECSZ(4096 32750) SHR(2) NUMBERED)

..* $$ EOJ

Figure 43. Job XTS9DEF (Define VSAM Files)

Statement 1

Alter the POWER statement to run the job in an appropriate class.

Statement 2

Specifies the VSE/VSAM user catalog.

Statement 3

Executes IDCAMS to define the required clusters.

Statement 4

Deletes the cluster before redefining it.

Statement 5

Defines the DIRWORK cluster. Modify the CYL parameter to match

the size of the database directory disk (BDISK).

Statement 6

Replace vvvvvv with the appropriate volume identifier.

Statement 7

Define the LMBRWRK cluster to contain all of the active pages for

the biggest dbspace to be reloaded with the RECOVERY=YES

parameter, or the biggest dbspace containing a LONG column.

Statement 8

Define LMBRLG1 to contain all of the changes executed on the

database for tables to be reloaded with the RECOVERY=YES

parameter. The maximum of this cluster would be the size of the

log disk; however, this is rarely required.

Statement 9

Define LMBRLG2 to contain 5 bytes per rollback LUW (logical unit

of work) in the log files during the RECOVERY process.

Statement 10

Define LMBRLG3 to contain LONGVARCHAR columns for the

updated rows.

Note: You can specify a secondary allocation for all of the clusters.

Chapter 4. Installing Data Restore

Step 5.3 Define Default Values for Data Restore Parameters

This step is optional.

While using Data Restore, you can pass parameters in SYSIPT by using the

OPTIONS statement. Instead of passing these parameters, you can modify and

assemble the LMBRPARM program to specify default values for them.

To customize your parameter defaults, punch the XTS9PARM.Z member and

specify the appropriate values in the LMBRPARM macro as shown in Figure 44 on

page 61.

Notes:

1. Do not change the source for the LMBRPARM macro definition. Change

statement 5 only.

2. To specify more than one parameter, separate each parameter with a comma.

Assembler continuation rules apply.

Data Restore Guide

(1)

--->

..* $$ JOB JNM=XTS9PARM,CLASS=0

// JOB XTS9PARM

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* XTS9PARM: Data Restore FEATURE

: CATALOG DEFAULT VALUES

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

(2)

--->

// LIBDEF PHASE,CATALOG=PRD2.RCVvrm

(2)

--->

// LIBDEF *,SEARCH=PRD2.RCVvrm

// OPTION CATAL

(3)

---> PHASE LMBRPARM,*

// EXEC ASSEMBLY,SIZE=512K

(4)

--->

MACRO

LMBRPARM &NOTA=E,&CASE=M,&DEVICE=TAPE,

&COMMIT=0,&MSGCLAS=1,&MSGDEV=3,

&DBAPW=SQLDBAPW,&BASE=SQL/DS V3R5,&LANG=S001,&CONFIRM=YES

LCLB

BIT1,&BIT2;

CL11’&PWD’

&BIT1

SETB

(’&DEVICE’ EQ ’TAPE’)

&BIT2

SETB

(’&DEVICE’ EQ ’DASD’)

AL1(&BIT1+&BIT2*2)

&BIT1

SETB

(’&NOTA’(1,1) EQ ’E’)

AL1(&BIT1)

&BIT1

SETB

(’&CASE’(1,1) EQ ’M’)

&BIT2

SETB

(’&CASE’(1,1) EQ ’U’)

AL1(&BIT1+&BIT2*2)

AL4(&COMMIT)

AL1(&MSGCLAS)

AL1(&MSGDEV)

CL8’&DBAPW’

CL8’&BASE’

CL4’&LANG’

CL1’&CONFIRM’

MEND

LMBRPARM CSECT

* in order to customize your default table

* modify the following statement specifying all required parameters

(5)

--->

LMBRPARM LANG=S001

END

LMBRPARM

// EXEC LNKEDT,PARM=’MSHP,RMODE=24’

..* $$ EOJ

Figure 44. Job XTS9PARM (Catalog Default Values)

Statement 1

Alter the POWER statement to run the job in an appropriate class.

Statement 2

Specifies the sublibrary for Data Restore.

Statement 3

Assembles and link-edits the LMBRPARM phase.

Statement 4

Defines the macro.

Statement 5

Specify your default values for any parameter defined in the

LMBRPARM macro (statement 4). The defaults entered here

override the installation defaults.

Refer to “OPTIONS and CONTROL Statements” on page 167 for additional

information on parameter values.

Chapter 4. Installing Data Restore

Complex Environment Considerations

Installation Considerations

The previous sections contain installation instructions for simple environments;

generally, with one or more databases in a single VM or VSE system, or in a single

VM/VSE Guest Sharing environment.

This section will consider more complex installations, with multiple databases in

multiple operating systems on multiple processors.

A complete installation of Data Restore, as described in previous sections, is

needed on every independent system which has a DB2 Server for VSE & VM

server installed. Some installation steps must be repeated for every additional

server on the same system. If you do not do these steps for a server, Data Restore

cannot be used with that server.

If you want to be able to perform Data Restore functions against more than one

server on the same system at the same time, you will need to repeat some other

steps. This requires that you have one set of work areas (i.e. a userid with minidisk

space under VM or a set of VSAM work files under VSE) per simultaneous use of

Data Restore.

Installations which use VSE Guest Sharing and also have servers running under

the same VSE system must install Data Restore on both the VM and the VSE

systems.

In general:

v Each SYSTEM with a DB2 Server for VSE & VM server must install the entire

Data Restore feature.

v Each ADDITIONAL server must have dbspaces, tables, and packages installed.

The following table (Table 5 on page 63) summarizes which installation steps you

must perform and which ones you may need to repeat, depending on your

environment and operational needs. Remember that “Step 3.6 Define Default

Values for Data Restore Parameters” on page 37 is optional.

Data Restore Guide

Table 5. Installation Steps Summary

Step Description:

Do Once

Repeat if

per

per Server?

Simultaneous Usage

System?

or Multiple Defaults

are needed?

VM:

“Step 1. Define the VM Resources” on page 34

Yes

¹ ³

“Step 3.1 Load Data Restore from Tape” on page 35

Yes

“Step 3.4 Create the Data Restore Modules” on page 36

Yes

“Step 2. Define the Database Manager Resources” on page 34

Yes

“Step 3.2 Create the Database Environment” on page 36

Yes

“Step 3.3 Load the Data Restore Packages” on page 36

Yes

“Step 3.6 Define Default Values for Data Restore Parameters” on

Yes

page 37

VSE:

“Step 1. Define the Library to be Installed” on page 40

Yes

² ³

“Step 2. Restore the Data Restore Distribution Library” on page 42

Yes

“Step 3.4

Link-edit the Data Restore PRDI” on page 46

Yes

“Step 3.1

Acquire the Required Dbspaces” on page 43

Yes

“Step 3.2

Create the Required Tables” on page 44

Yes

“Step 3.3

Reload the Data Restore Packages” on page 45

Yes

“Step 3.5

Define the VSAM Files for Data Restore” on page 46

Yes

Yes ²

“Step 3.6

Define Default Values for Data Restore Parameters” on

Yes

page 48

Notes on Table 5:

1. If multiple, simultaneous usage of Data Restore is required against multiple

servers, multiple userids must be defined and the files and modules must be

available to all of these userids. The minidisk containing the Data Restore

feature can be shared R/O among these userids, but each userid requires R/W

minidisk space for work files.

2. If multiple, simultaneous usage of Data Restore is required against multiple

servers, you must define multiple VSAM work files. You must either use a

separate VSAM user catalog for each set of identically named work files, or you

must specify different work file names in the same VSAM user catalog. In

either case, changes will need to be made to the JCL to point to the correct set

of work files. All jobs can share the same sublibrary containing the Data

Restore feature.

3. For VM: If you want different defaults to apply, you must set up a separate

minidisk for each set of defaults desired. As you can override all defaults using

control statements, it is normally not worthwhile to set up multiple minidisks

just to have different sets of defaults. This also requires the userid running Data

Restore to link and access the correct minidisk. Note that “Step 3.4 Create the

Data Restore Modules” on page 36 must be repeated, as the modules must be

recreated before the defaults become active.

For VSE: If you want different defaults to apply, you must set up a separate

sublibrary for each set of defaults desired. As you can override all defaults

using control statements, it is normally not worthwhile to set up multiple

Chapter 4. Installing Data Restore

sublibraries just to have different sets of defaults. This also requires JCL

changes to set the correct library search chain. Note that “Step 3.4 Link-edit the

Data Restore PRDI” on page 46 must be repeated, as the phases must be

recreated before the defaults become active.

For both: If you decide to use multiple defaults minidisks or sublibraries, you

must reinstall from the distribution tape or copy from the initial

minidisk/sublibrary, redefine the defaults, and then regenerate the CMS

modules or re-linkedit the VSE phases. Finally, you must set up the extra work

minidisk space or VSAM files.

A Complex Environment Example

Consider the following complex example, as shown in Figure 45 on page 64. In this

environment, it is assumed that the VSE-Virtual system can access the VM

databases via Guest Sharing.

VM-1

VSE-Virtual

DB-A

DB-B

DB-V1

DB-V2

VM-2

VSE-Native

DB-V3

DB-VTST

DB-C

DB-TST

Figure 45. A Complex Environment

The recommended sequence for installing Data Restore on all servers is as follows:

1. The Data Restore feature should be installed completely into DB-TST on VM-2

by doing VM installation “Step 1. Define the VM Resources” on page 34

through “Step 3.6 Define Default Values for Data Restore Parameters” on page

37.

2. Likewise, Data Restore should be installed completely into DB-VTST on

VSE-Native by doing VSE installation “Step 1. Define the Library to be

Installed” on page 40 through “Step 3.6 Define Default Values for Data Restore

Parameters” on page 48.

3. You can then test Data Restore under both VM and VSE to ensure it is installed

and working correctly.

4. Then you would repeat VM installation steps for DB-C on VM-2:

“Step 2. Define the Database Manager Resources” on page 34

“Step 3.2 Create the Database Environment” on page 36

“Step 3.3 Load the Data Restore Packages” on page 36

5. Then you would repeat VSE installation steps for DB-V3 on VSE-Native:

Data Restore Guide

“Step 3.1 Acquire the Required Dbspaces” on page 43

“Step 3.2 Create the Required Tables” on page 44

“Step 3.3 Reload the Data Restore Packages” on page 45

6. Next, a complete install of the feature would be done for, say, DB-A on VM-1

and again for DB-V1 on VSE-Virtual.

7. Then you would repeat VM installation steps for DB-B on VM-1:

“Step 2. Define the Database Manager Resources” on page 34

“Step 3.2 Create the Database Environment” on page 36

“Step 3.3 Load the Data Restore Packages” on page 36

8. Then you would repeat VSE Installation steps for DB-V2 on VSE-Virtual:

“Step 3.1 Acquire the Required Dbspaces” on page 43

“Step 3.2 Create the Required Tables” on page 44

“Step 3.3 Reload the Data Restore Packages” on page 45

This would complete the install of Data Restore on all systems and in all servers.

No extra steps are needed because of Guest Sharing access because servers also

exist on the VSE-Virtual system.

If you have a Guest VSE system which accesses VM servers via VSE Guest

Sharing, but does not also have DB2 Server for VSE databases, you need to define

a sublibrary and install Data Restore into it, as described in “Step 4. Define the

VSE Resources” on page 54 and “Step 5. Complete the VSE Installation Process” on

page 57.

If simultaneous usage of Data Restore is required against multiple databases on

the same system, you need to repeat some other steps. See the notes under Table 5

on page 63.

Security and Authorizing Access to the Server Minidisks (VM

Only)

The Data Restore feature must have READ and WRITE access to the server’s

database disks (i.e. the directory, log, and dbextent minidisks). If you have multiple

servers, this applies to these disks on all servers which are to be used with Data

Restore.

The following possible scenarios are considered:

1. An external security manager is used

In this case, you must authorize the Data Restore userid to have WRITE access

to all the databases disks, for each database userid.

2. No external security manager, all minidisks have identical read and identical

write passwords on all servers

In this case, you must set the READPW and WRITEPW parameters to the

correct passwords in the control file. These are described in “OPTIONS and

CONTROL Statements” on page 167.

3. No external security manager, all minidisks do not have identical read or write

passwords

You must put LINK statements into the VM Directory entry for the Data

Restore userid for all minidisks for the servers, using the same addresses as

used by the dbname SQLFDEF Q file of the server. If you have multiple servers

with identical addresses, this will not work, and you will need to set up

multiple Data Restore userids so they can each have one or more sets of LINK

commands in the VM Directory.

4. No external security manager, minidisks have no passwords

Chapter 4. Installing Data Restore

Chapter 5. Migration

This chapter describes the steps required to migrate from a previous release of the

Data Restore feature.

Migration under VM

Execute the following steps:

“Step 3.1 Load Data Restore from Tape” on page 35 in VM installation

“Step 3.3 Load the Data Restore Packages” on page 36 in VM installation

“Step 3.4 Create the Data Restore Modules” on page 36 in VM installation

“Step 3.5 Install in Additional Application Servers” on page 36 repeat step 3.3

only.

Migration under VSE

Execute the following steps:

“Step 2. Restore the Data Restore Distribution Library” on page 42 in VSE

installation

“Step 3.3 Reload the Data Restore Packages” on page 45 in VSE installation

“Step 3.4 Link-edit the Data Restore PRDI” on page 46 in VSE installation

Migration under VSE Guest Sharing

Execute the following steps:

“Step 3.1 Load Data Restore from Tape” on page 52 in VSE Guest Sharing

installation

“Step 3.3 Load the Data Restore Packages” on page 52 in VSE Guest Sharing

installation

“Step 3.4 Create the Data Restore Modules” on page 53 in VSE Guest Sharing

installation

To migrate any additional servers, execute “Step 3.3 Load the Data Restore

Packages” on page 52 after executing SQLINIT to the additional server.

“Step 4.5 Restore the Data Restore Distribution Library” on page 56 in VSE Guest

Sharing installation

“Step 5.1 Link-edit the Data Restore PRDI” on page 57 in VSE Guest Sharing

installation

Chapter 6. How to Apply Service

This chapter describes the steps required to apply service to Data Restore.

Applying Service for Data Restore for VM

Follow the steps below to apply service to Data Restore VM.

1. Logon to the Data Restore userid.

2. Link and access the Data Restore code disk in Write mode.

3. Copy the files from the supplied tape to the code disk, replacing any old files.

4. Run the exec XTS9GMOD to recreate the Data Restore module.

5. Perform any additional steps that may be described in the PTF Cover Letter.

Applying Service for Data Restore for VSE

Follow the steps below to apply service to Data Restore for VSE.

1. Load the tape into the Data Restore sublibrary.

2. Edit the JCL as required, then execute.

3. Execute job XTS9PRDI to link-edit the Data Restore phase.

4. Perform any additional steps that may be described in the PTF Cover Letter.

DB2 Server for VSE. Operations Guide / Handbooks (2004-2007) - page 41