IMS Enterprise Metadata - IMS UG June 2012 Phoenix

© 2012 IBM Corporation

IMS Enterprise Metadata

Kyle Charlet

STSM, IMS SOA and [email protected]

© 2012 IBM Corporation2

Overview of IMS Catalog

� The IMS catalog will contain 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


Metadata principles

� Simply defined, metadata is data about data.

– IMS example: metadata about an IMS database segment might include

information about data types, application-defined fields, user-defined types

� Metadata is not a means to an end

–Users use tools; tools manage and interact with metadata

� Metadata should

–Enhance understanding

– Improve consistency

– Improve impact analysis

– Improve productivity

– Improve governance

� Metadata needs to be linked

–For impact analysis

–For understanding data lineage

� Metadata needs to include physical implementation, logical design intent and

business semantics


What is metadata?

� Business metadata

– Business rules, definitions, terminology, glossaries, algorithms and

lineage using business language

– Audience: Business users

� Technical metadata

– Defines source and target systems

• Table and field structures and attributes

• Derivations and dependencies

– Audience: Specific tool users, AD, BI, ETL, profiling, modeling

� Operational metadata

– Information about application runs

• Frequency, record counts, component by component analysis and

other statistics

– Audience: Operations, management and business users

Literally, “data about data” that describes your company’s information

from both a business and a technical perspective


Types of technical metadata and storage medium

� 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

– FORMAT resources*– Application*

• Input/output message definitions

Catalog

Repository

IMS database

VSAM

* It is our intention to store this metadata in the repository


IMS Catalog

� Trusted 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)


Comprehensive view of database metadata

�Metadata is defined in a variety of locations–PSB/DBD source

• Not trusted, proprietary, not complete

–PSBLIB/DBDLIB• Not trusted, proprietary, not complete

–ACBLIB• Trusted

• Proprietary, not complete

–Application• Applications control the data

• COBOL copybooks, for example, further refine database segments and

assign meaningful data types

In aggregate, application and ACBLIB information provide a comprehensive view

of IMS database metadata. The IMS catalog will house this metadata.


Catalog overview – trusted information

ACBLIB

Catalog

PSB++

source PSBLIB++

• ACBGEN will populate ACBLIB and catalog in the same UOW

• Key points

• Only way to update catalog is via the GEN process

• Extended info is acquired via the IMS Explorer

DBD++

source DBDLIB++

PSBGEN

DBDGEN

ACBGENIMS Explorer

COBOL/PLI

source

Utility

DB client

route


Catalog access and interface

�Open systems

–Universal drivers

• SQL and DLI interfaces directly to the catalog

• XML – render catalog information as XML instance document valid

to published IMS metadata schema

� z/OS

–Universal drivers

• SQL and DLI interfaces directly to the catalog

• XML

–Traditional IMS languages

• DLI access directly to the catalog

• Batch access supported


Catalog runtime access

IMS

Connect

DBDB

Catalog

IMS

ODBM

DR

WAS z

CICS

DB2 z

DRDA/TCPIP

SQL/DLI

SQL/DLI

DRDA DLI

UsersIMS Explorer

SQL/DLI

Tools

Universal

Drivers

(SQL/DLI/XML)


Installation

� IMS provides PSBLIB and DBDLIB members for the catalog

–User to run ACBGEN

–IMS internally handles the rest of the initialization process

• MODBLKS creation (PDIR, DDIR)

• Loading of DMBs and PSBs into resident pools

� IMS provides utilities that will

–Create the catalog database

–Load the catalog from a user ACBLIB

� IMS provides an option that does not require DBRC for the catalog

–Many customers have expressed that the DBRC requirement for

HALDB databases puts undesired burden on test system infrastructure


Migration

� Standard database migration for the catalog

–No additional migration considerations necessary

� Catalog schema evolution

–Catalog database will implement the “IMS best practices” for allowing

the evolution of the catalog schema


Management

� Catalog supports all standard utilities for backup and recovery

� Catalog supports online reorg (it is a PHIDAM database)

� As part of initial catalog load process IMS will determine the size of the

catalog datasets

–User can allocate or defer to IMS to allocate on their behalf

� DBRC is optional


Coexistence

� Two models

–A single catalog can be data shared among multiple IMS systems

–Single catalog per IMS system

� ACBLIB and catalog will remain in sync with one another

–Managed by IMS

� Future

–IMS will be configured to load (cold start) from either catalog or

ACBLIB


Catalog databaseHEADER

(RESOURCE HEADER)

SS

(SENSEG)

PCB

PSB

SF

(SENFLD)

PSBVENDPSBRMK

(REMARKS)

PCBRMK

(REMARKS)

SFRMK

(REMARKS)

SSRMK

(REMAKRS)XDFLD

LCHILD

AREACAPXDBD SEGMDSET

(DATASET)

DBD

MAP

(DFSMAP)

DBDRMK

(REMARKS)

CAPXSEGM

CASE

(DFSCASE)

LCHRMK

(REMARKS)

SEGMRMK

(REMARKS)

CMAR

(DFSMARSH)

