This APAR has co-requisite APARs CX910050, CX910052 and CX910060.
Apply CX910061, then CX910050 and CX910060, if needed. If you have installed the Warehouse Database then also apply CX910052.

1. Trace summary GETPAGE counts incorrect.
2. Trace summary SQL totals by Table or Index incorrect when Bind Access Paths loaded.
3. STOP Group Trace for all DEST OPn when OPn may vary across members of the group.
4. When renaming EZ-DB2 software datasets omit authorized load library.
5. New function in Warehouse Manage SQL Workload. Enter X against an SQL to exclude that and all subsequent SQL from the Workload.
6. Workload name of "CACHE" causes REXX failure.
7. S0C4 in Impact Analyzer batch reports.
8. Faster drill to object statistics for large databases.
9. Allow duplicate statement names in DBRM.
10. Trace filter wildcards aligned to DB2 V9 so use * as a prefix delimiter, e.g. ABC* for anything starting ABC, and _ for wildcard, e.g. A_C* for anything starting with A in position 1 and C in position 3.
11. XPRINT prints the original report not the current filtered or sorted report.
12. When drilling on DBNAMEs you may use the wildcard character _ as well as %.
13. EZ-Stats copy statistics may fail with a REXX error allocating datasets.
14. Batch report options will remember target dataset or SYSOUT. Use DRILL to access report options.
15. Imapct Analyzer Report 25 filters do not work.

1. This APAR must NOT be applied while Traces or other EZ-DB2 procedures are running.
2. APAR CX910059, or later, is a mandatory pre-req.
3. This APAR is only necessary if you have applied APAR CX820047, or any subsequent APAR, that introduced capture of all SQL executing
CALL to STORED PROCEDURE by adding IFCID 233 to the trace. There is a bug in DB2 which corrupted the IFCID 233 Program Name and Statement Number which resulted in EZ-DB2 corrupting the XOPSQLFP VSAM files.This APAR will clean the VSAM files.
4. To fix the bug in DB2 apply IBM APAR PK60771.
5. It will not hurt to apply this APAR if there is no corrupt data to be found. If you are unsure if prior maintenance may have triggered this condition then apply this APAR.

1. EZ-DB2 Warehouse Database changes - this APAR should ONLY be applied if the EZ-DB2 warehouse database has been installed.

1. Restructure all XOPSQLCP VSAM files. This APAR is a co-requisite of CX910051 or later. It must be applied once after applying CX910051 or later.

1. Terminate group traces with scope group. Process all group member data.
2. CALL SP procedure statements may cause an abend processing workload data.
3. Impact Analyzer VNext filter processing incorrect where existing access paths are not available. Performance overhead reduced.
4. Impact Analyzer reports sort on CPU savings results in REXX abend.
5. Continuous Cache Traces fail to switch traces.

Notes : APAR CX910047 introduced capture of SQL issuing CALL to Stored Procedure. A bug in DB2 corrupted the program name and statement number in IFCID 233 which resulted in Tracer corrupting the data in XOPSQLFP. APAR CX910060 repairs this corruption. IBM APAR PK60771 corrects the bug in DB2.

1. Impact Analyzer compare current access paths with VNext performs an unnecessary explain when the two systems are on separate LPARs.
2. Prepare error in V7 Index Analysis.
3. Activating multiple subsystems in succession retains first subsytsem name.
4. IVP trace filters incorrect.

1. Change APAR panels to add database update options.
2. Correct errors in Tracer Filter panel defaults and allow wild cards in Correlation ID.
3. Reduce run times in XOP by only explaining SQL that might be affected by an index change and only using DESC when there is an ORDER or GROUP BY on the column DESC.
4. Stop XOP eliminating columns used in existing user indexes.
5. Allow input of Group Name in Subsystem Install which will enable the software for all the members of the group.
6. Support Trace at DB2 Group level. The DB2 Group Name must first be defined with DB2 Group = Y in the Activate Subsystem control panels. The panels will then allocate a member in ISPPROF for each member of the DB2 Group. In Tracer you may then opt to trace a single member of the Group or the entire Group.
7. Refinements to EZ-Index Analyzer Analysis.
8. Impact Analysis incorrect with filter on PLAN where members of the Plan are members of many other Plans.
9. New FILTER command on most reports. You may FILT on Program, DBRM, Package, Plan, Collid, Authid, Table and Index.E.g. FILT PROG ABC% to display only those report lines where program name start ABC. This only applies to drillable fields highlighted in yellow.

