IMS09 ims v14 higlights

Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 5.1

IMS V14 Hightlights

Rick Long

IMS Advance Technical & Intgration

Solutions Team

[email protected] © Copyright IBM Corporation 2015

© Copyright IBM Corporation 2015

IMS 14 Highlights

Agility •DEDB Alter enhancements

•User Exit enhancements

•IMS Connect Command enhancements

•OTMA Descriptor enhancements

•Dynamic MSC

Application

Deployment/Management

•Catalog - DDL interface

•IMS Management of ACBs

•Catalog Audit Trail

•ODBM Accounting

•Native SQL enhancements

•Cascaded Transaction Support

•Dynamic Refresh of (P)WFI regions

•DL/I ICAL support for control data

•DL/I ICAL diagnostics enhancement

IMS & DB2 •FDBR Resolve In-doubt Notification Exit enh

•ESAF Subsystem Definition enhancement

•ESAF Associate Thread Exit

Business Growth •OSAM DEB 24-bit storage VSCR

•OSAM HALDBs 8G support

•Automatic SDEP Buffer Management

•Fast Path 64-bit for high speed utilities

•OTMA TPIPE parallelism

Infrastructure •DBRC Migration and Coexistence

•DBRC REPAIR Command

•Reduced TCO enhancements

•IMS Repository enhancements

•64-bit Storage Manager

•OTMA enhancements

•APPC Flood Control

•ISC VTAM Enhancement for ERP messages

•Shared Queues Overflow protection


3

Database Manager Enhancements


IMS 14

PSBLIB

Catalog

• IMS DB changes start with catalog • IMS loads resource information from catalog

• ACBLIB/PSBLIB/DBDLIB can be created and updated from the catalog

• Tools requiring these libraries can continue to operate, but should be

migrated to catalog use

• PSB and DBD source can be generated from the catalog or from the DBDLIB

and PSBLIB

IMS Explorer

For Development

DDL

ACBLIB

DBDLIB

PSB

source

DBD

source

IMS

Optional – Not used by IMS

4


IMS Dynamic Database

• Target Market – IMS DB customers

• Challenge Addressed – Database schema change is static and requires system definition and

generation processes.

• Solution Statement – Allow optional use of Data Definition Language (DDL) to effect

database and schema change

– Provide audit trail to capture who is making changes to the IMS

Catalog

– Allow optional IMS management of ACBs • IMS Catalog is the trusted source of definitions

• ACBLIB is no longer used or needed by IMS

• IMS system can use either Catalog or ACBLIB for all definitions


Open Database Manager Accounting

• Challenge Addressed – There is no easy way to determine IMS DB usage for charge back to

application users

• Solution Statement – Provide optional SMF records that can be used for application charge

back

– Enabled through new parameter in CSLDIxxx • LOGOPT=(ACCOUNTING)

– SMF type 29, subtype 01 records

• Business Value – An audit trail for ODBM processing activity provides a way for charge

back and general usage monitoring


OSAM DEB 24-bit storage VSCR

• Challenge Addressed – Need to grow number of databases that can be allocated to a single

IMS

• Solution Statement – Reduce 24-bit storage usage for OSAM DEB control blocks by moving

the OSAM DEB extension into 31-bit storage

• Business Value – Allow growth of IMS Databases in a single IMS by reducing the

amount of 24-bit private used for each data set


OSAM HALDB 8G Support without OLR

• Challenge Addressed – When moving to OSAM HALDB the database size must be reduced

from 8G to 4G

• Solution Statement – Allow 8GB OSAM support for HALDBs

• Online reorganization support would still limit OSAM database to 4G – OSAM HALDB that is 8GB capable, can not use the HALDB online

reorganization process

• Option at the database level – Some HALDBs can be defined 8GB; others can be 4GB and use OLR

– DBRC commands enhanced to set 8G option for the OSAM HALDB

master database

• Business Value – Provides increased scalability for OSAM databases


DEDB Alter Enhancements

• Challenge Addressed – Need to change the DEDB Area definition SIZE, UOW, and/or ROOT

parameters to increase the size of an Area when SDEPs are defined

– Need to add an Area to a DEDB without bringing the DB offline

– Need to support XRF and FDBR environments when ACBSHR=N

Solution Statement

– Enhance the existing IMS 13 DEDB Alter capability to • Allow alter when SDEPs are defined

