PM22432: QCAPTURE GETS SQLCODE104 WHEN THE DB2 DECIMAL DELIMITER IS A COMMA. HIPER - see comments below. ABEND04E RC00C90101

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Capture can get sqlcode104 (sql0104n) when the Db2 z/OS decimal
  delimiter is a comma.  HIPER  - see text below
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1- Q Capture with Bi-directional             *
  *                 subscriptions                                *
  *                 2- SQL Capture, Q Capture                    *
  *                 3- All Q Capture customers.                  *
  *                 4- SQL Capture                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1- When DECIMAL=COMMA is set in         *
  *                      DSNHDECM, user might get an error       *
  *                      2- TIMESTAMP column data is being       *
  *                      truncated and loses subsecond           *
  *                      precision.                              *
  *                      3-  Q Capture terminates with return    *
  *                      code zero even after a subscription     *
  *                      gets an error.                          *
  *                      4- Capture goes down without an error   *
  *                      message.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1- Blank spaces were missing after commas in a SQL statement
  run for bi-directional subscriptions
  2- Capture incorrectly started using the SCALE column in the
  version tables to decode TIMESTAMP columns in preparation for
  parameterized TIMESTAMP types. Earlier versions of capture
  always populated this column with zero.
  3-  Q Capture overlays its nonzero return codes when it gets
  its log name for message ASN7156I.
  4- When capture comes down due to a compression dictionary
  error and LOGRD_ERROR_ACTION=S, the ASN error message was not
  being properly issued.
  

Problem conclusion

• 1- Blank spaces have been added to the statement to avoid the
  error
  2- TIMESTAMPs will be decoded and replicated properly with 6
  digit subsecond precision.
  3-  Modify Q Capture to fix this problem.
  4- The error message ASN0011 is now properly issued when
  capture comes down due to a compression dictionary error.
  

Temporary fix

Comments

• HIPER explanation
  DB2 holds page set control blocks (PSCB) when dealing with
  compression dictionaries for compressed tables with data
  capture changes for any application using IFI306.  Prior to
  this APAR, PM22432, the Qcapture log reader thread (which
  uses the IFI306 interface) did not issue commits.
  
  
  The lack of a commits by Qcapture means control block
  structures are retained, and are based on PSCB's which have
  hold the dbid/psid.  Since these PSCB's are not released, it
  might pose problems if the underlying objects are dropped
  and another was created (within the same database) and the
  dbid/obid's were reused while Qcapture was running.  This
  problem will surface when dealing with compressed tables
  with data capture changes on (even if these tables are not
  being replicated).  The symptom could be recursive DB2
  abends, ABEND04E with reason code 00C90101.
  
  To minimize the problem, Qcapture code was changed in this
  APAR, PM22432 (PTF UK60820). to add a SQL COMMIT every 30
  seconds to the log reader thread. This  commit will allow
  DB2 to release and free the PSCB's and prevent these
  abends outside of the 30 second commit window.
  >>>> Please note! <<<<
  Even with this APAR change installed, there is a 30 second
  window where compressed table spaces dropped and recreated
  (with data Capture changes on) within 30 seconds in the same
  database might see the abend.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK60819 UK60820 UK60821 UK60822

Modules/Macros

•    ASNACMD  ASNADMSP ASNAPPLY ASNCAP   ASNCCMD
  ASNLOAD  ASNMCMD  ASNMIG8  ASNMON   ASNPLXFY ASNQACMD ASNQAPP
  ASNQCAP  ASNQCCMD ASNQDEP  ASNQMFMT ASNQXFMT ASNRBASE ASNTDIFF
  ASNTRC   ASN2BASE
  

Fix information

• Fixed component name

  WS REPLICATION

• Fixed component ID

  5655L8800

Applicable component levels

• R910 PSY UK60819

     UP10/10/05 P F010

• R911 PSY UK60820

     UP10/10/06 P F010

• R912 PSY UK60821

     UP10/10/05 P F010

• R913 PSY UK60822

     UP10/10/05 P F010

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.