5650-DB2 IBM DB2 12 for z/OS V12.1

IBM Europe Sales Manual
Revised:  June 06, 2017.

Table of contents
TOC Link Product life cycle dates TOC Link Operating environment
TOC Link Program number TOC Link Planning information
TOC Link Abstract TOC Link Publications
TOC Link Highlights TOC Link Security, auditability, and control
TOC Link Description  

 
Product life cycle dates
Program NumberVRM Announced Available Marketing Withdrawn Service Discontinued
5650-DB212.01.002016/10/042016/10/21 - -
5615-DB211.01.002013/10/012013/10/25 2018/07/02 -
5615-DB211.00.002012/10/032013/03/08 2013/10/25 -

Back to topBack to top
 
Program number
  • DB2 12 for z/OS V12.1.0 (5650-DB2)
  • DB2 11 for z/OS QMF Enterprise Edition V12 and QMF Classic Edition V12 features V11.1.0 (5615-DB2)

Back to topBack to top
 
Abstract

DB2 12 takes DB2 to a new level, both extending the core capabilities and empowering the future. DB2 12 extends the core with new enhancements to scalability, reliability, efficiency, security, and availability. DB2 12 also empowers the next wave of analytics and mobile applications.

DB2 12 delivers selected features that bring valuable benefits to your business.

Extending IBM analytics leadership

  • Improvements in support of analytics workloads, including optimized performance and improved zIIP offload in support of in- transaction analytics. All parallel child task processing is now zIIP eligible.
  • Deliver insights faster with up to 50% elapsed query time improvement.
  • Improved DB2 Analytics Accelerator performance and expanded query support.

Mobile and Internet of Things (IoT) support for your enterprise

  • Support for SQL as a service (SQLaaS) through RESTful connectivity to your DB2 for z/OS data.
  • Support for modernized, multiplatform, automated application deployments using technology such as IBM Urban Code Deploy and z/OSMF, which provide agility and speed to market.
  • Enhanced support for cloud and mobile workloads with dramatic scalability improvements for tables, increasing the maximum table size from 16 TB to 4 PB, enabling support for up to 280 trillion rows in a single DB2 table.
  • Enhanced support for the next generation of mobile applications through the optimization of syntax that is common to mobile workloads such as OFFSET, SQL PL in triggers, and many other improvements.
  • Enhanced load capability that enables cloud and mobile workloads to upload data directly into a table on DB2 z/OS using a new high- performance, low-latency zLOAD API.

IBM Cloud Provisioning and Management

  • DB2 12 exploits the IBM Cloud Provisioning and Management functionality provided in IBM z/OS V2.2.These z/OS cloud capabilities provide added benefits to simplify and improve configuration and deployment of a number of components of the z/OS software landscape, thereby enabling you to improve the agility, efficiency, and economics of your IT infrastructure. With these added cloud capabilities, DB2 12 supports the following capabilities:
    • Rapidly provision environments for workload deployment and release the resources to a shared pool when complete.
    • Enable direct access of z/OS computing resources by end users through your existing self-service portal or by using IBM's sample portal.
    • Create service catalogs with customizable services that exploit the multitenancy and rapid elasticity of z/OS.
    • Invoke these new functions through a web browser-based user interface or through programmable REST interfaces.
    • Provision DB2 12 subsystems and other z/OS software subsystems such as IBM CICS Transaction Server for z/OS, IBM IMS for z/OS, IBM MQ for z/OS, and IBM WebSphere Application Server for z/OS.
    • Provision known DB2 database schemas by leveraging the IBM DB2 Change Management Solution Pack for z/OS, V1.1 (5655-CH1).

Extending the unique value of z Systems

  • Expanded in-memory processing for greater performance improvement and emerging use case support, such as synergy with the latest IBM z Systems processors, which offer significantly expanded memory capacity.
  • Up to 30% CPU improvement for query workloads and even higher CPU improvements in select query workloads exploiting DB2 12 query optimization. Up to 10% online transaction processing (OLTP) CPU savings with larger memory and activation of memory exploitation features.
  • High-volume insert performance equaling two times throughput increase for concurrent sequential insert without clustering.

Simplified management and application deployment

  • More flexible data partitioning enables partitions to grow past previous size limits and new partitions to be dynamically inserted.
  • Extends unprecedented query performance reliability and stability to dynamic SQL with dynamic plan stability.
  • Online schema enhancements that improve manageability and availability, in addition to support for improved partition management, reducing the need for planned outages.
  • Greater than 4GB active log data set, which simplifies log management and improves recovery time.
  • Exploitation of recent z Systems enhancements to compress LOB data, which can dramatically reduce the amount of storage and memory for storing and manipulating large objects.
  • Extended leadership with security enhancements, including support for TRANSFER OWNER and more granular ADMIN authority.
  • Enhanced system administrator capabilities to migrate and install DB2 systems while preventing unwanted access to user data.
  • Optimized management through improved utility performance, usability, and availability of your mission-critical assets through enhanced REORG partition processing, new FlashCopy and system-level backup capability, and further zIIP processor exploitation.
  • Single-phase catalog migration, which reduces the change windows involved in migrating completely to the new release.

Benefiting from enhancements in a faster, more consumable way

  • DB2 12 continually delivers new DB2 capabilities and enhancements in a single service stream as the code becomes ready. The result is that clients can benefit from new capabilities and enhancements without waiting for a new release. Clients can activate the new capabilities when a function level is delivered.
  • Function levels enable you to control the timing of the activation and adoption of new features, with the option to continue to apply corrective and preventative service without adopting new features and functions.

SAP solutions

  • Many enhancements are available for clients using SAP applications on DB2 for z/OS; for instance, query engine improvements and a new UDF cache for SAP Core Data Services (CDS). Also, the Zero Downtime Option (ZDO) of the SAP's Software Update Manager benefits from online DDL improvements. Scalability is enhanced with tables that can grow up to 4 PB in size. For the SAP fast loader, DB2 12 introduces the new ultra-fast remote load capability from DB2 Connect-based clients.
  • SAP has announced their successful validation and support of DB2 12 to run SAP applications immediately when DB2 12 is generally available. Details can be found in SAP Note 2302997.

Back to topBack to top
 
Highlights

IBM DB2 12 for z/OS continues to extend the value delivered to your business by IBM's industry-leading data server, while empowering your future, in the following ways:

  • Delivers business insights faster while helping to reduce costs
  • Enables easy access, scale, and application development for the mobile enterprise
  • Improves in-memory database performance, helping to reduce costs
  • Continues to be the industry gold standard for availability, reliability, and security for business-critical information

Back to topBack to top
 
Description

The demands of the mobile economy and the greater need for faster business insights, combined with the explosive growth of data, present unique opportunities and challenges for companies wanting to take advantage of their mission-critical resources. Built on the proven, trusted availability, security, and scalability of DB2 11 for z/OS and the z Systems platform, the gold standard in the industry, DB2 12 gives you the capabilities needed to securely meet the business demands of mobile workloads and increased mission-critical data. It delivers world-class analytics and OLTP performance in real-time.

DB2 for z/OS delivers innovations in these key areas:

Scalable, low-cost, enterprise OLTP and analytics

DB2 12 continues to improve upon the value offered with DB2 11 with further CPU savings and performance improvements utilizing more memory optimization. Compared to DB2 11, DB2 12 clients can achieve up to 10% CPU savings for various traditional OLTP, and heavy concurrent INSERT query workloads may see higher benefits, with up to 30% CPU savings and even more benefit for select query workload utilizing UNION ALL, large sort, and selective user-defined functions (UDFs).

DB2 12 provides more cost reduction with more zIIP eligibility of DB2 REORG and LOAD utility.

DB2 12 provides deep integration with the IBM z13, offering the following benefits:

  • More efficient use of compression
  • Support for compression of LOB data (also available with the IBM zEnterprise EC12)
  • Faster XML parsing through the use of SIMD technology

Enhancements to compression aids DB2 utility processing by reducing elapsed time and CPU consumption with the potential to improve data and application availability. Hardware exploitation to support compression of LOB data can significantly reduce storage requirements and improve overall efficiency of LOB processing.

DB2 12 includes the new SQL TRANSFER OWNERSHIP statement, enabling better security and control of objects that contain sensitive data. In addition, DB2 12 enables system administrators to migrate and install DB2 systems while preventing access to user data.

The real-world proven, system-wide resiliency, availability, scalability, and security capabilities of DB2 and z Systems continue to be the industry standard, keeping your business running when other solutions may not. This is especially important as enterprises support dynamic mobile workloads and the explosion of data in their enterprises. DB2 12 continues to excel and extend the unique value of z Systems, while empowering the next wave of applications.

Easy access, easy scale, and easy application development for the mobile enterprise:

In-memory performance improvements

As enterprises manage the emergence of the next generation of mobile applications and the proliferation of the IoT, database management system (DBMS) performance can become a critical success factor. To that end, DB2 12 contains many features that exploit in- memory techniques to deliver world-class performance, including:

  • In-memory fast index traverse
  • Contiguous and larger buffer pools
  • Use of in-memory pipes for improved insert performance
  • Increased sort and hash in-memory to improve sort and join performance
  • Caching the result of UDFs
  • In-memory optimization in Declare Global Temporary Table (DGTT) to improve declare performance
  • In memory optimization in Resource Limit Facility to improve RLF checking

DB2 12 offers features to facilitate the successful deployment of new analytics and mobile workloads. Workloads connecting through the cloud or from a mobile device may not have the same performance considerations as do enterprise workloads. To that end, DB2 12 has many features to help ensure that new application deployments are successful. Improvements for sort-intensive workloads, workloads that use outer joins, UNION ALL, and CASE expressions can experience improved performance and increased CPU parallelism offload to zIIP.

Easy access to your enterprise systems of record

DB2 12 is used to connect RESTful web, mobile, and cloud applications to DB2 for z/OS, providing an environment for service, management, discovery, and invocation. This feature works with IBM z/OS Connect Enterprise Edition (z/OS Connect EE,5655-CEE) and other RESTful providers to provide a RESTful solution for REST API definition and deployment.

The IBM Data Studio product, which can be used as the front-end tooling to create, deploy, or remove DB2 for z/OS services, is supported. Alternatively, new RESTful management services and BIND support are provided to manage services created in DB2 for z/OS. This capability was first made available in the DB2 Adapter for z/OS Connect feature of the DB2 Accessories Suite for z/OS, V3.3 (5697-Q04) product, working with both DB2 10 for z/OS and DB2 11 for z/OS.

Overview of DB2 features

DB2 12 for z/OS consists of the base DB2 product with a set of optional separately orderable features. Select features QMF Enterprise Edition V12 and QMF Classic Edition V12 are also made available as part of DB2 11 for z/OS (5615-DB2). Some of these features are available at no additional charge and others are chargeable:

Chargeable features for QMF V12 (features of DB2 12 for z/OS and DB2 11 for z/OS)

QMF Enterprise Edition provides a complete business analytics solution for enterprise-wide business information across end-user and database platforms. QMF Enterprise Edition consists of the following capabilities:

  • QMF for TSO and CICS
  • QMF Enhanced Editor (new)
  • QMF Analytics for TSO
  • QMF High Performance Option (HPO)
  • QMF for Workstation
  • QMF for WebSphere
  • QMF Data Service, including QMF Data Service Studio (new)
  • QMF Vision (new)

New enhancements for each capability are as follows:

QMF for TSO and CICS has significant improvements for the QMF for TSO/CICS client.

  • The QMF process of saving database tables, traditionally accomplished through the QMF SAVE DATA command, has been enhanced. QMF SAVE DATA intermediate results can now be saved to IBM DB2 Analytics Accelerator for z/OS 'Accelerator-only tables'. The ability to save intermediate results in Accelerator-only tables is also available for the command IMPORT TABLE and the new QMF RUN QUERY command with the TABLE keyword. This exploitation of the Accelerator may result in benefits such as improved performance, reduced batch window allocation for QMF applications, and reduced storage requirements.
  • By using the new TABLE keyword on the RUN QUERY command, you can now save data, using the SAVE DATA command, without needing to return and complete a data object. The RUN QUERY command with the TABLE keyword operates completely within the database to both retrieve data and insert rows without returning a report to the user.
  • Usability of the TSO client is improved by the enhanced editor feature (see the QMF Enhanced Editor section for more detail.).
  • Both the TSO and CICS clients now have the ability to organize queries, procedures, forms, and analytics into groups called folders, aiding in productivity and usability. QMF commands such as LIST, SAVE, ERASE, and RENAME have been updated to work with folders.
  • QMF TSO and CICS clients now have additional report preview options. After proper setting of the DSQDC_DISPLAY_RPT global variable, users will be able to enter a report mini-session, where queries can be run to view potential output without actually committing the results. The report mini-session can be useful for running and testing SELECT with change type queries. Upon exiting the report mini-session, the user will be prompted to COMMIT or ROLLBACK the query.
  • With Version 12, QMF's TSO and CICS clients deliver significant performance and storage improvements.
    • Using the new QMF program parameter option DSQSMTHD, users can make use of a second data base thread. The second thread is to be used for RUN QUERY and DISPLAY TABLE command processing. Usage of a second data base thread can assist with performance issues on SAVE operations with an incomplete report outstanding. Additionally, usage of the second thread can reduce storage requirements for SAVE DATA commands on large report objects because rows will not need to reside in storage but can be retrieved from the data base and inserted into the new table as needed.
    • Using the DSQEC_BUFFER_SIZE global variable, the QMF internal storage area used to fetch data base row data can be increased. By changing the default from 4 kilobytes to a value up to 256 kilobytes, QMF can increase the amount of data fetched in a single call to the data base. Less calls to the data base reduces the amount of time it takes to complete the report, which can result in significant performance improvements.
  • QMF's TSO and CICS clients now integrates with QMF Data Service, enabling users of this interface to access a broader range of data sources. The support enables access to z/OS and non-z/OS data sources, including relational and nonrelational data sources (see the QMF Data Service section for a description of accessible data types). This capability is available only through QMF Enterprise Edition.

QMF Enhanced Editor (new) provides usability improvements to the TSO client by bringing customizable highlighting and formatting for SQL syntax, reserved words, functions, and data types, and parenthesis checking. The new query assist feature provides table name suggestions, column name and data type information, and suggested column value information, plus a preview pane.

QMF Analytics for TSO has been enhanced as follows:

  • Three new statistics models have been added: Wilcoxon Signed-Rank Test, Mann-Whitney U Test, and the F-Test model.
  • A user-defined mapping capability has been added. OpenGIS WKT map definitions are available in either DB2 tables or exported data sets, which can be read to format user-specific maps.
  • Maps for Africa, North America, South America, and Germany have been added to the existing library of predefined maps.
  • The ability to choose columns for use in analytical analyses has been improved with enhanced data type targeting and information.
  • Mouse (graphics cursor) support is added for quicker interaction with the QMF Analytics for TSO functionality.
  • Saving analytics has been updated to display a list of existing analytics objects.

QMF for Workstation and QMF for WebSphere add additional support for DB2 Analytics Accelerator and enable QMF objects to be used as virtual tables in QMF Data Service.

  • Administrators now have the ability to specify whether the DB2 Analytics Accelerator should be used by QMF users when available (by database and query) through new resource limit options on the data source or object.
  • QMF Workstation and QMF for WebSphere can now write data to the DB2 Analytics Accelerator. Data can be saved as Accelerator-only tables or Accelerator-shadow tables. Queries could then be created against this data, enabling them to take advantage of the DB2 Analytics Accelerator.
  • QMF will detect DB2 Analytics Accelerator appliances and display these appliances under the data source. Users can also see tables that exist on the DB2 Analytics Accelerator and even add additional tables to the DB2 Analytics Accelerator by dragging and dropping tables into the appliance folder.
  • QMF-prepped data will be made accessible as virtual tables or stored procedures to external applications through data service connectors such as:
    • Mainframe Data Service for Apache Spark on z/OS
    • Rocket DV
    • Rocket Mainframe Data Service on IBM Bluemix
    • IBM DB2 Analytics Accelerator Loader

QMF Data Service enables DB2 QMF to access numerous data sources and greatly eliminates the need to move data in order to perform your analytics. It enables you to obtain real-time analytics insights using a high-performance in-memory mainframe solution.

The need for real-time information requires a high-performance data architecture that can handle the extreme volumes and unique requirements of mainframe data and that is transparent to the business user. DB2 QMF 's new data service includes several query optimization features, such as parallel I/O and MapReduce. Multiple parallel threads handle input requests, continually streaming and buffering data to the client. The mainframe MapReduce technology greatly reduces the elapsed time of the query by accessing the database with multiple threads that read the file in parallel.

Data definitions and schema information are extracted from a variety of places to create virtual tables. All of the implementation details are hidden to the user, presented instead as a single logical data source. The logical data source is easily administered through the new Eclipse-based QMF Data Service Studio. With QMF Data Service Studio, DB2 QMF now supports a broader range of data sources, including:

  • Mainframe: Relational/nonrelational databases and file structures: ADABAS, DB2,VSAM, and Physical Sequential; CICS and IMS
  • Distributed: Databases running on Linux, UNIX, and Microsoft Windows platforms: DB2, Oracle, Informix, Derby, and SQL Server
  • Cloud and big data: Cloud-based relational and nonrelational data, and support for Hadoop

Data prepared in QMF will be made accessible as virtual tables to external applications through Data Service connectors such as:

  • Mainframe Data Service for Apache Spark on z/OS
  • Rocket DV
  • Rocket Mainframe Data Service on IBM Bluemix
  • DB2 Analytics Accelerator Loader

QMF Vision (new) is a web client visualization interface that enables you to create, modify, and drill down on data visualizations that are displayed on a dashboard. Users have the ability to drag and drop whatever dimensions or measures are needed, or add more variables for increased drill-down capability. Column, pie, treemap, geo map, line,scatter charts and many more chart objects are available. This gives a business user the ability to analyze data and provide insights that might not be readily apparent.

The most commonly requested guided analytics capabilities, such as outlier detection and cardinality, are now provided out of the box. These capabilities are integrated into the architecture for an intuitive analysis experience. For one-off decision making, you can quickly create simple reports using the tabular chart, which gives you a line-by-line view of summary data. Reports can be formatted to produce multilevel grouping, hierarchical structures, and dynamic cross tabulations, all for greater readability.

This enhancement simplifies the sharing of insights and collaboration with other users. Dashboards can be dropped into the chat window and other users can immediately start collaborating. They can discuss performance results, strategy, and opportunities and discover new insights about the data. Users can connect to new data sources as well as work with existing QMF queries and tables.

QMF Classic Edition supports users working entirely on traditional mainframe terminals and emulators, including IBM Host On Demand, to access DB2 databases. QMF Classic Edition consists of the following capabilities in V12:

  • QMF for TSO and CICS
  • QMF Enhanced Editor
  • QMF Analytics for TSO
  • QMF High Performance Option (HPO)

Non-chargeable feature of DB2 12 for z/OS:

z/OS Application Connectivity to DB2 for z/OS consists of Universal Database Driver for z/OS Java Edition, a pure Java type 4 JDBC driver. It is designed to deliver high performance and scalable remote connectivity for Java-based enterprise applications on z/OS to a remote DB2 for z/OS database server.

Accessibility by people with disabilities

A US Section 508 Voluntary Product Accessibility Template (VPAT) containing details on accessibility compliance can be found on the IBM Accessibility website.

Section 508 of the US Rehabilitation Act

IBM DB2 12 for z/OS is capable as of October 21, 2016, when used in accordance with IBM's associated documentation, of satisfying the applicable requirements of Section 508 of the Rehabilitation Act, provided that any assistive technology used with the product properly interoperates with it. A US Section 508 Voluntary Product Accessibility Template (VPAT) can be requested at the Product accessibility information website.
Back to topBack to top
 

Operating environment

Hardware requirements

Processors:

DB2 12 operates on z196 or z114, or later, processors running z/OS V2.1, or later. The processors must have enough real storage to satisfy the combined requirements of:

  • DB2 for z/OS
  • z/OS
  • The appropriate DFSMS storage management subsystem components, access methods, telecommunications, batch requirements, and other customer-required applications

DB2 12 will probably require increased real storage as compared to DB2 11 for z/OS.

The configuration must include sufficient I/O devices to support the requirements for system output, system residence, and system data sets. Sufficient disk storage must be available to satisfy the user's information storage requirements and can consist of any direct-access facility supported by the system configuration and the programming system.

Auxiliary storage

DB2 is independent of disk, solid-state devices (SSDs), and tape device type. You can use any magnetic, optical, or tape device that is supported by the data facilities component of DFSMS or the DB2 data sets. Tape products are not supported for databases but can be used for the DB2 archive log and utility functions.

The following DB2 data sets are supported by the following device types:

  • Active recovery log data sets: disk
  • Archive recovery log data sets: disk, tape
  • Image copy data sets: disk, tape
  • Bootstrap data sets: disk
  • User data sets: disk, tape (if migrated by HSM)
  • DB2 catalog data sets: disk
  • Work data sets (for utilities): disk, tape

If these data sets are on disk that is shared with other z/OS systems, you should use global resource serialization to prevent concurrent access by more than one z/OS system.

The minimum disk space requirement, based on installing DB2 using the panel default values, is approximately 1.3 GB. You need additional disk space for your data.

If you use dual logging and tape for the log archiving device, you need at least two tape drives.

Data communication devices

DB2 operations can be controlled from:

  • The system console
  • Authorized IMS Transaction Manager terminals
  • Authorized CICS terminals
  • TSO terminals (by authorized users)

In addition to listing auxiliary storage and data communications devices, this section identifies function-dependent hardware requirements and virtual storage requirements.

Function-dependent hardware requirements for DB2

Certain functions of DB2 12 for z/OS have associated hardware requirements, as specified in the following list. If you do not use these DB2 functions, the hardware requirements do not apply.

  • Date sharing requires the Coupling Facility. See the latest Coupling Facility (CF) level recommended for your processor at the Parallel Sysplex website.
  • DRDA data stream encryption uses the following ICSF APIs: CSNECKM, CSNERNG, CSNFPKB, CSNFPKE, CSNEENC, and CSNEDEC. See the z/OS ICSF Application Programmer's Guide for additional information on the usage of these APIs, including hardware requirements. However, if possible do not use DRDA encryption and instead secure connections by using the z/OS Communications Server IP Application Transparent Transport Layer Security (AT-TLS).
  • DRDA AES user ID password encryption uses the following ICSF APIs: CSNEOWH, CSNERNG, CSNFPKB, CSNFPKE, CSNESYE, and CSNESYD. See the z/OS ICSF Application Programmer's Guide for additional information on the usage of these APIs, including hardware requirements.
  • DSNLEUSR stored procedure uses the following ICSF APIs: CSNBCKM, CSNBENC, and CSNEDEC. See the z/OS ICSF Application Programmer's Guide for additional information on the usage of these APIs, including hardware requirements.
  • Encryption and decryption functions: Built-in functions for encryption and decryption require cryptographic hardware in a cryptographic coprocessor, cryptographic accelerator, or cryptographic instructions.
  • LOB Compression uses zEnterprise Data Compression hardware. The z/OS environment needs to have the zEDC card installed to trigger the data compression capability. The zEnterprise data compress zEDC requires the following:
    • z/OS V2.1 operating system
    • IBM zEnterprise EC12 (with GA2 level microcode) or IBM zEnterprise zBC12
    • zEDC Express feature, which is the z Systems compression accelerator that can improve the speed of data compression and is sharable across up to 15 partitions and up to 8 cards per CPU
    • zEDC Express software feature must be enabled in the IFAPRDxx parmlib member
  • Single Instruction Multiple Data (SIMD) Exploitation with XML Parser requires both a z/OS processor and operating software APAR that supports SIMD instruction, as follows:
    • z13 processor, or above, supporting SIMD instruction
    • z/OS APARs:
      • For z/OS V2.1: z/OS V2.1 APAR OA44545 and APAR OA49910 (see APAR descriptions below)
      • For z/OS V2.2: z/OS V2.2 APAR OA49910
    • APAR OA44545 provides vector processing support for z13 processors that is included in z/OS V2.2.
    • APAR OA49910 allows IEAFP START when an EUT FRR is in effect.
  • Asynchronous Duplexing of CF lock structure requires the following:
    • DB2 12 enabling APAR PI66689
    • IRLM 2.3 APAR PI68378
    • z/OS V2.2 with APAR OA47796 and APAR OA49148
    • CFCC: For current information see the Driver 27 Customer Exception letter at CFCC firmware specified service level

Function-dependent hardware requirements for QMF V12.1 features:

There are six installation entities across the QMF Enterprise Edition and QMF Classic Edition separately orderable, chargeable features.

QMF TSO and CICS clients' requirements:

  • Operates on any z Systems hardware configuration that supports the required software.
  • Runs on any processor that is supported by the operating system. Some operations, however, will not work with columns that contain decimal floating point data if the processor on which QMF is running does not support decimal floating point instructions.
  • Accesses all of the DASD devices that are supported by z/OS and DB2 for z/OS, as well as all display devices supported by Graphical Data Display Manager (GDDM).
  • To implement a national language feature that uses a double-byte character set (DBCS), you need a workstation that supports DBCS. Ensure that this device is supported by GDDM.
    • For the amount of storage required to copy the QMF V12.1 libraries from the distribution media using SMP/E, seethe QMF program directory that is appropriate for your QMF edition and national language.
  • When you plan your region size, consider the storage required to load modules during initialization and the virtual storage requirements for report operations.
  • Restriction: For TSO only, consider the amount of space required to run applications other than DB2 QMF.

DB2 QMF for Workstation requires:

  • A hardware configuration that supports the Microsoft Windows operating system
  • Network connectivity
  • Minimum of 1 GB disk space and 1 GB of RAM

DB2 QMF for WebSphere requires:

  • Hardware configuration that supports the Microsoft or Linux operating systems
  • Minimum of 500 MB disk space
  • Minimum of 1 GB of RAM on each server in which it is installed and an additional 50 MB of RAM for each concurrent user

DB2 QMF Vision requires:

  • Hardware configuration that supports the Microsoft software
  • Minimum of 250 GB disk space and 8 GB of RAM
  • 4-core microprocessor

DB2 QMF Data Service requires:

  • Operates on any z Systems hardware configuration that supports the required software
  • Runs on any processor that is supported by the operating system

DB2 QMF Data Service Studio requires:

  • Any hardware configuration that supports the required Microsoft software
  • Approximately 1 GB of disk space (single language installation)
  • Minimum of 1 GB of RAM
  • Network connectivity

Software requirements

This section lists licensed programs or specific elements and features of licensed programs that are required in the DB2 12 environment. You can use subsequent versions or releases of the programs, unless stated otherwise. This section also identifies requirements that are associated with specific DB2 capabilities and optional programs that you can use with DB2 12. For the most current information, see the IT Infrastructure website.

Operating system and support programs

DB2 12 requires the function that is provided by the following licensed programs or their equivalents. Subsequent versions or releases of these products are acceptable.

  • z/OS Version 2.1 Base Services (5650-ZOS), or later, with the following base and optional elements:
    • DFSMS V2.1, or later
    • Language Environment Base Services
    • z/OS V2.1 Security Server (RACF), or later
  • IRLM V2.3 (delivered with DB2 12)

If DB2 12 is installed with IRLM V2.3 into the same SMP/E zone as any version of IMS with IRLM V2.3, IRLM V2R2 will be deleted during the SMP/E installation of IRLM V2.3

Notes:

  • New functions are available only after new function is activated unless explicitly stated otherwise in the product documentation. A general exception exists for optimization and virtual storage.
  • z/OS Unicode Services and appropriate conversion definitions are required. For additional information on Unicode conversions, see the the DB2 12 for z/OS Installation and Migration information and also Support for Unicode: Using Conversion Services, SA22-7649.
  • Some of the basic operation of a DBMS is provided by utility functions, such as backup, recovery, reorganization, loading and unloading data, gathering statistics and checking data, indexes, and large objects. Clients should ensure that these functions are provided either by ordering DB2 Utilities Suite for z/OS, V12.1 (5770-AF4) or by obtaining equivalent function elsewhere.

Virtual storage requirements

Most of DB2 data resides in shared memory of the DB2 address spaces, above the bar. DB2 12 requires 1 TB contiguous of 64-bit shared private storage above the 2 GB bar for each DB2 subsystem. This storage is virtual, controlled by the z/OS HVSHARE parameter in IEASYSxx. This storage is not backed at allocation, only as it is used. Most control blocks and buffers reside in the extended private area above the 2 GB bar, while modules and some data resides above the 16 MB line, but below the 2 GB bar.

The amount of space needed for the common service area (CSA) below the 16 MB line is less than 40 KB for each DB2 for z/OS subsystem and 24 KB for each IRLM subsystem. High concurrent activity, parallelism, or high contention can require more E/CSA. The amount of 64-bit above the bar common storage needed for each DB2 subsystem is a minimum of 6 GB contiguous controlled by the z/OS HVCOMMON parameter in IEASYSxx. Configure additional megabytes of 1MB LFAREA for maximum benefit.

DB2 12 requires that data sets for the catalog and directory reside on SMS-managed storage. These data sets must belong to an SMS data class that is defined with the extended addressability (EA) attribute. See prefix.SDSNSAMP(DSNTIJSS) for a sample SMS environment.

Function-dependent program requirements

The following functions of DB2 require specific licensed programs or features of licensed programs before they can be used.

Application execution: Applications written in high-level programming languages, such as applications or stored procedures written in the C language and using the ODBC or CLI interfaces to DB2, require Language Environment at run time. Applications or stored procedures written in Java, such as those using the JDBC or SQLJ interfaces to DB2, require IBM SDK for z/OS, Java 2 Technology Edition V6, or later, at runtime.

Requirements for dependent functions of DB2 12 for z/OS

Before using these features, see the installation information for these features to ensure you have all required and recommended products.

  • System-level Point-in-Time (PIT) Backup and Recovery function needs:
    • DFSMShsm
    • DFSMSdss
    • FlashCopy V1 (required for volume-level FlashCopy support for system-level backup and recovery)
    • FlashCopy V2 (required for data-level FlashCopy, enabling object- level recovery from system-level backup and FlashCopy image copy)
  • Encryption and decryption functions
    • Built-in functions for encryption and decryption require z/OS Cryptographic Services Integrated Cryptographic Service Facility (ICSF).
  • DRDA Data Stream Encryption can optionally use z/OS Cryptographic Services Facility (ICSF).

Requirements for dependent functions of the QMF features

QMF for TSO and CICS clients require:

  • IBM z/OS, V2.1, or later (5650-ZOS)
  • One of the following IBM DB2 for z/OS releases:
    • DB2 for z/OS, V11 (5615-DB2)
    • DB2 for z/OS Value Unit Edition, V11 (5697-P43)
    • DB2 for z/OS, V12 (5650-DB2)
    • DB2 for z/OS Value Unit Edition, V12 (5770-AF3)

QMF for Workstation requires one of the following operating systems:

  • Microsoft Windows Vista
  • Windows 7
  • Windows 8
  • Windows Server 2008
  • Windows Server 2012
  • Windows 10

QMF for WebSphere requires:

  • One of the following application web servers:
    • IBM WebSphere Application Server 7 or WebSphere Application Server 8 ( Note: QMF V12.1 has only been tested with WebSphere Application Server 8.5 and later.)
    • Apache Tomcat 7 or Apache Tomcat 8 DB2
  • To enable Data Service connectivity, Java 7, or later, is required. ( Note: QMF V12.1 uses the Data Server JDBC driver, which only supports Java 7, or later.)

QMF Vision installation entities requires:

  • One of the following operating systems:
    • Windows 7 64-bit, Windows Server 2008 R2 Service Pack 1, or Windows Server 2012with .NET Framework 3.5 enabled
  • One of the following browsers:
    • Chrome version 50.0.2661.102, or later
    • Firefox version 47.0.1, or later
    • Microsoft Edge version 25.10586.0.0, or later
    • Safari version 9.0.3, or later

DB2 QMF Data Service installation entities requirements:

  • IBM zEnterprise 114 (z114), IBM zEnterprise 196 (z196), or more recent IBM zEnterprise system
  • IBM z/OS, V2.1, or later (5650-ZOS)

Data Service load library

  • The load library for Data Service is allocated as a partitioned data set extended (PDSE). When a PDSE is used to store load modules, it stores them in structures called program objects .
  • You cannot copy a PDSE to a partitioned data set (PDS). For more information, see the IBM z/OS documentation.

Program Temporary Fixes (PTFs)

  • When you use VSAM data access with Data Service, you need to add the following PTFs:
    • RLS OA44111:
      • z/OS V1.13 UA75045
      • z/OS V2.1 UA75046
    • VSAM:
      • z/OS V1.13 UA75272

The QMF Data Service Studio installation entity requires one of the following operating systems:

  • Windows 8, Windows 7, Windows Vista, Windows Server 2012, Windows Server 2008, or Windows 10

Mandatory operational requisites of the QMF features

The TSO and CICS clients of QMF V12.1 operate with:

  • DB2 for z/OS, V10 (5605-DB2) (all modes except CM8, CM8, ENFM8, ENFM8) with APARs PM50434 and PM72274
  • DB2 for z/OS Value Unit Edition (5697-P31) (all modes except CM8, CM8, ENFM8, ENFM8) with APARs PM50434 and PM72274
  • DB2 for z/OS, V11 (5615-DB2)
  • DB2 for z/OS Value Unit Edition, V11 (5697-P43)
  • DB2 for z/OS, V12 (5650-DB2)
  • DB2 for z/OS Value Unit Edition, V12 (5770-AF3)

In addition:

  • For advanced graphical capabilities of the QMF Analytics for TSO client, GDDM-PGF, a component in z/OS, is required.
  • DB2 QMF for TSO and CICS running under CICS requires CICS Transaction Server for z/OS.
  • QMF Vision requires MongoDB 3.X , or later, to be installed. This is done when the optional QMF Vision component is selected during the QMF install and you are asked to download/install Mongo during this part of the QMF install.

The program's specifications and specified operating environment information may be found in documentation accompanying the program, if available, such as a readme file, or other information published by IBM, such as an announcement letter. Documentation and other program content may be supplied only in the English language.

Limited-use license for z/OS Application Connectivity to DB2 for z/OS

The zero-priced z/OS Application Connectivity to DB2 feature, a Type 4 JDBC driver, is licensed for installation and use solely on z/OS. Its sole authorized use is limited to connecting an application that runs on z/OS to Version 10, 11, or 12 of DB2 for z/OS running in a separate partition on the same server as the application or on a different z/OS server. You can also connect applications to a subsequent supported version of DB2 UDB for z/OS. Authorized use does not extend to applications that run on Linux or any other platform or operating system.

Optional program requirements

The following functions are enabled in conjunction with the specified optional licensed programs when used together with DB2. Note that the information is for expected toleration support for DB2 12.

Connectivity

For database applications that run on Linux, UNIX, or Windows operating systems, clients can use DB2 Connect, and then perform one of the following actions:

  • Install the IBM Data Server Driver package and deploy one of the client drivers to access DB2 for z/OS through a DB2 Connect Server.
  • Install the IBM Data Server Driver package and deploy one of the provided client drivers to access DB2 for z/OS directly.

Both of these approaches, direct access or access through the gateway, provide runtime support to access DB2 by applications that use ODBC, CLI, .NET, OLE DB, PHP, Ruby, JDBC, pureQuery, JPA, SQLJ, Python, Perl, and more. These approaches can be used alone or in combination, as needed.

It is recommended to use one of the client drivers provided with the IBM Data Server package (without the use of a DB2 Connect server) when accessing a remote DB2 for z/OS subsystem. To choose the right IBM Client Package for your needs, see the IBM DB2 10.5 for Linux, UNIX and Windows documentation at IBMKnowledge Center.

DB2 for z/OS supports DRDA as an open interface, enabling access from any client.

DB2 Connect V10.5 with the latest fix pack is the minimum requisite for DB2 12 for z/OS. All versions can access DB2 12 for z/OS, and special builds can be provided to exploit some of the DB2 12 features requiring IBM Data Server Changes, such as the following features:

  • A new client API to provide fast loading from mobile devices
  • A new client API to determine the DB2 function level
  • Support for continuous delivery
  • Improved security and scalability for client Sysplex workload balancing
  • Improved Sysplex support for distributed global transactions
  • Support for preserving prepared dynamic statements after a ROLLBACK
  • Improved client serviceability aids

DB2 12 acting as a client supports the following relational database products:

  • IBM DB2 Advanced Enterprise Server Edition for Linux, UNIX, and Windows, V10.5, or later (5725-L47)
  • IBM DB2 Enterprise Server Edition for Linux, UNIX and Windows, V9.7, or later (5765-F41)
  • IBM DB2 Advanced Workgroup Server Edition for Linux, UNIX, and Windows, V10.5, or later (5725-L15),
  • IBM DB2 Workgroup Server Edition for Linux, UNIX, and Windows V9.7, or later (5765-F35)
  • IBM DB2 Developer Edition, V9.7, or later (5724-N76)
  • Any other DRDA-compliant relational DBMS server

Web connectivity is provided by any of the DB2 Connect clients using one of the IBM Data Server clients or drivers.

For support services, go to the IBM Software website.

JDBC

DB2 12 supports the following JDBC APIC specification levels:

JDBC 3.0 API requires any of the following at run time:

  • IBM 31-bit SDK for z/OS, Java Technology Edition, V7 (SDK7) (5655-W43), or later
  • IBM 64-bit SDK for z/OS, Java Technology Edition, V7 (SDK7) (5655-W44), or later
  • IBM 31-bit SDK for z/OS, Java Technology Edition, V6 (SDK6) (5655-R31), or later
  • IBM 64-bit SDK for z/OS, Java Technology Edition, V6 (SDK6) (5655-R32), or later

JDBC 4.0 API requires any of the following at run time:

  • IBM 31-bit SDK for z/OS, Java Technology Edition, V7 (SDK7) (5655-W43), or later
  • IBM 64-bit SDK for z/OS, Java Technology Edition, V7 (SDK7) (5655-W44), or later
  • IBM 31-bit SDK for z/OS, Java Technology Edition, V6 (SDK6) (5655-R31), or later
  • IBM 64-bit SDK for z/OS, Java Technology Edition, V6 (SDK6) (5655-R32), or later

For more information on SDKs, go to the IT Infrastructure website and the IBM developer kits lifecycle dates website.

The following transaction management products work with DB2 12:

  • Information Management System (IMS)
    • IMS V14 (5635-A05)
    • IMS V13 (5635-A04)
  • Customer Information Control System (CICS)
    • CICS Transaction Server for z/OS, V5.1, V5.2, and V5.3 (5655-Y04), or later
    • CICS Transaction Server VUE for z/OS, V5.1, V5.2, and V5.3 (5722-DFJ), or later
    • CICS Transaction Server for z/OS, V4.1 and V4.2 (5655-S97), or later

Query support

The following query program works with DB2 12:

  • IBM DB2 Query Management Facility (QMF) family of products, Version 11 and 12

Programming languages

The following application development programming languages can be used to build applications for DB2 12:

Building applications using a DB2 precompiler:

  • Assembler
    • High Level Assembler, part of the System Services element of z/OS
  • C/C++
    • C/C++ (without Debug Tool), which is an optional priced feature of z/OS
  • COBOL (one of the following):
    • Enterprise COBOL for z/OS, V3.4 (5655-G53)
    • Enterprise COBOL for z/OS, V4.1 (5655-S71), or later
    • Enterprise COBOL for z/OS, V5.1 (5655-W32)
  • Fortran
    • VS Fortran V2.6 (5668-806, 5688-087, 5668-805); new data types and new SQL functions are not supported since DB2 9 for z/OS.
  • PL/I
    • Enterprise PL/I for z/OS, V3.9 (5655-H31)
    • Enterprise PL/I for z/OS, V4.1 (5655-W67), or later

Building applications using a DB2 coprocessor:

  • C/C++
    • C/C++ (without Debug Tool), which is an optional priced feature of z/OS
  • COBOL (one of the following):
    • Enterprise COBOL for z/OS, V3.4 (5655-G53)
    • Enterprise COBOL for z/OS, V4.1 (5655-S71), or later
    • Enterprise COBOL for z/OS, V5.1 (5655-W32)
  • PL/I (one of the following):
    • Enterprise PL/I for z/OS, V3.9 (5655-H31)
    • Enterprise PL/I for z/OS, V4.1 (5655-W67), or later

Building applications that are not supported with a precompiler or coprocessor:

  • Java: Applications or stored procedures written in Java, such as those using the JDBC or SQLJ interfaces to DB2, require IBM 31-bit SDK for z/OS, Java Technology Edition, V6 (SDK6) (5655-R31), or later, at run time. Optionally, the following may be used for applications written in Java:
    • IBM 64-Bit SDK for z/OS, Java Technology Edition, V6 (SDK6) (5655-R32), or later, at run time
    • Note: PIDs 5655-R31 and 5655-R32 are independent products and can coexist on the same z/OS system.

      For more information on SDKs, go to the IT Infrastructure website and the IBM developer kits lifecycle dates website.

  • REXX
    • z/OS V2R1 TSO/E REXX Reference (5650-ZOS)
  • SQL Procedure Language
    • Native SQL Procedure Language
    • External SQL Procedure Language, which requires a C language compiler
  • APL2 (one of the following):
    • Mainframe APL2 V2.2 (5688-228) (full APL2)
    • APL2 Application Environment (5688-229)

Operational support

The following programs provide operational support for DB2 12:

DFSMS features, part of the Systems Management optional feature of z/OS, specifically:

  • DFSMShsm for archiving
  • DFSMSdss for concurrent copy in utilities

Tools support

The following tools are the minimum level that provide support for DB2 12 for z/OS. For details on any additional requirements, go to the DB2 Tools Compatibility for DB2 12 for z/OS website.

IBM Tools for Database Administration and System Management Support, including the following tools:

  • DB2 Administration Solution Pack for z/OS, V2.2 (5697-DAQ)
  • DB2 Administration Tool for z/OS, V11.2 (5655-DAT), with APAR PI67731, or higher
  • DB2 Configuration Manager for z/OS, V4.1 (bundled in the DB2 Admin Solution Pack V2.2 (5697-DAQ))
  • DB2 Object Comparison Tool for z/OS, V11.2 (5655-DOC)
  • DB2 Query Workload Tuner for z/OS, V5.1 (5655-AB4)
  • InfoSphere Guardium Data Encryption for IMS and DB2 Databases, V1.2 (5655-P03)

IBM Tools for Database Application Management, including the following tools:

  • IBM DB2 Analytics Accelerator for z/OS, V5.1 (5697-DA5)
  • IBM DB2 Analytics Accelerator Loader for z/OS, V2.1 (5639-OLE)
  • IBM Application Performance Analyzer for z/OS, V13.1 (5655-Q09)
  • IBM DB2 Table Editor for z/OS, V4.5 (5697-G65)
  • IBM Debug Tool for z/OS, V13.1 (5655-Q10)
  • IBM Fault Analyzer for z/OS, V13.1 (5655-Q11)
  • IBM File Manager for z/OS, V13.1 (5655-Q12)

IBM Tools for Performance Management, including the following tools:

  • DB2 Management Solution Pack for z/OS, V1.1 (5655-MSP)
  • DB2 Performance Solution Pack for z/OS, V1.4 (5655-E74)
  • DB2 Query Monitor for z/OS, V3.2 (5655-V42)
  • DB2 SQL Performance Analyzer for z/OS, V5.1 (5697-W51)
  • IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS, V5.3 (5655-W37)

IBM Tools for Replication Management, including the following tools:

  • IBM InfoSphere Data Replication for DB2 for z/OS, V10.2.1 (5655-DRP), with APAR PI49204