• Allow the addition of one or more Areas to the end of a DEDB

• Segment Edit/Compression exit can be added – Assumes the user has an exit that can handle the mix of compressed and

non-compressed segments

– IMS does not provide an exit that supports a mix of compressed and non-

compressed segments

• Allow alter when using XRF/FDBR with ACBSHR=N

• Business Value – Improve data availability by allowing selected changes to a DEDB

without taking the database offline


Automatic SDEP Buffer Management

• Challenge Addressed – Asymmetric processing of SDEP buffers across sharing systems can

cause an out of space condition requiring a database outage to

correct

• Solution Statement – Provide automatic management of SDEPs to account for asymmetric

processing to ensure enough CIs are released

– New parameters added to DFSDFxxx to enable and control • SDEPAUTO, SDEPFREQ, SDEPEXP, SDEPTIME

• Business Value – Reduces unplanned outages for applications and/or databases due to

insufficient space for SDEPs


Fast Path 64-bit for High Speed Utilities

• Challenge Addressed – UOWs which have large numbers of segments might not be

processed due to ECSA constraints

• Solution Statement – Allows option to have the HSRE & HSSP buffers allocated in 64 bit

storage

– Storage location controlled by DD card - default is to use 31-bit

storage

– HSRE new keyword on SYSIN DD • FPBP64U Y | N

– HSSP new control card on the DFSCTL DD • SETU FPBP64U=Y | N

– Internal – utilizes the new 64-bit storage manager and uses the AREA

name as the storage pool name


Native SQL enhancements

• Challenge Addressed

– Data aggregation on the client side is expensive with heavy network traffic

– COBOL SQL user has to write extra code for aggregation resulting in additional CPU usage and performance impact

• Solution Statement – Enable SQL aggregate function to process IMS data from

COBOL applications using Native SQL engine • Aggregate function (AVG, COUNT, MAX, MIN, SUM) • GROUP BY with Aggregate function • GROUP BY with Aggregate, ORDER BY • GROUP BY more than one column

• Business Value

– Simplify COBOL SQL coding for aggregation

– Provides standard SQL aggregation for data warehouse and data mining


DBRC Enhancements

• Challenge Addressed – Inconsistencies in RECON data set records occur for unknown

reasons

– Users need to migrate to IMS 14 from existing releases

• Solution Statement – For DB users: new REPAIR.RECON command can be used to verify

and fix inconsistencies in the RECON data set related to DMB

numbers

– For All users: DBRC migration and coexistence with IMS 12 and IMS

13

• Business Value – Improve usability of the RECON when there are inconsistencies in the

RECON

– Consistent migration and coexistence with prior releases


FDBR Resolve In-Doubt Notification Exit –

DFSFIDN0

• Challenge Addressed – It can be difficult to code the DFSFIDN0 exit to properly resolve in-

doubt work when DB2 is involved in the unit of work

• Solution Statement – Provide a sample DFSFIDN0 user exit with IMS that issues a new

message for each in-doubt ESS UOR • DFS3722I identifies in-doubt work by: Subsystem Name, Subsystem

Type, Resolve-in-doubt Action, and Origin Application Schedule Number

(OASN)

• Automation can monitor the messages and act upon the in-doubt UOR

• Business Value – Improves usability when using both FDBR and DB2 z/OS

– Can reduce the time DB2 holds locks during an IMS abend situation


Systems Enhancements


ESAF Subsystem Definition Enhancement

• Challenge Addressed – SSM PROCLIB member does not allow a subsystem type to be

specified for any subsystem other than DB2 • Unable to distinguish MQ or WOLA subsystems from DB2

• Solution Statement – Subsystem type (SST=) values would be added for MQ and WOLA

• 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

• 56000009

• 4031

• Business Value – Improves usability


New ESAF Associate Thread Exit

• Challenge Addressed – Multiple applications running in a single dependent region can cause

extra overhead with the building and teardown of the DB2 structure for

a given transaction instance.

• Solution Statement – A new ESAF Associate Thread exit is provided that can be used by

DB2 or other external subsystems for connection pooling and to

determine if the create thread and terminate thread exit processing is

required

– External subsystems could use this exit in other ways

– The new exit gets control prior to the signon exit when signon is

required.

