Bra what's new in ims tools 2010

© 2010 IBM Corporation

Information Management


What’s new in IBM IMS Tools

Janet LeBlancSilicon Valley [email protected]

2010 – Information Management Tech Conference - Brazil

Janet LeBlancSilicon Valley [email protected]

© 2010 IBM Corporation2



Updates to IMS Tools

2009

� August 2009

– IMS Audit Management Expert, V1.2

– IMS Cloning Tool, V1.1

– IMS Connect Ext, V2.2

– IMS Performance Analyzer, V4.2

� October 2009– IMS Problem Investigator, V2.2

2010

� February 2010– IMS Tools Solution Packs:

•IMS Fast Path Solution Pack, V1.1 •IMS Performance Solution Pack, V1.1 •IMS Database Solution Pack, V1.1 •IMS Recovery Solution Pack, V1.1•IMS Tools Base, V1.1

– IMS Database Reorganization Expert, V4.1

– IMS Configuration Manager, V1.3

– IMS High Performance Image Copy, V4.2

� August 2010– IMS Recovery Expert V2.1




IMS Audit Management Expert




� Automation– Simplifies the collection of audit data

• Reduces manual efforts and increases productivity– Achieve more thorough audits– Reduces the cost of auditing

� Centralization – Collects and correlates information from many systems and data sources

into an audit repository– Provides a coherent view of IMS audit data into useful representations

• GUI and batch reports for examining the data – Supports internal and external auditors

� Segregation of duties– Provides segregation of duties

• Provides audit data integrity• Removes opportunity for data tampering• Auditors are no longer dependent on developers or database administrators to

set up or gather the audit information required• Frees up DBAs to perform their own duties and allows auditors to run audit

reports independently of the DBAs

Overview of IMS Audit Management Expert for z/OS




IMS Audit Management Expert for z/OS

�Data collection– Audit and report READ, INSERT, UPDATE and DELETE

accesses to databases– Audit and report READ, INSERT, UPDATE, and DELETE calls on

specific database segments• READ and DELETE calls retain the concatenated key of the audited

segment • UPDATE and INSERT calls retain the concatenated key of the audited

segment as well as the segment data, as found in the DLI call I/O area– Access to:

• Databases and segments from IMS Batch (DLI/DBB/BMP) jobs• Databases and segments from IMS Online regions• Database, image copy and RECON data sets as recorded in SMF • User access to the IMS system via SIGNON as recorded in the IMS

log • PSB and database ‘change of state’ activity as recorded in the IMS log • System STOP and START activity as recorded in the IMS log




Reporting GUI – Drilling Down




IMS Audit Management Expert




IMS Cloning Tool




IMS Cloning Tool V1.1

� Clones IMS systems (includes all databases)

– Uses volume-based fast replication, including:

• FlashCopy (IBM,EMC,HDS), TimeFinder/Snap(EMC), SnapShot (IBM,STK), Onsite Mirrors, Software Point-in-Time

– Performs the necessary operations so that the data can be used by the cloned IMS system

– IMS Cloning Tool takes an existing IMS system (complete installation and system generation process completed) and creates a new, or cloned, IMS system from it without having to repeat the entire installation and system generation processes

� Refreshes specific or sets of IMS databases

– Uses data set based fast replication, including:

• FlashCopy (IBM,EMC,HDS), TimeFinder/Snap(EMC), SnapShot (IBM,STK)

– Performs the necessary operations to enable the cloned databases to be used on the same or another IMS system

New




Copying/Cloning HALDB Databases

� Can be complex, expensive and can affect database availability

• HALDB partition numbers are stored in the RECON and in the database data sets themselves – can’t open if they don’t match

• Coordinating this manually complicates the copy process

HALDB partitions must be deleted and redefined in the target IMS

Each HALDB redefinition must use the same partition number and gap sequence that exists on the source IMS

• Unload utilities are traditionally run at a database level affecting application availability

• If used Image copy process, the steps are complex:

» delete the target database definition from the RECONs

» import the HALDB partition definition

» register the image copy to the target RECONs

» perform a database recovery on the target database

» Primary and secondary index and Indirect List Data Set (ILDS) rebuilds are performed




IMS Recovery IMS Recovery

Solution PackSolution Pack

IMS Database IMS Database


IMS Performance IMS Performance


Everything you need for…

IMS Fast Path IMS Fast Path


IMS Tools Base




What is IMS Fast Path Solution Pack ? ..

� “An All-In-One Fast Path full maintenance solution”1.IMS High Performance Fast Path Utilities (HPFPU)2.IMS High Performance Image Copy for z/OS V4R2 (HPIC) (new release)

3.IMS Library Integrity Utilities for z/OS V2R1 (LIU) 4.IMS Database Repair Facility (DB Repair)

� Each of these tools is also shipped as a separate product� One program directory, combined sample installation JCL, and simplified SMP/E install

� IMS Tools Base for z/OS is required

IMS Library Integrity UtilitiesIMS Library Integrity Utilities

UnloadReload

Reorganization

DB Integrity Check

Backup

