Simplifying IMSplex Management with DRD and the Repository a Usage Perspective - IMS UG July 2013 Phoenix

®

1

Simplifying IMSplex Management with DRD and the Repository: A Usage Perspective

Diane Goff, IMS Advanced Technical Skills

[email protected]

July 18, 2013

Phoenix IMS Users Group

2

Simplifying IMSplex Management with DRD and the Repository: A Usage Perpsecitive

Overview

� Dynamic Resource Definition (DRD) Introduction

– DRD objective/components

– Modifying resource definitions with DRD and IMS repository function

– DRD environment and enablement

– Automatic Import

– Recoverability of resources/descriptors

� DRD Utilities

– Migration to repository

– Fallback from repository

3


Overview (continued)

� DRD Usage

– Managing resources with DRD

• Dynamic updates

• Displaying attribute/status information

• Hardening updates to the repository

• Initial population of the repository

– Using TSO SPOC application to issue DRD commands

– DRD best practices

� Repository Administration

� Example Use Case Scenarios

� Repository Security Considerations

� Additional Reference Information

� DRD with Repository Benefits

� Summary/Q&A

4


Dynamic Resource DefinitionIntroduction

5


Dynamic Resource Definition (DRD)

� OBJECTIVE: To improve the availability of the IMS online environment

� Allow user to dynamically define and enable MODBLKS resource

definitions

– Databases

– Programs

– Transactions

– Routing Codes

� No requirement for IMS SYSGEN + IMS restart/online change

� Benefit: increased resource availability

� MODBLKS online change process not required

6


DRD Components

� Type-2 commands: CREATE, DELETE, DELETE DEFN, UPDATE,

IMPORT, EXPORT, QUERY

� IMSRSC repository that contains statically (SYSGEN) and dynamically

created definitions

– Resource definitions

– Model descriptors

� Import and export functions provided to save/restore resource definitions across a cold start

� DFSINSX0 (Destination Creation) user exit to dynamically create program and transaction resources (optional)

� UPDATE and QUERY support for MSC resources

– Supports resource modification without requiring system definition changes

or an IMS restart

7


Modifying MODBLKS Resources without DRD

//MODBLKSx

Control BlocksDDIRsPDIRsSMBsRTCEs

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

8


Modifying MODBLKS Resources with DRD

IMSRSC Repository


IMS CONTROL REGIONIMS CONTROL REGION

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

IMPORT

CREATEUPDATEDELETEIMPORTEXPORTQUERY

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 the IMSRSC repository

9


� “Runtime resource definitions”

– Resource information (attributes, status, relationship to other resources) stored in an online IMS as control blocks:

• Database directories = DDIRs

• Program directories = PDIRs

• Fast Path routing codes = RTCEs

• Scheduler message blocks for transactions = SMBs

– Controlled/maintained by IMS itself

– Reside in IMS control region

� “Stored resource definitions”

– Resource information that is stored offline, from which IMS builds runtime

resource definitions

• Reside in system data sets, such as IMS.MODBLKS or the IMSRSC

repository

– Controlled/maintained by user

Resource Terminology

10


Modifying MODBLKS Resources with DRD


IMS CONTROL REGIONIMS CONTROL REGION

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

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

Definitions can be EXPORTed to the IMSRSC repository

IMPORT

CREATEUPDATEDELETEQUERY

OLDS

WARM START

EMERGENCY RESTART

EXPORT



IMSRSC Repository

11


DRD Environment

� Cold start is required to enable DRD (with repository or RDDSs)

– Online Change for MODBLKS is disabled

– MODBLKS data sets are optional

– ACBLIB and FMTLIB Online Change is allowed

– MODBLKS SYSGEN no longer required

12


DRD Environment…

� Use of DRD with the repository function requires IMS 12 with:

– Repository Server (including PROCLIB member FRPCFG)

– Repositories

• IMSRSC repository to maintain stored resource definitions

• Catalog repository to maintain information about IMSRSC repository

– Common Service Layer (CSL) IMSplex configuration consisting of

• Operations Manager (OM)• Resource Manager (RM) • Structured Call Interface (SCI)• SPOC for entering type-2 commands• Optional resource structure with CQS address space

– IMS PROCLIB members with DRD/repository enablement parameters

• DFSDFxxx

– RM PROCLIB member with repository enablement parameters

• CSLRIxxx

13


DRD Environment

� Use of DRD with the repository function requires IMS 12 with:

– Entry point for DRD commands

• TSO Single Point Of Control (SPOC), Batch SPOC, REXX SPOC API, or other OM interface

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

14


Common Service Layer – Review

� An architecture to improve the systems management capabilities for IMS systems

– OM provides SPOC for DRD command entry + routes commands/consolidates responses + provides API for automation + has user input/output exits

– RM accesses the IMSRSC repository via the Repository Server + coordinates IMSplex-wide processes + maintains global resource information in structure

– SCI provides communication ability to IMSplex members, within or cross z/OS images + member registration services

� Benefits

– Provides a single system image (IMSplex)

– Ease of use through a single point of control