• Business Value – Can improve performance by eliminating overhead from excessive

creation and teardown of structures for SQL processing by DB2


Reduced Total Cost of Ownership Enhancements

• Target Market

– All IMS customers

• Challenge Addressed – How to continue to reduce the IMS TCO while maintaining the IMS standard

quality of service?

• Solution Statement – Several small items included in the release (see next chart)

• Business Value

– Continue to drive down the cost of CPU when running IMS


Reduced Total Cost of Ownership Enhancements

The following items are included in IMS 14

– z9® processor enforced as lowest-level hardware

– IMS exploits z9® instructions where appropriate

– Remove BMP-inserted transaction message restriction for SQ “local-

first” processing

– New 4518 “individual TCB” dispatcher statistics record

– Add 32K and 48K buffer sizes in CQS interface buffer manager

– BPETIMER CANCEL optimization

– Miscellaneous Logger performance fixes

– Optimized OTMA Callable Interface used by WOLA

– OTMA send-only with reroute optimization

– Call DFSYLUS0 directly to avoid pass-thru call from DFS6LUS0 to

DFSYLUS0


IMS Repository Enhancements

• Challenge Addressed • Manual processes are required to harden resource changes to the

repository

• Need to remove an IMS from the repository

• Need ability to determine if there are runtime resource definitions that

have not been exported to the repository

• Solution Statement • Enable AUTOEXPORT to IMSRSC repository from IMS at end of IMS

checkpoint – Only the resources modified or created since last export (via command or

AUTOEXPORT) are updated in the IMSRSC repository

• Provide a /CHE LEAVEPLEX command to allow an IMS to be removed

from the Repository

• Provide the ability to show new or modified resource definitions that have

not been exported to the IMS repository – Create a non-system RDDS that contains only the resource and descriptor

definitions that have not been exported to the IMSRSC repository using Log

Records Utility (DFSURCL0)

– QUERY command enhancement for resource that have not been exported -

SHOW(EXPORTNEEDED)


User Exit Enhancements

• Challenge Addressed – Need to take an IMS outage to refresh DFSAOE00

– Multiple vendor tools can replace/extend the IMS Monitor and need a

clearly defined runtime entry point

• Solution Statement – User exit interface allows:

• Ability to call multiple routines from a single user exit point

• Dynamic refresh of the exit using the REFRESH USEREXIT command

– IMS 14 enhanced exits • Type-2 AOI User Exit (AOIE - DFSAOE00)

• New IMS Monitor User Exit (IMSMON)

• Business Value – Increased availability for IMS

– Improved usability for tools that provide monitor functions


New 64-bit Storage Manager

• Challenge Addressed – IMS components are using 64-bit storage to help alleviate below the

bar storage constraints but there is no common service • Each IMS component must manage its own 64-bit storage

• Solution Statement – Provide a systems service to manage IMS storage obtained above the

bar

• Business Value – Providing a systems service to manage 64-bit storage eliminates

duplicate code spread throughout IMS. It also provides a central

component to update in order to exploit new hardware and z/OS

enhancements.


IMS Connect Command Enhancements

• Challenge Addressed – Unable to dynamically delete PORT and DATASTORE resources

– Unable to determine if certain IMS Connect commands complete

successfully • Successful completion code but the command has an asynchronous

component that does not result in a command response

• Solution Statement – Introduce DELETE PORT and DATASTORE commands

– Enhance UPDATE PORT and DATASTORE commands to allow

changes to selected attributes

– Introduce CREATE and DELETE IMSPLEX commands

– Convert selected IMS Connect commands to complete synchronously • Command response would reflect actual command result

• Business Value – Availability is increased by allowing dynamic creates, deletes and

updates for selected resources

– Usability is increased by providing a synchronous command response


Transaction Manager Enhancements


Cascaded Transaction Support

• Challenge Addressed – For 2-phase-commit (SYNCLVL=SYNCPT), IMS Connect and the IMS

Control Region must be on the same LPAR. • Otherwise IMS rejects the transaction with an error

• Solution Statement – Allow a Global Transaction using the IMS TM Resource Adapter to be

spread across IMS Connect and an IMS Control region that reside on

different LPARs • For performance reasons same-LPAR configurations are still the

preferred configuration for two phase commit transactions, multi-LPAR

support is for availability

– IMS Connect user message exit interface enhanced with new status

