A fix is available
APAR status
Closed as new function.
Error description
DB2 12 for z/OS uses a continuous delivery model to provide enhancements and new functions. These are associated with a DB2 function that becomes available - but not enabled - when you apply the fixing PTF(s). To enable the change set for a function level, use the DB2 -ACTIVATE FUNCTION LEVEL command. To facilitate activating a function level, this APAR adds a new batch job, DSNTIJAF, and a new installation CLIST mode, ACTIVATE
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All users of the DB2 12 for z/OS installation and migration * * process * **************************************************************** * PROBLEM DESCRIPTION: * * This APAR modifies the DB2 installation CLIST to faciliate * * activating a user-specified DB2 function level. * **************************************************************** * RECOMMENDATION: * * Apply the fixing PTF for this APAR * **************************************************************** DB2 12 delivers new capabilities as they become available, which means you can benefit from new capabilities without waiting for an entire new DB2 for z/OS release. After the code to support a particular enhancement has shipped in the service stream, you activate a function level to make the enhancements available in your DB2 environment. Function levels are specified by 9-byte strings that correspond to the DB2 version, release, and maintenance value. The format is VvvRrMmmm, where vv is the version, rr release, and mmm is the modification level. The function level is modified by means of the -ACTIVATE FUNCTION LEVEL command. Currently, the DB2 12 installation CLIST does not provide a mechanism for changing the function level.
Problem conclusion
In response, this APAR modifies the DB2 12 installation CLIST as follows: (1) It adds a batch job, DSNTIJAF, for activating a DB2 function level (2) It adds a DB2 installation CLIST mode of ACTIVATE for customizing DSNTIJAF and related jobs to change the function level. (3) It adds DB2 installation panel DSNTIP00 for specifying the desired function level, the default application compatibility level (DSN6SPRM.APPLCOMPAT), and the default SQL level (DSNHDECP.SQLLEVEL) for the DB2 precompiler and co-processor. ************* New installation job: DSNTIJAF ************* This APAR adds a new installation and migration job called DSNTIJAF that can be used to set the DB2 function level using batch processing. It consists of a single job step that executes IKJEFT01 (TSO batch command processor), starts the DSN command processor, runs the -ACTIVATE FUNCTION LEVEL command for a specified function level, and terminates. The expected return code is 0. When installing DB2, run the DSNTIJAF job immediately after running the DSNTIJTC (CATMAINT) job. For DB2 data sharing, run DSNTIJAF only for the originating member of the group. When migrating to DB2 12, do not run DSNTIJAF until DB2 is fully migrated and stabilized at function level V12R1M100. In MIGRATE mode, the installation CLIST does not produce a customized DSNTIJAF. To change the function level of a stabilized DB2, proceed as follows: (1) Optional: If you are raising the function level, run the DSNTIJAF job with the desired function level and the TEST option in the -ACTIVATE FUNCTION LEVEL command. Do this to verify that the specified function level is eligible for activation on the subsystem or data sharing group. (2) Optional: If you are raising the function level and the results of the preceding step indicate that the new function level requires a higher DB2 catalog level, run DSNTIJTC (CATMAINT) with the desired function level in the CATMAINT control statement to process related catalog level changes. (3) Run DSNTIJAF with the desired function level in the -ACTIVATE FUNCTION LEVEL command. (4) Optional: Consider whether to run job DSNTIJUZ to update your DB2 subsystem parameter (DSNZPxxx) module and DB2 application programming (DSNHDECP) module: -- When activating a lower function level, verify that the default application compatibility (DSN6SPRM.APPLCOMPAT) parameter and the default SQL level for the precompiler (DSNHDECP.SQLLEVEL) parameter in DSNTIJUZ both specify a levels that are lower than or equal to the new DB2 function level. After running DSNTIJUZ, use the -SET SYSPARM command or restart DB2 to make the APPLCOMPAT change effective. -- When activating a higher function level, consider maintaining your current APPLCOMPAT and SQLLEVEL parameter settings until you have have verified that all DB2 applications on the system can be bound and executed at the new function level. At that time, you can update DSNTIJUZ and change these settings to the DB2 function level you have activated. ************* New installation CLIST mode: ACTIVATE ************* To facilitate setting the function level, the installation CLIST adds a new INSTALL TYPE option on the main panel, DSNTIPA1. The new option, ACTIVATE, can be used to generate the jobs needed to activate a specified function mode level. In the future, activating a higher function level can possibly require activating a new catalog mode level. Note that activating a lower function level may require updating the DB2 configuration modules, DSNZPxxx and DSNHDECP, to reset the DSN6SPRM.APPLCOMPAT and the DSNHDECP.SQLLEVEL parameters to levels that are less than or equal to the new DB2 function level. The job set generated by ACTIVATE mode is currently DSNTIJTC (CATMAINT), DSNTIJAF (activates a function level), and DSNTIJUZ (builds the DB2 subsystem parameter (DSNZPxxx) module and the DB2 application programming (DSNHDECP) module). Before using ACTIVATE mode to move to a higher function level, ensure that DB2 is fully stabilized in DB2 12 at the current function level. In a data sharing environment, the process to activate a function level is done once for the data sharing group. ************* New installation panel: DSNTIP00 ************* If you specify ACTIVATE mode on DSNTIPA1, the CLIST will prompt you on a subsequent panel, DSNTIP00, that contains the following fields: 1. DB2 FUNCTION LEVEL -> Contains the DB2 function level setting. -> In MIGRATE and UPDATE modes, the CLIST ignores this field. It cannot be changed. -> In INSTALL and ACTIVATE modes, the CLIST applies the value of this field to the -ACTIVATE FUNCTION LEVEL command in the DSNTIJAF job and to the CATMAINT control statement in the DSNTIJTC job. Exception: The CLIST applies function level V12R1M100 only to DSNTIJAF and sets the CATMAINT level in DSNTIJTC to V12R1M500 because that is the lowest valid catalog level in DB2 12. 2. APPL COMPAT LEVEL -> Contains the desired default application compatibility (DSN6SPRM.APPLCOMPAT) parameter setting. This field was formerly located on panel DSNTIP41. Its setting must be less than or equal to the setting in the DB2 FUNCTION LEVEL field. -> In ACTIVATE mode, consider leaving the value unchanged when activating a higher function level. -> For information about this field in other modes, see the DB2 Installation Guide. 3. PRECOMPILER SQL LEVEL -> Contains the desired default SQL level for the precompiler (DSNHDECP.SQLLEVEL) parameter setting. This field was formerly located on panel DSNTIP41. Its setting must be less than or equal to the setting in the DB2 FUNCTION LEVEL field. -> In ACTIVATE mode, consider leaving the value unchanged when activating a higher function level. -> For information about this field in other modes, see the DB2 Installation Guide. ************* Activating a function level ************* In ACTIVATE mode, the CLIST will customize the following job set for activating the specified level: (1) DSNTIJTC (Tailor the DB2 catalog and directory - CATMAINT) -> The function level specified on panel DSNTIP00 will be edited into the CATMAINT control statement. Exception: For function level V12R1M100, the CATMAINT level in DSNTIJTC is set V12R1M500 because that is the lowest valid catalog level in DB2 12. (2) DSNTIJAF (Activate a specified function level) -> The function level specified on panel DSNTIP00 will be edited into the -ACTIVATE FUNCTION LEVEL command (3) DSNTIJUZ (Build the DSNZPxx and DSNHDECP modules) -> The DSN6SPRM.APPLCOMPAT level and the DSNHDECP.SQLLEVEL level specified on panel DSNTIP00 will be edited into the DSNZPxxx and DSNHDECP assembly steps. Recommendation: If you are raising the function level, run the DSNTIJAF job with the desired function level and the TEST option in the -ACTIVATE FUNCTION LEVEL command. Do this to verify that the specified function level is eligible for activation on the subsystem or data sharing group. If the results indicate that the new function level requires a higher DB2 catalog level, run DSNTIJTC (CATMAINT) with the desired function level in the CATMAINT control statement to process related catalog level changes. In DB2 data sharing, these operations have group scope. Therefore, run DSNTIJTC and DSNTIJAF on one member only. Run DSNTIJAF to activate the new function level. In DB2 data sharing, function level activation has group scope. Therefore, run DSNTIJAF on one member only. After activating the new function level, consider whether to run job DSNTIJUZ to update your DB2 subsystem parameter (DSNZPxxx) module and DB2 application programming (DSNHDECP) module: -> When activating a lower function level, verify that the default application compatibility (DSN6SPRM.APPLCOMPAT) parameter and the default SQL level for the precompiler (DSNHDECP.SQLLEVEL) parameter in DSNTIJUZ both specify levels that are lower than or equal to the new DB2 function level. After running DSNTIJUZ, use the -SET SYSPARM command or restart DB2 to make the APPLCOMPAT change effective. -> When activating a higher function level, consider maintaining your current APPLCOMPAT and SQLLEVEL parameter settings until you have have verified that all DB2 applications on the system can be bound and executed at the new function level. At that time, you can update DSNTIJUZ and change these settings to the DB2 function level you have activated. -> In DB2 data sharing, all members can share a single DSNHDECP module or have its own. Each member always has its own DSNZPxxx module. In ACTIVATE mode, the CLIST edits the DSNTIJUZ job for one member only. Therefore: --- If you changed the setting for DSN6SPRM.APPLCOMPAT on panel DSNTIP00 then you will need to make the same change manually to the DSNTIJUZ jobs for all other members. You can use the CLIST UPDATE mode for this purpose. --- If you changed the setting for DSNHDECP.SQLLEVEL on panel DSNTIP00 and you maintain a separate DSNHDECP module for each member then you will need to make the same change manually to the DSNTIJUZ jobs for all other members. You can use the CLIST UPDATE mode for this purpose.
Temporary fix
Comments
APAR Information
APAR number
PI70406
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-10-07
Closed date
2016-12-05
Last modified date
2017-05-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI43100
Modules/Macros
DSNTILA1 DSNTIP00 DSNTIPT DSNTINS3 DSNTINS2 DSNTINS1 DSNT46 DSNTINMF DSNTIJAF DSNTINST DSNTIPA1 DSNTINM3 DSNTINM1
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RC10 PSY UI43100
UP16/12/21 P F612
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
17 May 2017