35
IBM Software Group Rick Long – IMS LVL2 Database Service Team [email protected] Recovering from IMS System Failures ® © IBM Corporation 2005

Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

  • Upload
    ibm-ims

  • View
    394

  • Download
    11

Embed Size (px)

Citation preview

Page 1: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

IBM Software Group

Rick Long – IMS LVL2 Database Service Team

[email protected]

Recovering from IMS System Failures

®

© IBM Corporation 2005

Page 2: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

2

© Copyright IBM Corporation 2009. All rights reserved.U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCTS AND/OR SOFTWARE.

IBM, the IBM logo, ibm.com, IMS, IBM High Performance Pointer Checker for z/OS and CICS are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml

Other company, product, or service names may be trademarks or service marks of others.

Page 3: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Agenda for Today Describing the results of a failure of an IMS online system

Brief overview of emergency restart and what the restart options mean

Description of the actions required if ERE fails or is not possible◦ How to identify what was active at the time of failure◦ How to identify and close the open OLDS

Page 4: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Results of a failed IMS system Include◦ OLDS is open

Results of a failed IMS system

PRIOLD SSID=IMSG # DD ENTRIES=1 EARLIEST CHECKPOINT = 12.197 16:41:00.002614

DDNAME=DFSOLP02 DSN=IMSVS.IMSG.OLP02 START = 12.197 17:33:13.204815 FIRST DS LSN= 0000000000F9BEDC STOP = 00.000 00:00:00.000000 LAST DS LSN= 0000000000000000 LOCK SEQUENCE# = C9DF7D930C6F STATUS=ACTIVE FEOV=NO AVAIL PRILOG TIME=12.193 16:48:12.787416 VERSION=11.1

Page 5: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Results of a failed IMS system Include◦ OLDS is open◦ PRILOG record is open

Results of a failed IMS system

PRILOG RECORD SIZE= 2864 START = 12.193 16:48:12.787416 * SSID=IMSG VERSION=11.1 STOP = 00.000 00:00:00.000000 #DSN=17 GSGNAME=**NULL** FIRST RECORD ID= 00000000007084E6 PRILOG TOKEN= 0 EARLIEST CHECKPOINT = 12.197 16:41:00.002614

Page 6: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Results of a failed IMS system Include◦ OLDS is open◦ PRILOG record is open◦ SUBSYS record exists in RECON

Results of a failed IMS system

SSYS SSID=IMSG LOG START=12.193 16:48:12.787416 SSTYPE=ONLINE ABNORMAL TERM=ON RECOVERY STARTED=NO BACKUP=NO TRACKED=NO TRACKER TERM=OFF SHARING COVERED DBS=NO IRLMID=IRAI IRLM STATUS=NORMAL GSGNAME=**NULL** COEXISTENCE LEVEL=11.1

Page 7: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Results of a failed IMS system Include◦ OLDS is open◦ PRILOG record is open◦ SUBSYS record exists in RECON◦ DB Authorizations held from failure

Results of a failed IMS system

AUTHORIZED DATA BASES/AREAS=24 VERSION=11.1 XRF CAPABLE=NO ENCODED

-DBD- -AREA- -LEVEL- -ACCESS INTENT- -STATE-B1CST01 **NULL** 3 UPDATE 3 B1CST02 **NULL** 3 UPDATE 3 B1PRD01 **NULL** 3 UPDATE 3 B1CST03 **NULL** 3 UPDATE 3 B1CST04 **NULL** 3 UPDATE 3 B1CST05 **NULL** 3 UPDATE 3 B1PRD02 **NULL** 3 UPDATE 3 B1CST07 **NULL** 3 UPDATE 3

Page 8: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Results of a failed IMS system Include◦ OLDS is open◦ SUBSYS record exists in RECON◦ PRILOG record is open◦ DB Authorizations held from failure◦ IRLM held locks where converted to retained locks

Results of a failed IMS system

