dynamic change management in ims ims rug jan 2014 e-meeting east

© 2014 IBM Corporation

Dynamic Change Management in IMS,

Simplified to Deliver Higher Availability

Anu Vakkalagadda, Senior Software EngineerIMS Development, IBM

IBM User group e-MeetingJanuary 23, 2014

© 2014 IBM Corporation2

Please note

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.


Acknowledgements and Disclaimers

Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates.

The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. 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. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. 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 the applicable license agreement governing the use of IBM software.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

© Copyright IBM Corporation 2014. All rights reserved.

•U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM, the IBM logo, ibm.com, IMS 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.


Agenda

� Dynamic Resource Definition (DRD) review

� DRD with IMSRSC repository (IMSplex)–Basic components of a DRD with Repository environment–Simplified setup of DRD with Repository components– Making resource definition changes using IMSRSC

repository–Benefits for DRD with IMSRSC repository in an IMSplex–Security setup in IMSRSC repository–Best practices for migration and usage


Dynamic Resource Definition

(DRD) Review


Modifying MODBLKS Resources without DRD

//MODBLKSx

Control BlocksDDIRsPDIRsSMBsRCTEs

During IMS restart processing, resource definitions are loaded from the active MODBLKS library (cold start) or from the IMS log (warm/emergency restart).

COLD START

OLC

SYSGEN Process

IMS Control RegionIMS Control Region

After restart, these can only be added, changed, or deleted through the ONLINE CHANGE process or another RESTART (some definitions can be updated by command).

OLDS

WARM START

EMERGENCY RESTART

(runtime resource definitions)

(stored resource definitions)

RESTART

OLC


DRD with RDDS

System RDDS


IMS CONTROL REGIONIMS CONTROL REGION

During IMS cold start processing, resource definitions may be IMPORTed from a Resource Definition Data Set.

IMPORT

CREATEUPDATEDELETEQUERY

OLDS

WARM START

EMERGENCY RESTART

EXPORT



Definitions can be dynamically created, updated, or deleted using new or enhanced type-2 commands.

Definitions can be EXPORTed

to a Resource Definition Data Set.


DRD Objective

• Improve the availability of the IMS online environment. • Allow user to dynamically define (create, update) and enable MODBLKS resource definitions ( Databases , Programs ,

Transactions , Routing Codes)

• Store definitions so they are available for IMS coldstart • Benefits

• No requirement for MODBLKS SYSGEN, IMS restart or MODBLKS online change (OLC) • Changes imported when an IMS is down are made available to the IMS during warm or emergency restart (new for IMS V13)•Increased resource availability• Runtime changes made using type-2 commands in IMS

•Resources quiesced as needed


DRD with IMSRSC repository (IMSplex)


IMS Repository Function Overview

� The IMS Repository support provides a centralized store for resource definitions for all IMS systems in the IMSplex.

� Managing DRD definitions is the initial implementation of the IMS repository function

–replaces RDDSs at each IMS–DRD definitions are stored in the IMSRSC repository

� Provides full support for populating, managing, storing, sharing, and retrieving a consistent set of DRD stored resource definitions for multiple-IMS systems in the IMSplex or for a single-IMS system.

� Manual coordination of multiple RDDSs in a multiple-IMS IMSplex eliminated, replaced by basic functioning of the IMS repository

� Improvements in IMSplex systems and resource management with the IMSRSC repository

� A strategic direction for IMS architecture


PRIMARY

Modifying Resources using DRD with IMSRSC repository

IMSRSC Repository


IMS CONTROL REGIONIMS CONTROL REGION

Runtime definitions can be dynamicallycreated, updated or deleted usingtype-2 commands.

IMPORT

CREATEUPDATEDELETEIMPORTEXPORTQUERY

OLDS

WARM START

EMERGENCY RESTART

EXPORT



Runtime definitions can be EXPORTed

to the IMSRSC repository

During IMS cold start processing, resource definitions may be IMPORTed from the IMSRSC repository.

IMPORT

IMS change list


DRD with IMSRSC Repository Environment

� Use of DRD with the repository function requires IMS at Version 12 or higher with:–Repository Server (RS) address space

