Ims repository user groupkb

IMS Version 14 IMS 14

IMS Repository

Kenny Blackman –zGrowth IMS Washington Systems Center

[email protected]

© 2012 IBM Corporation2 IBM Confidential

Dynamic Resource Definition review

Supports MODBLKS resources which are represented by control blocks that define resources and their attributes in a running IMS system

Control block is generated for a MODBLKS resource when its respective SYSGEN macro is run

RESOURCE TYPE SYSGEN MACRO CONTROL BLOCK

Database DATABASE(DB/TM, DBCTL) DDIR(Database Directory)

Application Program APPLCTN(DB/TM, DBCTL, DCCTL) PDIR(Program Directory)

Transaction TRANSACT(DB/TM, DCCTL) SMB(Scheduler Msg Block)

Routing Code RTCODE(DB/TM, DCCTL) RTCE(Routing Code Table Entry)

© 2012 IBM Corporation3 IBM Confidential

DRD with RDDS review

System RDDS

Control Blocks DDIRs PDIRs SMBs RCTEs

IMS 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

(runtime resource definitions)

(stored resource definitions)

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.


RepositorySpare

RepositorySecondary

Types of IMS Technical Metadata and Storage Method DB

– PSB/DBD resources• Database structure definitions• Physical database definitions• Segment definitions• Field definitions

– Application• Data types• Application defined fields• Encodings• Redefines• User defined types• Structures

TM– MODBLKS resources

• Program definitions• Transaction definitions• Database definitions• Routing Code definitions

– MFS FORMAT resources– Application

• Input/output message definitions

IMS HALDBDatabase

VSAM

4

RepositoryPrimary

BSAMSystem RDDS

IMS Catalog


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

• Eliminates manual coordination of multiple System RDDSs in a multiple-IMS IMSplex

• Improves IMSplex systems and resource management with the IMSRSC repository

• A strategic direction for IMS architecture


IMS Repository Function Architecture

OperationsManager

(OM)

IMSControlRegion

RepositoryServer(RS)

SCI

SCI

SCI

XCF

XCF

XCF

RS Catalog Repository

Primary/Secondary

IMSRSC Repository

Primary/Secondary

Batch ADMIN Utility

(FRPBATCH)

Repository Server

z/OS Modify Commands

CSLURP10 / CSLURP20

Audit Log

XCF

Structured Call Interface

SCI

ResourceManager

(RM)

SCI

z/OS modify interface


IMS Repository Function Components

Repository Server (RS)– BPE-based address space– Managed by the RM CSL address space

Repositories–Catalog repository (not to be confused with the IMS Catalog)

–used to maintain the definitions for the repositories– IMSRSC repository(s)

–store the resource and descriptor definitions for the members of an IMSplex

Common Service Layer (CSL) IMSplex configuration consisting of–Operations Manager (OM)–Resource Manager (RM) –Structured Call Interface (SCI)–SPOC for entering type-2 commands

Batch utilities–Batch ADMIN utility FRPBATCH–RDDS to / from repository utilities

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


IMS Repository Function Components …

Repository Server (RS)– BPE-based address space

• Managed by the RM CSL address space– Two types

• Master Repository Server- Single instance

- Manages access to repository data sets - First RS address space to access repository

• Subordinate Repository Server - One or more instances - Used if master Repository Server goes down - Optional but recommended

IMS Version 14 IMS Version 14 IMS Version 14

9

IMS Repository Function components … Catalog repository (RS catalog data sets)

– Required per repository server – Manages the Repository Server (RS) functions– Manages information about IMS repository data sets– Composed of two pairs of data sets

• Primary index data set and primary member data set (required)• Secondary index data set and secondary member data set (required)• No spare capability

RS catalog data sets

Primary and secondary index data sets Primary and secondary member data sets


IMSRSC repository VSAM/KSDS data sets

IMS Repository Function Components …

IMS repositories– IMSRSC repository

• Index Data Sets• data that describes the repository member. • Similar to directory data for a PDS member.

• Member Data Sets– Resource lists for each IMS– Stored resource definitions – Changed resource lists

• Composed of up to three pairs of data setsPrimary index data set and primary member data set (required) Secondary index data set and secondary member data set (required) Spare index data set and spare member data set (optional)

Primary

Secondary

Spare (optional)

Primary

Secondary

Index Data Sets Member Data Sets

Spare (optional)


11

PRIMARY

Modifying Resources using DRD with IMSRSC repository

IMSRSC Repository

Control Blocks DDIRs PDIRs SMBs RTCEs

IMS CONTROL REGION

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

IMPORT

CREATEUPDATEDELETEIMPORTEXPORTQUERY

OLDS

WARM START

EMERGENCY RESTART

EXPORT

(runtime resource definitions)

(stored resource definitions)

Runtime definitions can be EXPORTed to the IMSRSC repositoryIMS 14 AUTOEXPORTDuring IMS cold start processing, resource definitions may be IMPORTedfrom the IMSRSC repository.

IMPORT

IMS 13 change list

IMS Version 12

12

IMS Repository Access through RM address space

Online operation– IMS type-2 commands

• UPDATE RM• QUERY RM• UPDATE IMS• QUERY IMS

• EXPORT DEFN TARGET(REPO)• IMPORT DEFN SOURCE(REPO)• DELETE DEFN

• QUERY DB/DBDESC/PGM/PGMDESC/TRAN/TRANDESC/RTC/RTCDESC SHOW(DEFN)

• DRD commands (CREATE, UPDATE, DELETE) work with runtime definitions, not the stored resource definitions in the repository

For dynamic enablement / disablement of repository and RDDS functions

For status of RM and IMS

For working with DRD stored resource definitions in the repository