20.49.33 S0000963 DXR101I IRAI001 STATUS SCOPE=LOCAL 071071 SUBSYSTEMS IDENTIFIED071 NAME STATUS UNITS HELD WAITING RET_LKS071 IMSG DOWN 0 0 0 26071 DXR101I End of display

Page 9: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

IMS DIMS CIMS BIMS A

SHAREDDATABASE

IMS A failedbut

UPDATE-LOCKsare held by CF for

this databaserestart

(/ERE & backout)of IMS A

If applications ofIMS B, IMS C or IMSD

request datalocked by IMS A

they will get U3303

(LOCK REJECT)

U3303 U3303 U3303

Page 10: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

System Recovery Objectives

◦ Bring IMS up quickly

◦ Complete database integrity

◦ Message Queue Integrity

IMS Recovery/Restart

Page 11: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Emergency Restart (/ERE )◦ OVERRIDE – SUBSYS record exists ◦ COLDCOMM – “clean start” for DC, “warm start for DB◦ COLDBASE – “clean start” for DB, “warm start for DC◦ COLDSYS - “clean start” for whole system

IMS Restart

Page 12: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Emergency Restart (/ERE )◦ IMS Queue options

BUILDQ (non shared queues)Lost or full message queue

FORMAT SM short message LM long messageRS restart data set

IMS Restart

Page 13: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

IMS Restart OptionsOVERRIDE.◦ Required if the SUBSYS record is present and the

ABNORMAL TERM flag = OFF◦ Will overwrite running IMS systemIMS restarts using the same SUBSYS record◦ Starts with OLDS open or closed◦ Continues DBRC AUTHORIZATIONS already held◦ OPEN OLDS closed and then archived◦ PRILOG closed and new one opened◦ Performs dynamic back-outs for all active PSBs◦ SUBSYS record

START RECOVERY = YES/NO Log start time updated to new timeABNORMAL TERM=OFF

Page 14: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

IMS Restart OptionsSSYS SSID=IMSG LOG START=12.197 17:43:08.096454 SSTYPE=ONLINE ABNORMAL TERM=OFF RECOVERY STARTED=NO BACKUP=NO TRACKED=NO TRACKER TERM=OFF SHARING COVERED DBS=NO IRLMID=IRAI IRLM STATUS=NORMAL GSGNAME=**NULL** COEXISTENCE LEVEL=11.1

AUTHORIZED DATA BASES/AREAS=18 VERSION=11.1 XRF CAPABLE=NO ENCODED

-DBD- -AREA- -LEVEL- -ACCESS INTENT- -STATE-B1CST08 **NULL** 3 UPDATE 3 B1PRD08 **NULL** 3 UPDATE 3 B1CST07 **NULL** 3 UPDATE 3 B1PRD07 **NULL** 3 UPDATE 3 B1CST06 **NULL** 3 UPDATE 3 B1PRD06 **NULL** 3 UPDATE 3 B1CST05 **NULL** 3 UPDATE 3 B1CST04 **NULL** 3 UPDATE 3 B1PRD04 **NULL** 3 UPDATE 3 B1CST03 **NULL** 3 UPDATE 3 B1PRD03 **NULL** 3 UPDATE 3 B1PRD02 **NULL** 3 UPDATE 3 B1CST09 **NULL** 3 UPDATE 3 B1PRD09 **NULL** 3 UPDATE 3 B1CST10 **NULL** 3 UPDATE 3 B1PRD10 **NULL** 3 UPDATE 3 B1CST01 **NULL** 3 UPDATE 3 B1PRD01 **NULL** 3 UPDATE 3 D1CSTX **NULL** 1 UPDATE 6 D1CSTP **NULL** 1 UPDATE 6 D2CSTX **NULL** 3 UPDATE 3 D2CSTP **NULL** 3 UPDATE 3

SSYS SSID=IMSG LOG START=12.193 16:48:12.787416 SSTYPE=ONLINE ABNORMAL TERM=ON RECOVERY STARTED=NO BACKUP=NO TRACKED=NO TRACKER TERM=OFF SHARING COVERED DBS=NO IRLMID=IRAI IRLM STATUS=NORMAL GSGNAME=**NULL** COEXISTENCE LEVEL=11.1

