ims 15 summary final - ibm.com · pdf fileims otma 1) ims otma security prefix is expanded to...

© 2014 IBM Corporation© 2012 IBM Corporation

IMS Version 15

© 2017 IBM Corporation

Summary

Large Systems Update 2017

Torben Flygenring [email protected]

IMS Version 14 IMS Version 15


Trademarks, copyrights, and disclaimers

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of other IBM trademarks is available on the web at

http://www.ibm.com/legal/copytrade.shtml

Other company, product, or service names may be trademarks or service marks of others.

THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED "AS IS" WITHOUT

WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OROTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO,

NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCTS OR SOFTWARE.

© Copyright International Business Machines Corporation 2017. All rights reserved.

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a

purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development,

release, and timing of any future features or functionality described for our products remains at our sole discretion.



https://www-01.ibm.com/software/data/ims/3



IMS V15 Announcement (GA - Oct. 27, 2017)

Announcement letter : https://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_sm/6/877/ENUS5635-A06/index.html&request_locale=en

Documentation in Knowledge Center

QPP program run with participation of 3 Nordic IMS Customers

IMS V13 EOS – Nov. 6, 2018

– 4

IMS 15

IBM CONFIDENTIAL 2 0 1 7



Network Security Credential Propagation

Challenge Addressed

Inability to log and audit a distributed end-user’s identity

Network security credentials may differ from the SAF identity used for IMS security

Solution

Enhancement that propagates the network security credential to IMS

Up to 246 bytes for client end-user identity

Plus up to 254 bytes for a realm or registry identity

Requires:

IMS 15, IMS Connect 15, IMS TMRA 15

For mobile support, IMS Service Provider and z/OS Connect EE

Business Value

Provides enhanced auditability and accountability in enterprise environments

Enhances IMS callout security with the original user credential for external

OTMA

5


Distributed Application,

Such as WAS

Sysplex

Shared-

Queues

Back-end

IMS Back-end(s)

z/OS

� RACF-ID

�Distributed ID

Audit Record

SMF

Log

IMS

IMS View: Network Security

Credential Propagation

IMS Front-end

LOGSTR=NO|YES

z/OS

z/OS

IMS ConnectForwards

network

credential on to

IMS OTMA

1) IMS OTMA security prefix is expanded to include

network userid and network session ID.

2) First 255 bytes of network credential is included in

RACF SMF record if OTMA descriptor LOGSTR=

parameter is YES.

3) IMS transaction authorization exit

DFSCTRN0 can be passed with the network userid and

session ID.

4) OTMA exits, DFSYIOE0, DFSYPRX0, and DFSYDRU0

can be used to access OTMA security prefix.

Logstream data

MSC remote

OTMA descriptor

RACF

OTMA

6



SMF

� To have the network security credential included in the RACF SMF records, code LOGSTR=YES in OTMA client descriptor.

LOGSTR=NO | YES

– LOGSTR is an optional parameter

• No: default

• Yes: specifies that the first 255 bytes of user-distributed identity need to be included in the RACF SMF process records– The identity which consists of network user id and session id must exist

in the OTMA input security prefix in order to be included in the SMF records

• The format of network user id and network session id in the SMF records is identical to corresponding format in the OTMA security prefix.

� Syntax errors result in DFS2385E

DFS2385E SYNTAX ERROR FOR DESCRIPTOR = descriptor errortext

OTMA

7



OTMA Exit Routines

� OTMA exit routines allow access to the OTMA security prefix

– DFSYIOE0 (OTMA input/output user edit exit)

– DFSYPRX0 (OTMA pre-routing user exit)

– DFSYDRU0 (OTMA destination resolution user exit)

• User exit parameter list for all exits is enhanced to indicate and pass

security data. See the individual Exit routine documentation for specific

information.

8

OTMA



OTMA Exit Routines…

� DFSCTRN0 (Transaction Authorization Exit)

– Storage area mapped by DSECT CTRNPARM parameter list has been

expanded to add:

• Address of the network userid

• Address of the network session

9

OTMA



Migration Considerations …

� To log the network credentials in RACF SMF records

– If LOGSTR=YES is specified in the OTMA client descriptor, the first 255

bytes of the network credential will be logged in the RACF SMF record.

� Large number of messages with network security credential propagation

– Can impact XCF and TCP/IP transmission

