System requirements
Product compatibility matrix
Db2 support
This version of UNLOAD PLUS supports IBM Db2 Versions 12 and later.
System requirements
This version of UNLOAD PLUS has the following system requirements:
- IBM System z10 processor or a later 64-bit z/Architecture processor
- Minimum hardware EC12 and Z114
- z/OS Version 2.4
Software requirements
This version of UNLOAD PLUS has the following requirements for additional IBM or BMC software:
- For all types of unload jobs, you must have a minimum of the following versions of BMC common components:
- Version 2.4.01 of BMCSORT
- Version 13.1.00 of the Db2 Utilities Common Code (D2U)
- Version 13.1.00 of the Db2 Solution Common Code (SCC)
To use SHRLEVEL CHANGE CONSISTENT YES when unloading data, UNLOAD PLUS requires version 6.2.01 or later of either the BMC SUF (also known as XBM) product.
For Db2 V13 support, XBM PTF BPE0556 is required. If you use the XBMID option to specify a particular SUF (also known as XBM) subsystem, that subsystem must be at this maintenance level. If you do not specify a particular SUF (also known as XBM) subsystem and SHRLEVEL CHANGE CONSISTENT YES is in effect, UNLOAD PLUS searches for an SUF (also known as XBM) subsystem at this level.
- To offload eligible processing to a zIIP, UNLOAD PLUS requires version 6.2.01 or later of either SUF (also known as XBM).
If you use the XBMID option to specify a particular SUF (also known as XBM) subsystem, that subsystem must be at this maintenance level. If you do not specify a particular SUF (also known as XBM) subsystem and ZIIP ENABLED is in effect, UNLOAD PLUS searches for an SUF (also known as XBM) subsystem at this level.
Required authorization
Using UNLOAD PLUS requires that you have the appropriate authorization within Db2 and through your system security package, such as the IBM Resource Access Control Facility (RACF) component of the z/OS Security Server.
You need sufficient authorization to access resources and perform the tasks accomplished during UNLOAD PLUS processing.
Authorization verification mechanisms for the Utility products
The products use one of the following mechanisms to verify authorization:
If the Db2 DSNX@XAC authorization exit is available for your system, the product uses this exit to verify authorization for external access. The exit is available from the following sources:
- IBM provides a sample exit with Db2 for the IBM Resource Access Control Facility (RACF) component.
- CA Technologies provides the DSNX@XAC exit with the CA-ACF2 and CA-Top Secret products.
We recommend this mechanism for implementing external security. The access control authorization exit must be available in the STEPLIB, JOBLIB, linklist, or in the SYS3.DSN exit.
- If the DSNX@XAC exit is not available, the product uses the standard Db2 method to check security.