A fix is available
APAR status
Closed as new function.
Error description
V10 new function (part 2). IDAAV2R1/K
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of DB2 10 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: IBM DB2 Analytics Accelerator (IDAA) * * support on DB2 10 for z/OS is * * being added by APARs PM50434, * * PM50435, PM50436, PM50437, and * * PM51918. * **************************************************************** * RECOMMENDATION: * **************************************************************** IDAA support on DB2 10 for z/OS is being added by APARs PM50434, PM50435, PM50436, PM50437, and PM51918. These APARs add the new subsystem parameters ACCEL and QUERY_ACCELERATION to enable the new support to the accelerator for improved query performance. DSNTEP2 and DSNTEP4 are updated to recognize messages from the accelerator. All users need to perform steps (1) and (2), under "Subsystem parameters and sample jobs" below, even if you do not plan to use IDAA. Step (3) is highly recommended. Steps (4) and (5) are required if you plan to use IDAA. All users running V10 NFM also need to perform step (a) or (b) under "DSNTEP2 and DSNTEP4" below. Subsystem parameters and sample jobs ------------------------------------ This PTF also adds two new DB2 subsystem parameters in DSN6SPRM: (A) ACCEL specifies whether query accelerator processing is to be enabled. Valid settings are: * NO : Query accelerator processing is disabled. If this option is selected, query accelerator processing cannot be started. ==> This is the default setting. * COMMAND: Query accelerator processing is enabled and can be started by command. * AUTO : Query accelerator processing is enabled and will be automatically started when the DB2 subsystem is started. (B) QUERY_ACCELERATION specifies the default value for the CURRENT QUERY ACCELERATION special register. The value entered here is used when the special register has not been set by means of the SET CURRENT QUERY ACCELERATION statement. Valid settings are: * ENABLE: Indicates that any given query will be accelerated only if DB2 determines that it is advantageous to do so (i.e., costing is performed). If there is an accelerator failure while running the query, or the accelerator returns an error, DB2 will return a negative SQL code to the application. * ENABLE_WITH_FAILBACK: This option is the same as ENABLE but with slight modification to the DB2 behavior for the cases when there is an accelerator failure or when the accelerator returns an error. In particular, this setting allows DB2 to re-execute (failback) the query in DB2 without the accelerator if the attempt to process the query in the accelerator fails. For special considerations when using this setting, refer to the discussion of the ENABLE WITH FAILBACK option of the CURRENT QUERY ACCELERATION special register in the DB2 SQL Reference. * NONE : Indicates that no query acceleration is to take place. ===> This is the default setting This PTF also introduces the following jobs to support query accelerators: * DSNTIJAS (creates the accelerator database) * DSNTEJAS (creates the virtual accelerator database) The job prologs contain specific guidance on how to configure the JCL to create databases for either type of query accelerator. If you have already installed or migrated to this version of DB2 you need to take the following actions after applying this PTF: (1) Update customized copies of DB2 installation CLIST members (2) Update your customized copy of job DSNTIJUZ (3) Update private copies of the DSNTIDxx CLIST input member (4) Customize and run job DSNTIJAS to create the query accelerator database (5) Customize and run job DSNTEJAS to create the virtual query accelerator database Detailed guidance for these actions follows: ---------------------------------------------------------------- (1) Update customized copies of DB2 installation CLIST members ---------------------------------------------------------------- ==> This action is required This PTF modifies CLIST member DSNTINST in the SDSNCLST target library only. You need to redo any record format changes and reapply any tailoring you have done to your copies of this CLIST. You may also want to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs processed by job DSNTIJVC reside. ---------------------------------------------------------------- (2) Update your customized copy of job DSNTIJUZ ---------------------------------------------------------------- ==> This action is required This PTF modifies DB2 installation job DSNTIJUZ in the SDSNSAMP target library. After applying this PTF, you need to update your customized copy of this job as follows: * Add the keyword parameter ACCEL=<x>, where <x> is AUTO, NO, or COMMAND to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. * Add the keyword parameter QUERY_ACCELERATION=<y>, where <y> is ENABLE, ENABLE_WITH_FAILBACK, or NONE to the invocation of the DSN6SPRM macro. Make sure to add a continuation character in column 72 if needed. * Run the first two steps of the DSNTIJUZ job you modified. * After the job completes, you must stop and restart DB2 for a change to ACCEL to take effect. You must either use the -SET SYSPARM command or stop and restart DB2 for a change to QUERY_ACCELERATION to take effect. ---------------------------------------------------------------- (3) Update private copies of the DSNTIDxx CLIST input member ---------------------------------------------------------------- ==> This action is recommended This PTF adds entries for ACCEL and QUERY_ACCELERATION to the CLIST default input member, DSNTIDXA, in the SDSNSAMP target library. You need to add these entries to all private copies of your CLIST output DSNTIDxx member. In each such copy, add the following lines: ACCEL CHAR M NONE NONE <x> QUERY_ACCELERATION CHAR M NONE NONE <y> Change <x> to the value you specified for ACCEL in step (2), above. Change <y> to the value you specified for QUERY_ACCELERATION in step (2), above. If you omit adding these parameters, the install CLIST will use the default settings the next time you run it to customize job DSNTIJUZ. ---------------------------------------------------------------- (4) Customize and run job DSNTIJAS to create the query accelerator database ---------------------------------------------------------------- ==> This action is required only for customers who want to enable query accelerator processing on DB2 V10 This PTF adds job DSNTIJAS in the SDSNSAMP target library. See the DSNTIJAS prolog for directions on how to customize it for your site. Refer to your query accelerator product documentation for information on how to initialize the query accelerator database. Run the job when you are ready to create and initialize the query accelerator database. ---------------------------------------------------------------- (5) Customize and run job DSNTEJAS to create the virtual query accelerator database ---------------------------------------------------------------- ==> This action is required only for customers who want to enable query accelerator processing on DB2 V10 This PTF adds job DSNTEJAS in the SDSNSAMP target library. See the DSNTEJAS prolog for directions on how to customize it for your site. Run the job when you are ready to create and initialize the virtual query accelerator database. DSNTEP2 and DSNTEP4 ------------------- This PTF updates the source code for DSNTEP2 and DSNTEP4 plus the shipped object decks (DSNTEP2L and DSNTEP4L) and shipped DBRMs (DSN@EP2L and DSN@EP4L). These changes do not become effective until you rebuild the load modules and rebind the plans. * On DB2 V10 systems running in conversion mode (CM) or enabling-new-function mode (ENFM), no further action is required for DSNTEP2/DSNTEP4 after applying this PTF. The updates will be used when you run the V10 IVP jobs after DB2 V10 enters new-function mode. * On DB2 V10 systems in new-function mode, proceed as follows: (a) If you use DSNTEP2 or DSNTEP4 (or both) as supplied by DB2, run IVP job DSNTEJ1L to relink the load modules from the shipped object modules and bind the plans from the shipped DBRMs. (b) If you use a modified version of DSNTEP2 or DSNTEP4 (or both) redo your modifications and then run IVP job DSNTEJ1P to recompile and link-edit the load modules and bind the plans for DSNTEP2 and DSNTEP4.
Problem conclusion
Temporary fix
Comments
IDAA support is implemented with PM50434, PM50435, PM50436, PM50437, and PM51918. For more information on how to use IDAA, please refer to the IDAA User's Guide. Additional Keywords: IDAAV2R1/K ž**** AE12/05/10 FIX IN ERROR. SEE APAR PM64396 FOR DESCRIPTION ž**** PE12/06/19 FIX IN ERROR. SEE APAR PM64396 FOR DESCRIPTION
APAR Information
APAR number
PM50435
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
A10
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-10-19
Closed date
2012-02-10
Last modified date
2012-08-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK76104
Modules/Macros
DSN@EP2L DSN@EP4L DSN@IAP DSN@XAZP DSNB1TAD DSNFMDIR DSNFPMSG DSNFVDIR DSNFXDIR DSNHAPLY DSNHPTAB DSNHSM2V DSNHSM7 DSNHSYMH DSNLMTOK DSNTEJAS DSNTEP2 DSNTEP2L DSNTEP4 DSNTEP4L DSNTIAP DSNTIA1 DSNTIDXA DSNTIDXB DSNTIJAS DSNTIJUZ DSNTINST DSNTLRAC DSNTRSTE DSNTSTOP DSNTSTRT DSNTXACT DSNTXAZP DSNTXSTB DSNUGUCA DSNVDT DSNVDTA DSNVDTM DSNWAACT DSNWAAPI DSNWACDF DSNWAFRR DSNWARDS DSNWVAPR DSNWVINT DSNWVSMT DSNWVZIT DSNWVZPS DSNWVZSA DSNWZDG2 DSNWZIFA DSNXTAD DSNX8API DSNX8CDA DSNX8CMD DSNX8CSA DSNX8CTG DSNX8CXA DSNX8EKG DSNX8EPL DSNX8ESW DSNX8INI DSNX8IN2 DSNX8LML DSNX8NFY DSNX8SMF DSNX8STA DSNX8STO DSNX8TER DSNYRMIT DSN9SCNA HDBAA10J
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RA10 PSY UK76104
UP12/02/28 P F202
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":"10.1","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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
13 August 2012