� Operational Considerations

– Since OTMA message prefix with the additional network security credential

info is stored on IMS message queue data sets

• Log volume and the usage of the queue buffer pool will be increased

• SHMSG and LGMSG might need to be resized

OTMA



Transaction Expiration - Enhancement

Challenge Addressed

Inconsistency between OTMA and non-OTMA environments when a transaction reaches the expiration time value

Transaction expiration support for non-OTMA was introduced in IMS 11

Solution

New: functionality to discard the expired OTMA input message without abending the message region with a pseudo ABENDU0243

TODUMP=YES/NO/U243 NO is now default

Benefit

– Saves CPU cycles needed to process the ABENDU0243 when unneeded

11

OTMA



Logger’s use of Media Manager - Writing to the WADS

� Target Market

– Primarily customers who experience replication problems when mirroring their WADS, however, all customers can benefit from increased throughput

� Challenge

– The time taken to mirror the WADS, especially over long distances, can create problems for synchronous replication

12

Systems



Logger’s use of MM for Writing to the WADS

� Solution

– Logger will now use DFSMS Media Manager to write to the WADS

– Media Manager leverages zHyperWrite to reduce replication latency

– When available, Media Manager also uses zSystem High Performance FICON (zHPF) to increase Logger throughput

– Media Manager is a no-charge feature

� Value

– IMS throughput is increased by reducing replication latency and reducing overall l I/O time

– IMS Logger processing runs faster and consumes fewer resources

13

Systems



Purpose of the IMS WADS

� Performance

� To write “small” chunks of data from a log buffer that have not yet

been written to the OLDS

� Enables the user of the Logger resume processing quickly, knowing

their log data has been hardened

� The WADS is a simple, small, sequential flat file

� For performance, the IMS Logger currently builds its own channel

program to write data to the WADS

� To exploit new zSystem I/O features requires a change in the current

design of the WADS interface

14

Systems



IMS Logging Today

15

(FLAT FILE)



IMS 15 Logging

16

(VSAM LDS)

IMS 15 Requires that the WADS be defined as a Linear VSAM data set.

Systems



WADS Improvements

� Positions the Logger to exploit new hardware features

– Media Manager uses new zSystem I/O features

• zHyperWrite: Reduces replication latency in HyperSwap-managed

metro mirror environments

• zHPF: Increases I/O throughput, when available

� Simplicity of code

– Media Manager’s interface is much more user-friendly than channel

programming

17

Systems



Logger’s use of zHyperWrite for the OLDS

� With a single parameter change, the amount of time spent in OLDS I/O can be decreased by reducing the OLDS replication latency by using zHyperWrite

� Reduce replication latency when writing to the OLDS

� Reduce the time needed to mirror the OLDS, especially over long distances, this can create problems for synchronous replication

18

Systems


Prerequisites and Design Assumptions

Requirements

– Primary and Secondary Volumes must be in a Metro Mirror relationship

in full duplex status

– Must be managed by HyperSwap

– To use zHyperWrite, the OLDS must be extended format files

• OLDS are already extended format if above-the-bar storage is being

used for the log buffers

• BUFSTOR=64 parameter of OLDSDEF statement in DFSVSMxx

PROCLIB member

No change to OLDS processing or usage (i.e. Log Archive, Reporting, etc.)

19

Systems



Move of the Logger Parms to DFSDFxxx

� An IMS Systems Programmer can consolidate where Logger parameters are specified and optionally add zHyperWrite support

– The Logger parameters are specified in multiple places. Also, use of zHyperWrite for the WADS and OLDS can be enabled or disabled without

recycling IMS.

� IMS 15

– Logger parameters are consolidated to the DFSDFxxx member

– zHyperWrite parameters are added to DFSDFxxx and can be changed with

a type-2 command.

� Value

– Increases availability by allowing a parameter change while IMS remains up

20

Systems



DFSVSMxx OLDSDEF Today

� Most parameters are currently defined in DFSVSMxx member

8192,4

2048,4

1024,8

IOBF=(2048,4,N,N)

IOBF=(6144,4,N,N)

IOBF=(8192,4,N,N)

OLDSDEF

OLDS=(00,01,02,03),MODE=DUAL,BUFNO=10,BUFSTOR=64,BLKSZ=24576

WADSDEF WADS=(0,1)

