STEP 0: Initial Scenario
Data d'actualització: 02/09/2011 10:46:16
ID: 25893
Creador: VIDAL I CANET, JOSEP LLUIS 
URL: https://mmedia.uv.es/html5/u/vi/vijo/25893_cpyren_intro.swf.mp4
Código de inserción:
<video poster="https://mmedia.uv.es/g?user=vijo&path=/odbclone/&name=cpyren_intro.swf.flv&resource_id=25893" controls="" autoplay="" autobuffer="" controlslist="nodownload">
<source src="https://mmedia.uv.es/html5/u/vi/vijo/25893_cpyren_intro.swf.mp4" type="video/mp4">
</video>
Categoría: Informática
Clasificación Unesco: Ciencias tecnológicas
Descripción: 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
Etiquetas: Online DB2 Z/OS Cloning clone subsystem LPAR
Resolucion: 
1920 x 1080
16:9
Puntuación: Sense puntuacio (puntuar).
Licencia CC: No asignada
Visitas: 1877
Añadir comentarioVídeos Relacionados
Cluster Web. Step 3: Comprobación
Para ello, vamos a utilizar la URL lynx 10.1.1.2/cgi-bin/environ.sh . Este es un cgi que nos da información sobre el entorno de ejecución del servidor web en z/os. Pound redireccinará esta URL a http://p390.uv.es/cgi-bin/environ.sh o bien a| http://129.35.161.134/cgi-bin/environ.sh Luego comprobaremos como pound detecta la caida del HTTP Server Backend y lo marca como muerto. A partir de ahí solo enviará las peticiones WEB a la LPAR zeuszvm. Posteriorment, levantaremos el HTTP Server de Valencia (/START HTTPD1), veremos como a los 30 segundos pound lo detecta como resucitado y reanuda el balanceo de peticiones a p390.
STEP 2.2: Change Catalog STOGROUPs HLQ:
So, now we got both systems up and runing, but TARGET DB2 storage groups point to source HLQ. So we have to update TARGET DB2 catalog to point to new HLQ. To do this we use REXX code to select all storage groups and generate DDL to: 1.- Alter all depenent tablespaces and indexspaces to a temporal storage group -> SYSADM.TEMP.CHTSSGT 2.- Drop all storage groups -> SYSADM.TEMP.DROPSTO 3.- Create all storage groups with new HLQ (VCAT) -> SYSADM.TEMP.CREASTO 4.- Alter all depenent tablespaces and indexspaces to their original storages groups -> SYSADM.TEMP.CHTSSGO The JCLs that automates all this stuff are RENSTOGC (generates DDL to change STOGROUP VCAT) and ALTSTOG (executes it)
Creación de un CGI en z/os. Edición y Ejecución.
Edición del CGI desde el OMVS con el editor vi. Posterior ejecución tanto desde el shell como desde el navegador.
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.
STEP 2.1 Change log inventory HLQ:
This is automated with job RBLDLOGI which prints DBF.BSDS01 log inventory, reads its output (SYSADM.TEMP.PRNTBSDS) and generates a JOB (SYSADM.TEMP.JU004) to: 1.-) Change BSDS HLQ 2.-) Delete LOGCOPIES with source HLQ 3.-) Create new LOGCOPIES with target HLQ and START/END RBAs taken from log inventory output. At this point we can start target system.Target DB2 subsystem is started in MAINTENACE MODE: /-DBF START DB2 ACCESS(MAINT)