Uploaded on


  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Maintain for DB2 z/OS Automatically maintain DB2 databases Overview Key Benefits Maintain for DB2 z/OS will distinguish your company from the Automatically maintain your DB2 rest with its state-of-the-art solutions for providing the best automatic database on an as-needed basis database maintenance possible. Your customers and internal users drive the need for better services for your business processes. Not Guarantee the fastest database only does this require an extension of online service times, e.g., from 6 maintenance possible a.m. to 10 p.m., but may also mean around-the-clock operations 24 hours a day 7 days a week. As a consequence, getting your database Use CPU and DBA resources maintenance completed in a smaller batch window, or even parallel to efficiently online operations, is more important than ever. Drastically reduce costs Within even the smallest of batch windows, Maintain performs the Achieve the best possible analysis that is necessary to generate only the as-needed utility performance of applications, maintenance and does this faster than any tool available on the market. which results from optimal The only thing better and faster is to combine this classic Maintain maintenance solution with IBM’s real-time statistics (RTS) and RealTimeMaintain to extend your DB2 maintenance beyond the batch window and into Eliminate manual processes real-time. and reduce errors Maintain’s intelligent monitoring of database growth and object Improve the security of DB2 update rates allows for the complete analysis of the largest DB2 data through timely backups systems on a daily basis. Even analysis for the most expensive utilities is done with the assurance that only the RUNSTATS and REORGs that really Support 24x7 operations with need to be done are generated for execution. an interface to real-time maintenance using IBM’s RTS Maintain for DB2 Maintain provides the fastest and most efficient classic maintenance available on the market. www.seg.de www.segus.com
  • 2. Make the most of classic maintenance Automatic inclusion of new Your critical business processes require secure data and high DB2 objects performing applications. In the classic maintenance arena, this implies a batch process on a routine basis that dynamically determines as needed Automatic exclusion of utilities. Implementing this routine classic maintenance is so easy with dropped objects Maintain because you can: Automatic adjustment to space requirements and device Group DB2 objects using generic notation so that similar objects types. undergo the same processing at the same time. Efficient use of advanced Define a flexible maintenance time schedule that identifies either; utilities like online REORG. when the maintenance thresholds are checked or the specific utility generation dates, or a combination of the two. Avoid the costly execution of Define the maintenance thresholds to be used in determining unnecessary RUNSTATS and which utilities should be generated for which objects. REORG Define a utility job strategy to be used in determining which jobs should be generated for which utility. Generate and control utility JCL intelligently Maintenance job strategies can be defined that are easy to integrate into any job scheduling environment. When defining a job strategy, you may group objects differently than you did for defining utility maintenance. For example, when defining objects for each of the specific utilities, you may have multiple object groups, each requiring the same utility, but with different thresholds. However, when defining a job strategy you may want to assign all objects to the same job by utility type. An intelligent job scheduler Maintain for DB2 z/OS ------- Job Name Detail ------------------------------- interface supports flexible job Command ===> _______________________________________________________________ DB2: D810 naming, dummy jobs, fixed Primary cmd: J(obs), A(ll jobs), P(rint) Line cmd: U(pdate job), E(dit skeleton), X(ref) number of jobs or job steps, and DATABASE . . . . MIVPT* TABLESPACE . . . . *_______ more. UTIL CMD JOB NEW PADDING #JOBS #STEPS # PER SKELETON --------------- --- -------- JOB ------- ----- ------ STEP -------- FORECAST _ S710RF__ N Y 5 5 10 MDB2VJOB REBIND AFTER _ ________ QUIESCE _ S710QU__ N Y 2 236 25 MDB2VJOB REORG _ S710RO__ N Y 1 100 MDB2VJOB ALTER BEFORE _ ________ NONPART INDEX _ ________ REBIND AFTER _ ________ COPY _ S710CO__ N Y 5 100 MDB2VJOB RUNSTATS _ S710RS__ N Y 2 236 25 MDB2VJOB REBIND AFTER _ ________ STOSPACE _ S710ST__ N 1 1 10 MDB2VJOB MERGECOPY _ ________ MODIFY RECOVERY _ S710MO__ N Y 5 10 10 MDB2VJOB MODIFY STATISTICS _ S710MS__ N Y 3 236 25 MDB2VJOB Once Maintain has generated only the necessary DB2 utilities for integration into your job scheduling system, BatchControl for DB2 utilities takes over; monitoring their execution, reporting bottlenecks, restarting broken utilities, and performing clean up. www.seg.de www.segus.com
  • 3. Define and generate DB2 utilities flexibly User-defined object grouping Maintain supports all functionalities and features of all IBM standard within a job DB2 utilities, as well as some fast utilities. Because different DB2 object groups obviously require different utility maintenance based on the Flexible job naming needs of your environment, the powerful utility generator of Dummy job generation if Maintain variably controls the timing of the generated JCL necessary depending on the object group, the type of utility, and the maintenance thresholds that you define. Dynamic job scheduler interface The following are just a few of the special features of utility generation GDGs are supported and can with Maintain: be dynamically generated Copies can be defined as full, incremental, or variable, which means Dependent utilities, e.g., full Maintain will determine whether an incremental copy or full COPY after REORG, handled as copy is needed based on the objects update rate and size. subsequent steps to the utility they depend on Automatic handling of index copies along with the copies of their Device types are generated affiliated table spaces. based on the type of utility Supports distinct SAP solutions Automatic maintenance of DB2 catalog and directory. regarding special maintenance requirements REORG decisions are based strictly on the newly gathered statistics and relevant historical information about the objects. Maintain manages REORGs so efficiently that you will never have to wait until the weekend for critical REORGs. RUNSTATS forecasting avoids unnecessary RUNSTATS. REBIND after REORG can always be generated without risk when using Maintain’s tool ImpactManager, which guarantees REBINDS that improve performance. Comprehensive logging of all activities provides detailed processing results. Online user request features allows ad-hoc utility generation for immediate execution. Interfaced with SpaceManager, Maintain automatically determines necessary alters and generates these within a REORG job during the normal batch window. www.seg.de www.segus.com
  • 4. Easily manage utility thresholds and parameters Using the online interactive dialog panels, you can easily define all the specific details of your maintenance strategy based on the specific needs of your DB2 environment. Once these definitions are entered, Maintain takes over completely; monitoring the DB2 object groups and generating the appropriate DB2 utility, as needed, based on the thresholds and/or time schedules you define. Always do REBINDs after RUNSTATS Maintain for DB2 z/OS ------- RUNSTATS Thresholds --------------------------- Command ===> ________________________________________________________________ without any risk with Impact- DB2: D810 Manager, a related product to DATABASE . . . : MIVPT* TABLESPACE . . . : * implement performance insurance RUNSTATS OBJECT . . . . . AL - AL(=TS+IX)/TS/IX/V(ariable) into the maintenance procedure. MAX PAGES . . . . . . . _______ - Max number of pages (only if OBJECT = V) RUNSTATS FORECAST . . . . Y - Y(es)/N(o) The following fields are valid only if FORECAST = Y (*): PCT PAGES TOTAL . . . . 5__ - Growth in pages total since last RUNSTATS PCT PAGES UPDT . . . . 5__ - Pages updated since last RUNSTATS STATISTICS GATHERED . . Y - Y(es)/N(o) RS AFTER LOAD/REORG . . Y - Y(es)/N(o) DAYS NO RUNSTATS . . . 7__ - Number of days with no RUNSTATS REBIND AFTER . . . . . . . Y - Y(es)/N(o) -------------------------- RUNSTATS Parameters --------------------------- SHRLEVEL . . . . . . R - R(eference)/C(hange) REPORT . . . . . . . N - Y(es)/N(o) UPDATE . . . . . . . AL - AL(l)/AP(=AccessPath)/SP(ace)/NO(ne) HISTORY. . . . . . . NO - AL(l)/AP(=AccessPath)/SP(ace)/NO(ne) FORCEROLLUP. . . . . N - Calculate aggregate statistics Y(es)/N(o) SAMPLE . . . . . . . 25 - Blank or percentage of rows to sample MIN PAGES . . . . ______ - Sample only tablespaces > this nbr of pages All REORG dependent actions, e.g., Maintain for DB2 z/OS ----- REORG Thresholds ------------------------------ Command ===> ______________________________________________________________ QUIESCE, COPY before, during, or DB2: D810 after REORG, etc. are easily DATABASE . . . : M410*___ TABLESPACE . . . : * triggered using a subsequent online panel. REORG OBJECT . . . . TP - TS/TP/V(ariable) MAX NBR OF PART . 254_ - Valid only if OBJECT = TP or V MAX PAGES TS . . ________ - Valid only if OBJECT = V REORG TABLESPACE THRESHOLDS MIN PAGES . . . . 32______ - No reorg if OBJECT is smaller than this size PCT INDREF. . . . 10_ - Percentage FARINDREF+NEARINDREF PCT OFFPOS. . . . 10_ - Percentage FAROFFPOS+NEAROFFPOS PCT DROP . . . . ___ - Percentage rows of dropped tables CLUSTERRATIO-1 . 95_ CLUSTERRATIO-2 90_ for OBJECTS > 1000___ pages CLUSTERRATIO-3 ___ for MEMBER CLUSTER REORG LOB THRESHOLDS ORGRATIO . . . . 2.00__ - Ratio of organization for LOB table spaces PCT FREESPACE . . ___ - Percentage FREESPACE REORG INDEX THRESHOLDS PCT LEAFFAR . . . ___ - Percentage LEAFFAR PCT DELETE . . . ___ - Percentage PSEUDO_DELETED_ENTRIES REORG REDUCE EXTENTS N - Y(es)/N(o) Make the distinguishing choice for your classic DB2 database maintenance; choose Maintain. SOFTWARE ENGINEERING GMBH SEGUS Inc Robert-Stolz-Strasse 5 D-40470 Dusseldorf 12007 Sunrise Valley Drive Reston, VA 20191-3446 Tel: +49-211-9 61 49-0 Fax: +49-211-9 61 49-32 Tel: 800-327-9650 Fax: 703-391-7133 http://www.seg.de Email: se.info@seg.de http://www.segus.com Email: info@segus.com © 2004 SOFTWARE ENGINEERING. All named references herein are trademarks of their respective companies. www.seg.de www.segus.com