LOGEDIT=(01)

ARCHDEF MEMBER(ARCHDSHR) ALL

OPTIONS,DISP=ON,SCHD=ON,LATC=ON,STRG=ON

OPTIONS,DLOG=ON,LOCK=ON,DL/I=ON,QMGR=ON,SQTT=ON

� Single/dual WADS and ARC parameters: DFSPBxxx member

– Optionally overridden as a JCL parameter on EXEC statement for the IMS CTL Region

� For DL/I Batch, Logger parameters in DFSVSAMP are ignored

21

Systems



DFSDFxxx Logger Section

� Add a <LOGGER> section to DFSDFxxx PROCLIB member:<SECTION=LOGGER>

OLDSDEF=(MODE=DUAL,

OLDS=(0,1,2,3)

DEGRADE=NO,

BUFNO=5,

BUFSTOR=64,

BLKSZ=24576)

WADSDEF=(MODE=SINGLE,

WADS=(0,1,2))

ARCHDEF=(MEMBER(ARCHDSHR) ALL)

LOGEDIT=(01,03)

ARC=2

ZHYPERWRITE=(OLDS=YES,WADS=YES)

� The zHyperWrite parameter is changeable via an IMS type-2 command

� To reduce complexity and redundancy, the logger parameters would be removed from

their previous locations

� Logger parameters in DFSVSAMP still ignored

22

Systems



Migration and Coexistence

� IMS 14 APAR PI64267

– Allows customers to change DFSDFxxx member ahead of IMS 15 migration

– Will allow parameters to be specified either as they are today, or in the

DFSDFxxx member

� Precedence of parameters:

– JCL parameter on EXEC statement*

– DFSPBxxx member*

– DFSDFxxx member (if specified)

– DFSVSMxx member

– Default values

� Once parameters are moved to DFSDFxxx,

– Can be safely removed from other locations e.g. DFSVSMxx

� Only applies to WADS and ARC parameters23

Systems



WLM Mobile/Cloud Workload Pricing

� What is it?

� IBM Mobile Workload Pricing (MWP) and Workload Pricing for Cloud (zWPC) are sub-capacity pricing option

– Sub-Capacity pricing for z/OS provides usage-based variable for Monthly

License Charge (MLC) software

– Purpose is to mitigate the cost of growth created by these workloads

� Currently

– Difficult to track and report the CPU Time for these Mobile/Cloud workloads

� Solution

– Implement Workload Manager (WLM) Classification Rules

� Benefit

– Provide data for processing cloud/mobile workloads on IMS.

– IBM z Systems Workload Pricing for Cloud and Mobile Workload

• Can reduce the cost of growth for new workloads

24




� WLM Classification

– Two new work qualifiers are introduced for IMS

• Connection Type (CT):– The port number of the TCP/IP Service that received the request for this

transaction.

• Client Transaction Name (CTN): – The name of the Transaction Pipe (TPIPE)

– The classification rules panel new column "Reporting Attribute” :• NONE, for all work. This is the default.

• MOBILE, for mobile work.

25




� z Systems Workload Pricing - MWP and zWPC

– Data collection and reporting process

– Two methods to identify the CPU time

1. WLM method

� Based on WLM classification rules

2. Original CSV file method

� For cases where WLM classification rules for mobile workload transactions are not available or applicable

� Run Sub-Capacity Reporting Tool (SCRT)

– Submit the results to IBM for each sub-capacity reporting period

Note : The SMF records and mobile workload transaction data must be retained for six months after the

billing period for auditing purposes.

26




� IMS provides customer specified information to WLM to identify mobile and

cloud access in workload manager reports and IMS log record.

– SMF 70 and SMF 89 records

• normal part of sub-capacity reporting

• CPU time is stored in new fields in the SMF 70 record

– IMS X’56FA’ Log Record

– Record workload eligible for offloading to specialty engine (zIIP/zAAP)

27




� Customers must be able to identify mobile/cloud transaction using:

– Client Transaction Name (CTN):

• IMS OTMA TPIPE name (Specified in Connection Profile)

– CM0 Generated Client ID GMPxxxxx

– CM1 IMS Connect Port Number

– Connection Type (CT):

• IMS Connect port number (Specified in Connection Profile)

– LUNAME:

• VTAM LU cannot classify mobile/cloud requests