– Shared resources across all IMS systems

– Reduces complexity of managing multiple IMS systems

– DRD with repository is just one of many IMS capabilities that leverage CSL

15


IMS Repository Function Architecture

Operations

Manager

(OM)

Structured

Call

Interface

Resource

Manager

(RM)

IMS

Control

Region

Repository

Server

(RS)

SCI SCI SCI

SCI

SCI

XCF

X

C

F

X

C

F

RS Catalog Repository

Primary/Secondary

IMSRSC Repository

Primary/Secondary

Batch ADMIN

Utility

(FRPBATCH)

Repository

Server

Commands

CSLURP10 /

CSLURP20

Audit L

og

X

C

F

16


Enabling DRD with repository

� Enable CSL (SCI, OM and RM) by defining parameters in DFSDFxxx <SECTION=COMMON_SERVICE_LAYER>

– DFSCGxxx also valid but not preferred

– Ensure RM is defined to use repository (CSLRIxxx)

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

– Set MODBLKS=DYN in <SECTION=DYNAMIC_RESOURCES>

– Define <SECTION=REPOSITORY>

� Set up Repository Server by defining parameters in FRPCFG

� Create catalog repository data sets

� Create IMSRSC repository data sets and define to Repository Server

� Decide how to populate IMSRSC repository

– Offline: Use DRD utilities

– Online: Issue type-2 EXPORT command

17


Enabling DRD

� Start Repository Server(s)

� Start IMSRSC repository

� Cold start IMS

– Required to switch to / from DRD

– If IMSRSC repository not previously populated with definitions with utilities, export resource definitions to IMSRSC repository to capture existing runtime definitions

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

18


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

– Definitions are used to create the internal control blocks needed to manage

resources

� During cold start, definitions can be imported from

– IMSRSC repository

– System RDDS

– MODBLKS data set

– Or not imported at all…

• AUTOIMPORT=NO

• AUTOIMPORT=AUTO with error and either

– IMPORTERR=CONTINUE

– REPOERR=NOIMPORT

Automatic Import with Repository

19


� MODBLKS data set (typically used for online change -- no DRD)

– Contains stored resource definitions from SYSGEN macros

• DATABASE, APPLCTN, TRANSACT, RTCODE

– Each IMS system has its own

� IMSRSC repository data set (used with DRD)

– Can contain stored resource definitions from SYSGEN macros

• DATABASE, APPLCTN, TRANSACT, RTCODE

– Also contains…

• Stored resource definitions from dynamically created resources

– Using command CREATE DB | PGM | TRAN | RTC

• Resource lists for each IMS

– List of stored resource definitions (DB/PGM/TRAN/RTC) for a particular IMS

MODBLKS Data Set Vs. the IMSRSC repository …

20


� IMSRSC repository data set (used with DRD)

– Also contains (cont’d)

• IMS change lists in IMS 13 (discussed in more detail later)

– Contain resource and descriptor names that were imported using

the IMPORT SCOPE(ALL) command when an IMS was down

– Applied at next warm/emergency restart after IMS log is

processed – internal import is done

– IMS change list is deleted at the end of warm/emergency restart

and at end of coldstart

– Shared among multiple IMS systems

MODBLKS Data Set Vs. the IMSRSC repository

21


Accessing the Repository

� All access to the IMSRSC repository (which contains stored resource definitions) is via the Repository Server (RS) using:

– Access through RM address space

• Online

–IMS type-2 commands

• Batch RM utilities

–RDDS to Repository (CSLURP10)

–Repository to RDDS (CSLURP20)

– Direct access (RM not used)

• Batch ADMIN utility (FRPBATCH)

• Repository server commands using the z/OS modify interface

22


Recoverability

� Resource and descriptor definitions

– Exist for the life of IMS or until deleted

– Are recovered from logs across warm and emergency restart

• Definitions are logged when created, updated, or deleted, and at system checkpoint time

– Are recovered across cold start if both:

• Previously exported to the IMSRSC repository with EXPORT command

• Imported during next cold start

23


Dynamic Resource DefinitionUtilities with Repository

24


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 MODBLKS

1. 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)

25


� To revert back to MODBLKS OLC from DRD, the MODBLKS data set must be re-created following these steps

– Allocate and populate a temporary RDDS

– Run the Repository to RDDS utility (CSLURP20) to copy repository contents to the temporary RDDS

• If repository is not available:

– Run the Create RDDS from Log Records utility

– EXPORT to RDDS to capture existing IMS definitions

– Use this RDDS as input to the Extract RDDS Contents utility (DFSURDD0) to generate Stage 1 macros

– Use these Stage 1 macros to generate MODBLKS

Re-Creating MODBLKS for Fallback from DRD

26


Dynamic Resource DefinitionUsage

27


Commands Used in Dynamic Resource Definition with Repository

� Type-2 commands entered through OM interface

Export resource or descriptor definitionsEXPEXPORT

Import resource or descriptor definitionsIMPIMPORT

Delete runtime resource or descriptor (either runtime or

stored definition)

DELDELETE