to assist in routing decisions

• Business Value – Increased flexibility of IMS configuration across LPARs

• Additional options for workload balancing

– Increased availability by allowing IMS Connect to route to an IMS on

another LPAR


DL/I ICAL Support for Control Data

• Challenge Addressed – Need to pass various types of user-provided information to an end

client

• Solution Statement – The DL/I ICAL function is enhanced with a new optional control data

field to allow user information to be passed to IMS Connect and its

clients

– With SOAP Gateway support, IMS Connect will be able to override the

XML converter for the outbound message.

• Business Value – Provide a simple method to pass metadata with a callout message

• E.g., XML converter override, security credentials, endpoint information

– Strengthen callout security with the security token included in control

data

– Reduce the number of OTMA destination descriptors in the system

due to unique converter names


OTMA TPIPE Parallelism

• Challenge Addressed – TPIPEs sending CM0 output, including synchronous callout

messages, require ACK before next message can be sent

– Only one Resume TPIPE (RT) can be active for any given TPIPE • Other Resume TPIPEs are queued and have to wait for the active RT to

terminate

– Multiple IMS Applications issuing DL/I ICAL to a single TPIPE • TPIPE serialization makes them wait longer, holding the dependent

regions, increasing region occupancy and transaction response times

• Solution Statement – Allow multiple active Resume TPIPEs for a single TPIPE

• Can be set by OTMA or IMS Connect – MULTIRTP=Y|N

• Can limit number of active Resume TPIPEs for an TMEMBER -

LIMITRTP

– IMS and IMS Connect command changes for display and

management


Synchronous Callout Diagnosis

Enhancements

• Challenge Addressed – Documentation is not clear regarding the 6701 log records written for

synchronous callout

• Solution Statement – Improved 6701 synchronous callout diagnostics record

• Changed several identifiers

• Business Value – Improves analysis of callout flows for problem determination


OTMA Enhancements

• Challenge Addressed – Several customer requirements are addressed

• Solution Statement – Allow user specified minimum and maximum limits for dynamic SAPs

to prevent selective dispatching for OTMA client (OIM) TCBs

– Listen for RACF ENF 71 messages to allow dynamic refresh of ACEE

cache

– New OTMASE option for Join (J) security to indicate who can access

OTMA, same as None (N) but provides RACF connection security

– QUERY OTMATI SHOW(CONVID) enhancement to show

conversation ID for OTMA transaction instance

– OTMA routing exits DFSYPRX0 | OTMAYPRX and DFSYDRU0 |

OTMAYDRU are now passed an ECB

– OTMA Input/Output Edit Exit DFSYIOE0 | OTMAIOED is now passed

a copy of the message prefix; it can modify the length or data of a

message segment; or it can cancel the segment or whole message.

ed security options


OTMA Descriptor Enhancements

• Solution Statement – Allow both destination and member descriptors to be allocated

dynamically • Eliminate fixed storage allocation at startup

• Default limits are the same - 255 member / 510 destination

• Can increase limits to 4095 using DFSOTMA member descriptor

– Summary of new parameters in IMS 14 for all enhancements – DDESCMAX - maximum number of destination (type-D) descriptors

– DSAP – system default for minimum allocation of save area prefixes (SAPs)

– DSAPMAX - system default max SAPs that an OTMA client can have

allocated

– LIMITRTP - default max number of active RESUME TPIPE requests

– MDESCMAX - max number of client (type-M) descriptors that can be defined

in DFSYDTx

– MULTIRTP – (NO | YES) default for TPIPE support of multiple active

RESUME TPIPE requests

• Business Value – Reduces ECSA storage usage if fewer descriptors are needed than

current limits


APPC Flood Control

• Challenge Addressed – If APPC/IMS gets flooded with too many APPC transactions IMS can

run out of storage and ABEND

• Solution Statement – Allow a user specified limit for the maximum number of APPC

conversations active concurrently in IMS

– Allow excess requests to queue in 64-bit storage

– New DFSDCxxx option to specify the maximum number of active

conversations (X) and maximum number of queued conversations (Y) • APPCMAXC=(x,y)

• Business Value – Reduce the number of IMS outages due storage exhaustion


Dynamic refresh of (P)WFI regions

• Challenge Addressed • Applications that run as Wait for Input (WFI) or Pseudo WFI (PWFI)

