0000000001305479
AUTHOR
Josep Lluis Vidal I Canet
showing 7 related works from this author
Persistència Sessions Automatrícula
2013
Persistència Sessions Automatrícula davant del reinici escalonat del cluster J2EE on està desplegada
STEP 2.1 Change log inventory HLQ:
2011
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 HLQ2.-) Delete LOGCOPIES with source HLQ3.-) 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 4: Clone checking
2011
Finally, we compare rows from the table that was been modified while source DB2 was clonned.Josep Vidal - System Programmer. For more questions you can reach me at: josepvidalcanet@gmail.com .
STEP 1: Copy Source DB2 DataSets to Target DB2
2011
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.
Persistent Sessions
2013
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
2011
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 3: Restart Target DB2
2011
Finally, we RESTART TARGET DB2 and it's stopped databases.