IMS Dynamic Resource Definition Implementation at BNP Paribas Fortis Leo Van Looy22 October 2015.

IMS Dynamic Resource Definition

Implementation at BNP Paribas Fortis

Leo Van Looy 22 October 2015

Agenda

• Introduction • Milestones in IMS Resource Definition @ BNPPF

• DRD objectives • IMSRSC Repository • BNPPF Environment Presentation• IMS Resource Definition in Development• IMS Resource Definition in other environments• DRD Maintenance jobs : developed at BNPPF• Project info• Conclusion

22/10/2015IT Mainframe Software 2

Introduction

BNP Paribas Fortis Bank

BNP Paribas

Net profit : EUR 811 M (1H 2015)

Balance Sheet : EUR 280 B (1H 2015)

Employees : 14.767 FTE (Q4 2014)

IMS ProductionIMSPLEX : 6 IMS members (4 Bank, 2 AG Insurance)

100% data sharing (Bank : 4,5 Tb DB2 ; 2,8 Tb IMS)

Up to 50 M transactions / day

Peak 1300 trx / s

DRD usage5 environments

1000 new IMS definitions in PROD in 2014

750 updates of IMS definitions in PROD in 2014

2600 deletes of IMS definitions in PROD in 2014 1141 of 1 application

27/02/2014CSM Application Services Local 3

• < 1998 : IMS system definition process, weekly IMS generation to add new PSBs, TRANs, Route Codes, Databases

• 1998 : Implementation of BMC Delta IMS / Delta Plus : • Dynamic add / update• Developers : automated input process

– New IMS resources – Online activation of IMS resources

• 2007 : Dynamic Resource Definition was introduced in IMS V10• Study Deltaplus <> DRD was done• No : not sysplex compliant

• 2014 : Migration of Deltaplus to DRD• Introduction of IMSRSC Repository (IMS V12) .

– Major enhancement – Centralizes consistent resource definitions for all IMS members the IMSplex


Milestones in IMS Resource Definition @ BNPPF

DRD objectives

• Improve availability of the IMS online environment• No need for IMS SYSGEN or MODBLKS online change• Suppression of Modblks datasets• Shared resources across all IMS members in a single place• Reduction of startup time of IMS (up to several minutes)• Fast execution of DRD requests

• Objectives not met by system (synchronisation & backout processing) Changes to resources are not coordinated IMSPLEX wide • Active on all IMS members or none • When error : rollback IMSPLEX wide• An IMS member down in the IMSPLEX @ DRD request : manual• Group of related resources as a whole

BNPPF developed


IMSRSC Repository

• Centralizes all resource definitions in one place in an IMSplex

• Eliminates manual coordination of multiple RDDSs in an IMSplex

• Exporting Resources the IMSRSC repository• no AUTOEXPORT feature to the Repository, • CREATE/UPDATE or DELETE statement is followed by an EXPORT command• no changes offline to IMSRSC repository

• Importing Resources from the IMSRSC repositoryAt COLD start IMS, AUTOIMPORT

All stored resource definitions are read from Repository in the IMS online system

At WARM start IMS, an IMPORT with option(UPDATE) is done by Automated Operations (TSA)


Environment PLXC (Development/Test/Acceptance)


Environment PLXB (QA)


Environment PLXA (Production)


IMS Resource Definition in Development

• PSBs and Transactions (databases)• Transport via SCCM Endevor• Storage of Resource Definition• Generation of the DRD statements• Activation in IMS online


IMS Resource Definition in DevelopmentPSBs and TRANSACTIONS ( Databases )

IMS Resource Definition in DEVELOPMENT environment • There is the ‘Applicative’ part of the parameters,

• The Application Developer introduces basic PSB parameters in the DEVELOPMENT environment

• ISPF panels guide the Application Developer to a consistent IMS resource definition

• The ’System’ part of the parameters that is generated @ the input of the request. • Customized by environment• following performance recommendations.

– Parameters such as Maxrgn, Parlim, Proclim…

• Databases• Under control / request of DBA• Manual


IMS Resource Definition in DevelopmentPSBs and Transactions


The developer introduces a new PSB/TRANSACTION in Data Manager

The parameters are stored in the PSB member and sent to SCCM tool Endevor

IMS Resource Definition in DevelopmentTransport via SCCM Endevor

• IMS definition parameters are stored in the PSB member• Definition of PSB together with• PSB generation in PSB/ACBLIB.


IMS Resource Definition in DevelopmentStorage of Resource Definition

• Generation : The parameters are checked and recorded • in ‘in house’ macros • transformed in DRD parameters• Stored in a DB2 table

– Customized per environment with versioning (including DB)– Applicative part– System part

• Prepare for activation : a record is created in an activate.list


IMS Resource Definition in DevelopmentGeneration of the DRD statements

• The record in Activate.list decides on the type of DRD statement : • NEWBMP add new BMP (CREATE PGM)• UPDBMP update existing pgm (UPDATE PGM)• NEWMPP add new pgm/tran (CREATE PGM + CREATE TRAN)• UPDMPP update existing pgm/tran (UPDATE PGM + UPDATE TRAN)• NEWBCDadd new (batch) pgm + tran (CREATE PGM + CREATE TRAN)• UPDBCD update batch + tran (UPDATE PGM + UPDATE TRAN)• NEWTRX adds new tran to exising pgm (CREATE TRAN)• NEWIMD in house pgm + tran (with model descriptor)• NEWDBDnew database (CREATE DB)