remain scheduled while waiting for new messages. When application

changes are rolled out into an IMS system, all instances of the

application need to be refreshed. It is not easy to determine where the

applications are running in order to recycle the regions

• Solution Statement • Provide a command that would terminate all instances of the application

that is waiting for a message

• UPDATE PGM …. START(REFRESH)

• Next time the application is scheduled a new copy would be loaded

• Applies to message-driven BMP WFI and MPP/JMP (P)WFI regions

• For a JMP region the JVM will be recycled

• Does not apply to IFP regions

• Preloaded programs in the DFSMPLxx list can only be deleted by

recycling the region

• Business Value • Enables faster rollout of application changes with less manual effort

• Reduces data integrity exposures due to missed application changes


Dynamic MSC

• Challenge Addressed – Eliminate planned outages for MSC definition changes

• Solution Statement – New startup parameters to select MSC feature and definition libraries

– Commands enhancements to Create and Delete MSC links

dynamically

– Automatic Export and Automatic Import of MSC definitions to a

centralized repository for permanent retention

– Use of dynamic definition for MSC is an option, users can continue to

use sysgen MSC macros if desired

• Business Value – Eliminate planned outages to modify MSC definitions

– Optionally Remove MSC from SYSGEN • Improves usability for cloning IMS’s within a IMSplex

– Reduce 24-bit private storage usage


ISC VTAM enhancement for ERP

messages

• Challenge Addressed – Need the ISC VTAM session to stay active after the originating IMS

receives an Error Recovery Procedure (ERP) message from the

partner subsystem

• Solution Statement – Provide a new option to keep the ISC VTAM session active after

receiving an ERP message • ERPKPSES=Y | N in DFSDCxxx PROCLIB member

• Business Value – Provide higher connectivity


Shared Queues Overflow Protection

• Challenge Addressed – IMS does not provide enough information for tools to make decisions

to prevent the message queue structure from becoming full

• Solution Statement – Provide information to the Queue Space Notification exit, DFSQSSP0,

to indicate how much of the message queue structure is used

– Additional information passed to DFSQSSP0 for both the primary and

overflow structures • Queue usage – Primary Structure

– Number of entries and elements - in use

– Number of entries and elements - total allocated

• Queue usage – Overflow structure – Number of entries and elements - in use

– Number of entries and elements - total allocated

• Business Value – Vendor tools could provide additional capabilities for message queue

overflow protection


IMS Prerequisites


IMS 14 Prerequisites

• Minimum level of Operating System - z/OS 2.1

– z/OS 1.13 would be supported for QPP customers through EOS

(September, 2016) • System z hardware - z9 or newer

– z/OS 2.1 runs on a minimum of z9

– Older machine types will not be supported

• Other software and hardware prerequisites are TBD

– Java Dependent Regions require JDK 7 or later

– IRLM 2.3

– DB2 10 or later

– CICS 4.1 or later

• ISC using TCP/IP requires CICS 5.1

– WebSphere MQ V7.0.1 or later

– WebSphere Application Server 8.5

– COBOL 5.1 or later – for Native SQL

– RDz V9.0.1.1 or later – for SOAP Gateway


IMS Migration and Coexistence


IMS 14 Migration

IMS 14 supports migration/coexistence for IMS 12 and IMS 13

– DBRC Migration/Coexistence SPEs • IMS V12 – APAR PI10131/UI22257 • IMS V13 – APAR PI10132/UI22258

– RSR Migration/Coexistence

OTMA TPIPE Parallelism Coexistence

– To allow IMS Connect 12 or 13 to work with IMS 14 MULTIRTP IMS

Connect previous versions require compatibility fixes

• IMS Connect V12 PM93880 / UK98633

• IMS Connect V13 PM93878 / UK98632

• Requires MULTIRTP enabled through OTMA Member descriptors

Repository Coexistence

– Coexistence APARs for the autoexport function

• IMS 12 – APAR PI27283/UI23503 IMS 13 – APAR PI27285/UI23504

• IMS 12/ IMS 13 Resource Manager (RM) does not support autoexport

repository request from IMS 14

– Recommendation: Enable autoexport once all IMSs and CSL are at

version 14 level


Questions?

IMS09 ims v14 higlights

Software

Transcript of IMS09 ims v14 higlights