STEP 2.2: Change Catalog STOGROUPs HLQ:

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

Compartir en Facebook   Compartir en Delicious Compartir en GoogleCompartir en Meneame Compartir en Myspace Compartir en Digg Enviar por correo

ID: 25889
Creador: VIDAL I CANET, JOSEP LLUIS RSS vijo
URL: https://mmedia.uv.es/html5/u/vi/vijo/25889_chmetadata_catalog.swf.mp4
Código de inserción:
<video poster="https://mmedia.uv.es/g?user=vijo&path=/odbclone/&name=chmetadata_catalog.swf.flv&resource_id=25889" controls="" autoplay="" autobuffer="" controlslist="nodownload">
<source src="https://mmedia.uv.es/html5/u/vi/vijo/25889_chmetadata_catalog.swf.mp4" type="video/mp4">
</video>
Categoría: Tecnología RSS Tecnología
Clasificación Unesco: Ciencias tecnológicas
Descripción: 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)
Etiquetas: Online DB2 Z/OS Cloning clone subsystem LPAR
Resolucion:  1024 x 1024  unknown
Puntuación: Sense puntuacio (puntuar).
Licencia CC: No asignada
Visitas: 696

Regulación

Añadir comentario
No hay comentarios
Vídeos Relacionados

Persistent Sessions

Demo sobre persistència de sessions. En el cluster de la gestió acadèmica s'aturen tots els nodes. Posteriorment, s'alça un i es comprova que les dades de la sessió es recuperen sense problemes.

STEP 0: Initial Scenario

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

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.

Persistència Sessions Automatrícula

Persistència Sessions Automatrícula davant del reinici escalonat del cluster J2EE on està desplegada

4.- Instalación zlinux. Elección del mirror de la debian

En este paso deberemos indicarle la IP del mirror de la debian para la arquitectura s390. Para la instalación utilizaremos 141.76.2.4 . Error en el video-tutorial, donde dice "la debian es una arquitectura que está para muchas distribuciones" tendría que decir "la debian és una distribución que está disponible para muchas arquitecturas".