– Use LTERM override (Specified in Interaction Profile)

28




� IMS provides to WLM:

– OTMA TPIPE name, port number, LUNAME or LTERM override.

– Processor time (both on standard CP and eligible for offloading)

– Sum of Standard Processor and eligibility for offloading

29


Eliminate need to calculate CNBA for DRA

� DRA Runtime

– CCTL (CICS) environments accessing IMS FP databases

– ODBM RRS=N environments accessing IMS FP databases

� Currently

– The current restriction of 9999 CNBA buffers for CCTLs can limit the number of parallel

DRA Threads that can be allowed for that CCTL.

� Solution

– IMS will calculate the total number of FP buffers (CNBA) to allocate for a CCTL (CICS)

or ODBM RRS=N connecting to IMS

– Dynamically expand FP buffers assigned to a CCTL when using 64 bit FP buffer

manager

– Allow the CNBA= parameter to be specified as 0 when FPBUF= and FPBOF= are non-

zero.

30

Systems



� Thread buffer limits still apply (FPBUF) and must be specified.

� IMS will calculate CNBA size when FPBUF > 0 and CNBA = 0

– CCTL Needed Buffer Allocation (CNBA) is calculated as follows:Maximum threads (MAXTHRD) x Fastpath normal buffers (FPBUF)

+ Fastpath overflow buffers (FPBOF)

– CCTL (CICS): Change specification of CNBA on the DFSPRP macro in the DFSPZPxx member(s)

– ODBM: Change CSLDCxxx member(s) global and/or local configuration

sections

– Recycle the connection to activate the changes

31

Systems




� IMS will calculate the total number of FP buffers (CNBA) to allocate for a CCTL

(CICS) or ODBM RRS=N connecting to IMS

– Dynamically expand FP buffers assigned to a CCTL when using 64 bit FP buffer

manager

– Allow the CNBA= parameter to be specified as 0 when FPBUF= and FPBOF= are non-

zero.

� Benefit

– With 64-bit FP buffer support, the CNBA limitation is not needed; allowing more buffers

allows for more scalability for CCTL usage

– Increase scalability for Open Database

32

Systems



Reduce IMS Sysgen

An IMS system programmer can define certain IMS attributes without a system

definition and generation

� Currently

– IMS System Definition is needed to establish a runtime environment

� IMS Direction

– Continue towards long-term goal of eliminating IMS system generation

• Remove building of sample PROCs from system generation

• Eliminate the IMS.OPTIONS dataset

• Eliminate the BUFPOOLS macro

• Eliminate the IMSCTF Macro

• Remove user exits from system generation COMM macro

� Value

– Simplifies IMS set up and customization

33



Current IMS PROCs

34

� Some sample IMS PROCs are built by sysgen

– PROCLIB parameter of IMSGEN macro determines whether the IMS PROCs are built

� Some sample IMS PROCs (such as SCI) will be built during SMP processing

Reduce IMS Sysgen



IMS PROCs Migration

35

� IMS.SDFSPROC– Copy to required members to IMS.PROCLIB, rename, and modified as needed

– Variable data

� System Definition macros will no longer be used to override variable data

IMS sets defaults – more laterCGeneration

– Conditional Statement Generation

� New sample procedures assume a ‘standard’ DB/DC system� For ‘non-standard’ environments the Prolog of the sample

Procedures contains instructions for how to modify

– DFSWTxxx and IMSWTxxx

� generated as multiple parts (000, 001, etc)

� new parts DFSWT000 and IMSWT000 generated as a single set

needs to be modified to specify the actual SPOOL definitions

– IMS and DCC

� Need to be modified to specify the actual DD statements for runtime

Reduce IMS Sysgen



Current IMS.OPTIONS

36

� IMS.OPTIONS is obsolete

– IMS.OPTIONS dataset contains one member – DFSVTAM

– DFSVTAM was originally used for conditional assembly during stage 2– No conditional assembly modules/macros need DFSVTAM anymore

� DFSALOC1 and DFSDDEF1 no longer allocate and reference IMS.OPTIONS

� IMS.OPTIONS dataset is no longer created

� Customer Action Required:

– Modify all custom JCL that reference IMS.OPTIONS– No stage 1 definition changes are necessary

� BUFPOOLS– Defines default storage buffer pool sizes during Stage 1 System Definition– The DFSPBxxx member and JCL overrides are the only places to define or