1. Fix occasional abend when processing 'SET CURRENT SQLID=?'.
2. Add checks to verify the correct log file is being used.

1. Process load of current cache only will not use secondary log files.
2. Repeating traces may terminate early.
3. New Option in Impact Analyzer VNext processing where existing access paths do not exist using DBRMLIB as filter.
4. Add new Trace Filters for CONNID, WRKSTN, APPNAME and USERID. Use new trace filters permitted in DB2 V9, for earlier DB2 the filter is performed manually. Allow eXclude.
5. Eliminate duplicate explains from preparation for Index Analysis.
6. DRILL on Impact Analyzer filter parameters reinstated.
7. Subsystem Install panels updated to allow entry of SCHENV parameter.
8. EZ-Stats may get Dynamic Allocation error generating JCL.
9. Index Analyzer reports may have errors where there are a large number of predicate sets on one table.

1. Use default table qualifier for PeopleSoft.
2. Reduce thread array size, clear down inactive data.
3. Increase default log file size for process of current cache data only.
4. Left scroll in SQL Statistics Drill may not work.
5. DB2 V9 plan tables generated incorrectly.

1. Add TOTAL-COST processing for DB2 V9.
2. Get around DB2 V9 bug giving spurious -910 errors.
3. Correct error handling comma as decimal point.
4. New Subsystem activation may generate the job for the wrong subsystem.
5. Trend Analysis database generation suppressed when not needed.
6. Possible GETMAIN failures or S0C1 abend processing large volumes of Cache.
7. Reduce region requirements processing Tracer log files by deleting redundant threads.
8. Tracer may not populate the Trend Analysis database on the first trace.
9. In Impact Analyzer alerts for SQL exceeding the average Timeron threshold may be lost.

1. NEW format SQL Statistics drill panel with DRILL to breakdown of Open/FETCH Costs.
2. Allow HLQ prefix changes through EZDB2I.
3. When loading data from Tracer into Warehouse you may now opt to replace the existing Warehouse Workload with the trace data being imported. This deletes the current data prior to the load.
4. Allow "Jobname" to be used more than once in the default jobcard and be correctly translated.
5. Allow restart of report generation on old traces.
6. XOPPATH may round Timerons to zero. Greater precision using Timerons for low cost SQL.
7. Reduce I/O drilling on consolidated SQL.
8. Edit and Explain may calculate incorrect percentage saved depending on Drill Level.
9. Abend in XOPPARS processing very large predicate set.
10. Very long Free Form SQL text may be truncated importing it into EZ-DB2.

This APAR upgrades EZDB2 R8.2 to R9.1

1. Make EZ-DB2 Version 9 compliant and bring EZDB2 R8.2 up to R9.1.
2. EZ-Tracer now reports on all calls to Stored Procedures using IFCID 233.
3. Alerts not generated by default.
4. Fixed abend on invalid input in Add Free-Form SQL Text.
5. Eliminate need for LPAR specific control of Workloads, Traces and Versions.
6. Correct error in EZ-Stats update catalog statistics using statistics from a different subsystem.

1. EZ-DB2 Warehouse Database changes - this APAR should ONLY be applied if the EZ-DB2 warehouse database has been installed in a DB2 V8 system in NEW Function Mode.

1. EZ-DB2 Warehouse Database changes - this APAR should ONLY be applied if the EZ-DB2 warehouse database has been installed in a DB2 V7 subsystem or a V8 system in Compatibility Mode.

1. EZ-DB2 Warehouse Database changes.

1. EZ-DB2 Warehouse Database changes.

1. Drill on Cache Filter Parameters inactive.
2. EZ-STATS CAF attach error.
3. Abend when processing certain invalid SQL.
4. Consolidation when JOIN predicate has 'IN'.
5. Minor bug fixes.

1. Fix consolidation for singleton SELECTs.
2. Fix interval switching when filtering on AUTHID.
3. Add CPU ID to password expiry messages.
4. Spurious Tracer Password expired messages.

1. Add new SET PROFILE command to Tracer SQL Consolidation options panel and to Alerts Controls panel.
2. Correct errors in qualifying SQL from programs with a mix of Static and Dynamic SQL.
3. Add bufferpools to option to create explain Plan Table.
4. Allow for long names in Tracer summary reports Table and Index drills.
5. Ignore Pruned access paths in Index Analyzer.
6. Load SQL from catalog parameters reset if database name changed.
7. Concurrent traces may experience dataset contention against ISPTLIB.
8. Link edit for z/OS.e will be generated for all subsequent APARs.