Image Copy

IMS Definition Libraries Management

DB RepairDB Space Utilization Analysis

IMS HP FP UtilitiesIMS HP FP Utilities DB Repair FacilityDB Repair Facility

IMS HP Image CopyIMS HP Image Copy

IMS Fast Path Solution Pack




DB Solution Pack helps daily DBA tasks

� DB Solution Pack provides a complete set of high performance tools to unload, load, reorganize, build indexes for, backup, verify, and report on full-function databases

UnloadLoad

Reorganization

DB Integrity CheckDB Repair

BackupImage Copy

IndexBuild/Recovery

IMS Definition Libraries Management

DB Space Utilization Analysis

DB Repair FacilityDB Repair Facility

IMS Database Reorganization Expert

IMS Index BuilderIMS Index Builder IMS High Performance Image Copy

IMS High Performance Image Copy

IMS High Performance Prefix Resolution

IMS High Performance Prefix Resolution

IMS Library Integrity Utilities

IMS Library Integrity Utilities

IMS High Performance Load

IMS High Performance Load

IMS High Performance Pointer Checker

IMS High Performance Pointer Checker

IMS High Performance Unload

IMS High Performance Unload




Index BuilderIndex Builder

Incremental

Image Copy

DB Integrity Check

BackupImage Copy

Database Recovery

Database Recovery FacilityDatabase Recovery FacilityIMS HP Change

Accum

IMS HP Change Accum

IMS HP Image CopyIMS HP Image Copy

IMS Recovery Solution Pack V1.1IMS Recovery Solution Pack V1.1

Build Indexes, ILDS

IMS Recovery Solution Pack

Recovery Health Check

Change

Accumulation

A solution for your Backup and Recovery needs

Recovery ExpertRecovery Expert




Rules Based

Routing

DB Integrity Check

Custom FORMs based reports

Dashboard

IMS Connect Event Collection

IMS Performance AnalyzerIMS Performance Analyzer

IMS Transaction

Index

Log data:

IMSDB2

Websphere MQ

IMS Connect

OMEGAMON

ISPFdialog

Extracts

Reports

IMS Problem InvestigatorIMS Problem Investigator

IMS Performance Solution Pack Transit Reports

IMS Performance Solution Pack V1.1IMS Performance Solution Pack V1.1

IMS Connect ExtensionsIMS Connect Extensions




IMS Tools Base provides common services

� Tools in IMS Database Solution Pack optionally use following services in IMS Tools Base:

– IMS Tools Generic Exits

– IMS Tools Knowledge Base (ITKB)

– IMS Tools Online System Interface (TOSI)

– Policy Services

– IMS HD Compression Ext

� Most of the tools in the Pack can use ITKB for centralized report repository

� Reorg Expert uses ITKB for policy repository and sensor data repository

� HPIC and Reorg Expert use TOSI (and Generic Exits) for automated IMS online command operation




IMS Database Reorganization Expert




Reorg Expert solutions

1.Central management of information and dataReorg Expert offers IMS DBAs the capability of centrally controlling the information and statistics data that are needed to plan and perform reorganization of IMS databases effectively

2.Policy-based database space managementReorg Expert reduces the amount of work and expertise required to perform complex report analysis for determining reorganization need

3.Conditional reorganizationReorg Expert helps avoid unnecessary reorganizations that are based on fixed schedules that do not consider if a reorganization is actually required or what type of reorganization is appropriate

Necessary info/data are always there in well-defined formatNecessary info/data are always there in well-defined format

Decision criteria and actions are documented in policiesDecision criteria and actions are documented in policies

Reorganization need/effectiveness are evaluated and notifiedReorganization need/effectiveness are evaluated and notified




Smart Reorg utility features at a glance

� All information are stored in and managed by IMS Tools KB repositories

� Sysplex-wide access to these repositories is supported by IMS Tools KB Server

IMS Tools KBServer

ISPF Report

Search/View

ISPF

System z

Server

Smart Reorg job

Sensor data records

and reports are sent to repository

A policy is retrieved from repository and is applied

Policy Repository*1

ReportRepository*2

Sensor DataRepository

TSO users

and/or

z/OS

operator

consoles

Notification messages are sent

Sysplex1. Sensor Data

Collection

2. Reorg policy

Definition

3. Conditional Reorganization

4. Exception Notification and

Reporting

5. Tracking exceptions and

reorgs

*1: ITKB Input Repository is used as the Policy Repository.*2: ITKB Output Repository is used as the Report Repository.

1

34

5

3

Policy

Management

2




Exception detection condition is defined in a rule

DB_PCT_OF_MAX_DS_SIZE

The percentage of allocated bytes (bytes for High Allocated RBA) compared to the maximum size (4 GB or 8 GB).

DB_PCT_BYTES_FREE_SPACE

The percentage of bytes of total free spaces to the total used bytes for the data set.

Sample Data Elements

A named set of threshold values for the threshold variables that are referred to in the condition descrition above is called a threshold set.

A Sample Condition Description

A Sample Set of Threshold Values

&1 = 85&2 = 20

