z/OS system requirements

The z/OS system has the recommended operating system version of 2.3 or later.
The Db2 for z/OS source uses Db2 version 11 or 12.
The Db2 subsystem has Application Connectivity to Db2 and the following features enabled:
Distributed data facility (DDF) access to Db2
TCP/IP protocol
If Application Connectivity is not enabled, see the following IBM documentation for more information:
For Db2 11: https://www.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/java/src/tpc/imjcc_jccinstallwithoutdb2z.html
For Db2 12: https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/java/src/tpc/imjcc_jccinstallwithoutdb2z.html
Ensure that a Workload Manager (WLM) address space exists for executing the Mass Ingestion Databases stored procedure.
If you have not set up a Db2 WLM address space, see the following IBM documentation for more information:
For Db2 11: https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/inst/src/tpc/db2z_setupwlmenvironment.html
For Db2 12: https://www.ibm.com/support/knowledgecenter/en/SSEPEK_12.0.0/inst/src/tpc/db2z_setupwlmenvironment.html
Ensure that the library where the stored procedure for Db2 for z/OS CDC will be received exists and is APF-authorized on the z/OS system.

Install the Stored Procedure Libraries and Customize the JCL

Verify that the Db2 for zOS Database Ingestion connector is available.
The Db2 for zOS Database Ingestion connector package contains the Db2 for z/OS stored procedure libraries. When the connector is enabled for the Secure Agent Group (runtime environment), the connector package .zip file is downloaded to the downloads folder in the installation location. The package name has the format package-DB2ZMI.
nnnnn
, where
nnnnn
is an incremented package version number. If multiple package versions exist, use the latest one.
Unzip the package-DB2ZMI.
nnnnn
.zip file. The stored procedure files are added to the Db2WLMStoredProcedure folder under the package name.
Use FTP to transfer the #STPINST file in the Db2WLMStoredProcedure folder to a sequential file, PDS, or PDSE on the z/OS system.
Notes:
Transfer the file without binary mode set.
Add a High Level Qualifier (HLQ) if needed to meet system requirements.
Use FTP or another file transfer method to transfer the DBMI.ZOS.DBRMLIB.XMI file to a data set on the z/OS system.
Notes:
Add or edit the High Level Qualifier (HLQ) if needed to meet system requirements.
Transfer the file in binary mode.
Ensure that the data set has the DCB attributes of LRECL=80, BLKSIZE=3120, and RECFM=FB.
You might need to pre-allocate the data set to specify the required attribute values.
Use FTP or another file transfer method to transfer the DBMI.ZOS.LOADLIB.XMI file to the z/OS system.
Notes:
Add or edit the High Level Qualifier (HLQ) if needed to meet system requirements.
Transfer the file in binary mode.
Ensure that the data set has the DCB attributes of LRECL=80, BLKSIZE=3120, and RECFM=FB.
You might need to pre-allocate the data set to specify the required attribute values.

Receive the DBRMLIB transmit data set:
RECEIVE INDATASET(DBMI.ZOS.DBRMLIB.XMI)
Notes:
If you specified a HLQ when transferring the data set to z/OS, include the HLQ.
When you see message
INMR906A Enter restore parameters or 'DELETE' or 'END' +
, enter your APF-authorized library:
DA(
your.library_name) UNIT(
unit) VOLUME(
volume)
The UNIT() and VOLUME() operands are optional. Include them if your installation does not put RECEIVE files on a work unit or volume by default.
Receive the LOADLIB transmit data set:
RECEIVE INDATASET(DBMI.ZOS.LOADLIB.XMI)
Use the same guidelines as in Step 1.
Customize the #STPINST file that contains the stored procedure JCL for your environment.
The JCL creates the stored procedure and a global temporary table that holds the results of the requests to the Db2 IFI for data. It also binds the stored procedure package.
Notes:
Based on the comments at the top of the JCL file, replace variables in the JCL with the values appropriate for your z/OS environment, including the Db2 subsystem name (!DSN!), stored procedure schema name (!SCHEMA!), stored procedure name (!STRPRC!), WLM environment name (!WLMENV!), and the name of the DBRMLIB transmit data set (!DBRMLIB! received in Step 1.
If you used a HLQ for the received data sets, include the HLQ in the JCL.
The WLM environment name is specified in the procedure APPLENV parameter or in the EXEC PARM of the WLM address space.
In the procedure parameter:
//STARTING EXEC DSNBWLMG,DB2SSN=DSNB,
APPLENV='DSNBWLM_GENERAL'
In the EXEC PARM:
PARM='DSNB,40,
DSNBWLM_GENERAL'
You can use the received LOADLIB library after it is APF-authorized, or copy the contents of the library to your own APF-authorized library.
The STEPLIB concatenation in the WLM address space must contain only APF-authorized libraries for the Db2 IFI to run.

Permissions Required for Executing the Stored Procedure on z/OS

Ensure that the user who executes the stored procedure job has SYSADM authority, or ask the Db2 for z/OS DBA to run it.

For the stored procedure to run, you must grant the following Db2 permissions to the procedure schema name specified in the #STPINST JCL file:

SELECT authority on Db2 catalog tables:

GRANT SELECT ON SYSIBM.* TO 
schema;

EXECUTE authority on the package name specified in the JCL.

GRANT EXECUTE ON PACKAGE 
package_name TO 
schema;

GRANT INSERT, DELETE ON 
schema.
stored_procedure_name_RS_TBL TO 
user