1. Correct failed link edit for z/OS.e

1. Add Table Filters to Load SQL from Catalog.
2. Consolidate SQL reports now show number of duplicated SQL where Program Name is listed as "Duplicat".
3. Correct errors in Alerts reports drill down.

1. Change EZ-DB2 install panel to allow entry of full DSN for SCEERUN and SCEELKED.
2. Allow SQL up to 256Meg but note SQL > 32K will not EXPLAIN under z/OS.
3. GETPAGES added to Trace and Interval Summary reports.
4. EZ-Tracer now provides a count of the number of times an SQL fails on Resource Limits.
5. New ALERT on SQL that fail on Resource Limits.
6. If the Trend Analysis Database is not installed the Consolidation and Trend Controls panel will indicate such.
7. Prepare error in XOPSTATU after ROLLBACK for missing Objects.
8. Drill errors in EZ-Stats.
9. Erroneous Tracer authorization check in Imapct Analyzer.
10. Index Analyzer WITH UR on catalog Access.
11. Impact Analyzer Alert reports sort on Alert ID and Description. Table Scan alerts suppressed if CARDF < Threshold.
12. Warehouse load SQL from Catalog had DD statement missing if Database Filter active.

1.S0C4 in XOPTRC2.
2. Some Statement Numbers and Cursor Names may be corrupted in long running jobs spanning log files. Typically only batch jobs affected.
3. Spurious "Job Not Submitted" messages may be output by Impact Analyzer creating new Workloads.
4. Impact Analyzer jobs split into two where two subsystems are different releases.
5. Possible database error in Index Analysis in DB2 V8 Full Function Mode.

1. Spurious messages for missing CONTOKEN processing new SQL in DBRMLIB in Impact Analyzer.
2. Impact Analyzer processing two subsystems on different LPARs requiring different Job Class will have corrupt JobCard.
3. Impact Analyzer Batch Reports fails S0C7.
4. Pass QUOTE and COMMA values though Impact Analyzer. Reduce Catalog access for Qualifier.
5. DRILL on SQL processes unnecessary data.
6. CACHE statistics not consolidated correctly.
7. Display PREPARE Statement Number in regular trace reports to be consistent with Cache reports.
8. Index Analyzer may not match Predicate Sets completely against existing User Indexes.

1. Make Hints in bulk may issue spurious No SQL Found message.
2. Prepare error in Index Analyzer when more than 100 SQL reference views.
3. Load Free Form SQL Text in Impact Analyzer sets SQL as Dynamic instead of Static and are ignored for Explains.
4. JCL errors in Export Warehouse Workloads.
5. New Alert for SQL that use UPPER/LOWER.
6. Include SDSNEXIT in JOBLIB for RUNSTATS steps.
7. Parser changes for CAST and arithmetic operators to avoid Explain failures.
8. Parser changes for - in cursor names.
9. Eliminate retrieval locks in Imapct Analayzer.

1. Allow Trace Existing SQL Only with SQL Consolidation OFF on a Workload populated with Free Form SQL Text to track all distinct occurrences of the SQL. You then see all the distinct combinations of parameter values to see which incur exceptional costs.
2. New SORT HASH command in Tracer report 22 to sort all the SQL by their post-normalization key. This groups all distinct occurrences of the same SQL together in descending order of Average CPU. Add the parameter TOTAL_CPU to sort by descending Total CPU.
3. NEW Tracer Restart Option 4 to allow restart of OLD traces to complete or regenerate the Summary, Trace and Workload Reports.
4. On-line HELP in EZDB2I brought up to date.
5. Use SYSOUT=(*,INTRDR) instead of SYSOUT=(A,INTRDR).
6. Terminate trace after DIAGnnnn complete.
7. Possible S0C4 in XOPTRC2.
8. Possible S0C1 in XOPANLZ.
9. Manage memory requirements in online reports processing. Display full SQL text on SQL drill if sufficient memory available.
10. Update to optional explain stored procedure to alter CCSID to 1047.
11. Correct parser errors.

1. NEW: CPU, Elapsed Time and GetPage Threshold filters added to EZ-Tracer enable you to trace only SQL that exceed the thresholds.
2. NEW: Option to load Free Form SQL Text into Tracer Workloads.
3. NEW: Option 9.1 facility to refresh the Job card from default.
4. XOPPATH may abend U4308 in Workloads with more than 50,000 SQL. Also U1006.
5. Index Analysis to terminate RC 16 when there are no valid SQL to process.
6. EZ-Tracer Index Utilization reports generated after manually explaining the SQL.
7. APAR Backout may submit job to wrong LPAR.

