Simplifying Resource Management - IMS UG June 2015 Tokyo

Greg VanceIMS STSM June 11, 2015

Simplifying Resource Management in IMS

IMS Tokyo RUG 2015

*

2

© Copyright IBM Corporation 2015. All rights reserv ed.U.S. Government Users Restricted Rights - Use, dupli cation or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM’s statements regarding its plans, directions, a nd intent are subject to change or withdrawal without notice at IBM’s sole discreti on. Information regarding potential future products is intended to outline ou r general product direction and it should not be relied on in making a purchasing deci sion. The information mentioned regarding potential future products is no t a commitment, promise, or legal obligation to deliver any material, code or f unctionality. Information about potential future products may not be incorporated i nto any contract. The development, release, and timing of any future feat ures or functionality described for our products remains at our sole discretion.

IBM, the IBM logo, ibm.com, Information Management, IMS, CICS, DB2, WebSphere and z/OS 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.

Disclaimer

Agenda

Taking advantage of the dynamic capabilities IMS can improve availability and allow you to be more agile in addressing you customer needs.

Introduction

Dynamic Resource Definitions (DRD)

Repository

Dynamic MSC

Load from Catalog

DDL

3

Data Cloud Engagement

Social. Mobile. Security. Empowering people with knowledge, enriching them through networks and changing expectations.

The emergence of cloud is transforming IT and business processes into digital services

Data is becoming the world’s new natural resource

There are three important shifts fundamentally changing IT

4

IMS Product Strategy is aligned with these shifts

� Core Capabilities– Reduce path length, contention,

I/O…

– Reduce planned outages

– More dynamic capabilities

� Data & Analytics

– Accelerate time to insight

� Cloud/Mobile

– Rapidly enable/control cloud &

mobile access to IMS resources

� Innovate and extend the

value of your IMS

investment

� Expand and empower the

IMS talent population

� Open interfaces & Java

� Modern tooling for

administrators,

developers and DBAs

Strategic Intent Investment

� Continue to deliver the

IMS Value Proposition

– Superior performance,

reliability, availability and

serviceability

– Minimize cost per transaction

5

Dynamic Resource Definitions

IMS Technical Symposium 2015

Agenda

A system program can create, modify or deleted certain system resources using Dynamic Resource Definitions without the need for Online Change or an IMS outage.

DRD can also simplify the IMS system generation process by removing the need to define MODBLK type resources as part of the stage1 system generation process.

This leads to more agility enabling you to adapt to shifting needs quicker.

Introduction

Dynamic Resource Definitions (DRD )

Repository

Dynamic MSC

Load from Catalog

DDL

7

Dynamic Resource Definition (DRD)

� Improve the availability of the IMS online environment

� Allow user to dynamically define and enable MODBLKS resource definitions– Databases – Programs– Transactions– Routing Codes

� IMS Repository provides an optional single centralized store for resource definitions for an IMSplex

– Across multiple IMSs or for a single standalone IMS

– Can make changes when an IMS is down

– Provides definitions when IMS cold start is required

� No requirement for MODBLKS data set,

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

� Reduce STAGE1 definitions

8

DRD Environment

� DRD requires:– Common Service Layer with Structured Call Interface and Operations Manager (CSL with

SCI/OM)�Resource Manager is not required

– IMS PROCLIB members with DRD enablement parameters�DFSDFxxx�DFSCGxxx (CSL parameters - can be replaced by section of DFSDFxxx)

– Data sets to hold resource definitions (RDDSs) � or IMSRSC Repository

– Entry point for DRD commands� IBM Management Console for IMS, TSO Single Point Of Control (SPOC), or other OM

interface

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

9

Modifying MODBLKS Resources without DRD

10

//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 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

Modifying MODBLKS Resources with DRD

11

RDDS

Control BlocksDDIRsPDIRsSMBsRTCEs

IMS CONTROL REGION

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

IMPORT

CREATEUPDATEDELETEIMPORTEXPORTQUERY

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 EXPORTedto a Resource Definition Data Set.

IMS Repository


Agenda

The IMS repository provides a common repository that can simplify the process of defining and/or sharing system resources.

This can improving confidence in the rollout of dynamic changes

Introduction


Repository

Dynamic MSC

Load from Catalog

DDL

13

14

IMS Repository Function

� Introduced in IMS 12

