Cluster Web. Step 3: Comprobación

Data d'actualització: 13/02/2012 09:32:18

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

ID: 28396
Embed code:
<video poster="" controls="" autoplay="" autobuffer="" controlslist="nodownload">
<source src="" type="video/mp4">

Category: Uncategorized RSS Uncategorized
Clasification Unesco: Not classified
Description: Para ello, vamos a utilizar la URL lynx . 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 o bien a| 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.
Resolution:  1000 x 1018  unknown
Score: Sense puntuacio (puntuar).
License CC: No asignada
Visits: 374

No comments
related videos

Applications Performance

How application design can affect performance

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

10.- Instalación zlinux. Instalación utilidades.

Una vez tenemos instalado el nucleo del sistema operativo, procedemos a instalar las utilidades estándar del sistema (ssh server, etc ...).

Items en Omeka

Com afegir items a una col·lecció amb Omeka