1. XOPTRC2 may abend S0C4 processing carried forward threads in the last log file.
2. XOPSTATD may fail if there is no GTT database defined.

1. Cursor names > 16 characters may not be processed properly in DB2 V8 leading to a U4038 abend in XOPPATH and SQL Nos of 52576.

1. CPU improvements to SQL consolidation.
2. Lower region size required for SQL consolidation.
3. XOPTRC2 abend U1006 on certain bad SQL text.
4. REFRESH text captured for MQTs. Note there is no IFCID to enable capture of statistics for the execute of REFRESH.
5. Tracer and Warehouse summary drills show full page reports.
6. New Tracer and Warehouse summary report on Indexes used in the EXPLAIN access paths.
7. FIND and RFIND may be used on Summary Reports.
8. DRILL for a list of Plan Tables now shows the DB2 Version valid for the Plan Table.
9. Correct errors in Thread counts where the thread overlaps log switches and Statement Type where a package contains a mixture of Static and Dynamic SQL.
10. Load ALL SQL from catalog may result in S0C4 in SQL consolidation.

1. Eliminate performance overhead in SQL consolidation.

1.Drill from Table Name in access path detail will display all indexes for Table Name regardless of Creator.
2. EZ-XOP check for SQLCODEs when creating an an Index with DEFINE NO.
3. DDF SQL with statement number zero may result in NO SQL TEXT.
4. XEQ sometimes generated on Job Cards instead of SYSAFF.
5. In EZ-Stats hitting ENTER reverts to page 1 of a multi-page display.
6. Updates of statistics in scrollable displays ignored without paging forward.

1. Fix problem with Tracing SQL from Stored Procedures called via DDF.

1. Processing costs reduced generating Alerts.
2. Change BIND parameters to use ENCODING(EBCDIC) to ensure local CCSID used by EZ-DB2 processes.
3. Index Optimizer Controls not saved on ENTER.
4. Drill on Authid GLBLTBL fails (Wrong Case).
5. Drill to SQL text shown NO SQL TEXT for DDF with statement number zero.

1. EZ-DB2 abends S0C7 processing a Hex string with more than 130 characters.
2. REXX error processing trace descriptions panel.
3. Dataset allocations errors may result where datasets are archived by HSM.

1. Edit and Explain of SQL Prepare Error.
2. Corruption of SQL text length in DB2 V7 for certain length values and CCSIDs.
3. Make sure stats for DSNDB06 get loaded.
4. Fix parameter and JCL error when loading from Catalog in Warehouse.

1. EXPLAINs of INSERTs may fail with authorization failures when using the explain stored procedure.
2. Tracer may not process DECLARE GLOBAL TABLE properly.
3. New OWNER parameter added for BIND of the Explain Stored Procedure.

1. Correct Impact Analyzer processing of DECLARE Global Temporary Table where DECLARE is not ordered before SQL referencing the GTT.

1. Impact Analyzer gets SQL unmatched in DB2 V7 plan members where QUERYNO = -1.
2. APAR panel doesn't process OWNER.
3. Export Workload REXX error.

1. Correct Impact Analyzer processing partially qualified columns in Select Lists in DBRMLIB members.
2. Add new JOB LOG drill on Impact Analyzer Summary report to view the process activity log.
3. Impact Analyzer may abend when provided an empty DBRMLIB.
4. A bug in DB2 may result in EZ-Tracer sharing an OPx destination with another trace and cause Abends.
5. Add support for Long Columns in EZ-Stats displays.

1. Add Qualifier Translation to SQL Drill Make Hint command.
2. Allow for IBM_SERVICE_DATA not defined WITH DEFAULT.
3. Impact Analyzer may fail using Package Version Filters.

1. EZ-Tracer deal with DB2 bug passing IFCID 239 in the trace.
2. EZ-Tracer check correct version of DB2.
3. EZ-Stats corrected for long fields in Tablespace name.
4. Workload Import/Export procedures enhanced.
5. New z/OS.e option in Install procedures.
6. Impact Analyzer may fail with Workloads created under EZDB2 V8.1.