IBM Tools for Utilities Management, including the following tools:

  • DB2 Utilities Solution Pack for z/OS, V3.1 (5697-USP)
  • DB2 Extended Utilities Suite for z/OS, V1.1 (5655-EUS)
  • DB2 Automation Tool for z/OS, V4.2 (5655-E37)
  • DB2 Cloning Tool for z/OS, V3.2 (5655-N15)
  • DB2 High Performance Unload for z/OS, V4.3 (5655-AA1)
  • DB2 Sort for z/OS, V2.1 (5655-AA9)
  • DB2 Utilities Enhancement Tool for z/OS, V2.2 (5655-T58)
  • DB2 Utilities Suite for z/OS, V12.1 (5770-AF4)

Back to topBack to top
 
Planning information

Customer responsibilities

Review the sections that describe the hardware and software dependencies for DB2 12 and QMF V12 features.

The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.

Migration considerations

DB2 12 is upwardly compatible with earlier releases of DB2 for z/OS. Migration with full fallback protection is available for clients running on DB2 11 for z/OS. Existing clients should ensure that they are successfully running on DB2 11 for z/OS (NFM) before migrating to DB2 12 for z/OS. Fallback SPE APAR PI33871 must be applied.

DB2 12 APAR PI69143 extends APPLCOMPAT to support controlling the use of new DB2 12 function for DDL and DCL (GRANT, REVOKE, TRANSFER) in DB2 12. Application of APAR PI69143 is required prior to starting DB2, to ensure that objects created with DB2 12 dependent capability or function are properly recorded in the DB2 catalog.

Clients should also use FIX CATEGORIES IBM.Migrate-Fallback.DB2.V12 and IBM.Coexistence.DB2.SYSPLEXDataSharing to identify and apply fixes that enable prior releases of DB2 to migrate to or fallback from DB2 12 for z/OS and fixes that enable DB2 11 to co-exist when in data sharing mode, respectively.

For more information on FIXCAT, go to the IBM Fix Category Values and Descriptions website.

Deprecated functions

During migration, be aware of the functions that are deprecated in DB2 12. Although they are supported in DB2 12, support for these functions might be removed in the future. Avoid creating new dependencies that rely on these functions, and if you have existing dependencies on them, develop plans to remove these dependencies.

The following functions are deprecated in DB2 12:

Resource limit table formats: DSNRLMTxx table formats and related index formats earlier than the DB2 11 format are deprecated in DB2 12. If tables with deprecated formats are detected, DB2 issues message DSNT732I, processing for the START RLIMIT command continues, and the resource limit facility starts using the deprecated objects.

Some BIND PLAN and REBIND Plan command options are no longer supported:

  • The MEMBER option of BIND PLAN and REBIND PLAN is no longer supported. If you specify MEMBER, DB2 issues a warning message, binds the specified DBRM into a package, and binds the package into a plan.

The following subsystem parameters are deprecated in DB2 12:

  • MATERIALIZE _NODET_SQLTUDF
    • In later DB2 releases, user-defined SQL table functions that are not defined with NOT DETERMINISTIC always behave as if MATERIALIZE_NODET_SQLTUDF is set to YES.

For current information on DB2 12 deprecated functions, go to IBM KnowledgeCenter website.

Compatibility

DB2 12 for z/OS is upwardly compatible with earlier releases of DB2 for z/OS. Migration with full fallback protection is available for clients who are running on DB2 11 for z/OS. Existing clients should ensure that they are successfully running on DB2 11 for z/OS (in new- function mode) before migrating to DB2 12 for z/OS. Fallback SPE APAR PI33871 must be applied.

Clients should also use FIX CATEGORIES IBM.Migrate-Fallback.DB2.V12 and IBM.Coexistence.DB2.SYSPLEXDataSharing to identify and apply fixes that enable prior releases of DB2 to migrate to or fallback from DB2 12 for z/OS and fixes that enable DB2 11 to co-exist when in data sharing mode, respectively.

For more information on FIXCAT, go to the IBM Fix Category Values and Descriptions website.
Back to topBack to top
 

Publications

A memo, program directory, and one copy of the following publications are supplied automatically with the basic machine- readable material:

DB2 12 for z/OS (5650-DB2)

DB2 12 for z/OS feature:

Title                                                       Order
                                                            number
----------------------------------------------------------- ---------
DB2 12 for z/OS Program Directory (ENU and JPN)             GI13-4624
DB2 12 for z/OS License Program Specification (ENU and JPN) GC27-8853

QMF Enterprise Ed 12 feature:

Title                                              Order
                                                   number
-------------------------------------------------- ---------
QMF Enterprise Edition V12 Program Directory (ENU) GI13-4627
QMF distributed components DVD kit                 LK5T-8907
QMF Enterprise Edition V12 Program Directory (MUL) GI13-4628
QMF distributed components DVD kit                 LK5T-8907

QMF Classic Ed 12 feature:

Title                                           Order
                                                number
----------------------------------------------- ---------
QMF Classic Edition V12 Program Directory (ENU) GI13-4625
QMF Classic Edition V12 Program Directory (MUL) GI13-4626

z/OS Application Connectivity to DB2 for z/OS feature:

Title                                                          Order
                                                               number
-------------------------------------------------------------- ---------
z/OS Application Connectivity to DB2 for z/OS Program          GI13-4629
Directory

DB2 11 for z/OS (5615-DB2)

QMF Enterprise Edition V12 feature:

Title                                             Order
                                                  number
------------------------------------------------- ---------
QMF 12 Enterprise Edition Program Directory (ENU) GI13-4635
QMF distributed components DVD kit                LK5T-8907
QMF 12 Enterprise Edition Program Directory (MUL) GI13-4636
QMF distributed components DVD kit                LK5T-8907

QMF Classic Edition V12 feature:

Title                                          Order
                                               number
---------------------------------------------- ---------
QMF 12 Classic Edition Program Directory (ENU) GI13-4633
QMF 12 Classic Edition Program Directory (MUL) GI13-4634

Back to topBack to top
 
Security, auditability, and control

DB2 12 for z/OS uses the security and auditability features of the host z/OS systems. It also provides facilities for the protection and control of its resources. These facilities include controls for:

  • System access
  • Data access and control
  • Concurrent access
  • Data recovery
  • Accounting and auditing
Trademarks

(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

** Company, product, or service name may be a trademark or service mark of others.
 © IBM Corporation 2017.
Back to topBack to top

Contact IBM

Considering a purchase?