Depending on the type, different DRD statements are generated

Can be a combination of CREATE and UPDATE statements.

Only 1 type of definition is created with a model descriptor


IMS Resource Definition in DevelopmentActivation in IMS Online

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


Activate.list

TYPE 2 commands CREATE PGMCREATE TRAN

DRD statements for EXPORT

Schedule IMS activation Once an hour, a process runs to add dynamically the definitions in IMS, invoking DRD

Batch SPOC utility (CSLUSPOC) executes the CREATE and EXPORT commands

IMS Resource Definition in other environments

• Preparation• IMS Activations• Example of an Activation schedule


IMS Resource Definition in other environmentsPreparation

• Via Endevor package : group of all development elements to be activated at the same time (PSB, Load modules, formats, • Includes IMS Resource definition macros

• The developer decides when (application DBA for DB)• All elements file-transferred together to the next environment

• In a staging area


TEST QA PROD

Acceptance

An ‘Activation Schedule’ is triggered starting jobs via Job Scheduler (Control-M)• The JCLs are composed dynamically based on the contents of the Package

The activation schedule• Analyses contents of a (set of) Endevor packages• Starts a process for every type of element• Home-made customisation manages the installation of an Endevor package.

Activation is always under control of Change Management• Environment TEST / Acceptance : the activation schedules runs ‘immediately’

• Environment QA, it runs twice an hour

• Environment PROD, it runs 4 times a day

• In all environments : « on demand ».


IMS Resource Definition in other environmentsIMS Activation

Example of an Activation schedule


A transaction can’t be scheduled while executing the DRD request on that transaction

When an IMS member is down at execution time of a DRD request, the request is not executed on that IMS. Definition is missing until Manual intervention.

DRD Maintenance jobs

• Delete obsolete IMS resources• Daily compare runtime and stored IMS resource definitions • Capture DRD requests executed while one of the IMS members was down• Daily check of the DB2 tables• Recovery process for corrupted repository data sets


DRD Maintenance jobs : developed at BNPPF

• Delete obsolete IMS resources• The goal : same definitions in the IMS online – IMS repository – DB2 tables • Daily• Collection of obsolete PSBs from Endevor• In-house procedure generates DELETE an DELETE DEFN statements for the PSBs

– DELETE for runtime definitions in the active IMS members– DELETE DEFN for stored definitions in the repository

• The PSB record is also removed from the IMSGEN DB2 table

• Daily compare runtime and stored IMS resource definitions • Home-made procedure :• Defined in IMS online and not in Repository• Defined in Repository and not in IMS online

• Capture DRD requests executed while one of the IMS members was down • Home-made procedure under construction:• Comparison IMS online with DB2 table


DRD Maintenance jobs : developed at BNPPF

• Daily check of the DB2 tables• Capture ‘Inactive’ PSB records in the DB2 table• A new PSB record is created in the DB2 table in status ‘Inactive’, • After successful execution of the DRD request, the record is changed to status ‘Active’• Daily check is done, and an automatic mail is send to highlight anomalies

• Recovery process for corrupted repository data sets

ALLNEW Allocate new repository datasets STOREPO STOP IMS repository EXPAND copy current IMS repository to new repositoryRENOLD rename current repository to old repositoryRENNEW rename new repository to current repositorySTAREPO START IMS repository

A control-M schedule has been created to be executed in case of ‘Repository error’This happened on our Development environment.Disk was full on which the Repository resides, an extend was not possible



Project info

• Phase 1 : DRD installationCreate RS catalog repository datasetsCreate IMSRSC repository datasets Create FRP config members XCF=IMSxRS Start Repository Server Define security settings Add and start repository IMSx_REPOSAdd repository section in CSLRIDIx Enable RM to use Repository Perform IMS sysgen, type=modblksPopulate Repository from modblks Automate start Repository Server

• Phase 2 : DRD StartupThe DRD startup was done during the weekly Control-M schedule for the stop/start of IMSAdd repository and activate DRD in DFSDFDIxDeactivate DeltaplusCold start IMS

• Phase 3 : Supressing the modblksFirst start up of DRD was with a newly generated modblksAfterwards, the MODBLKS were disabled at next stop/start of IMS


Project info

• In house development : Updating home-made procedures

• input process for the developer • IMS online activation

Activation was transparent for the developers.Before DRD activation : execution of Delta listsAfter DRD activation : execution of DRD requests

• Attention points Setting up the RACF security : authorize commands Exit IEFUSI needed to be changed to allow DRD system utilities to allocate 64-bit storage

• Original timing was respected : Roughly one year

LAB preparation Development Test QA PROD Acceptance

Jan 2014 April 2014 June 2014 Sept 2014 Feb 2015 Feb 2015

• Workload ( mandays ) 63 md + study

Conclusions

Objectives

Improve availability of the IMS online environment

No need for IMS SYSGEN or MODBLKS online change

Suppression of Modblks datasets

Shared resources across all IMS systems, in a single place

Reduction of startup time of IMS (up to several minutes)

Fast execution of DRD requests

Synchronisation and back-out BNPPF developed

Consistency checks

Online activation in IMS

Project of a year


Questions?


Questions?

IMS Dynamic Resource Definition Implementation at BNP Paribas Fortis Leo Van Looy22 October 2015.

Documents

ims members

ims productionimsplex

ims online environmentno

updates of ims definitions

ims control regions

ims system definition

weekly ims generation

ims v10study deltaplus