IBM IMS Solutions: Sharpen Your Competitive Edge with IMS 14

Transcription

1 IBM IMS Solutions: Sharpen Your Competitive Edge with IMS 14 Alison Coughtrie IMS Specialist European IMS Software Architecture Team October 22 nd 2015 With thanks to Betty Patterson IBM Distinguished Engineer and IMS Chief Architect 2015 IBM Corporation

2 Agenda How to Sharpen your competitive edge with IMS Driving Transaction Workload into IMS IMS Data the Core of your Business Improving Availability Improving Usability for External Subsystem Connections Going Mobile with IMS How IMS Tools extend your edge 1

3 There are three important shifts fundamentally changing IT Data Cloud Engagement Data is becoming the world s new natural resource The emergence of cloud is transforming IT and business processes into digital services Social. Mobile. Security. Empowering people with knowledge, enriching them through networks and changing expectations.

4 IMS Product Strategy is aligned with these shifts Strategic Intent Investment Continue to deliver the IMS Value Proposition Superior performance, reliability, availability and serviceability Minimize cost per transaction Innovate and extend the value of your IMS investment Expand and empower the IMS talent population 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 Open interfaces & Java Modern tooling for administrators, developers and DBAs 3

5 Delivering value to your businesses SOA and Open Integration Open Database Application Modernization Who: A large bank in AP What Business Need: reduce fraud through smarter transaction processing Solution: enable IMS application to call, in-line, to an enterprise fraud and anti-laundering solution Benefits Delivered: 65% response time improvement with a simplified architecture Who: A large insurance client What Business Need: Easier Access to IMS Data Solution: IMS Open Database infrastructure Benefits Delivered: Easy access to IMS data using SQL from any platform Helps to drive open standards and open technology into IMS Who: IT Service Provider for banks What Business Need: Evolve their core banking processes Solution: Promoted the use of Java on z/os, especially Java and COBOL interoperability hosted by IMS Benefits Delivered: Skills, rapid development, reduced application logic & complexity 4