QRY

UPD

CRE

Short Form

Update attributes of resource or descriptor

Update status of resource

UPDATE

Create resource or descriptor CREATE

Query attributes of resource or descriptor Query status of resource

QUERY

PurposeCommand

28


RTCE

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

29


DRD Command Entry and Response

� Operations Manager (OM)

– Commands must be entered through an OM interface

– OM will consolidate responses from all IMSs in IMSplex

� If any IMS returns a non-zero return/reason code to OM

– OM will return a non-zero return/reason code to SPOC, plus a completion

code for each resource

• If CC not 0, CCText explains reason

– SPOC displays completion code and text for each IMS and resource

30



� Sample command input and response

– PGM2 created even though command failed for PGM1

CCTextCCMbrNamePgmName

0IMS1PGM2

RESOURCE ALREADY EXISTS11IMS1PGM1

CREATE PGM NAME(PGM1,PGM2) SET(SCHDTYPE(SERIAL))

31



� In some cases, an “Error Text” will also be returned

� Sample command input and response

� IMS 12 Command Reference documents, for each command

– Return and reason codes

– CC (Completion Codes)

– CCText (meaning of completion code – if non-zero)

– ErrorText (further explanation – if applicable)

ACCTUPDT

ErrorTextCCTextCCMbrNameDBName

0IMS1CUSTMSTR

REFERENCED BY PROGRAM11IMS1ACCTMSTR

DELETE DB NAME(ACCTMSTR,CUSTMSTR)

32


� Use the type-2 CREATE command to create a resource or descriptor definitions

� Optionally define attribute values by:

– Specifying them in command syntax

– Referencing the name of an existing resource or descriptor definition

– Using the system default descriptor’s attribute values

� Dynamically created definitions are restored across coldstart as long as they are exported to the repository while the IMS is active, prior to being shut down

� No new repository-related parameters

Dynamically Creating Resource Definitions

33


� rsc-type | desc-type = resource or descriptor type (see slide 32 for resource command keywords (e.g., PGM, PGMDESC))

� NAME() = resource or descriptor names; they will all have the same attributes; wild cards not supported

� LIKE() = resource or descriptor name to use as model

� SET() = attribute names and values

� DEFAULT(Y) – valid for descriptors only

– Y causes this descriptor to become current system default descriptor

CREATE rsc-type | desc-type

NAME(name1,name2,...)

LIKE(RSC(rsc-name)) | LIKE(DESC(desc-name))

SET(attr1(val1),attr2(val2),...)

DEFAULT(Y) <<< valid for descriptors only

CREATE Command – Format

34


CREATE Command - Setting Attributes

� All attribute values are set either explicitly by SET command keyword or by default

� Hierarchy of attribute setting:

– SET command keyword – takes precedence over all others

– LIKE command keyword

• Attributes not SET are obtained from the specified model

• Can be LIKE DESC or LIKE RSC

• Takes precedence over current default descriptor

– If LIKE command keyword not specified

• Attributes not SET will be gotten from current system default

descriptor, which can be either:

– DFSDSxx1 (IMS-provided)

– User descriptor created with DEFAULT(Y)

35


IMS1

SPOC

z/OS 1

IMS2

z/OS 2

IMS3

z/OS 3

Operations

Manager

(OM)

SCI

SCI

SCISCI

CREATE TRAN

NAME(TRANA)

TRANA

TRANA

TRANA

CREATE TRAN NAME(TRANA)CREATE TRAN NAME(TRANA)CREATE TRAN NAME(TRANA)

CC = 0

CC = 0

CC = 0

CC = 0

IMS1 CC = 0

IMS2 CC = 0

IMS3 CC = 0

DRD Flow

36


IMS1

SPOC

z/OS 1

IMS2

z/OS 2

IMS3

z/OS 3

TRANA

TRANA

TRANA

IMS1 CC = 0

IMS2 CC = 0

IMS3 CC = 0

OM routes

command to each

IMS to create the

TRANA transaction

resource and

consolidates the

command response

from each system

SCI enables

communication

between the

SPOC/OM as well

as OM/IMS

Operations

Manager

(OM)

SCI

SCI

SCISCI

37


� Use the type-2 DELETE command to dynamically remove resource/descriptor definitions when they are no longer needed

– From the active IMS system

– From the repository

� Distinguish between DELETE and DELETE DEFN

– Use DELETE for runtime definitions in the active IMS system

– Use DELETE DEFN for stored definitions in the repository (“harden” runtime deletes offline) (replaces automatic export as with RDDSs)

� Considerations for deleting runtime resources

– To delete a resource

• Resource cannot be “in use”

• Recommendation: stop resource before attempting to delete

– QUERY command enhanced to display resource work status

• Show work that might cause delete command (or OLC) to fail

Dynamically Deleting Resource Definitions

38


� rsc-type | desc-type = resource or descriptor type

– See slide 32 for resource command keywords (e.g., PGM, PGMDESC)

� NAME() = names of resources or descriptors

– Can specify multiple names

– Can use wildcard character

