Charlotte User Group Meeting                       November 01, 2011IMS Database Recovery       Charles Jones    Senior So...
Recovery Topics• Recovery Overview    – Recovery Design    – Backout / Recovery Utilities• System Recovery    – System fai...
IMS Recovery Overview• In its simplest form:    – Restoring the database from a backup.• In its most complex form:    – Re...
IMS Recovery Design• Recover from media failures• Unstable environments    – site failure    – software failure• Whole sys...
IMS Recovery Design• Processing was in a single environment    – Online    – Batch5                               Charlott...
IMS Recovery Design• Online    – Offices closed at night    – No ATMs    – No Internet access6                            ...
IMS Recovery Design• Batch    – DLIBATCH - few BMPs    – Single threaded application processing7                          ...
IMS Recovery Design• Defined application processing environments    – Periods of Online    – Predetermined backup points  ...
IMS Recovery Design• Online Processing    – Single log stream      • Many OLDS/SLDS      • Single recovery stream    – Tra...
IMS Recovery DesignIMS1IMS2IMS3IMS4                  Charlotte User Group - Nov. 01   © Copyright IBM Corporation 2011
Backup / Recovery Utilities • Database Image Copy (Batch, Online or Concurrent)     – Creates copies of database data sets...
Recovery Processing • Terminology     – Full Recovery     – Time Stamp Recovery     – Point in Time Recovery12            ...
Recovery Processing • Terminology     – Full Recovery      • Recovery to the latest updates      • Complete recovery using...
Recovery Processing • Terminology     – Timestamp Recovery      •   To any point where the database is not allocated      ...
Recovery Processing • Terminology     – Point In Time Recovery      •   To any point      •   Recovery using partial logs ...
Change Accumulation • Accumulating batch logs               CA1                          DB              RECOVERED        ...
Recovering a Database                           DBRC                                       GENJCL.RECOV         RLDS2     ...
Recovery Processing ●   Performing Recovery Processing      –   Listing Recovery information      –   Generating Recovery ...
Listing Recovery Information //DBRC       EXEC DSPURX00 //STEPLIB    DD DSN=IMSVS.IMS910.SDFSRESL,DISP=SHR //DFSRESLB   DD...
Using GENJCL.RECOV to Recover a Database //DBRC        EXEC DSPURX00 //STEPLIB     DD DSN=IMSVS.IMS910.SDFSRESL,DISP=SHR /...
Charlotte User Group Meeting  November 01, 2011System Recovery       .              © Copyright IBM Corporation 2011      ...
System Recovery Overview • System Failures • System Restart Options     – Emergency Restart      •   OVERRIDE      •   COL...
System Failures • IMS system abends     – IMS Uxxx      • IMS SUBSYS record shows ABNORMAL TERM=ON      • Dynamic Backout ...
Results of Failed System • Results of a failed IMS system Include     – SUBSYS record exists in RECONSSYS SSID=IMSG      L...
Results of Failed System • Results of a failed IMS system Include      – OLDS is open     LIST.LOG OPEN SSID(IMSG)     PRI...
Results of Failed System • Results of a failed IMS system Include      – PRILOG record is open PRILOG RECORD SIZE=    3984...
System Restart Options • Emergency Restart (/ERE )     –   OVERRIDE – SUBSYS record already exists     –   COLDCOMM – “cle...
System Restart Options • OVERRIDE.     – Required if SUBSYS record is present and ABNORMAL TERM=OFF     – Will overwrite r...
System Restart Options • Use COLDCOMM. when:     – Normal ERE failed and message not critical to the business     – Can‟t ...
System Restart Options • Use COLDBASE. when:     – Normal ERE failed and database updates to be handled by       Batch Bac...
System Restart Options • Use COLDSYS. when:     – Normal ERE failed and database updates to be handled by Batch       Back...
System Restart Options • Restarting Failed IMS System     – BEST OPTION:      • ABNORMAL TERM=ON (enter /ERE)      • ABNOR...
Dynamic Backout • Invoked by ERE • Invoked by START DB command • Available in DLIBATCH if BKO=Y and DASD log used • Succes...
Charlotte User Group Meeting November 01, 2011Batch Backout      .              © Copyright IBM Corporation 2011          ...
Find the OPEN OLDS • SSID parameter is needed only if there are multiple IMS   systems sharing the RECON as in a data shar...
Find the OPEN OLDSLIST.LOG SSID(IMSG)PRIOLDSSID=IMSG     # DD ENTRIES=6EARLIEST CHECKPOINT = 07.200 18:18:15.4DDNAME=DFSOL...
Close the OLDS • Run DBRC command     – GENJCL.CLOSE SSID(IMSG) LIST • Run DFSULTR0 in CLS mode     –   DFSOLP – OLDS to b...
Find the Active PSBs • Run DFSULTR0      – SYSIN         • PSB      – IEFRDER         • IMSVS.IMSG.OLP01 – OLDS just close...
Listing the Failed Subsystem • LIST.SUBSYS ALL or LIST.SUBSYS SSID(xxxx)     LIST.SUBSYS ALL     07.200 19:41:23.0        ...
Find the Active PSBs     //DFSULTR0   EXEC PGM=DFSULTR0,PARM=IMSID=IMSG,DBRC=YES     //STEPLIB    DD DSN=IMSVS.IMSG.SDFSRE...
Find the Active PSBs     ***** RECOVERY REQUIREMENTS *****     PSB NAME   RECOVERY TOKEN             DATABASE        DSID ...
Running Batch Backout • BBO has to be run for each PSB listed in the active PSB   report from DFSULTR0 • BBO can be run af...
Run Batch Backout • LIST.BKOUT ALL will list the BKOUT records      BACKOUT        SSID=IMSG     #UORS=3         RECOVERY ...
BBO Log inputsBACKOUT SSID=IMSG    #UORS=3  RECOVERYTOKEN=C9D4E2C7404040400000001B000000D7  TIME=07.204 21:34:56.0    PSB=...
Run Batch Backout • The logs are supplied in the following order:     – The oldest log required in time sequence (earliest...
Run Batch Backout     //BBO EXEC PGM=DFSRRC00,REGION=8M,     //     PARM=(DLI,DFSBBO00,B1ACSTA,,0000,,0,,N,0,T,,N,Y,,,Y)  ...
Run Batch Backout • If there was No BKOUT record when BBO run the following   message will be produced. • It is not saying...
Charlotte User Group Meeting           November 01, 2011  Questions?charles@us.ibm.com                 .             © Cop...
Upcoming SlideShare
Loading in …5
×

IMS Database Recovery for Charlotte User Group

675 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
675
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IMS Database Recovery for Charlotte User Group

  1. 1. Charlotte User Group Meeting November 01, 2011IMS Database Recovery Charles Jones Senior Software Engineer IMS Database Support Silicon Valley Laboratory charles@us.ibm.com . © Copyright IBM Corporation 2011 5.1
  2. 2. Recovery Topics• Recovery Overview – Recovery Design – Backout / Recovery Utilities• System Recovery – System failures – System Restart options – Recovery processing terminology• Batch Backout – Finding active work / PSBs – Running Batch Backout2 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  3. 3. IMS Recovery Overview• In its simplest form: – Restoring the database from a backup.• In its most complex form: – Restoring the database from a backup and applying all the updates since that time in the same sequence, thus preserving the integrity of the database.3 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  4. 4. IMS Recovery Design• Recover from media failures• Unstable environments – site failure – software failure• Whole system outages4 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  5. 5. IMS Recovery Design• Processing was in a single environment – Online – Batch5 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  6. 6. IMS Recovery Design• Online – Offices closed at night – No ATMs – No Internet access6 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  7. 7. IMS Recovery Design• Batch – DLIBATCH - few BMPs – Single threaded application processing7 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  8. 8. IMS Recovery Design• Defined application processing environments – Periods of Online – Predetermined backup points – Defined batch processing – Second backup point (optional)8 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  9. 9. IMS Recovery Design• Online Processing – Single log stream • Many OLDS/SLDS • Single recovery stream – Transaction failures handled by Dynamic Backout – Recovery point is prior to allocation time9 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  10. 10. IMS Recovery DesignIMS1IMS2IMS3IMS4 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  11. 11. Backup / Recovery Utilities • Database Image Copy (Batch, Online or Concurrent) – Creates copies of database data sets • Database Change Accumulation – Creates data set containing only log records needed for Recovery – Sequenced by RBA within data set and database – Reduces time required for Recovery • Database Recovery – Recovers damaged database data set – Updates copy of database data set with changes logged after the copy was made • Batch Backout – Removes database changes made during execution of a batch program or an online PSB11 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  12. 12. Recovery Processing • Terminology – Full Recovery – Time Stamp Recovery – Point in Time Recovery12 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  13. 13. Recovery Processing • Terminology – Full Recovery • Recovery to the latest updates • Complete recovery using all the logs with updates on them • Normally run for media failures13 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  14. 14. Recovery Processing • Terminology – Timestamp Recovery • To any point where the database is not allocated • Recovery using the logs with updates on them • Normally run for application failures • No recovery point in the middle of an online session unless the database has been /DBR‟d14 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  15. 15. Recovery Processing • Terminology – Point In Time Recovery • To any point • Recovery using partial logs • All updates (UOW) commit at exact timestamp are included • Normally run for application failures15 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  16. 16. Change Accumulation • Accumulating batch logs CA1 DB RECOVERED CA2 RECOVERY DATA SET16 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  17. 17. Recovering a Database DBRC GENJCL.RECOV RLDS2 RLDS1 IMAGE IMAGE RECONS COPY DB IMAGE COPY RECOVERY COPY RECOVERED CA1 DATABASE DATA SET17 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  18. 18. Recovery Processing ● Performing Recovery Processing – Listing Recovery information – Generating Recovery jobs18 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  19. 19. Listing Recovery Information //DBRC EXEC DSPURX00 //STEPLIB DD DSN=IMSVS.IMS910.SDFSRESL,DISP=SHR //DFSRESLB DD DSN=IMSVS.IMS910.SDFSRESL,DISP=SHR //IMS DD DSN=&CLASSID..CMXXX.DBDLIB,DISP=SHR //JCLPDS DD DSN=&CLASSID..CMXXX.JCLLIB,DISP=SHR //JCLOUT DD SYSOUT=(*,INTRDR) //SYSPRINT DD SYSOUT=* //SYSIN DD * LIST.DB DBD(T01DBD1) DBDS /*LIST.DB DBD( ) – will display the DB record onlyLIST.DB DBD( ) DBDS – will display the DB, DBDS and all associated records (ALLOC,IC,RECOV,REORG…19 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  20. 20. Using GENJCL.RECOV to Recover a Database //DBRC EXEC DSPURX00 //STEPLIB DD DSN=IMSVS.IMS910.SDFSRESL,DISP=SHR //DFSRESLB DD DSN=IMSVS.IMS910.SDFSRESL,DISP=SHR //IMS DD DSN=&CLASSID..CMXXX.DBDLIB,DISP=SHR //JCLPDS DD DSN=&CLASSID..CMXXX.JCLLIB,DISP=SHR //JCLOUT DD SYSOUT=(*,INTRDR) //SYSPRINT DD SYSOUT=* //SYSIN DD * GENJCL.RECOV DBD(T01DBD1) ONEJOB JOB(T01RCJOB) LIST RCVTIME(timestamp) List the created JCL in SYSPRINT Member which contains the JOB card Create only one IC JOB DBD name to be recovered (could be group name) GROUP(grpname) can be used instead of DBD20 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  21. 21. Charlotte User Group Meeting November 01, 2011System Recovery . © Copyright IBM Corporation 2011 5.1
  22. 22. System Recovery Overview • System Failures • System Restart Options – Emergency Restart • OVERRIDE • COLDCOMM • COLDBASE • COLDSYS • Dynamic Backout22 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  23. 23. System Failures • IMS system abends – IMS Uxxx • IMS SUBSYS record shows ABNORMAL TERM=ON • Dynamic Backout invoked • MVS failures: – IMS SUBSYS record shows ABNORMAL TERM=OFF – No Dynamic Backout invoked23 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  24. 24. Results of Failed System • Results of a failed IMS system Include – SUBSYS record exists in RECONSSYS SSID=IMSG LOG START=07.200 18:18:12.0 SSTYPE=ONLINE ABNORMAL TERM=ON RECOVERY STARTED=NO BACKUP=NO TRACKED=NO TRACKER TERM=OFF SHARING COVERED DBS=NO IRLMID=**NULL** IRLM STATUS=NORMAL GSGNAME=**NULL** COEXISTENCE LEVEL=10.124 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  25. 25. Results of Failed System • Results of a failed IMS system Include – OLDS is open LIST.LOG OPEN SSID(IMSG) PRIOLD SSID=IMSG # DD ENTRIES=1 EARLIEST CHECKPOINT = 07.200 18:18:15.4 DDNAME=DFSOLP01 DSN=IMSVS.IMSG.OLP01 START = 07.200 19:40:17.3 FIRST DS LSN= 00000000003EFE52 STOP = 00.000 00:00:00.0 LAST DS LSN= 0000000000000000 LOCK SEQUENCE# = 000000000000 STATUS=ACTIVE FEOV=NO AVAIL PRILOG TIME=07.200 18:18:12.0 VERSION=9.125 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  26. 26. Results of Failed System • Results of a failed IMS system Include – PRILOG record is open PRILOG RECORD SIZE= 3984 START = 07.200 18:18:12.0 * SSID=IMSG VERSION=9.1 STOP = 00.000 00:00:00.0 #DSN=24 GSGNAME=**NULL** FIRST RECORD ID= 0000000000000001 PRILOG TOKEN= 0 EARLIEST CHECKPOINT = 07.200 18:18:12.0 DSN=IMSVS.IMSG.SLDS.G0030V00 UNIT=3390 START = 07.200 18:18:12.0 FIRST DS LSN= 0000000000000001 STOP = 07.200 18:19:31.6 LAST DS LSN= 00000000000A78C8 FILE SEQ=0001 #VOLUMES=000126 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  27. 27. System Restart Options • Emergency Restart (/ERE ) – OVERRIDE – SUBSYS record already exists – COLDCOMM – “clean start” for DC, “warm start” for DB – COLDBASE – “clean start” for DB, “warm start” for DC – COLDSYS - “clean start” for whole system27 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  28. 28. System Restart Options • OVERRIDE. – Required if SUBSYS record is present and ABNORMAL TERM=OFF – Will overwrite running IMS system • IMS restarts using the same SUBSYS record – Continues DBRC AUTHORIZATIONS already held – PRILOG record is maintained – Performs dynamic back-outs for all active PSBs – OLDS can be open or closed • OLDS will be closed • Archive job submitted to archive closed OLDS – On completion of Dynamic backout • OLDS Archived • PRILOG closed and new one opened • Releases DB authorizationSSYS SSID=IMSG LOG START=07.200 18:18:12.0 SSTYPE=ONLINE ABNORMAL TERM=OFF RECOVERY STARTED=NO BACKUP=NO TRACKED=NO TRACKER TERM=OFF SHARING COVERED DBS=NO IRLMID=**NULL** IRLM STATUS=NORMAL GSGNAME=**NULL** COEXISTENCE LEVEL=10.128 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  29. 29. System Restart Options • Use COLDCOMM. when: – Normal ERE failed and message not critical to the business – Can‟t get IMS to rebuild the IMS Queues – You have a tool to RE-QUEUE the messages • IMS restarts using the same SUBSYS record – Continues DBRC AUTHORIZATIONS already held – PRILOG record is maintained – Performs dynamic back-outs for all active PSBs – OLDS can be open or closed – On completion of Dynamic backout • OLDS Archived • PRILOG closed and new one opened • Releases DB authorization29 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  30. 30. System Restart Options • Use COLDBASE. when: – Normal ERE failed and database updates to be handled by Batch Backout – IMS will maintain the IMS Queues • IMS restarts using the same SUBSYS record – Continues DBRC AUTHORIZATIONS already held – Dynamic database back-outs bypassed – PRILOG record is maintained – BKOUT record(s) are written for BMP PSBs – Databases STOPPED by IMS for BMP PSBs – OLDS can be open or closed – On completion of COLDBASE • OLDS Archived • PRILOG closed and new one opened • Releases DB authorization30 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  31. 31. System Restart Options • Use COLDSYS. when: – Normal ERE failed and database updates to be handled by Batch Backout and the message queues are not required • IMS restarts using the same SUBSYS record – DBRC AUTHORIZATIONS already held – released – PRILOG record closed and new one opened – IRLM locks released – OLDS MUST be closed manually before /ERE DFS034I DATA BASE AUTHORIZATION AND LOCKS RELEASED. IMSG DFS034I DATA BASE AUTHORIZATION AND LOCKS RELEASED. IMSG DFS034I DATA BASE AUTHORIZATION AND LOCKS RELEASED. IMSG DFS994I *COLDSYS* EMERGENCY START COMPLETED. IMSG31 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  32. 32. System Restart Options • Restarting Failed IMS System – BEST OPTION: • ABNORMAL TERM=ON (enter /ERE) • ABNORMAL TERM=OFF (enter /ERE OVERRIDE) • IMS Restart (/ERE) Failed – Choices : • Do we NEED to maintain the message queues? – No: - /ERE COLDCOMM. – Yes: - /ERE COLDBASE. • If Neither COLDCOMM or COLDBASE works – Close the OLDS – /ERE COLDSYS32 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  33. 33. Dynamic Backout • Invoked by ERE • Invoked by START DB command • Available in DLIBATCH if BKO=Y and DASD log used • Successful Backout: – Reads logs to identify active PSBs with uncommitted UOW – Updates DB with „reversing‟ update – Logs new updates to OLDS or IEFRDER for future forward recovery requirements • Unsuccessful Backout : – Stops DB (online) – Creates BKOUT record in RECON – Updates DBDS record with BACKOUT NEEDED=Y33 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  34. 34. Charlotte User Group Meeting November 01, 2011Batch Backout . © Copyright IBM Corporation 2011 5.1
  35. 35. Find the OPEN OLDS • SSID parameter is needed only if there are multiple IMS systems sharing the RECON as in a data sharing environment. • Include LIST.LOG SSID(xxxx) to get the complete PRIOLD history so that when you close the OLDS you can see the previous OLDS. (next slide) LIST.LOG OPEN SSID(IMSG) PRIOLD SSID=IMSG # DD ENTRIES=1 EARLIEST CHECKPOINT = 07.200 18:18:15.4 DDNAME=DFSOLP01 DSN=IMSVS.IMSG.OLP01 START = 07.200 19:40:17.3 FIRST DS LSN= 00000000003EFE52 STOP = 00.000 00:00:00.0 LAST DS LSN= 0000000000000000 LOCK SEQUENCE# = 000000000000 STATUS=ACTIVE FEOV=NO AVAIL PRILOG TIME=07.200 18:18:12.0 VERSION=9.135 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  36. 36. Find the OPEN OLDSLIST.LOG SSID(IMSG)PRIOLDSSID=IMSG # DD ENTRIES=6EARLIEST CHECKPOINT = 07.200 18:18:15.4DDNAME=DFSOLP02 DSN=IMSVS.IMSG.OLP02 DDNAME=DFSOLP05 DSN=IMSVS.IMSG.OLP05START = 07.200 18:33:56.9 FIRST DS LSN= 00000000000AB774 START = 07.200 19:39:20.8 FIRST DS LSN= 00000000002A17D5STOP = 07.200 19:38:25.6 LAST DS LSN= 0000000000152CD2 STOP = 07.200 19:39:48.8 LAST DS LSN= 0000000000348B18LOCK SEQUENCE# = 000000000000 LOCK SEQUENCE# = 000000000000STATUS=ARC COMPLT FEOV=NO AVAIL STATUS=ARC COMPLT FEOV=NO AVAILPRILOG TIME=07.200 18:18:12.0 ARCHIVE JOB NAME=IMSGARCH PRILOG TIME=07.200 18:18:12.0 ARCHIVE JOB NAME=IMSGARCHVERSION=9.1 VERSION=9.1DDNAME=DFSOLP03 DSN=IMSVS.IMSG.OLP03 DDNAME=DFSOLP99 DSN=IMSVS.IMSG.OLP99START = 07.200 19:38:25.6 FIRST DS LSN= 0000000000152CD3 START = 07.200 19:39:48.8 FIRST DS LSN= 0000000000348B19STOP = 07.200 19:38:53.7 LAST DS LSN= 00000000001FA43C STOP = 07.200 19:40:17.3 LAST DS LSN= 00000000003EFE51LOCK SEQUENCE# = 000000000000 LOCK SEQUENCE# = 000000000000STATUS=ARC COMPLT FEOV=NO AVAIL STATUS=ARC COMPLT FEOV=NO AVAILPRILOG TIME=07.200 18:18:12.0 ARCHIVE JOB NAME=IMSGARCH PRILOG TIME=07.200 18:18:12.0 ARCHIVE JOB NAME=IMSGARCHVERSION=9.1 VERSION=9.1DDNAME=DFSOLP04 DSN=IMSVS.IMSG.OLP04 DDNAME=DFSOLP01 DSN=IMSVS.IMSG.OLP01START = 07.200 19:38:53.7 FIRST DS LSN= 00000000001FA43D START = 07.200 19:40:17.3 FIRST DS LSN= 00000000003EFE52STOP = 07.200 19:39:20.8 LAST DS LSN= 00000000002A17D4 STOP = 00.000 00:00:00.0 LAST DS LSN= 0000000000000000LOCK SEQUENCE# = 000000000000 LOCK SEQUENCE# = 000000000000STATUS=ARC COMPLT FEOV=NO AVAIL STATUS=ACTIVE FEOV=NO AVAILPRILOG TIME=07.200 18:18:12.0 ARCHIVE JOB NAME=IMSGARCH PRILOG TIME=07.200 18:18:12.0VERSION=9.1 VERSION=9.1 36 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  37. 37. Close the OLDS • Run DBRC command – GENJCL.CLOSE SSID(IMSG) LIST • Run DFSULTR0 in CLS mode – DFSOLP – OLDS to be closed – DFSPOLP – Previous OLDS – DFSWADS0 – WADS – SYSIN DD * • CLS • /*37 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  38. 38. Find the Active PSBs • Run DFSULTR0 – SYSIN • PSB – IEFRDER • IMSVS.IMSG.OLP01 – OLDS just closed ***** RECOVERY REQUIREMENTS ***** PSB NAME RECOVERY TOKEN DATABASE DSID ACTION REQUIRED B1ACSTA IMSG 0000001700000000 BACKOUT IS REQUIRED NO DATABASE NAMES FOUND DBNAME LIST MAY BE INCOMPLETE IMSG 0000001800000000 BACKOUT IS REQUIRED NO DATABASE NAMES FOUND DBNAME LIST MAY BE INCOMPLETE B1ACSTP IMSG 0000001B000000D7 BACKOUT IS REQUIRED B1CST04 - B1UPPRDA IMSG 0000001600000000 BACKOUT IS REQUIRED NO DATABASE NAMES FOUND DBNAME LIST MAY BE INCOMPLETE END OF REPORT38 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  39. 39. Listing the Failed Subsystem • LIST.SUBSYS ALL or LIST.SUBSYS SSID(xxxx) LIST.SUBSYS ALL 07.200 19:41:23.0 LISTING OF RECON PAGE 0008 ------------------------------------------------------------------------------- SSYS SSID=IMSG LOG START=07.200 18:18:12.0 SSTYPE=ONLINE ABNORMAL TERM=ON RECOVERY STARTED=NO BACKUP=NO TRACKED=NO TRACKER TERM=OFF SHARING COVERED DBS=NO IRLMID=**NULL** IRLM STATUS=NORMAL GSGNAME=**NULL** COEXISTENCE LEVEL=10.1 AUTHORIZED DATA BASES/AREAS=19 VERSION=9.1 XRF CAPABLE=NO ENCODED -DBD- -AREA- -LEVEL- -ACCESS INTENT- -STATE- B1PRD01 **NULL** 3 UPDATE 6 B1PRD02 **NULL** 3 UPDATE 6 B1PRD03 **NULL** 3 UPDATE 6 B1PRD05 **NULL** 3 UPDATE 6 B1PRD06 **NULL** 3 UPDATE 6 B1CST01 **NULL** 3 UPDATE 6 B1CST02 **NULL** 3 UPDATE 6 B1CST03 **NULL** 3 UPDATE 6 B1CST04 **NULL** 3 UPDATE 6 B1CST05 **NULL** 3 UPDATE 6 B1CST06 **NULL** 3 UPDATE 6 B1CST07 **NULL** 3 UPDATE 6 B1CST08 **NULL** 3 UPDATE 6 B1CST09 **NULL** 3 UPDATE 6 B1CST10 **NULL** 3 UPDATE 6 B1PRD07 **NULL** 3 UPDATE 6 B1PRD08 **NULL** 3 UPDATE 6 B1PRD09 **NULL** 3 UPDATE 6 B1PRD10 **NULL** 3 UPDATE 639 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  40. 40. Find the Active PSBs //DFSULTR0 EXEC PGM=DFSULTR0,PARM=IMSID=IMSG,DBRC=YES //STEPLIB DD DSN=IMSVS.IMSG.SDFSRESL,DISP=SHR //DFSRESLB DD DSN=IMSVS.IMSG.SDFSRESL,DISP=SHR //SYSPRINT DD SYSOUT=* //IEFRDER DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0011V00 // DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0012V00 // DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0013V00 // DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0014V00 // DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0015V00 // DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0016V00 // DD DISP=SHR,DSN=IMSVS.IMSG.OLP01 //SYSIN DD * PSB /*40 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  41. 41. Find the Active PSBs ***** RECOVERY REQUIREMENTS ***** PSB NAME RECOVERY TOKEN DATABASE DSID ACTION REQUIRED ________ ________________________ ________ _____ _____________________ B1ACSTA IMSG 0000001700000000 BACKOUT IS REQUIRED B1CST08 - B1CST09 - B1PRD07 - B1PRD08 - IMSG 0000001800000000 BACKOUT IS REQUIRED B1CST06 - B1CST07 - B1PRD07 - B1ACSTP ________ IMSG 0000001B000000D7 BACKOUT IS REQUIRED B1CST04 - B1UPCSTA ________ IMSG 0000001A00000000 BACKOUT IS REQUIRED B1CST01 - B1UPPRDA ________ IMSG 0000001600000000 BACKOUT IS REQUIRED B1PRD02 - END OF REPORT41 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  42. 42. Running Batch Backout • BBO has to be run for each PSB listed in the active PSB report from DFSULTR0 • BBO can be run after the IMS system has been brought up with a COLDBASE – BKOUT record should be written by IMS restart • If NO BKOUT records – BBO will still run and back out updates for PSB named42 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  43. 43. Run Batch Backout • LIST.BKOUT ALL will list the BKOUT records BACKOUT SSID=IMSG #UORS=3 RECOVERY TOKEN=C9D4E2C7404040400000001B000000D7 TIME=07.204 21:34:56.0 PSB=B1ACSTP CANDIDATE INFLT BMP COLDEND ASSOCIATED DATA BASES=1 BACKED DYN BKOUT -DBD- -OUT - -FAILURE- B1CST04 NO NO RECOVERY TOKEN=C9D4E2C7404040400000001A00000000 TIME=07.204 21:30:02.5 PSB=B1UPCSTA CANDIDATE INFLT COLDEND ASSOCIATED DATA BASES=1 BACKED DYN BKOUT -DBD- -OUT - -FAILURE- B1CST01 NO NO RECOVERY TOKEN=C9D4E2C7404040400000001600000000 TIME=07.204 21:30:02.5 PSB=B1UPPRDA CANDIDATE INFLT COLDEND ASSOCIATED DATA BASES=1 BACKED DYN BKOUT -DBD- -OUT - -FAILURE- B1PRD02 NO NO43 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  44. 44. BBO Log inputsBACKOUT SSID=IMSG #UORS=3 RECOVERYTOKEN=C9D4E2C7404040400000001B000000D7 TIME=07.204 21:34:56.0 PSB=B1ACSTP CANDIDATE INFLT BMP COLDEND ASSOCIATED DATA BASES=1 DSN=IMSVS.IMSG.SLDS.G0012V00 UNIT=3390 START = 07.204 21:29:58.1 FIRST DS LSN= 00000000000AAFAE BACKED DYN BKOUT STOP = 07.204 21:33:01.4 LAST DS LSN= 0000000000152A77 -DBD- -OUT - -FAILURE- B1CST04 NO NO RECOVERY TOKEN=C9D4E2C7404040400000001A00000000 TIME=07.204 21:30:02.5 PSB=B1UPCSTA CANDIDATE INFLT COLDEND ASSOCIATED DATA BASES=1 DSN=IMSVS.IMSG.SLDS.G0015V00 UNIT=3390 START = 07.204 21:33:58.2 FIRST DS LSN= 00000000002A15D5 BACKED DYN BKOUT STOP = 07.204 21:34:26.6 LAST DS LSN= 00000000003489DE -DBD- -OUT - -FAILURE- B1CST01 NO NO RECOVERY TOKEN=C9D4E2C7404040400000001600000000 TIME=07.204 21:30:02.5 PSB=B1UPPRDA CANDIDATE INFLT COLDEND ASSOCIATED DATA BASES=1 BACKED DYN BKOUT -DBD- -OUT - -FAILURE- B1PRD02 NO NO44 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  45. 45. Run Batch Backout • The logs are supplied in the following order: – The oldest log required in time sequence (earliest time) on the IEFRDER DD – Every log from the first to the recently closed last log on IMSLOGxx DD cards. – The IMSLOGxx start from 01 and go as high as needed. – The logs can be the OLDS or their archived SLDS – The OLDS must be closed to be usable by BBO • The IEFRDER Log file created by BBO is required as it might be needed by forward recovery should one be needed.45 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  46. 46. Run Batch Backout //BBO EXEC PGM=DFSRRC00,REGION=8M, // PARM=(DLI,DFSBBO00,B1ACSTA,,0000,,0,,N,0,T,,N,Y,,,Y) //STEPLIB DD DSN=IMSVS.IMSG.SDFSRESL,DISP=SHR // DD DSN=IMSVS.IMS910.SDFSRESL,DISP=SHR //DFSRESLB DD DSN=IMSVS.IMS910.SDFSRESL,DISP=SHR //IMSLOGR DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0011V00 //IMSLOG01 DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0012V00 //IMSLOG02 DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0013V00 //IMSLOG03 DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0014V00 //IMSLOG04 DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0015V00 //IMSLOG05 DD DISP=SHR,DSN=IMSVS.IMSG.SLDS.G0016V00 //IMSLOG06 DD DISP=SHR,DSN=IMSVS.IMSG.OLP01 //IEFRDER DD DSN=IMSVS.IMSG.SLDS(+1), // SPACE=(TRK,(100,10),RLSE),UNIT=SYSDA,DISP=(NEW,CATLG), // DCB=(DPR.IMSB.OLP00,BUFNO=20) //IMS DD DISP=SHR,DSN=hlq.CMXXX.DBDLIB // DD DISP=SHR,DSN=hlq.CMXXX.PSBLIB //SYSIN DD * COLDSTART46 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  47. 47. Run Batch Backout • If there was No BKOUT record when BBO run the following message will be produced. • It is not saying that the BBO is not valid or did not work, just that there was no BKOUT to start with. 03.09.43 J0030824 +DFS035I BATCH INITIALIZATION COMPLETE GIMS 03.10.55 J0030824 +DFS3293W PERFORMED BACKOUT NOT NEEDED 03.10.56 J0030824 +DFS092I IMS LOG TERMINATED GIMS47 Charlotte User Group - Nov. 01 © Copyright IBM Corporation 2011
  48. 48. Charlotte User Group Meeting November 01, 2011 Questions?charles@us.ibm.com . © Copyright IBM Corporation 2011 5.1

×