CPROP

(PROPERTIES)

CFLD

(FIELD)

DBDVEND

CFLDRMK

(REMARKS)

CMARRMK

(REMARKS)

DBDXREFDSETRMK

(REMARKS)

AREARMK

(REMARKS)

FLD

(FIELD)

MAR

(DFSMARSH)

FLDRMK

(REMARKS)

PROP

(PROPERTIES)

MARRMK

(REMARKS)

MAPRMK

(REMARKS)

CASERMK

(REMARKS)

RESERVED RESERVED RESERVED

. . .

RESERVED RESERVED RESERVED

RESERVED RESERVED

LCHIDX

(INDEX NAME)


Types of technical metadata and storage medium

� 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

– FORMAT resources*– Application*

• Input/output message definitions

Catalog

Repository

IMS database

VSAM

* It is our intention to store this metadata in the repository


IMS Repository

�Overview of the IMS Repository Function

� IMS Repository Function Components –Repository Server (RS) address space–Repository catalog data sets–Repository data sets–CSL requirements and RM usage

�Migration to DRD with the repository


Repository function overview

� 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


Repository benefits

� Consolidation of resource definitions in a single place

� 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


Repository population

Rep

MODBLKS

Utility

Utility

RDDS

Direct from RDDS

Direct from MODBLKS

IMS

Temp RDDS

Export command

RM


Repository function usage

� In IMS 12, the resource and descriptor definitions for Dynamic Resource Definition

(DRD) can be stored in an IMS repository

–Contains resource definitions for programs/transactions/databases/FP

routing codes & descriptors

–Called the IMSRSC, the IMS resource definition repository

–Provides an alternative to using RDDSs (resource definition data sets) for

DRD• Replaces one or more sets of RDDSs in an IMSplex with a single repository

–Eliminates the need to manually coordinate and manage separate RDDSs

per IMS across a multiple-IMS IMSplex

–Provides an alternative to using MODBLKS with SYSGEN and online

change

–Considered a strategic alternative to the RDDS

� IMS 12 can retrieve the stored resource definitions from the IMSRSC repository to

dynamically generate runtime resources for DRD


IMS 12 support for the DRD function

� DRD users in IMS 10 and IMS 11 moving to IMS 12

–Can use existing RDDSs from IMS 10 or IMS 11 for stored resource

definitions in IMS 12

–Can use existing RDDSs from IMS 10 and IMS 11 for stored resource

definitions at initial migration to IMS 12, then can migrate to the new

IMSRSC repository

• Best for incremental migration

–Can use the new IMSRSC repository to store definitions in IMS 12


Repository components

� A Common Service Layer (CSL) IMSplex configuration consisting of

–Operations Manager (OM)

• Used for new/modified type-2 commands for repository functions

–Resource Manager (RM)

• Used for managing the new Repository Server (RS) address space

• All online access to Repository Server is through RM address space

• New type-2 commands for managing the Repository Server

UPDATE RM

QUERY RM

• RM is enabled to the repository by specifying a Repository Section in the

RM initialization member (CSLRIxxx)



� A Common Service Layer (CSL) IMSplex configuration consisting of–Structured Call Interface (SCI)

• Used for communications within the CSL• Not used for communications between RM and the RS • RS is not considered a CSL manager

–Optionally, a resource structure in a Coupling Facility• Used for repository name and repository type consistency if present

• Managed by a Common Queue Server (CQS) address space• Multiple RMs in an IMSplex require that a resource structure exists

–SPOC (single point of control) for entering type-2 commands–Can be a single-IMS IMSplex or a multiple-IMS IMSplex



� Batch utilities

–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

–RDDS to / from repository utilities (Batch RM utilities)

• RDDS to Repository Utility (CSLURP10)

For migration

• Repository to RDDS Utility (CSLURP20)

For fallback


Repository migration overview

� From DRD with RDDSs to DRD with Repository

–Create non-system RDDS that contains current definitions via EXPORT

command or DRD utilities

–Set up repository parameters in PROCLIB members FRPCONFG,

BPECONFG, CSLRIxxx, DFSDFxxx

–Create catalog repository data sets and IMSRSC repository data sets

–Start the Repository Server address space

–Use the batch ADMIN utility to define the IMSRSC data sets to the

Repository Server

–Run the batch RDDS to Repository utility to populate the repository

–Cold start IMS with AUTOIMPORT specified

� From no DRD to DRD with Repository

–First implement DRD with RDDSs

• Set up DRD parameters in DFSDFxxx

–Cold start IMS using updated DFSDFxxx

• AUTOIMPORT will use MODBLKS for definitions

–Follow process to migrate from DRD with RDDSs to DRD with repository


Repository 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

Batch ADMIN

Utility

(FRPBATCH)

RM utilities

CSLURP10 /

CSLURP20

Audit L

og

X

C

F

Structured

Call Interface

SCI

Resource

Manager

(RM)

SCI

IMS Enterprise Metadata - IMS UG June 2012 Phoenix

Technology

Transcript of IMS Enterprise Metadata - IMS UG June 2012 Phoenix