• NAME(*) – all resources or descriptors (be careful)

• NAME(PART*) – resource or descriptors starting with PART

• NAME(ADDPART,BILL*)

� OPTION(ALLRSP)

– Ignored except when NAME(*)

– Indicates responses to be returned for all resources

• Default is to return response only for error conditions

DELETE rsc-type | desc-type

NAME(* | name1,name2,NAME*,...) OPTION(ALLRSP)

DELETE Command – Format

39


DELETE DEFN Command – Format…

� Deletes stored resource definitions from the repository, and is

processed by one command master IMS

� Use this command to harden runtime definition deletes to the repository

� TARGET(REPO) – delete definitions from repository

� TYPE() specifies a single resource/descriptor type

– DB, DBDESC, PGM, PGMDESC, RTC, RTCDESC, TRAN, TRANDESC

– In IMS 13, CHGLIST

� NAME() defines the names of the resources/descriptors to delete

– Wildcard supported (not the default like it is with DELETE command)

DELETE DEFN TARGET(REPO) TYPE()

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

40


� FOR(IMSID()) indicates the IMS resource list(s) the resources or

descriptors are deleted from within the repository

– Can specify a single IMSID, or a list of multiple IMSIDs (the IMS must be

defined to RM to use the repository and can be either active or inactive)

– Usage example:

QUERY PGM NAME(PGM1) SHOW(WORK)

UPDATE PGM NAME(PGM1) STOP(SCHD)

DELETE PGM NAME(PGM1)

DELETE DEFN TARGET(REPO) TYPE(PGM) NAME(PGM1)