• Repository data sets defined– IMSRSC repository data sets to maintain the stored resource

definitions– IMSRSC Repository catalog data sets to maintain information about

IMSRSC repository–Common Service Layer (CSL) IMSplex configuration consisting of

• Operations Manager (OM)• Resource Manager (RM)

–All RMs must be V12 or higher if IMSRSC repository is enabled

–RM resource structure is optional

–CQS address space is required if resource structure defined• Structured Call Interface (SCI)

–TSO SPOC or equivalent for entering type-2 commands


DRD Environment…

� Proclib members in IMS, RM and RS need to be defined as follows– IMS PROCLIB members with DRD/repository enablement

parameters• DFSDFxxx

–RM PROCLIB member with repository enablement parameters• CSLRIxxx

–RS Proclib member with Repository Server parameters• FRPCNFG

� All IMS online environments supported, including data sharing and shared queues


Accessing the Repository

� All access to the IMSRSC repository which contains the DRD stored resource definitions is handled by the Repository Server (RS) address space.

� RM provides services to manage the resource definitions in the IMSRSC repository and interacts with RS to access the IMSRSC repository–Used by online IMS type-2 commands–By batch RM utilities

• RDDS to Repository (CSLURP10)• Repository to RDDS (CSLURP20)

� Direct Repository Access is for Repository Administration (RM not used)–Batch ADMIN utility (FRPBATCH)–Repository server commands using the z/OS modify interface


IMS Repository Function Architecture

Operations

Manager

(OM)

IMS

Control

Region

Repository

Server

(RS)

SCI

SCI

SCI

XCF

X

C

F

X

C

F

RS Catalog Repository

Primary/Secondary

IMSRSC Repository

Primary/Secondary/Spare

Batch ADMIN

Utility

(FRPBATCH)

RM utilities

CSLURP10 /

CSLURP20

RS

Aud

it Lo

g

X

C

F

Structured

Call Interface

SCI

Resource

Manager

(RM)

SCI

IMS

Control

Region

SCI

IMS

Control

Region

SCI


Enabling DRD with repository

� Define CSL parameters in DFSDFxxx – Enable CSL by defining

<SECTION=COMMON_SERVICE_LAYER>– DFSCGxxx also valid but not preferred

� Enable IMS for DRD and repository by defining parameters in DFSDFxxx

– Set MODBLKS=DYN in <SECTION=DYNAMIC_RESOURCES>– Define <SECTION=REPOSITORY>

� Enable RM for IMSRSC repository by defining parameters in CSLRIxxx– Define <SECTION=REPOSITORY>

� Set up Repository Server by defining parameters in FRPCNFG – Create catalog repository data sets– Create IMSRSC repository data sets


Enabling DRD with repository …

� Start Repository Server(s)– Define the IMSRSC repository to RS and start it

� Start SCI, OM, CQS (optional) and RM with repository enabled.

� Populate IMSRSC repository from RDDS, MODBLKS or IMS log using CSLURP10 utility (optional)

� Cold start IMS if needed (Required to switch to DRD)– If IMSRSC repository not previously populated with resource definitions

using CSLURP10 utility, export resource definitions to IMSRSC repository using EXPORT command.

� Use type-2 commands to create, update, delete, import and export and query resource definitions

– Harden changes in the IMSRSC repository using EXPORT DEFN or DELETE DEFN commands to ensure changes are available for next coldstart.

– No autoexport to IMSRSC repository


� Allows all resource and descriptor definitions to be read in automatically during IMS cold start

� Definitions are used to create the internal runtime control blocks needed to manage resources

� During cold start, resource definitions can be imported from–IMSRSC repository–System RDDS–MODBLKS data set–Or not imported at all..

� Specified by the AUTOIMPORT= parameter

Automatic Import


Dynamic Resource Definition

Usage


Commands Used in Dynamic Resource Definition

Export the runtime resource or descriptor

definitions to the stored definitions (IMSRSC

repository or RDDS)

EXPEXPORT

Import resource or descriptor definitions from

the stored definitions (IMSRSC repository or

RDDS) into the runtime definitions

IMPIMPORT

Delete resource or descriptor (either runtime or stored

definition)