� A ‘repository’ is a generalized data storage facility that can be used to store various types of information

� The IMS repository function is a centralized method for storing and retrieving resource definitions in an IMSplex

– Enables multiple IMS systems in a multiple-IMS IMSplex to manage, store, share, and retrieve resource definitions

– Enables a single IMS system in a single-IMS IMSplex to manage, store, share, and retrieve resource definitions

� Focus is on improving the systems management and resource management aspects of handling IMS resource definitions

– Across multiple IMSs or for a single standalone IMS– For test systems, for production systems

� IMS 14 Enhancements IMS 14

IMS V12 DRD Resources and RDDS

15

SCI1

IMS1

OM1 SCI2

IMS2

SCI3

IMS3

SCI4

TRANNEW

IMS4

CREATETRAN (TRANNEW)

TRANNEW TRANNEW

IMS4 unaware of new tranRequires extra steps to update IMS4 RDDS

RDDS RDDS RDDS RDDS

IMS V12 Repository for DRD Resources

16

SCI1

IMS1

OM1

SpareSecondary

Primary

IMSRSCRepository

SCI2

IMS2

SCI3

IMS3

SCI4 RM Utility

CFRM Resource

Structure

RM4

Audit Log

Repository Server

RM3

RDDS

RACF

CREATETRAN (TRANNEW)

TRANNEW

IMS4

IMS4 will obtain updated information from repository on restart

17

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 IMSplexeliminated, replaced by basic functioning of the IMS repository

� Improvements in IMSplex systems and resource management with the repository

� A strategic direction for IMS architecture

Dynamic MSC


Agenda

A system programmer can dynamically update MSC resources without the need for and outage or OLC.

IMS 14 adds even more dynamic capabilities

Introduction


Repository

Dynamic MSC

Load from Catalog

DDL

19

20

MSC Considerations

� Static MSC definitions require an outage to change

� Can manage aspects of network dynamically – with planning

� Define dummy “spare” links in your sysgen– Can dynamically add logical sessions and create connections as needed to an IMS

� Dynamically modify and activate dummy definitions– UPDATE MSPLINK, MSLINK, MSNAME– Allows you to change most MSC configuration characteristics

� Ability to dynamically create and delete MSC resources through enhancements to the IMS type-2 commands.

IMS 14

Implementation considerations for Dynamic MSC

� Requires implementation of the CSL (Common Service Layer)– SCI, OM� IMS Type-2 commands are used to manage the environment

� Shared queues– If any IMS system in a shared queues group uses MSC, MSC must be enabled in all IMS

systems, even if they do not use MSC

� DFSDFxxx: <SECTION MSC>– MSCRSCS=DYN|NODYN

Background: Static MSC Environment Before IMS V14 with minimum CSL

22

IMS.SDFSRESLsystem generation

DFSVNUCxmember

UPDATE command(MSLINK | MSNAME |MSPLINK)(updates lost at next IMS cold start unless kept in sync manually in sysdef)

OperationsManager

(OM)

StructuredCall

Interface

SCI

SCI

SCI

MSPLINKMSLINK

MSNAMENAME

System definitionMSC macros

NRE & EREMSLINK & MSPLINK refreshed from IMS log

IMSControlRegion

MSPLINK &MSLINKcontrol

blocks in 24-bit storage

coldstart

NOTE: MSC MSNAME & NAME resources already in 31-bit LQB pool

Dynamic MSC Environment With SYSGEN

23

MSPLINKMSLINK

MSNAMENAME

System definitionMSC macros IMS.SDFSRESL

DFSCLL3xmember

system generation

IMSControlRegion

MSCRSCS=DYN

DFSDFxxx proclib member

coldstart with MSC=Y(recommended)

coldstart

OperationsManager

(OM)

SCI

SCI

CREATE/DELETE command for MSPLINKUPDATE command forMSLINK | MSNAME | MSPLINK

StructuredCall

Interface

SCI

Dynamic MSC Environment With IMSRSC Repository, no sysgen (Repository SPE)

24

OperationsManager

(OM)

StructuredCall

Interface

IMSControlRegion

MSPLINK &MSLINK control

blocks in 31-bit

MSCP & MSCL pool

storage

SCI

SCI

Coldstart with MSC=Y(mandatory)

DFSDFxxx proclib member

CREATE commandDELETE command

SCI