FOR(IMSID(IMS1,IMS2)

– Wildcards * and % supported



Routed to IMS1 and IMS2

DELETE DEFN Command – Format…

41


� OPTION(ALLRSP) ensures that the command response displays a line

of output for each resource/descriptor processed by command

– Only valid with NAME(*)



DELETE DEFN Command – Format

42


Dynamically Updating Resource Attributes and/or Status

� Use the type-2 UPDATE command to update:

– Resource/descriptor status and attributes

• MODBLKS: DB, PGM, TRAN, RTC

• MSC: MSPLINK, MSLINK, MSNAME

– MSC definitions have no CREATE | DELETE support

� Cannot update resource attribute if resource “in use”

� Recommendation: QUERY and /STOP resource before attempting to update

� Cannot update resource attributes and status in same command

� Updating (or creating) descriptor with DEFAULT(Y) sets this descriptor to current system default descriptor for that resource type

� No new repository-related parameters

43


� rsc-type | desc-type = resource or descriptor type (see slide 31 for resource command keywords (e.g., PGM, PGMDESC))

� NAME() = resource or descriptor names; they will all have the same attributes; wild cards not supported

� START() = brings resource online (details vary per resource)

� STOP() = makes resource unavailable (details vary per resource)

� SET() = attribute names and values

� DEFAULT(Y) – valid for descriptors only

– Y updates this descriptor to become current system default descriptor

UPDATE rsc-type | desc-type

NAME(name1,name2,...)

START() | STOP ()

SET(attr1(val1),attr2(val2),...)

DEFAULT(Y) <<< valid for descriptors only

UPDATE Command – Format

44


Displaying Resource Attributes and/or Status

� Use the type-2 QUERY command to:

– Display the attribute values of a resource/descriptor

– Display resource status

– Determine whether any current “work in progress” exists that would prevent a

resource from being updated or deleted successfully

� Applies to MODBLKS resources (DB, PGM, TRAN, RTCODE) and MSC

definitions (MSPLINK, MSLINK, MSNAME)

� If an IMS has unique resource attribute values, they can be maintained in the

repository for that specific system

– IMS-specific values are contained in the IMS system’s respective local section of the

repository

– Non-specific values (where the attribute values are the same for all IMSs) are

contained in the generic section of the repository

– Examples of potential IMS-specific attribute values:

• SIDR and SIDL values for remote transactions in MSC environment

• Transaction class

45


QUERY Command Enhancements

� NAME() = resource/descriptor name(s)

� SHOW() = scope of definition to display

� Use this command to display generic and IMS-specific definitions

– 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 all IMSIDs that have the specified resource

defined + a list of the repository resource definitions + any IMS-specific definitions

� Command output will display an L prefix for the columns containing the local IMS information

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

46


� Use the type-2 EXPORT command to:

– Save runtime resource/descriptor adds/changes to repository

• These definitions can be loaded at next coldstart

– Populate an empty repository for the first time after initially migrating to DRD

with repository

– Replaces ‘autoexport’ capability with RDDSs

� EXPORT writes an IMS system’s runtime resources/descriptors definitions to the repository, where they will kept as stored resource definitions

Saving Runtime Resource Definitions - Adds/Updates in Repository

47


EXPORT Command – Format…

� TYPE() defines the resource type

– ALL, ALLDESC, ALLRSC, DB, DBDESC, PGM, PGMDESC, RTC,

RTCDESC, TRAN, TRANDESC

� NAME() defines the names of the resources to export

– NAME(*) is the default

� STARTTIME() indicates the time after which all created/modified resources will be exported

� ENDTIME() indicates the cut-off time for when created/modified resources be exported

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

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

� TYPE() defines the resource type

– ALL, ALLDESC, ALLRSC, DB, DBDESC, PGM, PGMDESC, RTC,


� NAME() defines the names of the resources to export


� STARTTIME() indicates the time after which all created/modified resources will be exported

� ENDTIME() indicates the cut-off time for when created/modified resources be exported

Local time in yyyy.ddd hh:mm:ss:th format (only yyyy.ddd are required)

48


� SET(IMSID()) specifies one or more IMSIDs whose resource lists will be

updated in the repository as a result of EXPORT being issued

– Wildcards * and % supported

• Examples: IMS*, IMS%A

• If there are no IMS resource lists in the repository, EXPORT will fail

– The specified IMSID does not need to be active in the IMSplex

• EXPORT will create an IMS resource list for this IMSID, to be read when

IMS starts

– If SET(IMSID()) is omitted, the default is the IMSID of the command master

• Command master can be selected using the ROUTE parameter



EXPORT Command – Format…

49


� OPTION() controls how much command output is displayed and what

specific resources are exported

– OPTION(ALLRSP) will return a line of output for each successfully exported

resource/descriptor in the command response

– OPTION(CHANGESONLY) specifies that only resources/descriptors created

or updated since the last EXPORT will be exported to the repository

• This option is a new capability that did not exist with RDDS DRD

• OPTION(ALLRSP) automatically included



EXPORT Command – Format

50


� Use the type-2 IMPORT command to:

– Read resource/descriptor stored resource definitions from the repository into

the IMS system, where they become runtime resource definitions

– Percolate definitional changes made to the offline repository to 1+ active IMS systems, for example:

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

definitions

• Make changes to repository then roll them out to 1+ running IMS systems

Reading Stored Resource Definitions from Repository

51


IMPORT Command – Format…

� SOURCE(REPO) = read definitions from repository

� TYPE() defines the resource/descriptor type

– ALL, ALLDESC, ALLRSC ,DB, DBDESC, PGM, PGMDESC, RTC,


� NAME() defines the names of the resources to import


IMPORT DEFN SOURCE(REPO)

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

52


� OPTION() controls how much command output is displayed and what specific resources are imported

– OPTION(ABORT) will fail the IMPORT command if an error occurs while

importing a resource/descriptor

– OPTION(ALLRSP) will return a line of output for each successfully imported

resource/descriptor in the command response (valid with NAME(*))

– OPTION(UPDATE) will replace an existing resource with the one that exists in the RDDS or repository

• Required if a resource already exists in a running IMS system, otherwise

IMPORT will fail

• Work in progress cannot exist for the resource that IMPORT is attempting to replace with the stored definition (recommendation: stop, then query the resource to determine whether it is currently in use)

IMPORT DEFN SOURCE()


IMPORT Command – Format…

53


� SCOPE() is a new IMPORT parameter that indicates which IMS systems the IMPORT will apply to (cont’d)

– In IMS 12, SCOPE(ACTIVE) and SCOPE(ALL) provide the same functionality

– SCOPE() will apply the IMPORT command to only the active IMS systems in

the IMSplex

• IMSs that are down will need a manual IMPORT command performed at

/NRE or /ERE (coldstart and /ERE COLDSYS OK)



IMPORT Command – Format …

54


– In IMS 13, SCOPE(ALL) will apply the IMPORT command to each IMS in the

IMSplex, and is recommended (default)

• If an IMS is down, an IMS change list is created for it, which contains the resource names it would have imported had it been up

• IMS change list will be read during warm/emergency restart and will thus be kept synchronized with the other IMS systems in the IMSplex

• Use care when specifying a ROUTE list since this will take precedence over SCOPE(ALL), since IMS systems not specified on ROUTE will not receive the command



IMPORT Command – Format

55


– In IMS 13 SCOPE(ACTIVE) will apply the IMPORT command to only 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 required

at /NRE or /ERE, coldstart and /ERE COLDSYS OK)



IMPORT Command – Format

56


Repository Administration

57


Dynamically Enabling RM and IMS for Repository Usage

� Use the type-2 UPDATE RM command is to dynamically enable RM for repository usage

– Define CSLRIxxx (RM initialization PROCLIB member) with repository-

enabling settings first

� Use the type-2 UPDATE IMS command to dynamically enable IMS for repository usage

– Define DFSDFxxx (IMS System Definition PROCLIB member) with repository-enabling settings first and make sure that RM is already repository-enabled

– Command can also be used to disable automatic export, which is used with

when migrating from the original type of DRD with RDDSs to DRD with repository

58


Updating Audit Settings that Track Repository Access

� Access to the IMSRSC repository can be tracked in an audit log

� Auditing is initially activated in the FRPCFG PROCLIB member with the AUDIT_DEFAULT setting

– Can be later changed/overridden with the type-2 UPDATE RM command

� Use the AUDITACCESS() command keyword with the UPDATE RM