DELDELETE

QRY

UPD

CRE

Short

Form

Update runtime attributes of resource or

descriptor

Update status of resource

UPDATE

Create runtime resource or descriptor in IMS CREATE

Query stored and runtime attributes of resource

or descriptor

Query status of resource

QUERY

PurposeCommand


RCTE

SMB

PDIR

DDIR

IMS Control

Block

RTC

TRAN

PGM

DB

Resource

Keyword

TRANDESCTRANSACTTransaction

RTCDESCRTCODERouting Code

PGMDESCAPPLCTNProgram/PSB

DBDESCDATABASEDatabase

Descriptor

Keyword

SYSGEN

Macro

Resource

Type

� Examples– CREATE PGM…

– DELETE TRANDESC…

– UPDATE TRAN…

Reference Table for Resources & Keywords


� EXPORT command writes the IMS systems runtime resource/descriptor

definitions to the IMSRSC repository

– The stored resource definitions in the IMSRSC repository will be used at

the next IMS coldstart or during the IMPORT command

� Can be used to populate an empty repository for the first time after initially

migrating to DRD with repository

� Resource definitions of the specified name can be written by specifying

NAME keyword

� Resource definitions that have been modified since last EXPORT can be written using OPTION(CHANGESONLY)

� Resource definitions modified in a time range can be exported by specifying

STARTTIME() ENDTIME()

EXPORT to IMSRSC repository

EXPORT DEFN TARGET(REPO) TYPE() NAME()

STARTTIME() ENDTIME() SET(IMSID()) OPTION()


� IMPORT command reads resource/descriptor stored resource definitions from the IMSRSC repository into the IMS system, where they become runtime resource definitions

� Can be used to percolate definitional changes made to the offline repository to the active IMS systems, for example:

–Coldstart an IMS with no resources defined, issue IMPORT to read in its definitions

–Make changes to IMSRSC repository then roll them out to runningIMS systems

IMPORT from IMSRSC repository

IMPORT DEFN SOURCE()

TYPE() NAME() OPTION() SCOPE()


� SCOPE() keyword on IMPORT indicates which IMS systems the IMPORT will

apply to.

– SCOPE(ALL) will apply the IMPORT command to all IMS systems in the IMSplex for which the resource is defined. This is recommended (default).

• If an IMS is down, an IMS change list is created for it in the IMSRSC

repository by the command master IMS

– IMS change list contains the resource names it would have imported had it been up

• IMS change list will be read during warm/emergency restart and the

resource definitions of the resources imported when the IMS was down will be applied at the end of warm/emergency restart. This will synchronize the

IMS that was down when the IMPORT was issued with the other IMS

systems in the IMSplex

– SCOPE(ACTIVE) will apply the IMPORT command to all of the active IMS

systems in the IMSplex

• IMS systems that are down will not have an IMS change list created and

will not be synchronized with the other systems

– Manual IMPORT or other commands must be issued after IMS restart.

IMPORT Command – IMS V13 Changes


QUERY resource definitions

� QUERY commands can be used to query the runtime (IMS local) and stored (IMSRSC repository) resource definitions.

� The SHOW keyword controls the scope of definition to display.–SHOW(DEFN) returns both the stored and runtime IMS resource

definitions –SHOW(DEFN,GLOBAL) returns only the stored IMS resource

definitions –SHOW(DEFN,LOCAL) returns only the runtime IMS resource

definitions –SHOW(IMSID) returns all IMSIDs that have the specified resource

defined–SHOW(DEFN,IMSID) returns the stored resource definitions + the

stored definition for each IMS + the runtime IMS resource definitions

QUERY rsc-type | desc-type NAME() SHOW()


DELETE from IMSRSC repository

� Deletes stored resource definitions from the repository, and is processed by one command master IMS

� Use this command to harden delete of runtime resource definitions in the IMSRSC repository

–Recommendation is to delete the runtime resource definitions first in IMS using DELETE commands (like DELETE PGM etc) and then use the DELETE DEFN command to delete from the IMSRSC repository

–If resource definition is not deleted from the IMSRSC repository it can be made available at IMS at next coldstart

� DELETE DEFN TYPE(CHGLIST) to delete any residual change list that could not be deleted by IMS during normal processing

DELETE DEFN TARGET(REPO) TYPE()

NAME() FOR(IMSID()) OPTION()


Repository Server Batch ADMIN Utility (FRPBATCH)

� Used for Batch repository administration

� Invoked using FRPBATCH utility

Rename an existing user repository in the RS catalog repositoryRENAME

Update user repository definition in the RS catalog repositoryUPDATE

Request the Repository Server to stop a user repositorySTOP

Request the Repository Server to start a user repositorySTART

Add a user repository to the Repository Server catalogADD

List status information for all user repositories or detailed

information for a single user repository

LIST

Change data set dispositionDSCHANGE

Remove a user repository from the RS catalog repositoryDELETE

FunctionCommand


Repository Server Commands

� Used for online repository and RS administration

� Commands issued using z/OS Modify interface

Administrative functions – change repository data set disposition, display repository data set attributes, start/stop

repositories

ADMIN

Stop/shutdown specific repository serverSTOP

Shutdown one or more repository server address spacesSHUTDOWN

Refresh RACF profile definitionsSECURITY

Dynamically change audit level originally specified in FRPCFG member

AUDIT

FunctionCommand


Batch ADMIN and z/OS Modify Interface Commands

AUDIT (change audit level)

SECURITY (refresh in-storage profiles)

SHUTDOWN

UPDATE

ADMIN DSCHANGEDSCHANGE

DELETE

RENAME

ADD

STOP (stops Repository Server)

ADMIN STOP (repository, not Repository Server)STOP

ADMIN STARTSTART

ADMIN DISPLAYLIST

Repository Server z/OS Modify InterfaceBatch ADMIN


Example Use Case Scenarios


Creating/Updating Resources in a Cloned Environment

� Scenario: 3-way IMSplex with cloned systems IMSA, IMSB and IMSC is defined to the IMSRSC repository.

–IMSA and IMSB are active and IMSC is inactive. –Program named PGMCAR and Transaction named TRANCAR need

to be created in the IMSplex. –To create the runtime resources at test system IMSA, issue the

following commands:• CREATE PGM NAME(PGMCAR) routed to IMSA • CREATE TRAN NAME(TRANCAR) SET(PGM(PGMCAR)) routed

to IMSA


Creating/Updating Resources in a Cloned Environment ..

–To write the resource definitions to the repository for all IMS systems, issue:

• EXPORT DEFN TARGET(REPO) OPTION(CHANGESONLY) SET(IMSID(*))

– Newly created program PGMCAR and transaction TRANCAR are added to the IMS resource lists for IMSA, IMSB and IMSC and the resource definitions for PGMCAR and TRANCAR are written to the IMSRSC repository

–To activate the resource definitions in the IMSplex, issue:• IMPORT DEFN SOURCE(REPO) NAME(PGMCAR,TRANCAR)

SCOPE(ALL) OPTION(UPDATE)

–Updates PGMCAR and TRANCAR in IMSA

–Creates PGMCAR and TRANCAR in IMSB

–How about IMSC?


� How will IMSC apply all of these changes?–If IMSC is IMS V12:

• After IMSC is restarted, user needs to take one of the followingaction:

– Issue IMPORT DEFN SOURCE(REPO) NAME(PGMCAR,TRANCAR) routing to IMSC

– Issue CREATE commands at IMSC for PGMCAR and TRANCAR

–If IMSC is IMS V13, • An IMS change list is created in the IMSRSC repository by the

command master IMS during IMPORT command processing for IMSC with names PGMCAR and TRANCAR.

• IMSC at the end of restart (warm or emergency) reads the change list and the resource names PGMCAR and TRANCAR are automatically imported from the repository.

Creating/Updating Resources in a Cloned Environment …


Updating Resources in a Non-Cloned Environment

� Scenario: 2-way IMSplex with non-cloned systems IMSX and IMSY is defined to the IMSRSC repository.

–IMSX and IMSY are active

� Route commands to individual IMS systems, for example:–Route the following commands to IMSX only

