Migration step 24: Set up Db2-supplied routines
Installation jobs are provided for the setup of all Db2-supplied routines and supporting objects that are provided with the Db2 base product.
Before you begin
- All stored procedures and user-defined functions (except native SQL procedures) must run in WLM-managed stored procedure address spaces. You must assign each stored procedure to a WLM application environment, which routes the stored procedure work to the appropriate WLM-managed address space. For more information, see Setting up a WLM application environment for stored procedures during migration.
-
If the RACF® facility class is active and a profile was defined for MVSADMIN.WLM.POLICY, the user that runs the DSNTIJRV job requires READ access. To grant READ access to a user, an administrator must submit the following command:
PERMIT MVSADMIN.WLM.POLICY CLASS(FACILITY) ID(user) ACCESS(READ)If the RACF OPERCMDS class is active and a profile was defined for MVS.MCSOPER.*, the user ID that runs the DSNTIJRV job requires READ access. Alternatively, you can add a discrete profile for the DSNTRVFY console that is used in this job. To add a discrete profile for the DSNTRVFY console, an administrator must complete the following steps:
- Establish a discrete profile for MVS.MCSOPER.DSNTRVFY by issuing the following command:
RDEFINE OPERCMDS MVS.MCSOPER.DSNTRVFY UACC(NONE) - Grant READ access to the user that runs the DSNTIJRV job by issuing the following command:
PERMIT MVS.MCSOPER.DSNTRVFY CLASS(OPERCMDS) ID(user) ACCESS(READ) - Refresh the OPERCMDS class by issuing the following command:
SETROPTS RACLIST(OPERCMDS)REFRESH
- Establish a discrete profile for MVS.MCSOPER.DSNTRVFY by issuing the following command:
-
Resource Recovery Services (RRS) is also required for these jobs.
Important: Job DSNTIJRT defines, binds, and grants access to stored procedures and user-defined functions. The default setting for GRANT EXECUTE is PUBLIC, meaning that anyone who can access Db2 can use these stored procedures. Use the GRANT EXECUTE fields on panels DSNTIPRB through DSNTIPRP to specify different access lists when you run the installation CLISTS. -
Before running job DSNTIRT, review the configuration statements under the CFIGIN DD statement to verify the settings of the WLMENV, GRANTTO, and optional PKGOWNER parameters.
If you copy Db2 library data sets from one system to another, such as for installing a related test or production subsystem, ensure that you copy all of the Db2 library data sets to the same location. For example, if you copy the SDNSLOAD data set from one system to another but omit the DBRMLIB data set, the resulting mismatch can cause job DSNTIJRT to fail with SQLCODE -812.
Job DSNTIJRT issues certain GRANT statements, which causes an abend situation if it is run with the AUTH subsystem parameter set to NO. The NO setting of the AUTH subsystem parameter is not recommended because it disables all authorization checking in Db2 and disables the GRANT statement. For more information, see USE PROTECTION field (AUTH subsystem parameter).About this task
The DSNTIJRT and DSNTIJRV jobs install and validate the installation of routines that are supplied with Db2. These jobs are configured with the options that you specified on installation panel DSNTIPR1 and panels DSNTIPRA through DSNTIPRP.
You might have already installed these routines when on your Db2 11 subsystem. In that case, the purpose of running job DSNTIJRT is to drop and recreate the SYSPROC.DSNUTILU stored procedure so that it can accept utility statements of up to 2 GB in length. It also binds Db2 12 packages for Db2-supplied routines that were migrated from Db2 11. Running the job might result in other changes, such as adding routines that were available in Db2 11 but not installed on this subsystem and maintaining SQL objects that were modified during service of Db2 11.
Procedure
To install the Db2-supplied routines: