Generating tailored Db2 migration or function level activation jobs in the background
You can run a batch job to invoke the Db2 installation CLIST as a background process to generate JCL jobs and other artifacts, without viewing the Db2 installation CLIST panels in interactive mode. You can use this approach to generate artifacts for migrating Db2 to a new release or activating Db2 function levels.
Before you begin
You must use SMP/E to load the required Db2 13 libraries, as described in Making the Db2 product code available. At minimum, generating Db2 installation, migration, or function level activation jobs requires the following Db2 load libraries:
prefix.SDSNCLST
prefix.SDSNSPFM
prefix.SDSNSPFP
prefix.SDSNSAMP
prefix.SDSNIVPD (only if generating z/OSMF artifacts)
Ensure that the PTF for APAR PH52482 is applied in Db2 13.
By running the DSNTIJBC batch job with current and valid input files, you can avoid running the Db2 installation CLIST in interactive mode to submit or accept parameter values on every panel. This approach is especially useful if you are migrating or activating function levels for many Db2 subsystems.
The DSNTIJBC batch job included two steps:
Executes the DSNTIFMT program, which formats member DSNTINST, which is the Db2 installation CLIST, into a new member named DSNTINSB that can be run in batch mode.
Runs the ISPSTART command to run DSNTINSB in batch mode.
Figure 1. A diagram that illustrates how the DSNTIJBC job uses valid input files to run the Db2 installation CLIST as a background process
Procedure
Gather the following required input files:
A current and valid DSNTIDXx defaults input member for your Db2 subsystem.
The DSNTIDXA member for target Db2 release.
Copy the supplied parameter override file shown the following table for your specific activity, and customize it by following the instructions in the file.
Activity
Parameter override file to customize
Migrating a stand-alone Db2 or first data sharing member
DSNTIDOM
Migrating a subsequent data sharing member
DSNTIDON
Activating a Db2 function level
DSNTIDOA
The following table summarizes the required (R), optional (O), and not-applicable (N/A) parameters for each activity type. See the supplied parameter override files for descriptions of each parameter.
This parameter is not-applicable (N/A) if USE_ZOSMF_WORKFLOW=NO is specified.
If you use Db2 Value Unit Edition, you must also customize a parameter override file named DSNTIDVU, which contains notice and acceptance of the license terms.
Copy the DSNTIJBC batch job and customize step STEP02 with the data set name of the customized parameter override file.
For example, if prefix.SDSNSAMP(DSNTIDOM) is the customized parameter override file for migrating a Db2 stand-alone or first member of a data sharing group, you can specify the following values in the IPSTART command in DSNTIJBC.
If you use Db2 Value Unit Edition, you must also provide the data set name of the DSNTIDVU parameter override file in the IPSTART command in the DSNTIJBC job, as shown in the following example, where prefix.SDSNSAMP(DSNTIDVU) is the customized OTC LICENSE file.
Tip: If the customized DSNTIJBC job is in the same library as the <prefix>.SDSNSAMP used by the Db2 installation CLIST, ensure that <prefix>.SDSNSAMP is not allocated or opened for output when you submit job DSNTIJBC.