override buffer pool sizes

� IMSCTF

– Defines the SVCs for DBCTL, logging options, and the device type for DBCTL’s restart data set

– CPLOG= and PRDR= overridden by DFSPBxxx or JCL override specifications

Reduce IMS Sysgen



Default values

37

Default value for DFSPBxxx or JCL keywords

DFSPBxxx or JCL keywords Default value Description

DMB= 12288 bytes Size of the DMB control block pool

EPCB= 8192 bytes Size of the EPCB pool

FBP= 20480 bytes Size of the message format buffer pool

FRE= 30 Number of fetch request elements (FREs) for loading MFS control blocks into the message format buffer pool

PSB= 12288 bytes Size of the PSB control block pool in subpool 231 storage if the DL/I address space option is not used

PSBW= 12288 bytes Size of the PSB work area pool

CSAPSB= 4096 bytes Size of the PSB control block pool in the z/OS common storage area (CSA) if the DL/I address space option (LSO=S) is used

DLIPSB= 8192 bytes Size of the PSB control block pool in the DL/I address space if the DL/I address space option (LSO=S) is used

Reduce IMS Sysgen



IMSCTF

� LOG=(SNGL|DUAL, MONITOR)

– The sample PROCs in the sample library built by SMP will provide the DD

statement for each option commented out

• IEFRDER2 for dual system logging (batch systems)

• IMSMON for the IMS Monitor (online systems)

– Uncomment the DD statement to activate dual logging or the IMS monitor

� IMSCTF macro keywords CPLOG=, LOG=, PRDR=, RDS= are ignored

– MNOTE 2 generated if specified

� DFSPBxxx and JCL overrides are the only places to define IMSCTF parameters

– CPLOG=, PRDR=, RDS=

� SVCNO is To-Be-Determined


– Move IMSCTF specifications for CPLOG=, PRDR=, RDS= to DFSPBxxx

– Process IEFRDER2 and IMSMON DD statements for LOG=

38

Reduce IMS Sysgen



Current COMM User Exits

� User Exit loaded standalone from IMS NUCLEUS

– DFSCMTU0 – User Message Table

– DFSCNTE0 – CNT Destination Edit routine

– DFSCTTO0 (and user-defined) – Physical Terminal Output Edit routine

– DFSFEBJ0 – Front End Switch routine

– DFSME000-DFSME127 – MFS segment formats

– DFSPIXT0 (and user-defined) – Physical Terminal Input Edit routine

– DFSSIML0 – Shared Printer Message Router routine

39

Reduce IMS Sysgen



User Exits in the IMS Nucleus

� User exits are no longer in the NUCLEUS

� User exits are loaded as stand-alone

� The interface for the exits is not being changed

� The exits are not eligible for refresh


– Move COMM specifications to DFSPBxxx

• OPTIONS=USERMSGS, FESEXIT=, MFSEXIT=, SIMEXIT=

– Link user exits

– Ensure that user exits do not reference the NUCLEUS (VCONs)

– Link DFSCSI00 with the user exit if callable services are required

40

Reduce IMS Sysgen



64-bit JVM support for IMS Java Dependent Regions

� Currently

– Some Java applications are storage constrained by the 31 bit Java

Virtual Machine (JVM) that is currently utilized by IMS.

• The total addressing range for a z/OS 31 bit address space is approximately 2 gigabytes

� Solution

– Provide Heap storage relief by allowing Java applications to run in a 64 bit JVM environment.

• The total addressing range for a z/OS 64 bit address space is

approximately 16 exabytes.

� Benefit

– Allow customers to deploy more Java applications without regard to

storage constraints.

41

Application


Restrictions and Considerations

42

� JVM=64 is currently only supported in the JMP and JBP regions.

� COBOL and PL/I interoperability works only in a 31 bit LE environment.

Existing Java/COBOL or Java/PL/I applications will not work in a

JVM=64 environment

� JCL for running JBP and JMP applications needs to be modified

� IMS Universal Drivers 64 bit JVM support APAR PI64241

64-bit JVM support for IMS Java Dependent Regions

Application


43

Retain original Area data set name for DEDB Alter

Add new fields in unmapped space of DEDB segment without a database outage to users

