Protect IBM® z/OS® data and simplify compliance by encrypting data in full-function VSAM databases on the IMS log and in selected other data sets according to encryption policy—with minimal CPU overhead and without application changes and SLA impacts.
The need to protect sensitive client data has never been greater. With IMS 15.2 data on IBM z15, you can tag data in IMS storage as sensitive to ensure that it is redacted from data dumps that are traditionally used in diagnostics.
Centralized mainframe workloads and their interdependencies can make performance problems hard to isolate and resolve. The IBM z/OS Workload Interaction Correlator leverages summary data of middleware like IMS to dynamically define and correlate performance anomalies, making it easy to isolate and resolve those anomalies.
Propagate original user identities from distributed environments to IBM IMS™ with auditability and callout security. You can also report workloads for mobile transactions. IMS 15 works with IBM z/OS Workload Manager to track and report on mobile transactions and the amount of processing that they use.
Enable 64-bit storage and efficient memory management for native Java applications. IMS can capture the usage statistics for JVMs that run in IMS-dependent regions at specified time intervals, including elapsed run time, heap memory used, threads processed and more. The statistics can be viewed in System Management Facility (SMF). You can also use a new DD statement—//STDENV DD—in the dependent region startup JCL for improved security, flexibility and control over JVM settings.
Clients with applications that drive heavy OTMA transaction processing are familiar with the performance impact of message notification, TPIPE cleanup, and TPIPE flood control due to message volumes. With IMS 15.2 some OTMA messages can be processed in the shared queues environment; add to that a newly modified TPIPE cleanup process and enhanced TPIPE flood control and expect to see new efficiencies in OTMA message processing.
Help maximize performance by using the IMS logger to exploit DFSMS Media Manager hardware features. Improve CPU utilization by using CPOOL instead of STORAGE OBTAIN. A new parameter for the number of concurrent active threads—MINTHRDS—enables you to tune the minimum number of concurrent active threads for an individual data store. ESAF connection thread management reduces overhead on IMS connections to the ESAF.
Increase the maximum number of ports from 50 to 200. Support is added for specifying a timeout for idle connections. An option is included to generate a new unique client ID when a duplicate is detected.
Value unit pricing option
One-time-charge versions of IMS TM and IMS DB are offered for applications or workloads deployed in qualified IBM Z New Application License Charge logical partitions.
IMS 15 requires the following minimum version, release or modification levels (as long as those versions remain available and supported by IBM):
IBM z/OS and IBM Z® systems processor
IBM Db2®, IBM CICS®, IBM WebSphere® MQ and IBM WebSphere Application Server
IMS 15 runs only in z/Architecture® mode on an IBM System z10® processor or higher.