AUTHORIZED DATA BASES/AREAS=22 VERSION=11.1 XRF CAPABLE=NO ENCODED

-DBD- -AREA- -LEVEL- -ACCESS INTENT- -STATE-B1CST01 **NULL** 3 UPDATE 3 B1CST03 **NULL** 3 UPDATE 3 B1PRD01 **NULL** 3 UPDATE 3 B1PRD02 **NULL** 3 UPDATE 3 B1CST05 **NULL** 3 UPDATE 3 B1PRD03 **NULL** 3 UPDATE 3 B1CST07 **NULL** 3 UPDATE 3 B1CST04 **NULL** 3 UPDATE 3 B1PRD04 **NULL** 3 UPDATE 3 B1CST09 **NULL** 3 UPDATE 3 B1CST06 **NULL** 3 UPDATE 3 B1CST08 **NULL** 3 UPDATE 3 B1CST10 **NULL** 3 UPDATE 3 B1PRD06 **NULL** 3 UPDATE 3 B1PRD07 **NULL** 3 UPDATE 3 B1PRD08 **NULL** 3 UPDATE 3 B1PRD09 **NULL** 3 UPDATE 3 B1PRD10 **NULL** 3 UPDATE 3 D1CSTX **NULL** 1 UPDATE 6 D1CSTP **NULL** 1 UPDATE 6 D2CSTX **NULL** 3 UPDATE 3 D2CSTP **NULL** 3 UPDATE 3

Page 15: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

IMS Restart OptionsUse COLDCOMM. when: ◦ Normal ERE failed and messages are 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◦ Starts with OLDS open or closed◦ Continues DBRC AUTHORIZATIONS already held◦ OPEN OLDS closed and then archived◦ PRILOG closed and new one opened◦ Performs dynamic back-outs for all active PSBs◦ SUBSYS record

START RECOVERY = YES/NO Log start time updated to new timeABNORMAL TERM=OFF

Page 16: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

IMS Restart OptionsUse COLDBASE. when: ◦ Normal ERE failed and database updates to be handled by

Batch Backout◦ IMS will maintain the IMS QueuesIMS restarts using the same SUBSYS record◦ Continues DBRC AUTHORIZATIONS already held◦ Dynamic database back-outs bypassed◦ BMP PSB are identifed

Databases STOPPED by IMS and AUTHORIZATIONS released ◦ BKOUT record is written◦ OLDS can be open or closed◦ OLDS Archived on completion ◦ PRILOG record is closed and new one opened

Page 17: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

IMS Restart OptionsCOLD Start Messages

DFS3261I WRITE AHEAD DATA SET NOW ON DFSWADS1 IMSG DFS979I BATCH MESSAGE PROGRAM B1ACSTA WAS ACTIVE AT TIME OF FAILURE IMSGDFS979I BATCH MESSAGE PROGRAM B1ACSTA WAS ACTIVE AT TIME OF FAILURE IMSGDFS979I BATCH MESSAGE PROGRAM B1ACSTA WAS ACTIVE AT TIME OF FAILURE IMSG DFS979I BATCH MESSAGE PROGRAM B1ACSTP WAS ACTIVE AT TIME OF FAILURE IMSG DFS979I BATCH MESSAGE PROGRAM B1ACSTA WAS ACTIVE AT TIME OF FAILURE IMSGDFS981I DBD=B1CST04 WITHIN PSB=B1ACSTP STOPPED DUE TO COLDBASE START. IMSGDFS979I BATCH MESSAGE PROGRAM B1ACSTA WAS ACTIVE AT TIME OF FAILURE IMSGDFS979I BATCH MESSAGE PROGRAM B1ACSTA WAS ACTIVE AT TIME OF FAILURE IMSGDFS979I BATCH MESSAGE PROGRAM B1ACSTP WAS ACTIVE AT TIME OF FAILURE IMSGDFS979I BATCH MESSAGE PROGRAM B1ACSTP WAS ACTIVE AT TIME OF FAILURE IMSG DFS981I DBD=B1CST04 WITHIN PSB=B1ACSTP STOPPED DUE TO COLDBASE START. IMSGDFS981I DBD=B1CST04 WITHIN PSB=B1ACSTP STOPPED DUE TO COLDBASE START. IMSGDFS2484I JOBNAME=IMSGARCH GENERATED BY LOG AUTOMATIC ARCHIVING IMSG DFS2484I JOBNAME=IMSGARCH GENERATED BY LOG AUTOMATIC ARCHIVING IMSG DFS2484I JOBNAME=IMSGARCH GENERATED BY LOG AUTOMATIC ARCHIVING IMSG