Threshold Set

You can tweak these threshold

values“MED” =

Feature-2. Policy




Attributes of an exception

� Exception class– Represents the specific database event

category being monitored

� Exception severity level– Is a category representing the severity of

the detected exception– There are fixed three levels:

• WARNING• SEVERE• CRITICAL

� Exception message– Is the text that can be used by the

resulting policy action to describe the database event that crossed a rule threshold set

– Users can modify the message text

Class

Level

Exception

Message Text

� CRITICAL

� SEVERE

� WARNING

� CRITICAL

� SEVERE

� WARNING

Exception Class:

FRAGMENTED_FREE_SPACESFRAGMENTED_FREE_SPACESFRAGMENTED_FREE_SPACESFRAGMENTED_FREE_SPACES

* Name of the rule that detects the this exception:

IBM.FRAGMENTATION.10

Exception Class:

FRAGMENTED_FREE_SPACESFRAGMENTED_FREE_SPACESFRAGMENTED_FREE_SPACESFRAGMENTED_FREE_SPACES

* Name of the rule that detects the this exception:

IBM.FRAGMENTATION.10

An Example of Exception Class

“The fragmentation of free space in %RESOURCE%has increased”

* The symbol %RESOURCE% is replaced by a DBDname or a partition name.

“The fragmentation of free space in %RESOURCE%has increased”

* The symbol %RESOURCE% is replaced by a DBDname or a partition name.

An Example of Exception Message

Feature-2. Policy




Exception-to-Action mapping

� An action is the result of a rule condition being reached or exceeded during a policy evaluation

� A rule threshold set has been mapped to a severity level for the exception class associated with the rule

� In turn, the severity level is mapped to an action

Note: In IBM-provided REORG policies, severity-level-to-action mappings are fixed for each exception class and are not customizable.

ThresholdSet

Exception Class+ Severity Level

Action

HIGHHIGHHIGHHIGH

MEDMEDMEDMED

LOWLOWLOWLOW

CRITICAL

SEVERE

WARNING

REORGREORGREORGREORG

MESSAGEMESSAGEMESSAGEMESSAGE

An Example of threshold/exception/action mapping

Feature-2. Policy




Associating a database with a policy

� Smart Reorg utility provides three types of policy association:

– By database type• This is the default.• IBM-provided SYS.DBDTYPE.type

policies is selected

– By database name• This is intended to be used to specify

a database specific policy

– By policy name• This is intended to be used to specify

a same policy for a group of databases

//CREORG EXEC PGM=HPSGMAIN,PARM='DBD=SAMPLEDB,DBRC=Y'//STEPLIB DD DISP=SHR,DSN=IMSTOOL.LOADLIB// DD DISP=SHR,DSN=IMS.SDFSRESL// DD DISP=SHR,DSN=USER.PGMLIB//IMSDALIB DD DISP=SHR,DSN=IMS.MDALIB//IMS DD DISP=SHR,DSN=IMS.DBDLIB//HPSIN DD *(REORG)

CONDREORG=YESCONDREORG=YESCONDREORG=YESCONDREORG=YESITKBSRVR=FPQSVR00ITKBSRVR=FPQSVR00ITKBSRVR=FPQSVR00ITKBSRVR=FPQSVR00SPACEALLOC=YESNAMESWAP=YES

(CONDREORG)POLICYBY=DBTYPEPOLICYBY=DBTYPEPOLICYBY=DBTYPEPOLICYBY=DBTYPE