command to set the access level; valid values are:

– NOAUDIT for no auditing of member access

– SECURITY for auditing security failures only

– UPDATE for auditing member access with update intent

– READ for auditing member access with read and update intent

– SYSTEMREAD for auditing member access with system-level read, read, or update intent

• A “system-level read” is a read that occurs as part of the process for updating a resource

59


Displaying Information About User Repositories Being Managed by RM

� Use the type-2 QUERY RM command to see information about repositories being managed by RM, such as:

– Whether RM is enabled for repository or not

– Repository audit access level

• Indicates the type/level of member access auditing -- defined in FRPCFG

member, in CSLRIxxx (RM initialization) member, or with UPDATE RM command

– RM status information:

• CONNECTED = RM connected to repository

• DISCONNECTED = RM disconnected from repository

• SPARERECOV = repository spare recovery in progress

• SPARERCVERR = repository spare recovery error

• NOTAVAIL = repository unavailable

60


Displaying Repository Settings in IMS

� Use the type-2 QUERY IMS command to determine whether the IMS system is

currently enabled for repository usage or not

� The QUERY IMS command can also be used to determine whether automatic export (applies only to RDDS DRD) is currently enabled or not

– Used in a migration scenario from DRD with RDDS to DRD with repository

61


Repository Server Batch ADMIN Utility

� Invoked via JCL statements with FRPBATCH

� Enables repository administration

� Commands issued from 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

62


� Initial setup of the repository environment involves allocating user repositories (AKA “IMSRSC repositories”) that will contain stored resource definitions

� User repositories must then be defined to the RS catalog repository

� Use Batch Admin utility ADD command to specify user primary, secondary, and (optional) spare repository data set names

– Here, you can specify whether or not the repository data sets will be opened

automatically when the repository is started with command parameter

– Also here, you can define security class to be used to restrict access to the repository with command parameter (optional)

Defining User Repository to RS Catalog Repository

63


Starting and Stopping User Repositories

� Once user repositories have been defined to the RS catalog repository with the Batch Admin ADD command, start them with the Batch Admin START command

� If any user repository settings require updates, use the Batch Admin STOP command in preparation

– A stopped repository rejects connection attempts and is deallocated/closed by the Repository Server

64


� Attributes of the primary, secondary, or spare repository data set can be

dynamically updated using the Batch Admin UPDATE command

– Examples:

• Changing auto-open feature (whether the repository data sets are opened

when repository is started)

• Modifying security class being used to restrict repository access

� Repository must be stopped before it can be updated

� The name of a user repository can be changed using the Batch Admin RENAME command

– Name defined in RS catalog repository will be updated

� To remove a user repository from the RS catalog repository, use the Batch Admin DELETE command

– Physical data sets are not deleted (use the z/OS Access Method Services (IDCAMS)

utility or a similar method)

Updating User Repository Settings

65


� Primary or secondary user repository data set (RDS) failure

– Recovery process involves a user action item of assigning a new data set

status using the Batch Admin DSCHANGE command to one of two possibilities:

• ‘DISCARD’

• ‘SPARE’

� If a spare RDS was defined during initial environment setup:

– Repository Server drives recovery and replaces the failed data set with the

spare, leaving user with two RDSs: the primary and secondary (one of which

the spare just replaced)

– User must then allocate a new spare RDS and assign the ‘SPARE’ status to it

� If no spare was defined:

– Failed RDS is automatically stopped and user must manually assign a ‘DISCARD’ status to it

– User must then allocate a new RDS pair, then start the repository

Recovering from a User Repository Data Set Failure

66


Displaying Information About Repository Data Sets

� Use the Batch Admin LIST command to display details associated with a single repository or all repositories that are defined to the RS catalog

repository:

– Repository name

– Repository status

– Date of last update

– USERID that last updated user repository

67


Offline Repository Management - Examples* ------------------------------------------------------------------- *

LIST REPOSITORY(IMSRSC_REPOSITORY)

Repository Name . : IMSRSC_REPOSITORY

Last updated date/time : 2010/07/27 00:52:46 USRT001

Status . . . . . . . . : STOPPED

Auto-open . . . . . . . : YES

Security Class . . . . : NOT DEFINED

Repository Data Set pair 1

Index (RID) . . : IMSTESTS.FRP1.IMSPRI.RID

Member (RMD) . : IMSTESTS.FRP1.IMSPRI.RMD

Status . . . . : COPY1


Index (RID) . . : IMSTESTS.FRP1.IMSSEC.RID

Member (RMD) . : IMSTESTS.FRP1.IMSSEC.RMD

Status . . . . : COPY2


Index (RID) . . : IMSTESTS.FRP1.IMSSPR.RID

Member (RMD) . : IMSTESTS.FRP1.IMSSPR.RMD

Status . . . . : SPARE

FRP4750I - LIST command processing completed successfully

* -------END-OF-JOB-------------------------------------------------- *

68


Example JCL for Batch ADMIN

Commands

//FRPBAT EXEC PGM=FRPBATCH,PARM='XCFGROUP=FRP2PLEX'