ResourceManager

(RM)

SCI

AUTOIMPORT=AUTOMSCRSCS=DYNREPOSITORY=(TYPE=IMSRSC)SYSID=n

RepositoryServer(RS)

XCF

XCF

RS Catalog Repository

Primary/Secondary

IMSRSC Repository

MSC Definitions

EXPORT commandIMPORT commandforLTERM | MSLINK | MSNAME |MSPLINK

(updates can be automatically saved across cold start if stored in the repository)

UPDATE command forMSLINK | MSNAME | MSPLINK

MSC Enhancements

� Benefits– Reduces 24-bit private storage usage for MSC users

� even if dynamic MSC not enabled– Simplifies enablement of MSC– Centralizes MSC startup options into one DFSDFxxx proclib member– Reduces planned outages for changing MSC definitions– Provides a centralized location for all MSC definitions– Simplifies cloning of MSC-enabled IMS systems in a shared queues IMSplex by

allowing you to remove MSC resources from sysgen– Provides type-2 command advantages when creating and deleting MSC resources such

as wildcards, command completion codes, and timestamps

25

Load From CatalogCatalog Managed ACBs


Agenda

The IMS load from catalog support provides an infrastructure that simplifies application deployment and by eliminating the need for DBDLIBs, PSBLIBs and ACBLIBs.

Introduction


Repository

Dynamic MSC

Load from Catalog

IMS DDL

27

Overview of IMS Catalog

� The IMS catalog contains information about IMS program resources, database resources, and relevant application metadata that IMS controls:

– All program- and database-related information defined to the IMS database system including databases, fields, segments, data types, and more

– Changes made to any of these resources when you create, alter, or delete any IMS resource information will be reflected in the catalog

� The IMS catalog is a key component of the IMS growth strategy:– Simplification– Integration– Dynamic database– Versioning

28

IMS 12 catalog

� Trusted IMS metadata information

� Comprehensive view of IMS database metadata (including application metadata) managed by IMS with standard access patterns (JDBC/SQL)

� Offers metadata discovery and exchange via IMS Open Database and the IMS Explorer for Application Development

� Scalable Open Database solution – large scale deployment into virtualized production and test environments

� Enables broad IMS integration into the IBM and non-IBM portfolio of tools (Optim Development Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc)

29

ACBLIB

Catalog

PSBsource PSBLIB

DBDsource DBDLIB

PSBGEN

DBDGEN

ACBGENIMS Explorer

IMS

Catalog runtime access

30

IMSConnect

DBDB

Catalog

IMS

ODBM

DR

WAS zCICSDB2 z

DRDA/TCPIP

SQL/DLI

SQL/DLI

DRDA DLI

UsersIMS Explorer

SQL/DLI

Tools

UniversalDrivers

(SQL/DLI/XML)

Load from Catalog

� Provides IMS customers the ability to load directly from the IMS catalog instead of the ACBLIB.

� The IMS catalog can be dynamically updated through the use of DDL from a workstation to create, alter, or delete IMS database and program resources without needing to perform a DBDGEN, PSBGEN, and ACBGEN

31

PSBLIB

CatalogIMS ExplorerDDL

ACBLIB

DBDLIB

PSBsource

DBDsource

IMS

Replacing the ACBLIB with the IMS catalog

� To replace the ACBLIB, IMS will automatically maintain an extension in the IMS catalogcalled the directory.

– The directory will consist of one or more data sets that operate similar to the ACBLIB and contain the binary runtime format of database control blocks.

– The directory will be automatically managed by IMS when the catalog is updated. – Simply update the catalog, and that will trigger IMS to manage the updates to the

directory. � A customer with a directory-enabled IMS catalog will not need to understand or

manage the directory.

� The removal of the ACBLIB is optional– requires the customer to indicate IMS is using the catalog with a directory.

Enabling Load from Catalog

� Update the DFSDFxxx PROCLIB member, with the following parameter added to the CATALOG section:

– DIRECTORY=(N|Y)� Y: Specifies that load from catalog is enabled. When directory is enabled then IMS

will load from catalog instead of ACBLIB.� N: When this parameter is N or is omitted, load from catalog is disabled.

� The Catalog Definition exit routine (DFS3CDX0)– an alternative to the DFSDFxxx member of the IMS.PROCLIB data set to enable and