1. Add new parameters to allow translation of COLLID between one version and another in Impact Analyzer.
2. Impact Analyzer updated to use QUERYNO when coded in SQL statements.
3. Impact Analyzer enhanced to allow entry of multiple Plan/DBRM and/or Collection/Package/ Version in filter parameters.
4. Trend Analysis fails in second and subsequent traces using 24x7 repeat traces.

1. Improve messaging in HINT creation.
2. Indicate DSN_STATEMENT_TABLE present in Plan Table Lists.
3. Qualifier translation file allocations may violate SMS storage management rules.
4. Possible S0C7 in SQL Parser.

1. DB2 trace data managed better when there are gaps with missing IFCIDs in the trace.
2. RID failures were missed.
3. Parallelism CPU may not be captured.
4. Possible cursor sort failure in Tracer report number 22 on z/OS.e systems.
5. Alerts on V8 reserved words in predicate list.
6. Batch SPUFI SQL rejected.

1. XOPPATH may Abend processing Global Temporary Tables.
2. Final SQL Consolidation run of XOPTRC2 may wait on log dataset.
3. Allow DECLAREs of GTT to be imported into workloads.
4. Add Filter by TABLE and CICS Transaction ID to EZ-Tracer.
5. Tracer Option to generate access paths DRILL function enabled.

1. Add options to Impact Analyzer to create HINTs for all, or a subset, of the SQL in a Workload using the selected Version of Access Paths within the Workload.
2. Add options in Impact Analyzer to use HINTs for a new EXPLAIN.
3. Impact Analyzer processing packages with SQL identical to SQL in other packages but using a different qualifier may consolidate them into one SQL.
4. Link edits changed to facilitate activation under z/OS-e.
5. New ALERTS added.
6. Update Impact Analyzer to deal with SYNONYMs when processing a DBRMLIB.
7. EZ-Stats database selection panels enhanced to simplify the process. Statistics update jobs may now be generated to run repeatedly.
8. EZ-Cache is now available for analyzing Dynamic SQL in cache. Free to existing users of EZ-Tracer it is a separate option for new users.

1. Add Qualifer Translation to Impact Analyzer to allow generation of Access Paths against any environment.
2. Match Access Paths in Plan Tables correctly where multiple versions of a package or member of plan exist bound to different qualifiers.
3. Add MAKE HINT command (MH) from Access Path displays. Use this command to make a HINT from your favorite Access Path.
4. Suppress Timeron Alerts when comparing against BIND access paths for which Timerons do not exist.
5. Add DRILL to Tracer Filter parameter options.
6. Invalid SQL text parsed correctly. Correct (CAST ? AS FLOAT).
7. Clearer messaging in Impact Analyzer logs.
8. Job cards may be tailored to include SYSAFF if required.

1. 20-40% reduction in CPU processing Trace data.
2. Split EZ-Tracer controls for Full and Cache Traces so each has their own control panel. Cache Filter parameters panel tailored to Cache requirements. New DRILL to lower level panels.
3. New controls in Trace Filter options to run traces collecting no Fetches and to run Sample traces where the trace is not permanently active.
4. Warehouse SQL explains enhanced to Declare Global Temporary Tables first.
5. Alerts Summary report and reports menu enhanced. New reports created for DBRMs, Collections and Packages.
6. Consolidate In-List for UPDATE SQL corrected.
7. Add new Alert 110 for SQL with Stage 2 Row Statistics.
8. The CPU cost of producing Tracer Reports has been cut by 50%.
9. New RESTART controls for Tracer to allow the appropriate JCL to be regenerated depending on which part of the process failed.
10. Trace Filters for PLAN, AUTHID and PROGRAM now allow Wildcard * to specify any character as well as % to define a prefix.
11. EZ-Tracer clears the current trace buffer at the end of each interval to ensure SQL appear in the interval in which they were executed in a quiet DB2 System.
12. A Trace that captures zero SQL will now run to completion to produce a nil return.
13. A new option has been added to CACHE Traces. Include Current Stats at Start = Y/N/O.
14. A new consolidation control for Table qualifiers has been added to always fully qualify Table names before consolidating.
15. Possible program failure in Impact Analyzer processing a DBRMLIB.
16. CACHE Statistics not processed correctly.

1. Increase default max report lines in Tracer report generation.
2. Increase default trace buffer size.
3. Correct possible invalid Trace entries in XOPSUMTP generated under an earlier release.
4. Add IVP to non-Warehouse install.
5. Allow temporary report files HLQ to be just USERID with no additional qualifier.

This APAR brings EZ-DB2 V8.1 up to EZ-DB2 V8.2