//SYSPRINT DD SYSOUT=*

//SYSIN DD *

//*

ADD REPOSITORY(IMS_REPOS) -

REPDSN1RID(IMSTESTS.REPO.IMSPRI.RID) -

REPDSN1RMD(IMSTESTS.REPO.IMSPRI.RMD) -

REPDSN2RID(IMSTESTS.REPO.IMSSEC.RID) -

REPDSN2RMD(IMSTESTS.REPO.IMSSEC.RMD) -

AUTOOPEN(NO)

//*

START REPOSITORY(IMS_REPOS) MAXWAIT(30,CONTINUE)

//*

LIST REPOSITORY(IMS_REPOS)

//*

STOP REPOSITORY(IMS_REPOS) MAXWAIT(30,CONTINUE)

//*

RENAME REPOSITORY(IMS_REPOS) REPOSITORYNEW(IMS_PROD_REPOS)

//*

UPDATE REPOSITORY (IMS_PROD_REPOS) -

REPDS1RID(IMSTESTS.PRODREPO.IMSPRI.RID) -

REPDS1RMD(IMSTESTS.PRODREPO.IMSPRI.RMD) -

AUTOOPEN(NO)

//*

DELETE REPOSITORY(IMS_PROD_REPOS)

69


Repository Server z/OS Modify Interface Commands

� Enables repository administration

� Commands issued from z/OS console

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

70


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

71


Example Use Case Scenarios

72


Updating Security Settings

� Updating security settings to protect repository from unauthorized access

– Changing RACF security class name associated with a user repository in RS catalog repository with batch ADMIN UPDATE command

• UPDATE REPOSITORY(REPO1) SECURITYCLASS(XFACILIT)

– Changing RACF definitions

• RDEFINE XFACILIT FRPREP.REPO1 UACC(NONE)

• PERMIT FRPREP.REPO1 CLASS(XFACILIT) ID(ANGIE) ACCESS(READ)

– Refreshing RACF in-storage profiles with z/OS modify interface SECURITY command

• F REPOSVR1,SECURITY REFRESH

73


Recovery After a Repository Data Set Fails

� If a write error occurs on a primary or secondary data set pair within repository, its disposition status is changed to DISCARD

� Repository Server manages recovery process if SPARE data set present

� User’s only task is to allocate/define a new spare data set and assign it to SPARE disposition with DSCHANGE command

74


Recovery Example

� Scenario: a repository named REPO1 contains a primary (COPY1), secondary (COPY2) and spare (SPARE) data set are defined

� Write error occurs on the primary and Repository Server drives recovery

– Primary data set is automatically changed to disposition of DISCARD

– Secondary data set’s definitions are copied to spare

– Repository Server changes spare to primary

– Issue command to determine which RDS has been discarded (with batch ADMIN LIST or z/OS modify interface ADMIN,DISPLAY command)

– Delete and define the discarded primary data sets to replace old spare (best practice: new spare should be larger than previous)

– Change disposition of this new data set to SPARE

• Batch ADMIN command: DSCHANGE REPOSITORY(REPO1) RDS((1) ACTION(SPARE))

• z/OS modify interface command: F REPOSVR1,ADMIN DSCHANGE (REPO1,S,1)

75


Displaying and Printing Stored Definitions in Repository

� When IMS systems are active

– Issue QUERY command with SHOW(DEFN) specified to display list ofresources (and their attribute values) within repository

• Includes a display of which IMS systems have specific resources defined

• Example: QUERY DB NAME(*) SHOW(DEFN) to display all databases

– Tip: For the best command output results view, opt to group lines by either column or resource (not wrap) under SPOC preferences:

� When IMS systems are inactive

– Run CSLURP20 “Repository to RDDS” utility to generate non-system RDDS with repository contents

– Run DFSURDD0 “Extract RDDS contents” utility to generate a query report containing a list of resources with attribute values

– Follow this process for each IMS that is using the repository, one at a time

76


Repository Security Considerations

77


Repository Security Implementation

� Repository Server resources can be restricted from unauthorized access, including:

– User repository

– RS catalog repository

– Members within a user repository

– Audit levels associated with an individual repository

� Choose a class to protect Repository Server resources in

– FACILITY or

– 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

78


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

– Authorized RM caller

• IMS via commands such as:

– EXPORT TARGET(REPO)

– IMPORT SOURCE(REPO)

– DELETE DEFN

– QUERY with SHOW(DEFN)

– Non-authorized RM callers

• CSLURP10 (RDDS to Repository RM utility)

• CSLURP20 (Repository to RDDS RM utility)

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

– Batch ADMIN utility

– z/OS modify interface

Repository Access

79


� 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

80


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.REPO1 UACC(NONE)

• RDEFINE XFACILIT FRPREP.* UACC(NONE)

� RS catalog repository

� Repository users can access/update with batch ADMIN commands


• FRPREP.CATALOG

– Example

• RDEFINE XFACILIT FRPREP.CATALOG UACC(NONE)

81


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