• UPDATE PGM NAME(PGMAAA) SET(TRANSTAT(Y))• EXPORT DEFN TARGET(REPO) TYPE(PGM) NAME(PGMAAA)

–Route the following commands to IMSY only• DELETE PGM NAME(PGMDDD)• DELETE DEFN TARGET(REPO) TYPE(PGM) NAME(PGMDDD)

FOR(IMSID(IMSY))


Generating an IMSRSC Repository from MODBLKS

� Several DRD utilities are available to assist with migration, fallback and recoverability

� To populate an IMSRSC repository with all resource definitions in MODBLKS1. Create a temporary resource definition data set (RDDS) 2. Populate this RDDS with MODBLKS definitions using one of the

following

– Create RDDS from MODBLKS utility (DFSURCM0)

– Create RDDS from Log Records utility (DFSURCL0)

– Issue an EXPORT with TYPE(ALL) and NAME(*) command to populate a non-system RDDS

3. Use this populated RDDS as input to RDDS to Repository utility (CSLURP10)


Copying Repositories

� To copy the contents of one repository to another in a cloned environment:– Capture all stored resource definitions in the initial repository by running

CSLURP20 “Repository to RDDS” utility against it, specifying any one IMSID in the JCL, and using a non-system RDDS as output

– Transfer these stored definitions to a different repository by running CSLURP10“RDDS to Repository” utility specifying all IMSIDs in the JCL, using the non-system RDDS as input, and the new repository as output

Repository

2Repository

1

Non-System

RDDS

CSLURP20 with

IMSID(IMS1)

CSLURP10 with

IMSID(IMS1, IMS2, IMS3)

IMS1 IMS2 IMS3


IMS1

IMS2

IMS3

Repository

1

CSLURP20 with

IMSID(IMS1)

CSLURP20 with

IMSID(IMS2)

CSLURP10 with

IMSID(IMS1) only

Non-System

RDDS1

Non-System

RDDS2

Non-System

RDDS3

CSLURP10 with

IMSID(IMS2) only

Repository

2

CSLURP20 with

IMSID(IMS3)

CSLURP10 with

IMSID(IMS3)

only

Copying Repositories …

� To copy the contents of one repository to another in a non-cloned environment:

–Capture all stored resource definitions in the initial repository by running CSLURP20 “Repository to RDDS” utility against it for each IMS, each time using a different non-system RDDS as output

–Transfer these stored definitions to a different repository by running CSLURP10 “RDDS to Repository” utility once for each IMS, using the non-system RDDS as input and the new repository as output


Repository Security Considerations


� Access to a user repository can be gained through RM by either of the following types of RM callers– Authorized RM caller

• IMS online commands– Non-authorized RM callers

• RM Batch utilities (CSLURP10, CSLURP20)

� Access to a Repository Server can be gained directly by either of the following

– Batch ADMIN utility

– z/OS modify interface

Repository Access


� Connection security– Used by both authorized and non-authorized RM callers when they

attempt to connect to the repository– RM specifies its USERID on its startup JCL, to be used in RACF

authorization • If RM is authorized to access the repository, so is IMS since it is

an authorized RM caller– RM Utilities specify their USERIDs in JCL, to be used for SCI

registration and for RACF authorization

� Member-level security– Only used with non-authorized RM callers that access individual

members within the repository • CSLURP10• CSLURP20

Types of Repository Security


Repository Security Implementation

� Repository Server resources can be restricted from unauthorized access, including:– User repository– RS catalog repository– Resource Names or Members within a user repository

� You can choose a RACF class to protect RS resources in– RACF FACILITY class– User-defined class (recommended if using member-level security

due to 39-character profile name length restriction of FACILITY class)

• Add new class to RACF Class Descriptor Table (ICHRRCDE)• Update RACF Router Table (ICHRFR01) with new class

� Protect resources by defining general resource profiles

� Grant access to users using defined resource profiles


Protecting Repository Server Resources

� Define profiles to restrict access to Repository Server resources to authorized users

� User repository– Format for defining resource profile

• FRPREP.repositoryname

– Example• RDEFINE XFACILIT FRPREP.IMSRSC_REPOSITORY1

UACC(NONE)

• RDEFINE XFACILIT FRPREP.* UACC(NONE)

