11.- Instalacion zlinux. Finalización de la instalacion

Data d'actualització: 02/12/2011 10:39:40

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

ID: 28048
Creator: VIDAL I CANET, JOSEP LLUIS RSS vijo
Category: Uncategorized RSS Uncategorized
Clasification Unesco: Not classified
Description: Una vez finalizada la instalación procedemos a parar el ramdisk de instalación para posteriormente hacer IPL del volumen sobre el que hemos instalado la debian para la arquitectura s390.
Labels:
Resolution:  1024 x 1024  unknown
Score: Sense puntuacio (puntuar).
License CC: No asignada
Visits: 257

Regulation
DownloadDownload
Add comment
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

11.- Instalacion zlinux. Finalización de la instalacion

Una vez finalizada la instalación procedemos a parar el ramdisk de instalación para posteriormente hacer IPL del volumen sobre el que hemos instalado la debian para la arquitectura s390.

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)

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