DEDB Alter utility supports DEDB database with 1-stage randomizer if the DEDB database contains only 1 Area without first changing the randomizer from 1-stage to 2-stage in DEDB definition.

Database

DEDB ALTER Enhancements


44

New DEDB Alter ALTERDB function supports:

� Adding new fields in unmapped space of one or more existing DEDB segments

� Increasing segment length of one or more variable-length DEDB segments

� Supports randomizer and Edit / Compression exit changes

� Adding new fields in unmapped space of one or more segments and increasing segment length of one or more variable-length DEDB segments can also be done implicitly using existing DEDB Alter functions:

– ALTERAREA

– ADDAREA

– REPLRAND

Does not support DEDB Alter for ALTERAREA and ADDAREA changes

Database



45

DEDB Alter ALTERDB function supports:

Increasing segment length of one or more variable-length DEDB segments

Adding new fields in unmapped space of one or more existing DEDB segments

Database



46

DEDB Alter utility supports DEDB database with 1-stage randomizer if the DEDB database contains only 1 Area without first changing the randomizer from 1-stage to 2-stage in DEDB definition.

DEDB Alter 1-stage randomizer supports:

ALTERAREA

REPLRAND

ALTERDB

DEDB Alter 1-stage randomizer does not support:

ADDAREA

Database




Program Create User Exit

Run an IMS BMP or JBP without having to pre-define the program directory

� Runtime

– BMP and/or JBP dependent regions

� Current

– BMP and JBP regions require the program directory to be predefined

• Stage-1 APPLCTN macro or the IMS type-2 CREATE PGM command

• U0428 ABEND indicating the program directory is not defined

� Solution

– New Program Creation user exit (PGMCREAT) for BMP/JBP programs

– Used to define:

• new program directory (PDIR)

• One optional database directory (DDIR)

� Benefit

– Simplifies the creation of runtime program resources for application programs that run in BMP and JBP regions

47



� Dynamic resource definition must be configured and enabled by specifying MODBLKS=DYN in the DFSDFxx or DFSCGxxx PROCLIB member

� Define PGMCREAT user exit type

– DFSDFxxx PROCLIB member

� User exit can be enabled by one of the following:

– Restarting IMS

– Using the REFRESH USEREXIT command

• REFRESH USEREXIT TYPE(PGMCREAT) MEMBER(PX0)

� Display

– QUERY USEREXIT TYPE(PGMCREAT)

– PGM and DB resource created by exit

• QRY PGM and QRY DB commands

– DEFNTYPE=PGMCREAT

48

Program Create User exit



Program Create User exit

� IMS user writes a Program Create user exit which contains logic to tell IMS to create a program directory (PDIR)

– Called during application program scheduling

• Application program is in the ACBLIB/Catalog but the program directory block is not found in IMS

– Return to IMS to create the program and/or database along with attributes for the PDIR and DDIR

• Attributes not specified obtained from the default descriptor

– Return to IMS to not create a program

• U0425 Abend

� User exit is linked into an authorized library in the JOBLIB, STEPLIB, or

LINKLIST library concatenated in front of the IMS.SDFSRESL

� Exporting resource definitions to the IMSRSC repository

– PGMCREAT sets PGMCR_FC_EXPORT bit

– Type-2 Command EXPORT TARGET(REPO)

� IMS Sample

– IMS.ADFSSMPL (DFSPGCX0)

49



IMS DB Enhancements

� IMS Dataset encryption

� Use DDL to define IMS Databases (FF and FP)

� DEDB Alter (ALTERDB)

� DEDB Alter for Catalog Managed ACB’s

� Catalog Managed ACB’s

50



IMS TM Enhancements

� UserId propagation

� IMS Connect RACF statistics gathering

� RACF passwords special characters

� IMSRSC for MSC

� IMS Connect max ports 50 -> 200

� More Queue Manager buffers

51



IMS System Enhancements

� Media Manager for IMS Logger

� New MINTHREADS for better performance

� Improved ESAF connection thread management

� Automatic calculation of FP buffers (CNBA)

� CQS automatic structure checkpoint

� SYSGEN improvements

� Consolidation of Logger parameters

52



IMS Application Enhancements

� Workload reporting for mobile

� JVM 64 bit support

� Dynamic PGMCREAT for BMP and JBP

53


� The ability to become more agile by delivering code/function more

frequently

– Eliminates ad hoc SPEs

