Knowledgebase
Q&A
Latest Updates
Nov
11
New EZ-DB2 Maintenance - CX910307
Posted by Clive Petley on 11/11/16 @ 5:33 PM

New EZ-DB2 Maintenance - CX910307 has been issued.

EZ-DB2 users should download the latest maintenance and apply as soon as convenient.

  • Increase Field Length for WLM Environment name for Stored Procedures.
  • Ensure all storage is correctly initialized to prevent problems with IGVINITGETMAIN.
  • New option to allow VSAM SMB (System Managed Buffers) in place of BLSR (Batch LSR).

Read more »



Nov
9
New EZ-DB2 Maintenance - CX910306
Posted by Clive Petley on 09/11/16 @ 5:51 PM

New EZ-DB2 Maintenance - CX910306 has been issued.

EZ-DB2 users should download the latest maintenance and apply as soon as convenient.

  • Enable plan filters for Tracer Workloads in Impact Analysis, speed up report production.

Read more »



Oct
26
New EZ-DB2 Maintenance - CX910305
Posted by Clive Petley on 26/10/16 @ 4:51 PM

New EZ-DB2 Maintenance - CX910305 has been issued.

EZ-DB2 users should download the latest maintenance and apply as soon as convenient.

  • Fix XOPSQLXP file status 22 error when running EZ-Tracer with reporting option: APPLID = Y.
  • Correct the datatype when adding CAST to un-typed parameter markers.
  • Fix various minor REXX bugs.
  • Speed up report production for Impact Analyzer on Tracer Workloads.

Read more »



Sep
29
New EZ-DB2 Maintenance - CX910304
Posted by Clive Petley on 29/09/16 @ 1:19 PM

New EZ-DB2 Maintenance - CX910304 has been issued.

EZ-DB2 users should download the latest maintenance and apply as soon as convenient.

  • Cache traces fail when accelerator stats are being generated.

This APAR also includes the following changes from APARs CX910302 and CX910303:

  • Identify duplicate SQL when loading work-load in Impact Analyzer.
  • Fix -171 explain errors when TRIM function contains parameter markers.

Read more »



Sep
13
New EZ-DB2 Maintenance - CX910301
Posted by Clive Petley on 13/09/16 @ 2:29 PM

New EZ-DB2 Maintenance - CX910301 has been issued.

EZ-DB2 users should download the latest maintenance and apply as soon as convenient.

  • Prevent trace jobs locking the PROFILE dataset, when running the first trace for a new workload.
  • Correct DB2 level flags, to prevent problems in Batch Impact Analyzer runs.

Read more »