– FRPMEM.repositoryname.DFS.RSC.membername

– RDEFINE XFACILIT

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


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

rscname

Example

rsctype 8-byte resource name to be secured

82


� Audit levels associated with an individual repository


– FRPAUD.repositoryname.DFS.RSC.TYPE

– Example

• RDEFINE XFACILIT FRPAUD.REPO1.DFS.RSC.TYPE UACC(NONE)


83


Granting User Access to Repository Server Resources

� After defining resource profiles, grant access to appropriate users

� User repository

– RDEFINE XFACILIT FRPREP.REPO1 UACC(NONE)

– PERMIT FRPREP.REPO1 CLASS(XFACILIT) ID(VIEWER1)

ACCESS(READ)

– PERMIT FRPREP.REPO1 CLASS(XFACILIT) ID(ADMIN1)

ACCESS(ALTER)

� RS catalog repository

– RDEFINE XFACILIT FRPREP.CATALOG UACC(NONE)

– PERMIT FRPREP.CATALOG CLASS(XFACILIT) ID(ADMIN1)

ACCESS(ALTER)

84


Granting User Access to Repository Server Resources

� Members with a repository

– RDEFINE XFACILIT

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

– PERMIT FRPREP.REPO1 CLASS(XFACILIT) ID(USRUTL10)

ACCESS(UPDATE)

– PERMIT FRPMEM.REPO1.DFS.RSC.CSLPLEX1.TRAN.PART

CLASS(XFACILIT) ID(USRUTL10) ACCESS(UPDATE)

– PERMIT FRPMEM.*.*.*.*.*.**

CLASS(XFACILIT) ID(USRUTL20) ACCESS(READ)

� Repository audit levels

– RDEFINE XFACILIT FRPAUD.REPO1.DFS.RSC.TYPE UACC(NONE)

– PERMIT FRPAUD.REPO1.DFS.RSC.TYPE CLASS(XFACILIT)

ID(USRZOSMI) ACCESS(UPDATE)

85


� Able to group several user IDs together for higher efficiency when defining resource profiles and granting access to them

– PERMITs will reference RACF group rather than each individual user ID

� Example

RDEFINE XFACILIT FRPREP.REPO1 UACC(NONE)

ADDGROUP FRPVIEW

ADDGROUP FRPEDIT

PERMIT FRPREP.REPO1 CLASS(XFACILIT) ID(FRPVIEW) ACCESS(READ)

PERMIT FRPREP.REPO1 CLASS(XFACILIT) ID(FRPEDIT) ACCESS(UPDATE)

CONNECT <VIEWER1> GROUP(FRPVIEW)



CONNECT <UPDATER4> GROUP(FRPEDIT)

CONNECT <UPDATER5> GROUP(FRPEDIT)

RACF Groups

86


Additional Information About IMS 12 and DRD with Repository

87


� Discusses all IMS 12 capabilities

from a user perspective, including

DRD with Repository

� Free download at

http://www.redbooks.ibm.com

88


IMS 12 Performance White Paper is Available

� Detailed results of our internal

performance tests, including

information about DRD with

repository testing

� Environment, functions tested,

MIPS and throughput results

� Available for download at

www.ibm.com/ims

89


Summary

90


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 therepository

� A strategic direction for IMS architecture

91


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

92


Value of the IMS 12 Repository for DRD

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

– Generic resource definition plus IMS-specific resource definitions

– EXPORT process is a single unit or work for entire IMSplex, all succeeds or

all fails

– EXPORT process controlled by user (no AUTOEXPORT)

• Can select CHANGESONLY or by time periods

– DELETE of stored resource definitions controlled by user

– Can UPDATE an existing runtime definition via IMPORT

– EXPORT reflected in all IMSs in an IMSplex, whether up or down at the time

– QUERY will display stored resource definitions from repository

– DFSINSX0 (Destination Creation Exit) supports export to repository

93



� 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

• Previously available DRD RDDS utilities can be used in backup/recovery

scenarios

– IVP available to assist with installation of repository

– Supported by TSO SPOC Manage Resources application

94



� Provides security capabilities for auditing and compliance

– Full support for RACF (SAF) interfaces

– Repository audit log (optional)

• Includes both online and batch access

– OM type-2 repository commands found in optional 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

95


Summary…

� Dynamic Resource Definition (DRD) Introduction

– DRD objective/components

– Modifying resource definitions with DRD and IMS repository function

– DRD environment and enablement

– Automatic Import

– Recoverability of resources/descriptors

� DRD Utilities

– Generate repository from MODBLKS

– Re-create MODBLKS for fallback from DRD

96


Summary (continued)

� DRD Usage

– Managing resources with DRD

• Dynamic updates

• Displaying attribute/status information

• Hardening updates to the repository

• Initial population of the repository

� Repository Administration

� Example Use Case Scenarios

� Repository Security Considerations

� Additional Reference Information

� DRD with Repository Benefits

97


Questions?

Technology

Simplifying IMSplex Management with DRD and the Repository a Usage Perspective - IMS UG July 2013 Phoenix