6 Delivering value to your businesses Mobile and Wearables Cloud and API Development Business Analytics Who: Proof of Concept What Business Need: Demonstrate the art of the possible Solution: Mobile device and bluetooth wearable (EEG/ heart monitor, IMS, z/os Connect Benefits Delivered: a System of engagement and z Systems System of Record real time possibilities Who: API Developers What Business Need: Quickly build an application talking to legacy transactions Solution: IBM Bluemnix, z/os Connect and IMS Benefits Delivered: App development is about speed and choice Who: Large European Bank What Business Need: Real-time analytics Solution: IDAA & IMS Benefits Delivered: Skills, rapid development, reduced application logic & complexity 5

7 Driving Transaction Workload into IMS

8 IMS Connect -The TCP/IP gateway to IMS Enables access for Messages into and out of IMS applications through IMS TM IMS Mobile Feature Pack and z/os Connect IMS to IMS, WebSphere Application Server, IMS Soap Gateway, and IBM DataPower through Open Transaction Manager Access (OTMA) IMS to IMS through Multiple Systems Coupling (MSC) IMS TM to CICS through InterSystems Communications (ISC) Direct IMS Database access through Open Database System Management using IBM Management Console for IMS or IMS Operations Manager IMS Connect is a component of IMS and executes in a z/os address space Any TCP/IP Client T C P / I P z/os IMS Connect IMS 7

9 Enabling Cascaded Transactions Distributed global transactions can combine IMS transactions with other workload requests (WAS, CICS, DB2 requests) into one unit of recovery Resource Recovery Services (RRS) coordinates the syncpoint processing for global transactions Allow a global transaction using the IMS TM Resource Adapter to flow across an IMS Connect and an IMS Control region that reside on different LPARs For those transactions that require 2-phase commit (SYNCLVL=SYNCPT) Distributed WAS with IMS Resource Adapter z/os IMS Connect IMS IMS 14 z/os Why this is important Increases flexibility and workload balancing of IMS across LPARs Increases availability by allowing IMS Connect to route to another LPAR 8

10 Enable connectivity using OTMA Descriptors Open Transaction Manager Access (OTMA) allows IMS to send/receive transaction messages to/from TCP/IP clients such as IMS Connect through transaction pipes Client descriptors define properties for an OTMA client Destination descriptors define message destinations that are routed through OTMA. Better storage management for OTMA descriptors Eliminate fixed storage allocation at startup IMS 14 Can increase limits using DFSOTMA member descriptor Why this is important Reduces ECSA storage usage if fewer descriptors are needed than current limits Improved scalability for application connectivity growth

11 Improved Scalability for OTMA Transaction Pipes Allow multiple activeresume TPIPEs for a single Transaction Pipe (TPIPE) TPIPEs sending CM0 output require ACK before next message can be sent Multiple IMS Applications issuing ICAL to a single TPIPE IMS 14 Why this is important Synchronous callout to an external server - potential reduction in application wait time Asynchronous message delivery - Potential throughput improvement Failover; throughput or workload balancing Client1 Resume TPIPE ALTCID=ICONTP1 Client2 Resume TPIPE ALTCID=ICONTP1 Client3 Resume TPIPE ALTCID=ICONTP1 TPIPE= ICONTP1 Message1 Message2 Message3 10

12 Improving OTMA Security and Usability Automatically refresh OTMA cached userids when they are changed in RACF Secure connections for OTMA clients using RACF without having to enable transaction and command security Improve dispatching during busy periods by allowing user specified limits for the save area prefix allocation for OTMA clients Allow conversations to be released easily via /EXIT CONV by showing the conversation identifier via QUERY OTMATI Enable callable service requests from OTMA routing exits DFSYPRX0 OTMAYPRX and DFSYDRU0 OTMAYDRU Allow OTMA Input/Output Edit Exit DFSYIOE0 OTMAIOED to modify the message Why this is important Improves security Removes performance bottleneck for peak loads Improves usability of user exits IMS 14

13 Increase scalability for APPC conversations Automatic scaling for APPC conversations and flood prevention IMS system defaults for maximum number of active conversations queued conversations in 64-bit storage IMS 14 User can specify limits with APPCMAXC= parameter in DFSDCxxx When the number of APPC conversations exceeds the limit, new conversations are queued to 64-bit storage When the number of queued conversations is reached, new conversations are rejected Why this is important Improves IMS resiliency and reduces unplanned outages due to APPC message flooding 12

14 Enable IMS Application callout request to specify control data Enhanced DL/I ICAL function allows user information to be passed to IMS Connect and its clients XML string can have IBM and/or user defined tags IMS 14 All tags are passed to each component to interrogate Some usage scenarios Pass security credential information to an external web service which can be used to authenticate the callout request Override the XML converter name specified in the OTMA destination descriptor or the static endpoint address value in the WSDL for SOAP Gateway Why this is important Strengthens callout security with the security token included in control data Reduces the number of OTMA destination descriptors due to unique converter names Provides flexible and dynamic endpoint routing 13

15 IMS Data -The core of your business

16 Growing your Full Function Databases High Availability Large Database (HALDB) enables independent partitions for full function databases allowing growth greater than 40 terabytes Supports OSAM and VSAM Use HALDB Online Reorganization to reorganize partitions without an application outage Allow OSAM database growth by supporting 8GB OSAM for HALDBs You can choose either 8GB OSAM HALDB or the use of Online Reorganization for each database Reduce 24-bit storage usage for OSAM Database control blocks Why this is important OSAM DEB Increased extension scalability moved for OSAM into databases 31-bit storage IMS 14

17 Growing your Fast Path Data Entry Databases Fast Path 64-bit buffer manager takes the guess work out of defining Data Entry Database (DEDB) buffer pools IMS manages the subpools automatically Multiple subpool sizes are used based on the database High Speed Reorganization (HSRE) and High Speed Sequential Processing (HSSP) buffers can now use 64-bit storage IMS 14 Why this is important Reduces need for 31-bit common storage (ECSA) Allows the HSSP and HSRE utilities to run against UOWs with a very large number of segments

18 Now is the time to enable the IMS Catalog What is the Catalog used for? Comprehensive view of trusted 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 Development Enables broad IMS integration into the IBM and non-ibm portfolio of tools Use the IMS Catalog as the source for all program and database schemas IMS loads resource information from the catalog ACBLIB is no longer used or needed by IMS IMS 14 Why this is important Removes the external need for PSBGEN, DBDGEN, and ACBGEN

19 Defining IMS Databases with Agility Use a command to dynamically change an OSAM or VSAM buffer pool without recycling IMS systems Enable application programs to use different logical versions of the same database with database versioning without an application change Change the structure of an HALDB or DEDB using HALDB Alter or DEDB Alter without a DB outage Use Data Definition Language (DDL) to make database schema changes No longer need to use system definition and generation to introduce new programs and databases IMS 14 Why this is important DDL is the industry standard DDL-authoring tools are prevalent in the market

20 Dynamic Database Definition Resources Terminology Dynamic Database Definition Resources Refers to objects such a DBDs, PSBs etc. The objects coded by Macro statements Dynamic Resource Definition Resources Refers to Databases, Program, Transactions etc. The resources that were coded in a SYSGEN 19

21 Dynamic Database Definition IMS 14, enables you to dynamically define and modify IMS database and application program resources in the IMS catalog Leverages the use of industry standard Data Definition Language (DDL) commands An alternative to the existing DBDGEN, PSBGEN, ACBGEN, and Online Change processes Provides an audit trail to capture information about catalog updates Once enabled, the runtime database and program resource definitions are loaded from the catalog by IMS ACB, DBD, and PSB libraries no longer used by IMS at runtime, but the libraries can be maintained Possibly needed for tools, utilities and processes relying on the libraries User responsible for keeping ACB, DBD, and PSB resources in sync with IMS catalog resources 20

22 Dynamic Database Definition Benefits Dynamic implementation of IMS database and program resource definitions No system outage required to create or modify IMS databases Improved IMS database availability Reduced time and complexity to create or modify an IMS database DDL authoring tools can be used to model database changes, create DDL command streams and activate database definition changes Improved Database Administrator productivity Existing PSBGEN, DBDGEN, and ACBGEN processes no longer needed Aligns IMS with industry practices and expectations 21

23 Database Definition Language for IMS Use DDL to create, modify, and delete IMS databases and application program resources and activate definitions in a target IMS system immediately no gen processes no Online Change process DDL commands can be submitted from a Java client using the IMS Universal Drivers or through tools that support the Universal Drivers DDL commands supported CREATE DATABASE CREATE TABLE CREATE TABLESPACE CREATE PROGRAMVIEW ALTER DATABASE ALTER TABLE ALTER TABLESPACE DROP DATABASE DROP TABLE DROP TABLESPACE DROP PROGRAMVIEW COMMENT ON The IMS catalog and directory are required to use DDL definitions 22

24 IMS Catalog

25 IMS Catalog Review Contains information about IMS program and database resources, and application metadata Includes all program and database related information defined to an IMS system, including databases, fields, segments, data types, and more Changes made to any of these IMS resources are reflected in the catalog metadata IMS HALDB database PHIDAM / OSAM HALDB database with 4 Data Set Groups Secondary Index is a HALDB database Catalog DBDs and PSBs are shipped with IMS

26 Types of IMS Metadata DB PSB/DBD resources Database structure definitions Physical database definitions Segment definitions Field definitions Application Data types Application defined fields Encodings Redefines Catalog IMS database TM User defined types Structures MODBLKS resources Program, Transaction, Database and Fast Path Routing code definitions Repository Primary Repository Secondary VSAM data sets Repository Spare

27 IMS Catalog Review Using the IMS Catalog and ACBLIB IMS database and program resource definitions start with DBD and PSB macro coding, followed by DBDGEN and PSBGEN Followed by ACBGEN & Catalog Populate Utility processing Catalog and active ACB member are kept in sync via the ACBGEN process IMS runtime database and program control blocks obtained from ACBLIB IMS metadata is available from the catalog PSB source PSBGEN PSBLIB ACBLIB IMS IMS Explorer ACBGEN & Catalog Populate DBD source DBDGEN DBDLIB Catalog

28 IMS Catalog Benefits Trusted IMS metadata information stored in the catalog Comprehensive view of IMS database, application and program metadata managed by IMS with standard access methods (JDBC/SQL/DLI) Facilitates large scale Open Database solutions Metadata discovery and exchange possible through the IMS Explorer for Development and IMS Open Database Supports IMS integration with IBM and ISV tooling (Data Studio, Cognos, QMF, Optim Development Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc )

29 IMS Resource Definitions Today IMS databases and programs are defined in Catalog Contains multiple instances of database, application and program metadata ACBLIB Contains the active ACB control blocks defining the application DBD and PSB resources Used by IMS to load the ACB control blocks at runtime DRD Repository Defines the resources available for use in an IMS system see diagram on following pages

30 Running with IMS Catalog and IMS COLD Start Catalog IVPDB1 IVPDB1 ts22 ts23 IMS1 Resident DMB Pool ACBLIBA IVPDB1 ts23 DBs Repository DB IVPDB1

31 Running with IMS Catalog and ACBLIB Appl call to IVPDB1 database IMS obtains the runtime control blocks from ACBLIB Catalog metadata available IMS1 Resident DMB Pool IVPDB1 ts23 Catalog IVPDB1 IVPDB1 ACBLIBA IVPDB1 ts22 ts23 ts23 DBs IVPDB1 Repository DB IVPDB1

32 IMS Management of ACBs

33 IMS Management of ACBs In IMS14, customers may enable IMS management of ACB control blocks for database and program views Build and define database and program views using SQL DDL statements No longer need to code DBD and PSB macros No longer need DBD, PSB, and ACB libraries No need to use Online Change or recycle IMS system to activate an ACB When IMS receives the DDL statements ACBs are generated automatically, but cannot be used until stored in the directory If directed, IMS can add the ACBs to the IMS directory automatically ACBs not activated automatically are stored in a staging directory dataset and can be added to the IMS directory using an IMPORT command IMPORT DEFN SOURCE(CATALOG) SQL DDL statements can be submitted to IMS through products such as the IMS Enterprise Suite Explorer for Development or Java programs

34 IMS Management of ACBs ACBs are stored in the IMS directory which is an extension of the catalog The directory has functionality similar to an ACBLIB Directory records have a format much like the ACBs in an ACBLIB The directory is kept in sync with the catalog IMS maintains a boot strap data set (BSDS) containing information about the directory data sets IMS will self-manage the IMS directory data sets Directory data sets are automatically allocated another data set is allocated when a directory data set becomes full When IMS ACB management is enabled IMS will reference the directory data sets to get the runtime application control blocks IMS will use the directory to indicate which members are active in the IMS catalog 1:1 relationship between ACBs in the directory and the catalog If the catalog is shared then directory data sets are shared If the catalog is non-shared then directory data sets are non-shared

35 IMS 14 Catalog Partition A Partition B Partition C Catalog Database IMS Explorer For Development DDL Catalog Partition A Partition B Catalog Secondary Index IMS Directory Directory BSDS An IMS Catalog is made up of several components A catalog HALDB database (many partitions, 4 Data Set Groups) A Secondary Index Directory dataset(s)

36 Details: IMS Catalog with Managed ACBs Definition of the ACB related data sets is automatic IMS creates directory data sets as PDSEs Data set names will be an extension of the HALDB catalog data set name <HALDB data set prefix>.di<suffix> Example» IMSTEST.DFSCD000.DI01001» IMSTEST.DFSCD000.DI01002 Suffix will be automatically created by IMS Allows IMS to support multiple directory data sets automatically IMS will use DFSDIRxx DD for directory data set allocation If multiple directory data sets are allocated by IMS xx starts with 01 and will be incremented by 1

37 Details: IMS Catalog with Managed ACBs Maintaining IMS release independence of ACB members IMS maintains catalog release independence IMS 14 catalog is compatible with IMS 12 or 13 IMS 12 or 13 catalog is compatible with IMS 14 without the directory ACB members are still release dependent Long term direction is release independent ACBs Until ACBs are release independent IMS catalog will use multiple data sets for each release Examples» IMSTEST.DFSCD000.DI01001 > Directory for V14» IMSTEST.DFSCD000.DI01002 > Directory for V14» IMSTEST.DFSCD000.DI02001 > Directory for V14+1» IMSTEST.DFSCD000.DI02002 > Directory for V14+1

38 Details: IMS Catalog with Managed ACBs PDSE Benefits Automatic reuse of space No manual compression required Allows up to 123 extents PDSE directory automatically extends No out of directory block errors Maximum size of a PDSE member is 15,728,639 records Maximum number of PDSE members is 524,236 All updates to a PDSE are atomic, unlike a traditional PDS Canceled jobs or system crashes will not corrupt a PDSE Can be shared across a SYSPLEX

39 Enabling IMS Catalog ACB Management Indicate the IMS catalog and IMS ACB management are enabled in the CATALOG section of the DFSDFxxx PROCLIB member CATALOG SECTION parameters CATALOG=NO Specifies the IMS catalog is disabled Default value and value if CATALOG section is omitted CATALOG=YES Specifies the IMS catalog is enabled Catalog runtime resources must be included in the IMS system DFSCP000, DFSCD000, and DFSCX000

40 Enabling IMS Catalog ACB Management CATALOG SECTION parameters (continued) ACBMGMT=CATALOG IMS catalog must be enabled and populated using MANAGEDACBS=SETUP IMS manages runtime application control blocks using the IMS catalog IMS will abend if the internally managed directory data sets are not found DBD, PSB and ACB libraries no longer required ACBMGMT=ACBLIB IMS catalog is enabled and populated User manages the runtime control blocks using gen utilities, ACBLIB, and OLC IMS catalog will be used by IMS to retrieve metadata Default option if IMS catalog is enabled <SECTION=CATALOG> CATALOG=Y /*Enable IMS catalog*/ ALIAS=DFSC /*Use standard catalog prefix DFSC*/ ACBMGMT=CATALOG /*IMS manages the runtime application control blocks*/ RETENTION=(INSTANCES=5,DAYS=365) /*Retention criteria*/

41 Pre-IMS 14: IMS with Catalog and ACBLIB Production IMS Development IMS DFSDFPRD <SECTION=CATALOG> CATALOG=Y DFSDFTST <SECTION=CATALOG> CATALOG=Y Tools PSB source PSBGEN PSBLIB ACBLIB IMS ACBGEN & Catalog Populate IMS Explorer DBD source DBDGEN DBDLIB Catalog

42 IMS 14: Transition to IMS Catalog Managed ACBs Tools PSB source Development IMS PSBGEN PSBLIB Optional DFSDFTST <SECTION=CATALOG> CATALOG=Y ACBMGMT=CATALOG IMS Explorer SQL DDL DBD source DBDGEN DBDLIB ACBGEN & Catalog Populate Utility Catalog IMS Directory BSDS DFSDFPRD <SECTION=CATALOG> CATALOG=Y ACBMGMT=ACBLIB Tools Production IMS PSB source PSBGEN PSBLIB ACBGEN & Catalog Populate ACBLIB IMS IMS Explorer DBD source DBDGEN DBDLIB Catalog

43 IMS 14: Transition to IMS Catalog Managed ACBs Tools Application Development IMS DFSDFTST <SECTION=CATALOG> CATALOG=Y ACBMGMT=CATALOG Catalog IMS IMS Explorer SQL DDL Directory BSDS Production IMS DFSDFPRD <SECTION=CATALOG> CATALOG=Y ACBMGMT=CATALOG Tools PSB source PSBGEN PSBLIB Optional IMS Explorer SQL DDL DBD source DBDGEN DBDLIB ACBGEN & Catalog Populate Utility Catalog IMS Directory BSDS

44 IMS 14: Total Transition to IMS ACB Management Tools Application Development IMS DFSDFTST <SECTION=CATALOG> CATALOG=Y ACBMGMT=CATALOG IMS Explorer SQL DDL Catalog Directory BSDS IMS Tools Production IMS DFSDFPRD <SECTION=CATALOG> CATALOG=Y ACBMGMT=CATALOG IMS Explorer SQL DDL Catalog Directory BSDS IMS

45 Running with IMS Catalog Managed ACBs IMS databases and programs are defined in IMS Catalog Defines the active instance of a database or program resource Contains additional instances of database, application and program metadata Contains the application control blocks (ACBs) DRD Repository Defines the resources available for use in an IMS system see diagram on following pages

46 Running with IMS Catalog Managed IMS COLD Start Catalog IVPDB1 IVPDB1 ts22 ts23 IMS1 IMS Directory Resident DMB Pool IVPDB1 ts23 DBs Repository BSDS DB IVPDB1

47 Running with IMS Catalog Managed ACBs Appl call to IVPDB1 database IMS obtains the runtime application control blocks from the catalog Catalog metadata available Catalog IVPDB1 IVPDB1 ts22 ts23 IMS1 IMS Directory Resident DMB Pool IVPDB1 ts23 IVPDB1 ts23 DBs IVPDB1 Repository BSDS DB IVPDB1

48 IMS ACB Management Advantage Optional No longer used by IMS PSBLIB PSB source IMS Explorer For Development DDL Catalog DBDLIB DBD source ACBLIB IMS Create DDL statements to build or modify IMS database or program resources IMS processes SQL DDL statements Activation of some DDL commands can happen automatically or commands are held in pending activation state until an IMPORT command is entered IMPORT DEFN SOURCE(CATALOG) IMS application control blocks will be loaded from the catalog at runtime

49 Maintaining DBDLIB, PSBLIB and ACBLIB Two methods to retain and maintain DBD, PSB and ACB libraries Run the ACB Generation & Catalog Populate utility (DFS3UACB) Builds the application control blocks in ACBLIB Updates the IMS catalog metadata and flags the active resources Activates the ACBs by loading them into the IMS directory OR Run the ACB Maintenance utility, DFSUACB0 Builds the application control blocks in ACBLIB AND Run the IMS Catalog Populate utility, DFS3PU00 Updates the IMS catalog metadata and flags the active resources Activates the ACBs by loading them into the IMS directory

50 Special Cases with IMS Managed ACBs IMS catalog supports GSAM databases Today, GSAM database control blocks are stored in DBDLIB and PSBLIB, not in ACBLIB With ACB management, GSAM databases will be stored in the IMS catalog IMS will use the directory to load the GSAM runtime control blocks at each dependent region schedule IMS catalog supports Logical DBDs Today, Logical database control blocks are stored in the DBDLIB, not in ACBLIB With ACB management, Logical DBDs will be stored in the IMS catalog Logical DBD runtime control blocks will not be loaded from the directory Instead, loaded during construction of the runtime control blocks Support for Resident PSBs and DBDs is unchanged Support for DOPT PSBs is unchanged PSBs will be read from the IMS Catalog FP MSDBs will not be supported with IMS ACB management

51 Batch Implications Batch jobs can be enabled for IMS management of ACBs Specify use of the IMS catalog and ACB management DFSDFxxx PROCLIB member added to JCL parm or User exit DFS3CDX0 can be used as an alternative to modifying the JCL IMS will load application control blocks from the catalog If present, IMS ignores DBDLIB and PSBLIB or ACBLIB Overrides the DLI or DBB processing option specified in the JCL When IMS is managing ACBs but the batch job needs to use DBDLIB/PSBLIB or ACBLIB Do not specify a DFSDFxxx PROCLIB member or use the DFS3CDX0 exit User can build DBDLIB and PSBLIB from the catalog using the IMS Catalog Database Library utility, DFS3LU00 ACBLIB can be created from DBD and PSB library members User must keep the DBD and PSB library members in sync with the catalog If used, ACBLIB if must also be kept in sync with catalog Batch regions running in a system without the catalog and ACB management enabled IMS continues to use DBDLIB and PSBLIB or ACBLIB

52 Existing DB Utilities and Tools Existing database batch utilities must be updated to access the IMS catalog Same as batch support Requires DFSDFxxx PROCLIB member on JCL or Use DFS3CDX0 user exit as alternative to modifying the JCL OR Users can build DBDLIB & PSBLIB from the catalog IMS Catalog Database Library utility (DFS3LU00) User has responsibility to keep the DBD & PSB library members in sync with the catalog

53 New and Modified IMS Utilities

54 New IMS Catalog Database Library Utility DFS3LU00 Used to build DBD and PSB source from the IMS catalog and related DBDLIB, PSBLIB, and ACBLIB members Utility will read from catalog and transform members into source code Similar to IMS Enterprise Suite Explorer for Development function Source may be used to generate DBDLIB, PSBLIB and ACBLIB members Or Utility can create DBDLIB and PSBLIB members Utility may be used until vendor and customer tools are updated to use the IMS catalog instead of DBDLIB, PSBLIB and ACBLIB

55 New IMS Catalog Database Library Utility - DFS3LU00 DBDLIB DFSDFxxx PSBLIB Catalog Catalog Database Library Builder Utility DFS3LU00 ACBLIB SYSIN DBDSLIB (source) PSBSLIB (source)

56 Modified IMS Catalog Populate Utility -DFS3PU00 Introduced in IMS 12 to perform initial load of IMS catalog metadata from the members in one or more ACBLIBs Can run in IMS DL/I batch or IMS BMP regions Can automatically create the IMS catalog database data sets 4 Data Set Groups, ILDS, Primary and Secondary Indices User may define allocation attributes for the data sets in DFSDFxxx PROCLIB member OR Utility can estimate the size of the catalog database data sets based on size of the ACB library and expansion percentages specified in the DFSDFxxx PROCLIB member without updating the IMS catalog

57 Modified IMS Catalog Populate Utility -DFS3PU00 When an IMS 14 system is enabled for IMS ACB management (DFSDFxxx: SECTION=CATALOG CATALOG=YES and ACBMGMT=CATALOG) When adding ACBs to an IMS system Will upgrade the IMS catalog to contain some additional information Can activate application control blocks read from the ACBLIB Stores ACBs in the IMS directory for the active IMS catalog members OR Will upgrade the IMS catalog to contain some additional information Can save the ACBs to an IMS-managed staging directory data set for deferred activation Saves ACBs in the staging directory data set and can be activated in the IMS directory later via an IMPORT command» IMPORT DEFN SOURCE(CATALOG)

58 Modified IMS Catalog Populate Utility -DFS3PU00 When an IMS 14 system is enabled for IMS ACB management (DFSDFxxx: SECTION=CATALOG CATALOG=YES and ACBMGMT=CATALOG) Can estimate the size of the IMS catalog datasets Based on scanning members in the input ACB libraries Can automatically build the following data sets One or more directory data sets Runtime application control blocks flagged as active in the IMS catalog A boot strap data set Details about the IMS directory data sets A staging directory data set Pending IMS directory members If any of the IMS catalog database data sets have not been created Utility creates them automatically

59 Modified IMS Catalog Populate Utility - DFS3PU00 SYSINP DD is an option control statement Changed options to control utility actions if IMS ACB management is enabled DUPLIST New DFS* informational messages DFS4436I, DFS4531I, DFS4522I, DFS4542I, DFS4539I Lists DBD or PSB resources from input ACBLIB that are not added to the IMS catalog, the IMS directory or the staging directory data set because duplicate instance is already in the IMS catalog or IMS directory ISRTLIST New DFS* informational messages DFS4520I, DFS4521I, DFS4537I, DFS4538I If IMS ACB management is enabled, lists DBD or PSB resources that are either added to the IMS directory or saved to the staging data set for importing into the IMS directory later

60 Modified IMS Catalog Populate Utility -DFS3PU00 SYSINP DD is an option control statement New option to control utility actions if IMS management of ACBs is enabled MANAGEDACBS= Use this control statement to: Set up IMS to manage the runtime application control blocks (ACBs) for your databases and programs Update an IMS system that manages ACBs with new or modified ACBs from an ACB library Save ACBs from an ACB library to a staging data set for later importing into an IMS system that manages ACBs The MANAGEDACBS= statement is specified as follows:

61 Modified IMS Catalog Populate Utility -DFS3PU00 SETUP Creates a new IMS directory and corresponding BSDS required by IMS to manage ACBs Existing instances of the IMS directory data sets are scratched and recreated Loads the IMS directory with the ACBs contained in the concatenated ACBLIBs STAGE Builds a staging directory data set for ACBs to be added or replaced in an existing IMS directory ACBs in the staging directory data set are not activated until you issue the IMPORT DEFN SOURCE(CATALOG) command Do not specify STAGE when doing an initial load of the IMS catalog or before you enable the IMS management of ACBs STAGE parameter is for staging updates to existing IMS directory data sets only If the staging data set exists, it is scratched and recreated Any application control blocks in the existing data set are lost Copies all ACBs in the ACBLIBs that do not already exist in the IMS system to the staging directory data set If an ACB already exists in the IMS system Saves the ACB to the staging data set based on whether the ACB timestamp meets the criteria of the UNCOND or LATEST parameter

62 Modified IMS Catalog Populate Utility -DFS3PU00 STAGE (continued) LATEST (default value) If an ACB member exists in the IMS system do not save an instance of the ACB to the staging directory data set unless the ACBLIB member has a later timestamp than the ACB in the IMS system UNCOND If an ACB already exists in the IMS system save an instance of the ACB to the staging data set unconditionally, unless the timestamp of ACBLIB member is the same as the timestamp of the ACB in the IMS system UPDATE Updates an existing IMS directory from the input ACBLIBs Do not specify UPDATE when doing an initial load of the IMS catalog or before you enable IMS ACB management UPDATE parameter is for updating existing IMS directory data sets only Inserts ACBs not already in the IMS system into the IMS directory unconditionally

63 Modified IMS Catalog Populate Utility - DFS3PU00 UPDATE (continued) If an ACB exists in the IMS system Replaces the ACB depending on the timestamp of the ACBLIB member and the specification of the UNCOND or LATEST parameter LATEST (default value) If an ACB already exists in the IMS system do not replace it with a new instance of the ACB unless the ACBLIB member has a later timestamp than the ACB in the IMS system UNCOND If an ACB already exists in the IMS system replace it with an instance of the ACB from an ACBLIB unconditionally, unless the timestamp of the ACB in the ACBLIB is the same as the timestamp of the ACB in the IMS system

64 Loading the IMS Catalog with the DFS3PU00 Utility Requirements Enable the IMS catalog database by generating and loading the catalog DBDs, PSBs, and ACBs Code the DFSDFxxx PROCLIB member <SECTION=CATALOG> to enable catalog Define the IMS catalog HALDB master database and partitions to DBRC or the IMS Catalog Partition Definition data set For GSAM databases, you must include both the DBDLIB and PSBLIB used to generate the ACBLIB members For logical databases, you must include the DBDLIB used to generate the ACBLIB members DFS3PU00 can initially load the IMS catalog by using the IMS-provided PSB DFSCPL00, which includes a PCB defined with PROCOPT=L Running the DFS3PU00 utility with the PSB DFSCPL00 deletes any existing records in the IMS catalog DFS3PU00 can also update the IMS catalog by using PSB DFSCP001 (DLI, DBB, BMP)

65 IMS Catalog Populate Utility - DFS3PU00 IMSACBnn IMSACB02 IMSACB01 ACBLIBs MANAGEDACBS= SYSINP DFSDFxxx member IMS Catalog DBDLIBs Catalog Populate Utility DFS3PU00 Catalog Directory PSBLIBs Logs SYSPRINT

66 IMS ACBGEN & Catalog Populate Utility - DFS3UACB IMS catalog updated by the ACBGEN and Catalog Populate utility Utility introduced in IMS 12 Generates the members in ACBLIB and inserts corresponding metadata in the IMS catalog within the same job step Enhancements in IMS 14 If ACBLIB is used to manage runtime application control blocks use the ACB Generation and Catalog Populate utility as is generates ACB member(s) in an ACBLIB and creates corresponding DBD and PSB metadata in an IMS catalog in a single step If IMS management of ACBs is enabled and DDL used to update the catalog DFS3UACB utility might not be needed Runtime application control blocks will be obtained from the IMS catalog Should not be needed, except maybe for tools Same enhancements as the IMS Catalog Populate utility, DFS3PU00 Run in load mode (PSB DFSCPL00) or update mode (PSB DFSCP001)

67 IMS Catalog Record Purge Utility - DFS3PU10 IMS Catalog Record Purge utility used to remove the segments that represent a DBD or PSB instance, all instances of a DBD version, or an entire DBD or PSB record from the IMS catalog DFSDFxxx PROCLIB member provides defaults for utility When the active instance of a database or program resource is deleted from the IMS catalog The IMS directory data set member will also be deleted

68 Changing Catalog Resources An IMS catalog with a directory enables the concept of dynamic database definitions Simplified methods to change database and program resources 1. Issue DDL to make resource definition changes Catalog is updated, ACBLIB members are not updated Catalog updates can be committed or updates are held in a pending active state Final environment with no ACBLIB needed 2. Update DBD / PSB source code to make resource definition changes Run DBDGEN / PSBGEN and the ACBGEN & Catalog Populate Utility Catalog is updated and ACBLIB members are updated Catalog updates can be committed or updates can be held in a pending active state Migration / Coexistence technique until DDL is used exclusively

69 Activate Pending Changes With the IMPORT Command IMPORT command has been extended to activate and load the pending resource definition changes in the IMS catalog Similar to OLC commands which trigger IMS to load changes from ACBLIB into the online system Format of the command IMPORT DEFN SOURCE(CATALOG) Operates on the entire catalog at one time Cannot import individual catalog members all or nothing During the IMPORT IMS will: Query the status of the resources affected by the changes Activate the changes Prepare and identify resources being changed for affected resources, quiesce all activity and take them offline Move the pending changes from the IMS catalog into the directory Coordinate the resource changes across the IMSplex for shared IMS catalogs Make the resources available, activate the previously quiesced resources

70 Activation Processing IMPORT does not require DDL use to activate resource changes Catalog resource updates can be made by DDL or by IMS Catalog Populate utility or the purge utility For an Online IMS If the catalog is shared Single IMS updates the catalog & directory Sharing IMS systems get refresh from catalog & directory If the catalog is non-shared Each IMS needs to update their own catalog & directory If mixed CATALOG & ACBLIB environment Activation occurs on an IMS using the directory User must do activation via OLC for an IMS using the ACBLIB If an IMS is Offline Does not participate in the coordination of the resource activation When the IMS restarts the catalog will indicate which instance of the member is now active and it will be loaded

71 Deleting Catalog Resources with DDL Deleting a resource with DDL Processing happens automatically during DDL IMPORT command is not required to delete catalog resource

72 Example: IMS with ACBLIB & Catalog Code changes to IVPDB1 DBD Run DBDGEN Create staging DBDLIB member Submit ACBGEN & Catalog Populate utility Create staging ACBLIB member Create pending catalog member IMS1 Resident DMB Pool IVPDB1 ts23 Catalog IVPDB1 ts22 IVPDB1 ts23 IVPDB1 ts24 Staging ACBLIB Staging DBDLIB IVPDB1 ts24 IVPDB1 ACBLIBA IVPDB1 ts23 DBs IVPDB1 Repository DB IVPDB1

73 Example: IMS with ACBLIB & Catalog (cont) Take changed resources offline UPDATE DB STOP(ACCESS) Perform online change INIT OLC PHASE(PREPARE) TYPE(ACBMBR) NAME(.) INIT OLC PHASE(COMMIT) IMS1 Resident DMB Pool IVPDB1 ts24 Catalog IVPDB1 IVPDB1 IVPDB1 ACBLIBA IVPDB1 ts24 ts22 ts23 ts24 Staging ACBLIB IVPDB1 ts24 DBs IVPDB1 Repository DB IVPDB1

74 Example IMS with ACBLIB & Catalog (cont) After online change resource is available for use Catalog IVPDB1 IVPDB1 IVPDB1 ts22 ts23 ts24 IMS1 Resident DMB Pool IVPDB1 ts24 ACBLIBA IVPDB1 ts24 DBs IVPDB1 Repository DB IVPDB1

75 Example: IMS with DDL and Catalog Issue DDL to update the IVPDB1 database Pending catalog member created IMS Catalog IVPDB1 IVPDB1 IVPDB1 (Active) ts22 ts23 ts24 IMS1 Resident DMB Pool IVPDB1 ts23 IMS Directory IVPDB1 ts23 DBs IVPDB1 Repository DB IVPDB1 BSDS

76 Example: IMS with DDL and Catalog (cont) Perform IMPORT from catalog IMPORT DEFN SOURCE(CATALOG) IMS Catalog IVPDB1 IVPDB1 IVPDB1 (Active) ts22 ts23 ts24 IMS1 Resident DMB Pool IVPDB1 ts24 IMS Directory IVPDB1 ts24 DBs IVPDB1 Repository DB IVPDB1 BSDS

77 Example: IMS with DDL and Catalog (cont) After IMPORT, the changed resource is available for use IMS Catalog IVPDB1 IVPDB1 IVPDB1 (Active) ts22 ts23 ts24 IMS1 Resident DMB Pool IVPDB1 ts24 IMS Directory IVPDB1 ts24 DBs IVPDB1 Repository DB IVPDB1 BSDS

78 Architectural Considerations Dynamic Database Definition function is disabled by default IMS catalog must be defined, populated and enabled IMS managed ACBs must be enabled IMS directory data sets and the BSDS can be built by IMS Internally created tasks are used to update the catalog number of PSTs may need to be increased if getting near your maximum Increased usage of 64 bit storage with the function enabled improved performance Internal construction of DMBs and PSBs are in a new code path Any customized exits used in the generation of these control blocks? Requires CSL - SCI and OM DBDLIB, PSBLIB and ACBLIB will no longer be maintained by IMS DBDGEN, PSBGEN and ACBGEN can be manually maintained

79 Operational Considerations Operational Characteristics IMS will manage the directory Databases and programs can be created and updated through DDL No longer need to maintain DBD source, PSB source, DBDLIB, PSBLIB, and ACBLIB Migration / Coexistence path will allow for continued usage of DBD and PSB source during transition Operational Considerations Catalog should be updated through DDL Catalog can still be updated with the Catalog Populate utility Allows support for existing path of source to catalog via DBDGEN / PSBGEN / ACBGEN Reorganize the IMS catalog database with OLR Image Copy the IMS catalog on a regular basis Include IMS catalog components in a Global Mirroring consistency group Audit data will be collected for IMS catalog database updates

80 Migration Considerations Use of the new IMS ACB management feature is optional Define HALDB catalog database, install/gen catalog DBD/PSB/ACBs, and enable the IMS catalog and IMS ACB management DFSDFxxx PROCLIB member <SECTION=CATALOG> CATALOG=YES ACBMGMT=CATALOG Run the Catalog Populate utility with MANAGEDACBS=SETUP Creates a new IMS directory and corresponding BSDS required by IMS to manage ACBs Loads the IMS directory with the ACBs contained in the concatenated ACBLIBs IMS obtains runtime ACB control blocks from the IMS catalog No longer need to gen ACB control blocks using utilities No longer need to use Online Change to in-effect ACB changes DBD, PSB and ACB libraries can be retired Start adding and changing database definitions dynamically using DDL

81 Accessing Information about Catalog Resources Partition A Partition B Partition C IMS Explorer For Development DDL Catalog Partition A Partition B IMS Directory API Tool BSDS Catalog API invoked by a Tool or Program Reads the directory only Does not use DL/I to read the catalog

82 IMS Catalog API The Catalog API provides a way to obtain information about IMS catalog resources Retrieve DBD information - mapped by IDBD macro (DBDLIB format) Retrieve PSB information - mapped by DFSIPSB macro Retrieve DBD or PSB in ACBLIB member format List members - mapped by ACBDIR macro Specify current or pending member definition on the request Handles allocation of the catalog data sets Transforms the requested data into a specified response format Must be called from Assembler program API does not perform DL/I calls

83 Change or add a DEDB Area without taking the Database offline Builds on IMS 13 DEDB Alter capability to change the physical attributes of a DEDB Area without a DB outage Can be used with Sequential Dependents (SDEPs) Add Areas to a DEDB Add a Segment Edit/Compression exit Allow alter when using XRF/FDBR with ACBSHR=N IMS 14 Why this is important Improves data availability by allowing selected changes to a DEDB without taking the database offline

84 Reduce unplanned outages due to insufficient space for Sequential Dependents IMS can automatically manage DEDB sequential dependent storage when processing of the SDEPs is asymmetric across the IMS systems Automatic SDEP buffer management reduces the need to perform manual steps to prevent an out of space condition in the SDEP that could cause a database outage. SDEP management accounts for asymmetric processing to ensure enough CIs are released Enable and control through new parameters in DFSDFxxx SDEPAUTO, SDEPFREQ, SDEPEXP, SDEPTIME IMS 14 Why this is important Reduces unplanned outages for applications and/or databases due to insufficient space for SDEPs 92

85 View data with IMS Explorer for Development Visualize IMS database structure as defined to IMS Change IMS Database and Program Definitions source Graphically access IMS data using SQL View your mainframe datasets Submit JCL and inspect output in JES Explore the IMS Catalog Invoke transactions for unit test Enable services for the IMS Mobile Feature Pack Issue DDL to manage IMS database schema IMS 14 Automatic Generation

86 Improving Availability

87 Sharing the IMS Message Queues Allows multiple IMS systems to share messages on a single set of queues in a Coupling Facility across a Parallel Sysplex Improves workload distribution, increases availability and can easily add capacity Indicates to the Queue Space Notification exit, DFSQSSP0, how much of the message queue structure is used Allows BMP-inserted transaction messages to be eligible for local-first processing IMS Application Program (Transaction) CF Message Queues IMS Application Program (Transaction) IMS 14 Why this is important Can improve availability and reduce cost 95

88 Dynamically defining resources without an IMS outage Improve the availability of the IMS online environment by dynamically defining certain types of resources Database Directory, Program Directory, Transaction, Routing Code, Descriptors OTMA Destination Descriptor IMS Connect configuration Enabled through commands and/or user exit Enhanced to fully manage MSC resources Create and Delete commands for MSC resources IMSRSC Repository enabled for MSC IMS 14 Why this is important Improved availability when changing definitions Elimination of need for system definition and system generation processes

89 Improving usability for the IMS Repository The IMS repository is a common store for managing resource definitions in an IMSplex Provides consistent definitions across IMS systems Allows resources to be removed from sysgen yet preserved for cold start Enable AUTOEXPORT to IMSRSC repository from IMS at end of IMS system checkpoint Provide the ability to show changes that have not yet been hardened to the IMS repository QUERY. SHOW(EXPORTNEEDED) IMS 14 Why this is important Improves usability of the IMS Repository Reduces the chance of an IMS terminating without hardening changes to the IMS Repository

90 Enable faster rollout of application changes with less manual effort IMS optimizes the scheduling process allowing an application to remain scheduled waiting for the next input message Eliminates unnecessary application program termination and rescheduling improving performance and reducing CPU usage Pseudo Wait-for-Input (PWFI) option for MPP and JMP regions BMP transactions defined WFI Adds to operational processes to refresh application New command to terminate these applications in order to refresh an application UPDATE PGM. START(REFRESH) IMS 14 Why this is important Enables faster rollout of application changes with less manual effort Reduces data integrity exposures due to missed application changes 98

91 Refresh user exits without an IMS outage Improved usability for user exits Specify multiple exit routines for a single user exit type Refresh User Exits dynamically using a command Additional exits with this capability Type-2 AOI user exit (AOIE DFSAOE00) New IMS Monitor (IMSMON) user exit type Why this is important IMS 14 Increases availability for IMS by allowing refreshing of user exits without an IMS outage Improves usability for tools that provide monitor functions by providing an API for extensions 99

92 Managing change in IMS Connect Commands allow dynamic change for IMS Connect configuration Allow additional commands to dynamically manage IMS Connect resources Introduces DELETE PORT and DATASTORE commands Enhances UPDATE PORT and DATASTORE commands to allow changes to selected attributes IMS 14 Introduces CREATE and DELETE IMSPLEX commands Provides synchronous command responses for selected IMS Connect Why this is important Increases availability allowing dynamic creates, deletes and updates for selected resources Increases usability providing a synchronous command response 100

93 Improving Usability for External Subsystem Connections

94 Improving Usability for External Subsystems Provide SubSystem Type values to define IBM MQ and WebSphere Optimized Local Adapter subsystems in addition to DB2 SST = DB2 MQ WOLA Positional SSM definitions assume SST=DB2 Commands and log records changed to show SST value for subsystem /DIS SUBSYS /DIS OASN SUBSYS IMS 14 Why this is important Improves usability by allowing you to distinguish between DB2, MQ and WOLA when multiple external subsystems are connected to IMS 102

95 Simplifying the FDBR Resolve In-Doubt Notification Exit Simplify the resolution of in-doubt work for an external subsystem during Fast Database Recovery (FDBR) Provides a sample Resolve In-Doubt Notification Exit, DFSFIDN0, that can trigger automation to resolve in-doubt work without having to write custom code IMS 14 Issues a message for each in-doubt ESS UOR with the subsystem information Automation can monitor the messages and act upon the in-doubt UOR Why this is important Improves usability when using both FDBR and DB2 for z/os Can reduce the time DB2 z/os holds locks during recovery 103

96 Going Mobile with IMS

97 Learn more

98 z/os Connect bridges Systems of Record with Systems of Engagement for optimized service delivery MobileFirst Platforms run either on-prem (using Linux on z Systems) or in the cloud (via Bluemix) MobileFirst Platform (on-prem) MobileFirst Platform (cloud) z/os Connect CICS IMS WebSphere DB2 Analytics Serving mobile data directly from z/os is 40% less expensive than exporting to a system of engagement Analytics run on SoR system for optimal performance and security

99 Consistent enterprise connectivity for mobile and cloud IBM WebSphere Liberty z/os Connect Shipped with WAS, CICS, and IMS Unifies z/os connectors a common solution for mobile, cloud, and web Simplified integration Hide complexity of connecting to z/os using REST Batch, WAS Batch, WAS Mobile-Optimized APIs Enterprise Applications Cloud-based Services Cloud APIs Enterprise Systems Integration IBM WebSphere Liberty z/os Connect Enterprise Data On-Premise Enterprise APIs Enterprise Transaction Processing CICS, IMS Systems of Engagement Systems of Record

100 IMS Cloud and Mobile Integration Available Today! IMS Mobile Feature Pack Deliver IMS applications and data to mobile and cloud developers in a secure, governed, and optimized way via: An integrated platform that supports full discovery, modeling, enablement, and deployment of both IMS transactions and IMS data Built on z/os Connect: the singular approach WebSphere, CICS, IMS, and DB2 for z/os Uses IMS Connect for connectivity to IMS Transactions Uses IMS Explorer for Development to quickly and easily expose IMS transactions as RESTful services 34,925 TPS! IMS Mobile Feature Pack Performance Benchmark Available 27% increase in throughput w/ z13 at equivalent CPU as compared to zec12 108

101 How IMS Tools Extend Your Edge

102 IMS Tools for IMS Database Management System Solutions for IMS Databases IMS Database Solution Pack Autonomics IBM Management Console IMS Online Reorg Facility DB Reorg Expert Unload Load Prefix Resolution/Update Index Builder HP Image Copy HP Pointer Checker IMS DB Repair Facility IMS Library Integrity Utilities IMS HALDB Toolkit IMS Fast Path Solution Pack Autonomics IMS Management Console HP FP Utilities FP Advanced Utilities FP Online Utilities IMS DB Repair Facility IMS HP Image Copy IMS Library Integrity Utilities IMS Recovery Solution Pack DB Recovery Facility HP Change Accumulation HP Image Copy DRF Extended Functions IMS Performance Solution Pack IMS Connect Extensions IMS Performance Analyzer IMS Problem Investigator Utilities/Utility Management Utilities/Tools for IMS Databases IMS DB Reorganization Expert IMS HP Unload IMS HP Load IMS Index Builder IMS HP Prefix Resolution IMS HP Pointer Checker IMS Cloning Tool IMS Database Control Suite Backup and Recovery Performance Management IMS HP Image Copy IMS DEDB Fast Recovery IMS Recovery Expert V2 IMS Buffer Pool Analyzer IMS Performance Analyzer IMS Problem Investigator IBM Transaction Analysis Workbench Regulatory Compliance IBM Infosphere Guardium Data Encryption for DB2 and IMS Databases

103 IMS Tools for IMS Transaction Management System Solutions for IMS TM Utilities/Tools for IMS TM / Systems IMS Performance Solution Pack IMS Connect Extensions IMS Performance Analyzer IMS Problem Investigator Performance Management IMS Buffer Pool Analyzer IMS Connect Extensions IMS Performance Analyzer IMS Problem Investigator IBM Transaction Analysis Workbench IMS Network Compression Facility System / TM Administration IMS Command Control Facility IMS ETO Support IMS HP Sysgen Tools IMS Queue Control Facility IMS Workload Router IMS Configuration Manager IMS Sysplex Manager Application Management Batch Terminal Simulator Program Restart Facility

104 What s Next? Discover 2 new Point of View RedGuides your starting point for: IMS and Mobile IMS and Analytics Adopt 2 follow-on RedBook Solution Guides Deploy IMS 14 Technical Roadshow from our Washington System Center team

105 Where can I learn more about IMS? The IMS YouTube channel Look for IMS Playlists which groups specific videos on the following topics: Fundamentals Security Mobile Analytics Simplified Interfaces Tools