– Allows flexibility for certain types of changes that are best on a release boundary including:

• Raising the bar on minimum hardware and software levels

• Dropping support for function

• Major changes to infrastructure control blocks

• Changes that require full reassembly of IMS

� IMS 14

– Continues to deliver new function until the next version of IMS

• V15 GA was Oct. 27

IMS is Moving toward Continuous Delivery

Continuous Delivery


Why Continuous Delivery?

Issues with current process

• Two year release cycle causes new function to be delivered too late

� Clients already have solutions in place by the time release is delivered

• Major enhancements not widely exploited across our client set

• Exploitation of new technology is provided too late for clients to be among the

first to exploit for business critical applications

Focus for Continuous Delivery

• Right function is available at the right time

• Strategic function delivered when ready

• Focus is on delivering what our client set needs to drive their business forward


Customer Feedback

• Allow me to enable the function, do not make it a default

• Customers are OK if CD is delivered via the service process

• Deliver code every 4 to 6 months

• Sync deliveries with RSUs

• Delivery and implementation should be consistent within the Z platform



� For the z/OS Environment

– http://www.redbooks.ibm.com/redpapers/pdfs/redp5340.pdf

� For the IMS environment

– https://www.linkedin.com/pulse/do-you-have-questions-ibms-move-continuous-delivery-jasminder-singh

• “In March 2016, this IBM Redpaper was released, articulating how z/OS

was moving to a continuous delivery implementation model. As software that runs on z/OS, IMS chose to align with this and deliver production-

ready features and functions on a more frequent basis.”

– Almost all new functions will be shipped disabled, or turned off with a few

exceptions

• A command or parameter will allow the function to be activated

Continuous Delivery Strategy



� For the IMS Environment…

– The continuous delivery (CD) model is intended to enhance the most recent in-service version of IMS

• As soon as new IMS function or support for new technology is developed

and tested, it is immediately released in a PTF

– When a new version of IMS is released, continuous delivery enhancements are

applied only to the new version of IMS, and the previous version is designated as

a long term support release (LTSR) and is no longer enhanced

• In most cases, new functionality or support is delivered disabled by default, so that you can enable them when you are ready. However, some functionality might be delivered enabled, due to technical or strategic requirements. For those enhancements that are delivered disabled, most will be enabled by a command or new parameter.

• https://www.ibm.com/support/knowledgecenter/SSEPH2_14.1.0/com.ibm.ims14.doc.rpg/ims_cd_process_overview.htm

Continuous Delivery Strategy …

IMS 14 and IMS 14 CDIMS 15 and IMS 15 CD



IMS 15 (5635-A06) Packaging

59



IMS 15 Packaging

IMS 15 Transaction manager Value Unit Edition (VUE)

IMS 15 ETO Value Unit Edition (VUE)

Program number: 5655-TM4

Subscription and Support (5655-TMS)

IMS 15 Database manager Value Unit Edition (VUE)

Program number: 5655-DS5

Subscription and Support (5655-DSR)

IMS Enterprise Suite 3.2

Program number: 5655-TDA

Subscription and Support (5655-T61)

60



Migration

DBRC Migration and Coexistence

MINVERS support

Allows 13.1, 14.1, and 15.1 as the MINVERS values

Default for INIT.RECON command is now MINVERS(‘13.1’)

CHANGE.RECON UPGRADE

The MINVERS value to the greater of 13.1 or to the current existing value

MINVERS 14.1 is required

For DEDB Alter with ALTERAREA for a DEDB area with SDEP defined

For 8 Gigabyte OSAM HALDB

61



IMS 15 Migration/Coexistence

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

DBRC Migration/Coexistence

IMS V13 –APAR PI62555

IMS V14 –APAR PI62558

OTMA TPIPE Parallelism Coexistence

To allow IMS Connect 13 to work with IMS 14 / IMS 15 MULTIRTP

IMS Connect previous versions require compatibility fixes

IMS Connect V13 PM93878 / UK98632

MSC Repository –migration/coexistence on IMS V13, V14

V13 PI49334/UI32565 attribute format map table mig/coex

V14 PI49208/UI32429 attribute format map table mig/coex

IMS 15 Repository function can coexist with lower levels of IMS

62

ims 15 summary final - ibm.com · pdf fileims otma 1) ims otma security prefix is expanded to...

Documents