Page 18: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

IMS Restart OptionsUse 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. IMSG

Page 19: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Restarting IMS after Restart failureRestarting Failed IMS System◦ BEST OPTION: /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 worksClose the OLDS /ERE COLDSYS optionally (FORMAT RS)

Format the RDS data set for external subsystem accessINIT start CICS

/NRE CHKPT 0 FORMAT ALL

Page 20: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Steps to Run Manual Back Out1. List the OPEN OLDS. 2. Close the OPEN OLDS3. Find the Active PSBs4. Run Batch Backout5. Restart IMS

Page 21: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Find the OPEN OLDSSSID 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 come to 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= 00000000003EFE52STOP = 00.000 00:00:00.0 LAST DS LSN= 0000000000000000LOCK SEQUENCE# = 000000000000 STATUS=ACTIVE FEOV=NO AVAIL PRILOG TIME=07.200 18:18:12.0 VERSION=9.1

Page 22: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Find the OPEN OLDSLIST.LOG SSID(IMSG)

PRIOLD SSID=IMSG # DD ENTRIES=6 EARLIEST CHECKPOINT = 12.197 16:41:00.002614

DDNAME=DFSOLP04 DSN=IMSVS.IMSG.OLP04 START = 12.197 17:32:38.415424 FIRST DS LSN= 0000000000DCE8ED STOP = 12.197 17:32:49.956549 LAST DS LSN= 0000000000E6827A LOCK SEQUENCE# = C9DF7DA9123E STATUS=ARC COMPLT FEOV=NO AVAIL PRILOG TIME=12.193 16:48:12.787416 ARCHIVE JOB NAME=IMSGARCH VERSION=11.1

DDNAME=DFSOLP05 DSN=IMSVS.IMSG.OLP05 START = 12.197 17:32:49.956549 FIRST DS LSN= 0000000000E6827B STOP = 12.197 17:33:01.538164 LAST DS LSN= 0000000000F01BDE LOCK SEQUENCE# = C9DF7DB41D77 STATUS=ARC COMPLT FEOV=NO AVAIL PRILOG TIME=12.193 16:48:12.787416 ARCHIVE JOB NAME=IMSGARCH VERSION=11.1

DDNAME=DFSOLP00 DSN=IMSVS.IMSG.OLP00 START = 12.197 17:33:01.538164 FIRST DS LSN= 0000000000F01BDF STOP = 12.197 17:33:01.599799 LAST DS LSN= 0000000000F027F3 LOCK SEQUENCE# = C9DF7DB42CAA STATUS=ARC COMPLT FEOV=NO AVAIL PRILOG TIME=12.193 16:48:12.787416 ARCHIVE JOB NAME=IMSGARCH VERSION=11.1

DDNAME=DFSOLP01 DSN=IMSVS.IMSG.OLP01 START = 12.197 17:33:01.599799 FIRST DS LSN= 0000000000F027F4 STOP = 12.197 17:33:13.204815 LAST DS LSN= 0000000000F9BEDB LOCK SEQUENCE# = C9DF7DBF3D3F STATUS=ARC COMPLT FEOV=NO AVAIL PRILOG TIME=12.193 16:48:12.787416 ARCHIVE JOB NAME=IMSGARCH VERSION=11.1