For displaying stored resource definitions in the repository and their attributes


13

• 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 repositoryEXPORT DEFN TARGET(REPO) TYPE() NAME() STARTTIME() ENDTIME() SET(IMSID()) OPTION()


14

• 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 running IMS systems

IMPORT from IMSRSC repositoryIMPORT DEFN SOURCE() TYPE() NAME() OPTION() SCOPE()


15

IMS 13 Repository Change List

IMPORT DEFN SOURCE(REPO) … SCOPE(ALL) to

OperationsManager(OM)

StructuredCallInterface

ResourceManager(RM)

IMS1ControlRegion


SCI SCI SCI

SCI

XCF

XCF

IMSRSC Repository

Primary/Secondary

IMS2 Change List

IMS2ControlRegion

SCI

/NRE /ERE

IMPORT DEFN SCOPE (ALL)OPTION(UPDATE)

© 2012 IBM Corporation16

IMS 13 Repository Change List

IMPORT DEFN SOURCE(REPO) … SCOPE(ACTIVE) to

OperationsManager(OM)

StructuredCallInterface

ResourceManager(RM)

IMS1ControlRegion


SCI SCI SCI

SCI

XCF

XCF

IMSRSC Repository

Primary/SecondaryIMS2 NO Change List

IMS2ControlRegion

SCI

/NRE /ERE

IMPORT DEFN SCOPE (ACTIVE)

IMPORT DEFN ROUTE(IMS2)


17

• 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


18

QUERY resource definitions

• QUERY commands can be used to query the runtime and stored resource definitions.

• The SHOW keyword controls the scope of definition to display.– SHOW(DEFN) returns both repository and local IMS resource

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

definitions – SHOW(DEFN,LOCAL) returns only local IMS resource definitions – SHOW(IMSID) returns all IMSIDs that have the specified resource

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

the repository definition for each IMS + the local IMS resource definitions

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

IMS Version 14

19

IMS Version 14

IMS Repository Access through RM address space Batch ADMIN utility (FRPBATCH)

• Commands for managing IMSRSC repositories - Functions such as ADD a new IMSRSC repository, LIST the characteristics of an IMSRSC repository, START or STOP an IMSRSC repository

Batch RM utilities

– RDDS to Repository Utility (CSLURP10) • Utility to write the contents of a system or non-system RDDS to an IMSRSC

repository– To initially populate an IMSRSC repository– To update definitions in an IMSRSC repository

• Requires SCI and RM– Repository to RDDS Utility (CSLUPR20)

• Utility to generate a non-system RDDS from an IMSRSC repository– Used for backup and migration/fallback

• Requires SCI and RM


20

Repository Server Batch ADMIN Utility (FRPBATCH)• Used for Batch repository administration• Invoked using FRPBATCH utility

Command Function

ADD Add a user repository to the Repository Server catalog

UPDATE Update user repository definition in the RS catalog repository

RENAME Rename an existing user repository in the RS catalog repository

DELETE Remove a user repository from the RS catalog repository

DSCHANGE Change data set disposition

LIST List status information for all user repositories or detailed information for a single user repository

START Request the Repository Server to start a user repository

STOP Request the Repository Server to stop a user repository

IMS Version 14

21

IMS 14

Repository Server z/OS Modify Interface Commands Enables repository administration Commands issued from z/OS console

Command Function

ADMIN Administrative functions – change data set disposition, display data sets, start/stop repositories

AUDIT Dynamically change audit levelSECURITY Refresh RACF profile definitionsSHUTDOWN Shutdown one or more repository server address spacesSTOP Stop/shutdown specific repository server

IMS Version 14

22

IMS 14

IMS 14 Respository Enhancements

– Create non-system RDDS from Log Records Utility (DFSURCL0)• enhanced to create a non-system RDDS that contains only the resource and

descriptor definitions that have not been exported to the IMSRSC repository• IMS Log and any X'22' Log records

– Automatic export to the IMSRSC repository at IMS checkpoints• Only the resources modified or created since last successful export (via

command or AUTOEXPORT) are exported to the IMSRSC repository– /CHECKPOINT command enhancements for LEAVEPLEX keyword

• allow an IMS to be removed from the Repository– QUERY command enhancement for unexported resources

Benefits– Improves usability of the IMS Repository – Reduces the chance of an IMS shutting down without hardening changes to the IMS

Repository– If IMS terminates abnormally, it provides the ability to determine if any new or

modified resource definitions need to be written to the repository


23

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


24

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)

– Updates PGMCAR and TRANCAR in IMSA– Creates PGMCAR and TRANCAR in IMSB– When the IMSplex (IMSs and RM) are V13, this

IMPORT will create a IMS change list for IMSC with PGMCAR and TRANCAR.


25

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

• After IMSC is restarted, user needs to issue the following commands routed to IMSC:

– IMPORT DEFN SOURCE(REPO) TYPE(PGM) NAME(PGMCAR)

– If IMSC is IMS V13, the IMS change list created during IMPORT command is read at the end of restart of IMSC and the resource names PGMCAR and TRANCAR are automatically imported from the repository.

Creating/Updating Resources in a Cloned Environment …


26

Updating Resources in a Non-Cloned Environment (Unique Systems)

• Scenario: 2-way IMSplex with non-cloned systems IMSA and IMSB is defined to the IMSRSC repository. – IMSA and IMSB are active

• Route commands to individual IMS systems, for example:– Route the following commands to IMSA only

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

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

FOR(IMSID(IMSB))


IMS Repository Function Benefits

Consolidation of resource definitions in a single place, the repository DRD definitions are the initial implementation of the IMS repository function (to replace

RDDSs) 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 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 repository A strategic direction for IMS architecture

Technology

Ims repository user groupkb