Start of change

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.

Restriction: If you are preparing to install a new Db2 subsystem, you must run the Db2 installation CLIST in interactive mode instead. See Generating tailored installation, migration, or function level activation jobs by running the Db2 installation CLIST in interactive mode.

About this task

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
Running the Db2 installation CLIST as a background process

Procedure

  1. 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.
  2. 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.
    Required Parameters Migrating standalone or first data sharing member Migrating subsequent data sharing members Activating function levels Related information
    BATCH_MODE R R R  
    USE_ZOSMF_WORKFLOW R R R USE Z/OSMF WORKFLOW field
    INSTALL_TYPE R R R INSTALL TYPE field
    MIGRATE_INPUT_DATA_SET R R N/A DATA SET(MEMBER) NAME field
    DATA_SHARING R R N/A DATA SHARING field (DSHARE subsystem parameter)
    MIGRATE_FIRST_GROUP_MEMBER R R N/A DATA SHARING field (DSHARE subsystem parameter)
    DB2_SMPE_LIBRARY_NAME_PREFIX R R R LIBRARY NAME PREFIX field
    DB2_SMPE_LIBRARY_NAME_SUFFIX R R R LIBRARY NAME SUFFIX field
    INSTALL_DATA_SET_PREFIX R R R DATA SET NAME PREFIX field
    INSTALL_DATA_SET_SUFFIX R N/A N/A DATA SET NAME SUFFIX field
    DEFAULT_PARAMETER_INPUT_MEMBER R R R INPUT MEMBER NAME field
    PARAMETER_OUTPUT_MEMBER R R R OUTPUT MEMBER NAME field
    TARGET_FUNCTION_LEVEL R 2.a N/A R TARGET FUNCTION LEVEL field
    CONSOLE_NAME R 2.a R 2.a N/A  
    INSTALL_IC_PREFIX O N/A N/A INSTALL IC PREFIX field
    INSTALL_DS_PREFIX O N/A N/A INSTALL DS PREFIX field
    TEMP_CLIST_LIBRARY O O N/A TEMP CLIST LIBRARY field
    SAMPLE_LIBRARY O O O SAMPLE LIBRARY field
    CLIST_LIBRARY O N/A N/A TEMP CLIST LIBRARY field
    APPLICATION_DBRM O N/A N/A APPLICATION DBRM field
    APPLICATION_LOAD O N/A N/A APPLICATION LOAD field
    DECLARATION_LIBRARY O N/A N/A DECLARATION LIBRARY field
    APPL_COMPAT_LEVEL O N/A O APPL COMPAT LEVEL field (APPLCOMPAT subsystem parameter)
    PRECOMPILER_SQL_LEVEL O N/A O PRECOMPILER SQL LEVEL field (SQLLEVEL DECP value)
    JDBC_SQLJ_ENV_VAR_DIR O N/A N/A JDBC/SQLJ ENV VAR DIR field
    DB2_BASE_JAVA_DIR O N/A N/A DB2 BASE JAVA DIR field
    JAVA_ENV_DATA_SET O N/A N/A JAVA ENV DATA SET field
    JAVA_ENV_VAR_FILE O N/A N/A JAVA ENV VAR FILE field
    JVM_PROPERTIES_FILE O N/A N/A JVM PROPERTIES FILE field
    WORKFLOW_DEFINITION_LIBRARY O 2.a O 2.a O 2.a Panel DSNTIPM1
    JCL_TEMPLATE_LIBRARY O 2.a O 2.a O 2.a Panel DSNTIPM1
    PATH_FOR_ZOSMF_ARTIFACTS O 2.a O 2.a O2.a Panel DSNTIPM1
    CURRRENT_FUNCTION_LEVEL N/A N/A O CURRENT FUNCTION LEVEL field
    Notes:
    1. 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.
  3. 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.
      ISPSTART CMD(%DSNTINSB + 
        OVERPARM(prefix.SDSNSAMP(DSNTIDOM)) + 
        ) BREDIMAX(1)
    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.
      ISPSTART CMD(%DSNTINSB + 
        OVERPARM(<prefix>.SDSNSAMP(DSNTIDOM)) + 
        OTCLPARM(<prefix>.SDSNSAMP(DSNTIDVU)) + 
        ) BREDIMAX(1)
  4. Submit the customized DSNTIJBC batch job.
    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.
    When the job completes, it generates tailored JCL jobs that are described in Installation and migration jobs that the CLIST tailors.

What to do next

End of change