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

2. 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 Software2

3. 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 Production IMSPLEX : 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 usage 5 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 Local3

4. < 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 complian t 2014 : Migration of Deltaplus to DRD Introduction of IMSRSC Repository (IMS V12). –Major enhancement –Centralizes consistent resource definitions for all IMS members the IMSplex 27/02/2014CSM Application Services Local4 Milestones in IMS Resource Definition @ BNPPF

5. 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 22/10/2015IT Mainframe Software5

6. 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 repository At 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) 22/10/2015IT Mainframe Software6

7. Environment PLXC (Development/Test/Acceptance) 22/10/2015IT Mainframe Software7

8. Environment PLXB (QA) 22/10/2015IT Mainframe Software8

9. Environment PLXA (Production) 22/10/2015IT Mainframe Software9

10. 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 27/02/2014CSM Application Services Local10

11. IMS Resource Definition in Development PSBs 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 27/02/2014CSM Application Services Local11

12. IMS Resource Definition in Development PSBs and Transactions 22/10/2015IT Mainframe Software12 The developer introduces a new PSB/TRANSACTION in Data Manager The parameters are stored in the PSB member and sent to SCCM tool Endevor

13. IMS Resource Definition in Development Transport via SCCM Endevor IMS definition parameters are stored in the PSB member Definition of PSB together with PSB generation in PSB/ACBLIB. 22/10/2015IT Mainframe Software13

14. IMS Resource Definition in Development Storage 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 22/10/2015IT Mainframe Software14

15. IMS Resource Definition in Development Generation of the DRD statements The record in Activate.list decides on the type of DRD statement : NEWBMPadd new BMP (CREATE PGM) UPDBMPupdate existing pgm (UPDATE PGM) NEWMPPadd new pgm/tran (CREATE PGM + CREATE TRAN) UPDMPPupdate existing pgm/tran (UPDATE PGM + UPDATE TRAN) NEWBCDadd new (batch) pgm + tran (CREATE PGM + CREATE TRAN) UPDBCDupdate batch + tran (UPDATE PGM + UPDATE TRAN) NEWTRXadds new tran to exising pgm (CREATE TRAN) NEWIMDin 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 22/10/2015IT Mainframe Software15

16. IMS Resource Definition in Development Activation in IMS Online Definitions can be dynamically created, updated, or deleted using enhanced type-2 commands. 22/10/2015IT Mainframe Software16 Activate.list TYPE 2 commands CREATE PGM CREATE 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

17. IMS Resource Definition in other environments Preparation IMS Activations Example of an Activation schedule 27/02/2014CSM Application Services Local17

18. IMS Resource Definition in other environments Preparation 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 22/10/2015IT Mainframe Software18 TEST QA PROD Accep tance

19. 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 ». 27/02/2014CSM Application Services Local19 IMS Resource Definition in other environments IMS Activation

20. Example of an Activation schedule 27/02/2014CSM Application Services Local20 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.

21. 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 27/02/2014CSM Application Services Local21

22. 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 22/10/2015IT Mainframe Software22

23. 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 ALLNEWAllocate new repository datasets STOREPOSTOP IMS repository EXPANDcopy current IMS repository to new repository RENOLDrename current repository to old repository RENNEWrename new repository to current repository STAREPOSTART 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 22/10/2015IT Mainframe Software23

24. 27/02/2014CSM Application Services Local24 Project info Phase 1 : DRD installation Create RS catalog repository datasets Create IMSRSC repository datasets Create FRP config members XCF=IMSxRS Start Repository Server Define security settings Add and start repository IMSx_REPOS Add repository section in CSLRIDIx Enable RM to use Repository Perform IMS sysgen, type=modblks Populate Repository from modblks Automate start Repository Server Phase 2 : DRD Startup The DRD startup was done during the weekly Control-M schedule for the stop/start of IMS Add repository and activate DRD in DFSDFDIx Deactivate Deltaplus Cold start IMS Phase 3 : Supressing the modblks First start up of DRD was with a newly generated modblks Afterwards, the MODBLKS were disabled at next stop/start of IMS

25. 27/02/2014CSM Application Services Local25 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 lists After 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 QAPRODAcceptance 27/02/2014CSM Application Services Local25 Jan 2014 April 2014 June 2014 Sept 2014 Feb 2015 Workload ( mandays ) 63 md + study

26. 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 27/02/2014CSM Application Services Local26

27. Questions? 22/10/2015CSM Application Services Local27 Questions?