configure the IMS™ Directory parameters in order to Load IMS from Catalog. – This exit routine is available in batch processing environments only.– The sample user exit has been modified to turn on Flags to enable/disable IMS

parameters (CATALOG/DIRECTORY).

IMS with Catalog and ACBLIB

Production IMS

DFSDFPRD<SECTION=CATALOG>

CATALOG=Y

ACBLIB

Catalog

PSBsource PSBLIB

DBDsource DBDLIB

PSBGEN

DBDGEN

ACBGEN& CatalogPopulate

IMSTools

IMS Explorer

34

IMS ExplorerSQL DDL

Catalog IMS

DFSDFTST<SECTION=CATALOG>

CATALOG=Y

ACBMGMT=CATALOG

DFSDFPRD<SECTION=CATALOG>

CATALOG=Y

ACBMGMT=CATALOG

Catalog

PSBsource PSBLIB

DBDsource DBDLIB

PSBGEN

DBDGEN

ACBGEN& CatalogPopulateUtility

IMS

Tools

IMS ExplorerSQL DDL

Catalog managed ACBs configurations

Tools

Optional

35

IMS DDL


Agenda

The IMS catalog can be dynamically updated through the use of DDL to create, alter, or delete IMS database and program resources without needing to perform a DBDGEN, PSBGEN, and ACBGEN

Introduction


Repository

Dynamic MSC

Load from Catalog

IMS DDL

37

IMS 14

Dynamic Database Definition

� Simplify database creation and modifications

� Use DDL to manipulate IMS databases and program views – Define – Modify – Delete

� Bypass the database generation related processes – DBDGEN– PSBGEN – ACBGEN

� Simplify activation of object changes in IMS– Changes may be activated when committed

38

Data Definition Language - DDL

� The Data Definition language is a language syntax used to describe a data structure. This structure may be a database, records, fields, set and access paths of a user data model. This can also refer to the layout and format of the data stored in a particular structure.

� In a generic sense, DDL is used in reference to any formal language syntax that describes data or information structures.

� DDL is an industry standard for commands used to define databases and their structures.

� DDL can be used to create, alter or delete database objects.

� All database systems have a uniqueness to the data structures required in their unique environment. While each system uses industry standard DDL to define its structures, because of this uniqueness, each system uses its own syntax extensions that are specialized to their own DBMS environment.

� IMS is no different in this respect.

39

Dynamic Database Definition

� IMS 14 provides for using the standard DDL. IMS 14 also includes extensions specific to IMS structures to allow more detailed database definitions. These extensions closely match the current non DDL definitions used in IMS.

� Provides potential for managing several processes under a single submission

� Many options existing in the PSBGEN and DBDGEN macros are unique to IMS. – e.g., DB Access Types: PHIDAM, HIDAM, PHDAM, etc.

� IMS provides defaults through a template stored in the IMS catalog

� This template is based on IMS recommended defaults – Modifiable to user requirements– The recommended defaults can be seen in the syntax train tracks

40

DDL defaults and Enhanced IMS syntax

� Overriding the IMS system defaults – Enhanced DDL syntax

� All parameters that can be specified in the DBDGEN or PSBGEN macros are optional parameters in the IMS Enhanced DDL syntax

� The IMS Enhanced DDL syntax can be used with existing defaults – Defaults values may be overridden when specified

� DDL syntax has also been Enhanced to fully specify their PSB definitions– If a PSB is defined in the same commit scope as a CREATE or ALTER database call,

no default PSB will be generated

41

Standard DDL syntax

� Basic DDL statements– CREATE object

� Define & generate– ALTER object

� Redefine & regenerate– DROP object

� Delete

42

IMS GEN statement DDL

Database DBD DATABASE

Segment SEGM TABLE

Dataset DATASET TABLESPACE

Area AREA TABLESPACE

Program PSBGEN PROGRAMVIEW

PCB PCB SCHEMA

Senseg SENSEG SENSEGVIEW

Dynamic Database - Data Definition Language

� SQL incorporates DDL to modify the schema of a database

� Authoring DDL is straight-forward with sophisticated tooling support in the industry

� SQL/DDL can be used to update/add metadata in the catalog without the need of a GEN

– Directly update the catalog

� IMS can be notified of such an update and load the new definitions

43

Thank You!


Simplifying Resource Management - IMS UG June 2015 Tokyo

Technology