/*

//CREORG EXEC PGM=HPSGMAIN,PARM='DBD=SAMPLEDB,DBRC=Y'//STEPLIB DD DISP=SHR,DSN=IMSTOOL.LOADLIB// DD DISP=SHR,DSN=IMS.SDFSRESL// DD DISP=SHR,DSN=USER.PGMLIB//IMSDALIB DD DISP=SHR,DSN=IMS.MDALIB//IMS DD DISP=SHR,DSN=IMS.DBDLIB//HPSIN DD *(REORG)

CONDREORG=YESCONDREORG=YESCONDREORG=YESCONDREORG=YESITKBSRVR=FPQSVR00ITKBSRVR=FPQSVR00ITKBSRVR=FPQSVR00ITKBSRVR=FPQSVR00SPACEALLOC=YESNAMESWAP=YES

(CONDREORG)POLICYBY=DBTYPEPOLICYBY=DBTYPEPOLICYBY=DBTYPEPOLICYBY=DBTYPE

/*

POLICYBY=DBTYPEPOLICYBY=DBTYPEPOLICYBY=DBTYPEPOLICYBY=DBTYPEPOLICYBY=DBTYPEPOLICYBY=DBTYPEPOLICYBY=DBTYPEPOLICYBY=DBTYPE

POLICYBY=DBDNAMEPOLICYBY=DBDNAMEPOLICYBY=DBDNAMEPOLICYBY=DBDNAMEPOLICYBY=DBDNAMEPOLICYBY=DBDNAMEPOLICYBY=DBDNAMEPOLICYBY=DBDNAME

POLICYBY=NAMEPOLICYBY=NAMEPOLICYBY=NAMEPOLICYBY=NAMEPOLICYNM=MY.POLICY.GROUP1POLICYNM=MY.POLICY.GROUP1POLICYNM=MY.POLICY.GROUP1POLICYNM=MY.POLICY.GROUP1

POLICYBY=NAMEPOLICYBY=NAMEPOLICYBY=NAMEPOLICYBY=NAMEPOLICYNM=MY.POLICY.GROUP1POLICYNM=MY.POLICY.GROUP1POLICYNM=MY.POLICY.GROUP1POLICYNM=MY.POLICY.GROUP1

By database type

By database name

By policy name

Policy to be selected

SYS.DBDTYPE.SYS.DBDTYPE.SYS.DBDTYPE.SYS.DBDTYPE.typetypetypetype

SYS.DBDNAME.SYS.DBDNAME.SYS.DBDNAME.SYS.DBDNAME.dbdnamedbdnamedbdnamedbdname

MY.POLICY.GROUP1MY.POLICY.GROUP1MY.POLICY.GROUP1MY.POLICY.GROUP1

(type = HDAM, HIDAM, PHDAM, PHIDAM, HISAM, or SHISAM)

Feature-3. Conditional Reorg




Report Example – Summary of Policy Evaluation

IMS DB Reorg Expert - V4R1 Database Diagnosis Report Page: 25655-S35 Date: 12/16/2009 Time: 00.05.14

Summary of Policy Evaluation (DBD: BKDB ) -----------------------------------------------------------------Name of Policy Applied............ SYS.DBDTYPE.HIDAM Policy Locale..................... Global Reorganization Need............... Yes

Exceptions before Reorganization --------------------------------------------------------------------------------The number of available extents for a data set of BKDB is small

Class: DATA_SET_EXTENTS_AVAILABILITY Level: CRITICAL Rule: G:IBM.DBDS_EXTENTS.10 Threshold Set: HIGH

The size of a data set in BKDB, which still has a certain amount of free space, has increased

Class: GROWING_DBDS_WITH_FREE_SPACES Level: CRITICAL -> REORG Rule: G:IBM.DBDS_GROWTH.20 Threshold Set: HIGH

The fragmentation of free space in BKDB has increased Class: FRAGMENTED_FREE_SPACES Level: CRITICAL -> REORG Rule: G:IBM.FRAGMENTATION.10 Threshold Set: HIGH

A data set of BKDB has many pointers that point to other bocks or CIsClass: EXCESSIVE_SEGMENT_SCATTERING Level: SEVERE Rule: G:IBM.SEGM_SPREAD.10 Threshold Set: MED

--------------------------------------------------------------------------------

Exceptions after Reorganization --------------------------------------------------------------------------------BSN2800I GENERAL STATUS: RESOURCE=BKDB ACTION_NAME=REORG EXECUTION_STATUS=SUCCESSFUL

The number of available extents for a data set of BKDB is small Class: DATA_SET_EXTENTS_AVAILABILITY Level: CRITICAL Rule: G:IBM.DBDS_EXTENTS.10 Threshold Set: HIGH

--------------------------------------------------------------------------------

Summary of Policy Evaluation and Action: --------------------------------------------------------------------------------BSN2904I BKDB HAS BEEN REORGANIZED, BUT IT IS STILL IN A CRITICAL STATE --------------------------------------------------------------------------------


Summary of Policy Evaluation (DBD: BKDB ) -----------------------------------------------------------------Name of Policy Applied............ SYS.DBDTYPE.HIDAM Policy Locale..................... Global Reorganization Need............... Yes

Exceptions before Reorganization --------------------------------------------------------------------------------The number of available extents for a data set of BKDB is small

Class: DATA_SET_EXTENTS_AVAILABILITY Level: CRITICAL Rule: G:IBM.DBDS_EXTENTS.10 Threshold Set: HIGH

The size of a data set in BKDB, which still has a certain amount of free space, has increased

Class: GROWING_DBDS_WITH_FREE_SPACES Level: CRITICAL -> REORG Rule: G:IBM.DBDS_GROWTH.20 Threshold Set: HIGH

The fragmentation of free space in BKDB has increased Class: FRAGMENTED_FREE_SPACES Level: CRITICAL -> REORG Rule: G:IBM.FRAGMENTATION.10 Threshold Set: HIGH

A data set of BKDB has many pointers that point to other bocks or CIsClass: EXCESSIVE_SEGMENT_SCATTERING Level: SEVERE Rule: G:IBM.SEGM_SPREAD.10 Threshold Set: MED

--------------------------------------------------------------------------------

Exceptions after Reorganization --------------------------------------------------------------------------------BSN2800I GENERAL STATUS: RESOURCE=BKDB ACTION_NAME=REORG EXECUTION_STATUS=SUCCESSFUL

The number of available extents for a data set of BKDB is small Class: DATA_SET_EXTENTS_AVAILABILITY Level: CRITICAL Rule: G:IBM.DBDS_EXTENTS.10 Threshold Set: HIGH

--------------------------------------------------------------------------------

Summary of Policy Evaluation and Action: --------------------------------------------------------------------------------BSN2904I BKDB HAS BEEN REORGANIZED, BUT IT IS STILL IN A CRITICAL STATE --------------------------------------------------------------------------------

Policy name

The locale where the policy is defined

Result of decision on reorganization need

Summary message, which shows that a CRICTICAL exception still remains after

the reorganization.

Exceptions detected before the reorganization. In this example,

� Three CRITICAL exceptions were detected

� Two of them can be removed by REORG (unload and reload)

� One sever exception was detected

Exceptions that still remain after the reorganization. In this case, one CRITICAL exception remains.

Result of the reorganization processing (success/failure)

1

2

3

4

1’

Feature-4b. Exception Reporting




Report Example – IMS Space Utilization Statistics


Data Set Statistics (DBD: BKDB , DSG: 01) --------------------------------------------------------------------------------

==================================== IMS Space Utilization Statistics

====================================

Note: The mark * in column P means that the data element is used in the policy.

Data Element Name P Before Reorg After Reorg Difference------------------------ - ---------------- ---------------- ------------------DB_BYTES_SEG 2,465,800,000 2,465,800,000 0DB_BYTES_FREE_SPACE 1,610,723,680 283,136,678 -1,327,587,002DB_BYTES_UNIDENTIFIED * 110 0 -110DB_PCT_BYTES_FREE_SPACE * 39% 10% -29DB_PCT_BYTES_SEG * 60% 89% +29DB_PCT_UNUSED_BYTES * 1% 1% 0DB_NUM_SEG 85,620,000 85,620,000 0DB_NUM_VLSEG 8,560,000 8,560,000 0DB_NUM_VLSEG_SPLIT * 0 0 0DB_PCT_NUM_VLSEG_SPLIT * 0% 0% 0DB_NUM_UNIDENTIFIED * 51 0 -51DB_AVG_NUM_UNIDENTIFIED * 0 0 0DB_NUM_FSE * 23,728,638 673,759 -23,054,879DB_AVG_NUM_FSE * 23.75 1.00 -22.75DB_NUM_FSE_MIN * 23,558,660 673,759 -22,884,901DB_NUM_FSE_MAX * 718,662 673,759 -44,903DB_AVG_NUM_NOREUSE_FSE * .17 0 -.17DB_NUM_PTR 85,070,408 84,946,241 -124,167DB_NUM_PTR_DIFF_BLK * 32,424,879 663,666 -31,761,213DB_PCT_NUM_PTR_DIFF_BLK * 38% 1% -37


Data Set Statistics (DBD: BKDB , DSG: 01) --------------------------------------------------------------------------------

==================================== IMS Space Utilization Statistics

====================================

Note: The mark * in column P means that the data element is used in the policy.

Data Element Name P Before Reorg After Reorg Difference------------------------ - ---------------- ---------------- ------------------DB_BYTES_SEG 2,465,800,000 2,465,800,000 0DB_BYTES_FREE_SPACE 1,610,723,680 283,136,678 -1,327,587,002DB_BYTES_UNIDENTIFIED * 110 0 -110DB_PCT_BYTES_FREE_SPACE * 39% 10% -29DB_PCT_BYTES_SEG * 60% 89% +29DB_PCT_UNUSED_BYTES * 1% 1% 0DB_NUM_SEG 85,620,000 85,620,000 0DB_NUM_VLSEG 8,560,000 8,560,000 0DB_NUM_VLSEG_SPLIT * 0 0 0DB_PCT_NUM_VLSEG_SPLIT * 0% 0% 0DB_NUM_UNIDENTIFIED * 51 0 -51DB_AVG_NUM_UNIDENTIFIED * 0 0 0DB_NUM_FSE * 23,728,638 673,759 -23,054,879DB_AVG_NUM_FSE * 23.75 1.00 -22.75DB_NUM_FSE_MIN * 23,558,660 673,759 -22,884,901DB_NUM_FSE_MAX * 718,662 673,759 -44,903DB_AVG_NUM_NOREUSE_FSE * .17 0 -.17DB_NUM_PTR 85,070,408 84,946,241 -124,167DB_NUM_PTR_DIFF_BLK * 32,424,879 663,666 -31,761,213DB_PCT_NUM_PTR_DIFF_BLK * 38% 1% -37

Free spaces fragmentation on each database block has been resolved by unload and reload of the database.

Segments of a database record fit in a single database block in almost all database records.

Allocated space is more efficiently used by segment data.

Feature-4b. Exception Reporting




IMS Configuration Manager




Introduction to IMS Configuration Manager

� IMS Configuration Manager consists of a resource manager and a parameter

manager

� The resource manager provides offline management of IMS resources with an online resource installer that leverages the capabilities of the IMS Operations

Manager (OM)

� The parameter manager provides a robust smart editor for IMS parameters,

syntax checking, and an edit history




Benefits

� Create and update IMS resources with more frequently and more

reliably while providing unparalleled

levels of availability

� Provide greater autonomy for

application developers

� Deskill the process of managing

resources and parameters

� Integrate DRD into existing change

management processes

� Automate install and backout with an

intelligent resource installer

� A complete audit history of all install activity performed through the product




IMS Configuration Manager resource installer

� The installer provides enhanced services on top of the IMS type-2 command

interface

� Autonomically determines whether an install or update is required

� Rollback option

� Full-logging and auditing

of install activity




Parameter management

� Enhanced parameter listing and search– Semantic search: finds parameters and members based on keywords;

identifies missing parameters and members

– Listing of PROCLIB members that are active on a given system

– Edit history for all members

� Enhanced ISPF edit session that provides:– Checking of parameter syntax

– Ability to insert parameters from a model

– Context sensitive help for all parameters

– Retains many ISPF edit functions

– Does not alter or modify the member in anyway (unless you explicitly add or

modify parameters)

– Allows you to back up members before saving them

– In the future will be extended to perform checking of entire PROCLIBs




IMS HP Image Copy




1. HASH pointer check support for Fast Recovery image copies

� HASH check is done for output image copy data sets, after FlashCopyor Snapshot is done

� Verifies that your image copy data set is correct

� Provides a quick and easy way for high reliable backup processing with the FlashCopy or Snapshot function

� In 4.1, HASH check is done only when you create the secondary image copy in the standard IC format. In 4.2, HASH check is doneeven when you have a primary Fast Recovery image copy only, or when you have a secondary copy in the Fast Recovery IC format




2. Checkpoint Restart enhancement for stacking image copies

� If one of the image copy processes fails, you can restart the failed image copy process and its subsequent image copy processes either: – On the same stacked tape, or– On the new stacked tape

� The unit of restart is a database (for full-function DB) or a partition (for HALDB). If an error occurs on one of the data set groups in a single database, the whole data set groups of it will be subject to the restart.

� You don’t have to re-run the job from the beginning of the databases to be stacked. You can save the time and resource




3. Conditional image copy registration for the Image Copy function

� You can use the NOTIFYMODE keyword to select the image copies that are to be registered to DBRC RECON

� With the NOTIFYMODE=COND parameter, – You can avoid registering image copies for which pointer error detected

at the end of the job step

– You can avoid the duplicated image copy registrations for the image copies which are subject to be processed twice by the restart function




4. New FASTIC= mode using FlashCopy to reduce unavailable time of databases

� You can shorten the unavailable time of the database when taking stacked

image copies, by using the new FASTIC mode that is enabled with the

FASTIC=(,FDUMP) keyword.

� The output image copy data set is created by following method:1. The temporary image copy data sets, also called as shadow image copy data sets,

are created by Snapshot or FlashCopy.2. After all temporary image copy data sets are created, actual image copy data sets are

created from the temporary data sets on a DASD volume or on a tape in the standard image copy format.

3. IMS HP Image Copy deletes the temporary image copy data sets.

� The advantage: – The unavailable time of the database is much shorter compared to the normal stacking

method. IMS HP Image Copy gets the database back to online when temporary image copy data sets are created.




5. Database quiesce support for IMS Version 11

� By using the TOIAUTO_Q keyword, you can take batch image copies of online

databases without taking the databases offline

� You don’t need to terminate online applications before the batch image copy

process begins

� IMS Version 11 or later required

� IMS Type 2 command needs to be available through the OM API




IMS Recovery Expert V2




Database and Storage Administration Trends and Directions

� Large IMS systems require high availability– Fast and non-intrusive backup facilities are required– Fast recovery capabilities required to minimize down time and promote high availability– Most backup, recovery solutions do not leverage storage-based fast-replication facilities

� Storage-based fast-replication facilities are under-utilized– Tend to be used by storage organizations– Tend not to be used by database administrators (DBAs)

� Storage aware database products allow DBAs to use fast-replication in a safe and transparent manner

– Provides fast and non-intrusive backup and cloning operations– Simplifies recovery operations and reduces recovery time– Simplifies disaster recovery procedures




IMS System Level Backup

� A System Level Backup is a backup of the

entire IMS environment at a point in time

� Leverages storage-based fast replication to

drive the volume backup – Backup in seconds– Significantly reduce costs:

• Offload copy to storage processor• Saves CPU and I/O resources

• Faster than data set copies

� Data consistency ensures data is dependent

write consistent– IMS Suspend – Storage-based consistency functions– Equivalent to a power failure

IMS

Source IMS Volumes

Storage Processor APIs

TargetVolumes IMS

System Backup

IMS RE

39




IMS System Level Backup

� Can be used in combination with other backups (image copies)

� Can include more than just databases

� Automated backup offload (archive/recall)– Copies system backup from fast replication disk to

tape for use at either local or disaster site (or both)

� Backup IMS without affecting applications– Backup windows reduced or

eliminated– Extends processing windows

� DB2 BACKUP SYSTEM– Proven concept– Available for years

Tape Processing

Storage Processor APIs

Storage-AwareBackup and

Recovery

IMS

Offload

Restore

SLB

System Backup

SourceDatabaseVolumes

40




IMS Intelligent Recovery Manager

� Ability to perform efficient local recoveries using available recovery resources and tools

– Provides centralization

� Leverages existing IMS backup and recovery tools– IMS Recovery Solutions Pack

� The complete suite of IMS backup and recovery utilities look like a single product from the end-users perspective.

– Sophisticated ISPF interface– Centralizes backups - provide a single point of control for all backup and recovery processes– Only one product is needed for all recovery processes (local recovery, disaster recovery, rebuilding

damaged index, applications, etc.)

� Simplifies and Automates Recovery Processes– Recovery JCL built once (in advance)– Run-time analysis to determine recovery resources available

• Combination of SLB and other IMS recovery assets• Can be directed to use IMS recovery assets only

– Run-time analysis of what recovery utility to invoke– Spawns jobs to perform recovery tasks– Takes the technical knowledge out of having to create complex recovery JCL




IMS Intelligent Disaster Recovery Manager

� Performs local site procedures to prepare for offsite disaster recovery or disaster restart in advance

– Identify image copies, change accumulations, and archive logs and what copy for transport to DR site• Tape pick list

– Copy of RECON is created and conditioned with any logs, change accums and image copies being sent to DR site

• Removes the requirement to modify the RECON at the DR site• If logs and change accums aren’t required, they are marked in error in the conditioned recon so they won't be

pulled in– IMS RE repository backed up and sent offsite– Recovery JCL is created, backed up, and sent offsite

� Performs intelligent remote site restore operations for disaster recovery or disaster restart procedures

� Restore IMS RE DR PDS– Run JCL to restore IMS Recovery Expert Repository– Run JCL to restore image copies if disaster recovery– Run JCL to restore system level backup if disaster restart– IMS emergency restart

� Reduces recovery time objectives by transforming disaster recovery into a disaster restart process




Functions and Features

� ISPF Interface used to:– Register an IMS environment

– Analyze IMS data set layout for SLB usage

– Setup SLB backup profiles• Copy blades - supports IBM, EMC, and HDS storage systems and fast-replication facilities using

integrated copy blades• Offload SLBs

– Setup application profiles to allows users to recover IMS databases or groups of related

databases that represent applications from a system backup or image copies• IMS Recovery Expert can invoke additional recovery utilities after restoring the databases to bring

them to a more current point-in-time

– Setup disaster recovery profile• See later slide

– System restore• Displays all the system backups that have been performed

– Build JCL to perform backup, offload, application recovery, DR preparation, or system

recovery





� Backup Validation– Provides extensive backup validation to ensure that the backup contains all IMS files and

catalog structures required for a successful recovery

� Metadata Repository– Backups recorded in a meta-data repository

� Tape Offload Support– DFSMSdss or FDR

– Compression and encryption support

� Tape-Based Disaster Restart– IMS Recovery Expert provides disaster recovery support by transforming traditional IMS

disaster recovery procedures into a tape-based disaster restart methodology





� Automation and Management of Disaster Recovery– Disaster Recovery Profile indicates what recovery assets will be sent to recovery site

• System Backups

• Archive Logs

• Change Accumulation Files

• Image Copies

– Intelligent Disaster Recovery Manager runs at some set interval at local site• Analyzes, prepares, and identifies new assets to be sent to recovery site

• Copies the RECON and conditions with the recovery assets to be used at the remote site

• Creates a DR PDS that contains:

Backup of conditioned RECON

Backup of IMS RE Repository

JCL that will be executed at the DR site to restore the SLB and recover the system

• Produces a detailed report showing all tapes that need to be transported to the DR site.

• The user simply has to submit the predefined jobs that were created at the local site to perform the

actual recovery of the IMS system.

– Using IMS Recovery Expert to automate and manage traditional disaster recovery processes simplifies disaster recovery procedures and makes the recovery process less error-prone




IMS System Analysis and Configuration

� Discovers and analyzes the IMS subsystem and displays an interactive report

showing DASD volume usage

� Provides colored alerts and warnings when detecting anything preventing a

successful system backup

� Helps segregate IMS log and database data to support a system backup methodology

� Identifies ICF catalog placement requirements




IMS System Analysis and ConfigurationVerify Data Set Placement




IMS System Analysis and Configuration (2)




Create a System Backup Profile




IMS Recovery ExpertBackup Validation Processes

�Ensures backups are usable for a restore process–All IMS subsystem volumes are included in the backup

–All IMS log volumes are included in a FULL system backup

–User catalogs used by the IMS subsystem, including the log data sets, are included in backup

–IMS logs and database data are on separate volumes • FULL restore only if log structures and data are not separated

–All source volumes are valid, online, and available–All target volumes are valid, offline, and available

–Target backup volumes not in use by other backup profiles

–All source and target volumes are the same device type




Offloading a System Level Backup

� Options defined in the System Backup

Profile

� Multiple Copies Can be Created

� Up to 99 generations can be managed

� Data can be compressed

� Data can be encrypted




System Backup Reports

� System Backup

information maintained

in Repository

� Can Build JCL to restore

entire system

� Can view information

about objects in the system backup




Full System Restore

� Local or remote site– Most likely full system restore only used at remote site

� Ability to recover to point-in-time besides SLB time– Drives recovery utilities – roll forward recovery

� Other/IMS system data sets can be restored– OLDS, WADS, RDS, etc.– ACBLIBs, DBDLIBs, etc.– User specified data sets

� IMS is emergency restartable after a full system restore and no recovery– ‘Disaster Restart’




Application Recovery

� Related databases can be grouped – “Application”– Masking, wildcarding, DBRC groups

� All databases and indexes in the group are recovered to same point in time

� Recovery utilities and options are defined– Usually defaults are set during product configuration

� Run-time recovery analysis– What recovery assets are available– What recovery utilities to invoke– JCL used to perform recovery does not change




IMS Recovery Expert Controlled Recovery Execution

IMS

Databases

RECON

IMS RE

Repository

IMS System

Backup

IMS Recovery Expert

Change

Accumulation

Utility

(HPCA)

Database

Recovery

Facility

(DRF)

Index

Rebuilder

(IIB)

HALDB

ILDS/Index

Rebuild

(DFSPREC0)

Post

Recovery

Image Copy

Utility

(HPIC/HPPC)

Data Set

Restore/

DBRC

Notifications

Fast-replicationData Set Restore

IMS RE Invoked Recovery Processes

IBM

Fla

shcop

y

EM

C S

NA

P

IBM

DfS

MS

dss




Disaster Recovery

� System Level Backup maybe used for ‘Disaster Restart’– Recover to Objective is SLB time– No other recovery assets shipped to remote site

� Disaster Recovery Management for other recovery assets– Archive Logs

• Copy 1, Copy 2, or create a copy

– Change Accums• Not used, used, create a copy

– Image Copies• IC1, IC2, or create a copy




DR Preparation Utility

� Scheduled on a periodic basis at local site– After an SLB is created

– After log is archived

– Time basis

� Identifies and or creates new recovery assets– Tape pick list

� Creates a conditioned RECON

� Creates a PDS to be shipped to remote site– JCL to restore SLB

– JCL to copy remote site recovery assets to disk– JCL to recover all databases if ‘other’ recovery assets are used

– Copy of conditioned RECON if ‘other’ recovery assets are used

– Copy of IMS Recovery Expert Repository




Disaster Recovery Profile




Remote Site Recovery Assets




IMS Recovery Expert V2Summary of Benefits

� Simplifies and automates an IMS SLB methodology– Leverages storage-based fast-replication– Fast, non-intrusive, and reduces CPU, I/O and storage utilization

� IMS SLBs can be used for IMS system, application, or database recovery– Parallel recovery reduces system and database recovery time

� Database recovery can leverage existing products

� IMS SLBs simplify disaster recovery procedures– Transforms IMS DR procedures into a disaster restart process

� Less skills required to implement advanced IMS backup, recover, and disaster

recovery solutions




IMS Tools Product Portfolio

HALDB ToolkitSequential Randomizer Generator

Online Reorganization FacilityIMS Cloning ToolIMS Database Control Suite

IMS HP Image CopyDEDB Fast RecoveryIMS Recovery Expert V2

Batch Terminal SimulatorBatch Backout ManagerProgram Restart Facility

Data Base Administration

Utility Management

Backup and Recovery

Application Management

Performance Management

Command Control FacilityETO SupportHP Sysgen ToolsQueue Control FacilityIMS Workload Router

TransactionManagement

System Administration

RegulatoryCompliance

Buffer Pool AnalyzerNetwork Compression Facility

IMS Configuration ManagerIMS Sysplex Manager

IMS Audit Management ExpertIBM Data Encryption for IMS and DB2 Databases

IMS Tools Base for z/OS

IMS Tools Generic ExitsTOSIPolicy ServicesIMS Tools Knowledge BaseIMS HD Compression Ext

IMS Fast Path Solution Pack for z/OS

IMS HP Fast Path UtilitiesIMS DB Repair FacilityIMS HP Image CopyIMS Library Integrity Utilities

IMS Database Solution Pack for z/OS

DB Reorganization Expert- Unload, Load, Index Build, Prefix Resolution/UpdateHP Image CopyHP Pointer CheckerLibrary Integrity Utilities

IMS Performance Solution Pack for z/OS

IMS Connect ExtensionsIMS Performance AnalyzerIMS Problem Investigator

IMS Recovery Solution Pack for z/OS

Image CopyRecoveryChange AccumulationRecovery Health Check




Q & A




Summary

� IMS Tools from IBM provide, integrated, easy-to-use solutions that fit your company’s needs

� IBM is dedicated to the continued success and support of IMS and the mainframe. We’re invested for the long term, right beside you.

� We are continuing to invest in our IMS Tools technology and have a vision for our IMS Tools that centers around autonomic computing

Date post:	18-Nov-2014
Category:	Documents
Upload:	ibm-ims
View:	882 times
Download:	3 times

Bra what's new in ims tools 2010

Documents