� RS catalog repository– Format for defining resource profile

• FRPREP.CATALOG

– Example• RDEFINE XFACILIT FRPREP.CATALOG UACC(NONE)


� Members within a repository (for non-authorized RM callers only)

� FRPMEM.repositoryname.DFS.RSC.membername

Protecting Repository Server Resources…

plexname rsctype rscname+ +

plexname 8-byte CSL plexname where repository is defined (MUST start with

characters “CSL”)

8-byte resource type: DB,DBDESC,PGM,PGMDESC,

TRAN,TRANDESC,RTC,RTCDESC

rsctype

rscname 8-byte resource name to be secured

Example: RDEFINE XFACILIT

FRPMEM.REPO1.DFS.RSC.CSLPLEX1.TRAN.PART UACC(NONE)


Best Practices


Best Practices for IMS Repository and Migration

� Listed are some best practices to take into consideration for IMS Repository Usage and Migration

–Populate IMSRSC repository from the IMS MODBLKS, Sysgen macros or IMS log using CSLURP10 utility

–Enable IMS and RM with IMSRSC repository at start-up or type-2 commands. IMSs can be updated to IMSRSC repository on a rolling basis

–Use EXPORT DEFN TARGET(REPO) OPTION(CHANGESONLY) command periodically or after changes are made to ensure changesare hardened to the IMS repository

• in a cloned environment use SET(IMSID(*))

• in a non-cloned environment route the command to each IMS without

SET(IMSID()) specified, will default to the IMSid of the IMS processing the command


Best Practices for IMS Repository and Migration

–Formulate resource naming conventions –Use QUERY SHOW(DEFN,IMSID) commands to display stored and

runtime resource definitions to ensure definitions are in-sync between IMS systems and the IMSRSC repository

–Plan and practice what to do if the repository data sets are corrupted• May need to scratch and re-allocate the IMSRSC repository DSN

• May need to populate the IMSRSC repository from the active IMSs using EXPORT commands or using the CSLURP10 utility

• May be able to restore from back-ups

–Enable OM Audit Trail to track IMSplex activity, including command input and command responses.


Summary


Value of the IMS 12 repository for DRD

� Full support for populating, managing, storing, sharing, and retrieving a consistent set of DRD stored resource definitions for multiple-IMS IMSplexes and single-IMS IMSplexes in a single place

� Provides improved availability–Repository can be enabled/disabled without an IMS outage via

command–Duplexing of data plus spare capability improves data availability

� Provides single source consistency for DRD stored resource definitions –No need for multiple sets of RDDSs in a multiple-IMS IMSplex –No need for coordinating multiple sets of RDDSs in a multiple-IMS

IMSplex–Repository architecture controls consistency and integrity of data


Value of the IMS 12 Repository for DRD

� Provides improved functionality and flexibility for managing resources across an IMSplex

–EXPORT process controlled by user (no AUTOEXPORT)–DELETE of stored resource definitions controlled by user–Can UPDATE an existing runtime definition via IMPORT –DFSINSX0 created resource definitions can be exported to the IMSRSC

repository–QUERY commands to display both runtime and stored resource

definitions



� Provides support for both test and production environments–Repository Server can include data from different IMSplexes though

one per IMSplex recommended–Multiple IMSRSC repositories can exist within one Repository Server

though one per Repository Server recommended–Migration and fallback utilities available based on RDDSs –IVP available to assist with installation of repository–Supported by TSO SPOC Manage Resources application



� Provides security capabilities for auditing and compliance

� Full support for RACF (SAF) interfaces–Repository audit log (optional)–OM type-2 commands optionally found in OM Audit Trail

� Provides comprehensive set of repository administration tools–Includes batch utilities and command interfaces for repository

management • Can be performed when IMS is down

� A strategic IMS architectural direction–Based upon BPE, CSL, IMSplex architecture


Questions?


Become part of IMS’s Social Community

53

dynamic change management in ims ims rug jan 2014 e-meeting east

Technology

ibm products

ibm logo

copyright ibm corporation

use of ibm software

ibm trademarked terms

standard ibm benchmarks

current list of ibm

ibm user group emeeting