STEP 0: Initial Scenario

Data d'actualització: 02/09/2011 10:46:16

Share with Facebook   Share with Delicious Share with GoogleShare with Meneame Share with Myspace Share with Digg Mail

ID: 25893
Category: Computer science RSS Computer science
Clasification Unesco: Technological sciences
Description: The main purpose of this video-tutorial is to show you how to clone a DB2 subsystem to other subsystem running in the same Z/OS LPAR. Each step is explained with a video (screen cast). It is supossed that you have two DB2 subsystems, in this case DB8G (source) and DBF (target), both up & running. The procedure is automated in three main steps contained in library SYSADM.ODBCLONE. First step is related with the physical COPY from SOURCE datasets to TARGET DB2 datasets. While the remaining, are related with making target DB2 BSDS & CATALOG consistent with the location of the DATASETS copied from source subsystem
Labels: Online DB2 Z/OS Cloning clone subsystem LPAR
Resolution:  1920 x 1080  16:9
Score: Sense puntuacio (puntuar).
License CC: No asignada
Visits: 340

No comments
related videos

12.- Instalación zlinux. Conexión al zlinux

Después de hacer IPL, procederemos a logarnos en la debian s/390 tanto por consola como via ssh.

DB2 HA & DR. Part III

Cluster DB2 Activo/Activo con pureScale

STEP 3: Restart Target DB2

Finally, we RESTART TARGET DB2 and it's stopped databases.

STEP 4: Clone checking

Finally, we compare rows from the table that was been modified while source DB2 was clonned. Josep Vidal - System Programmer. For more questions you can reach me at: .

STEP 1: Copy Source DB2 DataSets to Target DB2

First of all, we execute REXX code to simulate DB workload. This workload consist in inserting on row per second in table sysadm.prv. Second, we stop TARGET (/-DBF STOP DB2) and delete all its datasets except the TARGET SDSN libraries and installation jobs . Finally, we proceed to COPY SOURCE datasets to TARGET DB2, while renaming HLQ (High Level Qualifier). The JCL that implements this is called CPYREN and is executed while source DB is up and running.