Tor ims db-hints_and_tips-sept14-2010

21
© 2010 IBM Corporation IBM Software Group IMS Database: Hints and Tips for Increased Availability, Manageability, and Ease of Use Gary Wicks [email protected]

Transcript of Tor ims db-hints_and_tips-sept14-2010

Page 1: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation

IBM Software GroupIMS Database: Hints and Tips for Increased Availability,

Manageability, and Ease of Use

Gary [email protected]

Page 2: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation2

IBM Software Group

Trademarks

IBM, IBM eServer, IBM logo, e-business logo, CICS, DB2, MQ, ESCON, Enterprise Storage Server, GDPS, IMS, MVS, OS/390, Parallel Sysplex, Redbook, Resource Link, S/390, System z9.iSeries, pSeries, System p,xSeries, System x, OS/400, i5OS, System Storage, TotalStorage,VM/ESA, VSE/ESA, WebSphere, z/OS, z/VM, z/VSE, and zSeries are trademarks or registered trademarks of International Business Machines Corp. in the United States, other countries, or both.

Linux is a registered trademark of Linux Torvalds in the United States, other countries, or both.

Microsoft is a registered trademark of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States, other countries, or both.

Page 3: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation3

IBM Software Group

DisclaimersCopyright © 2009 by International Business Machines Corporation.

No part of this document may be reproduced or transmitted in any form without written permission from IBM Corporation or except as expressly provided in a contract between you and IBM.

Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This information could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or programs(s) at any time without notice.

Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM’s intellectually property rights, may be used instead. It is the user’s responsibility to evaluate and verify the operation of any on-IBM product, program or service.

THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no responsibility to update this information. IBM products are warranted according to the terms and conditions of the agreements (e.g., IBM Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. IBM is not responsible for the performance or interoperability of any non-IBM products discussed herein.

The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights. Inquiries regarding patent or copyright licenses should be made, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

Page 4: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation4

IBM Software Group

Objectives

Every release of IMS includes enhancements to IMS Database. Sometimes these enhancements make a big splash; sometimes they are made available through the service stream and don’t get as much attention. But they are important and often deliver big impact!

Implementing these functions can help you to:

–Increase IMS availability –Simplify IMS manageability–Derive more ease of use–Enhance IMS base functions–Enhance dynamic IMS capabilities

Page 5: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation5

IBM Software Group

Agenda

Database enhancements

– Full Function– DEDB

Database Management enhancements

– DBRC

Dynamic Resource Definition

IMS V11 Database Quiesce

Source for these enhancements (APAR / PTF / Version level) will be located in a summary page at the end of this presentation

Page 6: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation6

IBM Software Group

LOCKTIME Change (V10 and V11 APARs)

Periodically an application will require a modification to the LOCKTIME setting

–This setting determines when IMS will timeout an application waiting for a database lock

–A periodic application (for instance, one that runs once a quarter) with a large number of database updates may require a different setting for LOCKTIME

–The LOCKTIME parameter is set in the DFSVSMxxmember of the IMS PROCLIB data set (or DFSVSAMP DD statement for IMS batch procedures)

–IMS must be restarted to change LOCKTIME

Page 7: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation7

IBM Software Group

Dynamic LOCKTIME

Introduces new type-2 command parameters

– QUERY IMS TYPE(LOCKTIME)– UPDATE IMS SET(LCLPARM(LOCKTIME(values)))

• Where values can be any combination of:MSG(xx), MSGOPT(a|s), BMP(yy), and BMPOPT(a|s) Where (xx): Time in seconds 1 to 32767 for online regions, (a or s): abend timed out application or send status code, (yy) Time in seconds 1 to 32767 for BMPs. See APAR text for details

Allows a change to LOCKTIME when business needs change– LOCKTIME can be changes for that periodic application

• Reset back to old values when application completes• No IMS outage required

Page 8: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation8

IBM Software Group

Dynamic LOCKTIME

Updating IMS LOCKTIME values does not affect the lock timeout value in an IRLM. To change the lock timeout value in an IRLM, use the existing MODIFY IRLM command.

It is generally recommended to use the same timeout values for both IMS and IRLM. When using two values in IMS, setting the IRLM timeout value to the lower of the two IMS values allows IMS and IRLM to act together.

Page 9: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation9

IBM Software Group

FF Response Mode Recovery Option (V9 and V10 APARs)

Full Function Response Mode not retained after terminal logoff or user signoff (base level)

–User not in response mode when they log back on• Can enter new transactions without receiving output from original

transaction

Option added to recover when user or terminal signs back on (maint level)

–User in response mode when they log back on• Cannot enter new transaction until output received

–Does not recover FF response mode across an IMS restart

IMSIMS

User

Response ModeTrans

IMSIMS

User

User logs off

IMSIMS

User

User Log BackOn

Page 10: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation10

IBM Software Group

DEDB Areas : Different Access Levels (V10 and V11 APARs)

All Areas within a FP DEDB have the same access level

–Business needs require some areas to have READ access and other areas to have UPDATE access

Type-2 command is modified to modify individual area access level

–UPDATE AREA NAME(area1,area2,..) START(ACCESS)• SET(ACCTYPE()) is added with RO RD UP and EX

–Access level cannot be greater than access level of DEDB

Page 11: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation11

IBM Software Group

Non-Recoverable SDEPs (V10 APAR)

Unable to make DEDBs non-recoverable via the DBRC NONRECOV option if SDEPs are defined

–No way to use SDEPs as a temp location to store data without the overhead of logging

• Could be used when data being stored is not important enough to recover if there is outage

Allows DEDBs to be non-recoverable, even if SDEPs are defined for the DEDB

–Reduces log volume–Reduces CPU use

Page 12: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation12

IBM Software Group

DBRC DELETE.DB Performance Improvements (V10 and V11 APARs)

Deleting certain DB records from the RECONs can cause a system slowdown

–DEDB with large number of areas or DBDSs that have a large number of associated ALLOC records

–This ties up the RECONs with large amount of I/O• Can prevent other work from processing

Method of processing DELETE.DB modified

–Fewer RECON accesses, less I/ORECON

IMS

Page 13: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation13

IBM Software Group

DBRC Change Accumulation improvements (V10 APAR)

Change Accum utility fails with DSP0711I: Invalid purgetime, if RECONs changed since JCL generated

– Later Image copy, archived OLDS, on-line reorg, and off-line reorg will change the RECONs and cause the Change Accum to fail

– Problem more likely to be hit on busy system

Allows the Change Accum utility to tolerate some RECON changes

–If RECON changes

• Informational messages are issued• Different results based on discovered condition will occur: CC

0s or CA failure. Review APAR for more information

Page 14: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation14

IBM Software Group

DRD - Exporting and Importing Definitions Background (V10 APARs)

DB / DBDESCPGM / PGMDESC

TRAN / TRANDESCRTC / RTCDESC

RDDS

Control BlocksDDIRsPDIRsSMBsRCTEs

Descriptors

IMS CONTROL REGION

CREATEUPDATEDELETE

DBPGMTRANRTC

MODBLKS

/CHE xxxx

/NRE CHKPT 0

/NRE CHKPT 0

/NRE or /ERE

OLDS

CheckpointRecords

No longer required:•MODBLKS Sysgen process•MODBLKS staging, active, and inactive data sets•MODBLKS online change process

Page 15: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation15

IBM Software Group

DRD : Import/Export Commands

New type-2 commands introduced

–EXPORT DEFN

• Provides ability to export subset of resources• Provides ability to append to RDDS• RDDS can be moved to another IMS

–IMPORT DEFN

• Provides ability to import subset of resources

• RDDS can be from another IMS

MODBLKS

RDDS

IMS

Page 16: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation16

IBM Software Group

DRD : Unable to Build or Recover RDDS OfflineRDDS Extraction Utility (DFSURDD0) – base V10

–Offline Batch Utility to convert RDDS data into:

• SYSGEN macro statementsAPPLCTN, DATABASE, RTCODE, TRANSACT

• Type-2 CREATE commandsCREATE DB, CREATE DBDESC, CREATE PGM…

What happens if the RDDS is lost?

–How can I create a new RDDS offline?

• MODBLKS dataset• SYSGEN macros• IMS Log

MODBLKS

RDDS

IMS

Page 17: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation17

IBM Software Group

DRD : Maintenance Utilities (V10 and V11 APARs)

DRD Maintenance Utilities provide a way to move resource information

–Input• MODBLKS dataset• SYSGEN macros• IMS log• RDDS

–Output• RDDS• SYSGEN macros• CREATE commands

ISPF panel driven

MODBLKS

RDDS

IMS

Page 18: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation18

IBM Software Group

TSO SPOC Print Options (V10 APAR)

TSO SPOC users have single options for command output–Some commands have large amount of output

TSO SPOC print options allow user to set output style–Wrap, by column, or by resource

IMSControlRegion

SCI

OperationsManager

(OM)

SCI

TSO SPOC

SCI

z/OS

Page 19: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation19

IBM Software Group

V11 - DB QuiesceIssue Quiesce command– Command is processed by one IMS in the IMSplex. That IMS

coordinates with the other IMSs within the same DBRC sharing group and establishes a new recovery point in the RECON

IMS

IMS

IMS RECONRECON

Quiesce and hold– Reach the quiesce point and keep the resource quiesced– Allows IC utilities to be run after database has been quiesced– Must issue another command to release the quiesce on the database– Hardens SVSO and SDEPs to DASD

Quiesce and go– Reach the quiesce point and release the quiesce in a single command– Used to quickly establish a new recovery point for a resource

Page 20: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation20

IBM Software Group

These functions can help with manageability and costPTF #APAR #Function

UK35086PK50292SPOC Print Options

UK43484PK63186DRD Maintenance Utilities

UK41049PK66704DRD EXPORT Command

UK41047PK66682DRD IMPORT Command

UK59092 PK90142 Dynamic LOCKTIME

UK32360PK53989FF Response Mode Recovery

UK43479PK68143DBRC DELETE.DB Perf Enh

PTF #APAR #Function

UK42764PK74403DEDB Area Different Access

UK35862PK56321Non-Recoverable SDEPs

UK42502PK53223Change Accum

These functions help with growth and scalability

Summary:

Page 21: Tor ims db-hints_and_tips-sept14-2010

© 2010 IBM Corporation21

IBM Software Group