7.- Instalación zlinux. Instalación del BOS

Data d'actualització: 01/12/2011 10:37:38

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

ID: 28033
Creador: VIDAL I CANET, JOSEP LLUIS RSS vijo
URL: https://mmedia.uv.es/html5/u/vi/vijo/28033_bos.mp4
Código de inserción:
<video poster="https://mmedia.uv.es/g?user=vijo&path=/zlinux/&name=bos.mp4&resource_id=28033" controls="" autoplay="" autobuffer="" controlslist="nodownload">
<source src="https://mmedia.uv.es/html5/u/vi/vijo/28033_bos.mp4" type="video/mp4">
</video>
Categoría: Sin categorizar RSS Sin categorizar
Clasificación Unesco: Sin categorizar
Descripción: Durante este paso instalaremos los paquetes básicos necesarios para correr una debian s/390 mínima.
Etiquetas:
Resolucion:  1024 x 1024  unknown
Puntuación: Sense puntuacio (puntuar).
Licencia CC: No asignada
Visitas: 844

Regulación
DescargarDescargar
Añadir comentario
No hay comentarios
Vídeos Relacionados

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)

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.

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)

Cluster Web. Step 1: Instalar pound

Práctica del servidor HTTP. Implantaicón de un cluster WEB Objetivo: Crear un cluster WEB para aumentar el nivel de servicio (disponibilidad y rendimiento) balanceando las peticiones entre los dos servidores backend WEB z/os. Requisitos: * 1 LPAR emulada zlinux (instalada en la práctica anterior) * p390.uv.es: LPAR z/os corriendo el servidor IBM HTTP Server V5R3M0 (VLC) * zeuszvm.moppssc.ibm.com: LPAR z/os corriendo el servidor IBM HTTP Server V5R3M0