DDNAME=DFSOLP02 DSN=IMSVS.IMSG.OLP02 START = 12.197 17:33:13.204815 FIRST DS LSN= 0000000000F9BEDC STOP = 00.000 00:00:00.000000 LAST DS LSN= 0000000000000000 LOCK SEQUENCE# = C9DF7DC68419 STATUS=ACTIVE FEOV=NO AVAIL PRILOG TIME=12.193 16:48:12.787416 ARCHIVE JOB NAME=IMSGARCH VERSION=11.1

Page 23: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Close the OLDSRun 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

Page 24: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Find the Active PSBsRun 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 INCOMPLETEIMSG 0000001800000000 BACKOUT IS REQUIRED NO DATABASE NAMES FOUND DBNAME LIST MAY BE INCOMPLETE

B1ACSTPIMSG 0000001B000000D7 BACKOUT IS REQUIRED

B1CST04 -B1UPPRDA

IMSG 0000001600000000 BACKOUT IS REQUIRED NO DATABASE NAMES FOUND DBNAME LIST MAY BE INCOMPLETE

END OF REPORT

Page 25: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

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 /*

Page 26: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

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 REPORT

Page 27: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Run Batch BackoutBBO 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 ERE COLDBASE◦ BKOUT record(s) should be written by IMS restart

COLDSTART Key word of BBO will build BKOUT Records for any active PSB (except the PSB being used in this run)

If NO BKOUT records ◦ BBO will still run and back out updates for PSB named

Page 28: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Run Batch Backout

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 NO

•LIST.BKOUT ALL will list the BKOUT records

Page 29: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Run Batch BackoutEach run of BBO might need different number of SLDS/OLDS data sets as input.

BBO has to find the start of the Unit of Recovery (UOR)

The worst case should be same DSNs as DFSULTR0 had to use.

Page 30: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

BBO Log inputs BACKOUT

SSID=IMSG #UORS=3

RECOVERY TOKEN=C9D4E2C7404040400000001B000000D7

TIME=07.204 21:34:56.0PSB=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.5PSB=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.5PSB=B1UPPRDA

CANDIDATE INFLT COLDEND ASSOCIATED DATA BASES=1

BACKED DYN BKOUT -DBD- -OUT - -FAILURE-

B1PRD02 NO NO

DSN=IMSVS.IMSG.SLDS.G0012V00 UNIT=3390 START = 07.204 21:29:58.1 FIRST DS LSN= 00000000000AAFAESTOP = 07.204 21:33:01.4 LAST DS LSN= 0000000000152A77

DSN=IMSVS.IMSG.SLDS.G0015V00 UNIT=3390 START = 07.204 21:33:58.2 FIRST DS LSN= 00000000002A15D5STOP = 07.204 21:34:26.6 LAST DS LSN= 00000000003489DE

Page 31: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Run Batch BackoutThe logs are supplied in the following order:◦ The oldest log required in time sequence (earliest time) on the

IMSLOGR 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.

Page 32: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

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),DCB=BUFNO=20,

// SPACE=(TRK,(100,10),RLSE),UNIT=SYSDA,DISP=(NEW,CATLG)

//IMS DD DISP=SHR,DSN=RLONG.CMXXX.DBDLIB

// DD DISP=SHR,DSN=RLONG.CMXXX.PSBLIB

//SYSIN DD * COLDSTART/*

Page 33: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Run Batch BackoutIf 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 GIMS03.10.55 J0030824 +DFS3293W PERFORMED BACKOUT NOT NEEDED03.10.56 J0030824 +DFS092I IMS LOG TERMINATED GIMS

Page 34: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Run Batch Backout

QUESTIONS?

[email protected]

MSOffice6

Page 35: Recovering from IMS Failures IMS Queues - IMS UG May 2014 San Ramon

Slide 34

MSOffice6 Would be good to have a summary of your presentation here too. , 9/08/2007