PI14020: Q APPLY GENERATES INCORRECT IBMSNAP_LOGMARKER VALUE IN CCD TARGET TABLE WHEN LOGMARKERTZ=LOCAL IS SET FRAPAR

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Q Apply generates incorrect IBMSNAP_LOGMARKER value in CCD
  target table when LOGMARKERTZ=LOCAL is set
  
  1(PI17397)- ASNLOAD does not insert UPDANY
  signal in a update anywhere setup when
  there are multiple tables in the same
  table space.
  .
  2(PI17368)- When users DECIMAL=COMMA is enabled
  in DSNHDECP, the program ASNQEXRP
  encountered an ASN message ASN0552E
  with a sqlcode "-104".
  3- SUSPEND command causes CPU to shoot
  up.
  .
  4(PI14020)- Q Apply started with parameter
  LOGMARKERTZ=LOCAL generates incorrect
  timestamp values for IBMSNAP_LOGMARKER
  columns for CCD or PIT target tables.
  .
  5(PI17374)- Admin thread of Q Capture may cause
  authorization errors in MQ in trying
  to open XMITQ for MQOO_OUTPUT.
  .
  6- ASNTDIFF outputs all the warning
  and information messages to JESMSGLG
  (system console).
  .
  7(PI17379)- Apply fails to stop after all the
  browser threads exit successfully.
  .
  8(PI17394)- After receiving the command "STATUS
  SHOW DETAILS" or NMI requests, Q Apply
  returns an incorrect value of the
  field ACTIVE_QSUBS.
  .
  9- A regression causes freeing
  incorrect number of bytes when code
  page conversion routines are called
  for LOB data
  .
  10-  SQL Capture terminates with
  ABENDS0C4 after displaying ASN0079E.
  .
  11(PI17401)- peer-to-peer Q Capture warm start
  abends with S0C4 if 'IBMQREPVERNODE'
  and 'IBMQREPVERTIME' versioning column
  rows are dropped fromBMQREP_SRC_COLS.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1- SQL replication                           *
  *                 2- ASNQEXRP                                  *
  *                 3- SQL Capture                               *
  *                 4- Q Apply                                   *
  *                 5- Q Capture users                           *
  *                 6- ASNTDIFF                                  *
  *                 7- Q Apply                                   *
  *                 8- Q Apply                                   *
  *                 9- Q Apply users using separate LOB          *
  *                 subscriptions (LOB_SEND_OPTION=S)            *
  *                 10- Q Apply                                  *
  *                 11- All z/OS peer-to-peer Q Capture          *
  *                 customers.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1- ASNLOAD does not insert UPDANY       *
  *                      signal in a update anywhere setup when  *
  *                      there are multiple tables in the same   *
  *                      table space.                            *
  *                      2- When users DECIMAL=COMMA is enabled  *
  *                      in DSNHDECP, the program ASNQEXRP       *
  *                      encountered an ASN message ASN0552E     *
  *                      with a sqlcode "-104"                   *
  *                      3- SUSPEND command causes CPU to shoot  *
  *                      up.                                     *
  *                      4- Q Apply started with parameter       *
  *                      LOGMARKERTZ=LOCAL generates incorrect   *
  *                      timestamp values for IBMSNAP_LOGMARKER  *
  *                      columns for CCD or PIT target tables.   *
  *                      5- Admin thread of Q Capture may cause  *
  *                      authorization errors in MQ in trying    *
  *                      to open XMITQ for MQOO_OUTPUT           *
  *                      6- ASNTDIFF outputs all the warning     *
  *                      and information messages to JESMSGLG    *
  *                      (system console).                       *
  *                      7- Apply fails to stop after all the    *
  *                      browser threads exit successfully.      *
  *                      8- After receiving the command "STATUS  *
  *                      SHOW DETAILS" or NMI requests, Q Apply  *
  *                      returns an incorrect value of the       *
  *                      field ACTIVE_QSUBS.                     *
  *                      9- A regression causes freeing          *
  *                      incorrect number of bytes when code     *
  *                      page conversion routines are called     *
  *                      for LOB data                            *
  *                      10-  SQL Capture terminates with        *
  *                      ABENDS0C4 after displaying ASN0079E.    *
  *                      11- peer-to-peer Q Capture warm start   *
  *                      abends with S0C4 if 'IBMQREPVERNODE'    *
  *                      and 'IBMQREPVERTIME' versioning column  *
  *                      rows are dropped from                   *
  *                      IBMQREP_SRC_COLS.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1- UPDANY signal should be inserted IBMSNAP_SIGNAL table before
  rows are deleted from the target table.
  2- The problem occurs when the program ASNQEXRP issues the
  generated query statements.
  3- Capture was not properly sleeping after the SUSPEND command.
  4- When using LOGMARKERTZ=LOCAL parameter, Q Apply may populate
  incorrect timestamp values in IBMSNAP_LOGMARKER column for CCD
  or PIT target tables. Only the rows from initial load are found
  to have correct timestamp values as source local time. However
  for regular replicated row changes Q Apply incorrectly adds the
  target local timezone to the timestamp value already adjusted
  for source local timezone.
  5- The XMITQ should only be opened for MQOO_INQUIRE.  This is
  for reporting of XMITQ depth in IBMQREP_CAPQMON
  6- The ASN INFO and WARN messages should be sent to SYSPRINT.
  7- There exists a possible memory visibility issue after the
  browser threads exit.
  8- Inappropriate initial values are set by Q Apply on the field
  ACTIVE_QSUBS.
  9- Refer to problem description
  10-  SQL Capture removes source table registration information
  from its memory without removing references to the registration
  information after it displays ASN0079E.  SQL Capture displays
  ASN0079E if a user deletes rows for active registrations from
  the  IBMSNAP_REGISTER table while SQL Capture is executing.
  SQL Capture terminates with ABENDS0C4 when it references the
  source table registration information it has removed.
  11-  Q Capture allocates a Q subscription nonkey column list
  large enough to contain all nonkey column numbers, sets the
  column number of the first 2 nonkey columns in column list to
  65535, and writes the nonkey columns numbers beyond the end of
  the column list.
  

Problem conclusion

• 1- Change ASNLOAD to insert UPDANY signal to IBMSNAP_SIGNAL
  table before the rows are deleted from the target table.
  2- The problem is fixed by inserting a whitespace character
  after a comma character.
  3- Capture will sleep properly after the SUSPEND command.
  4- Q Apply has been fixed to generate IBMSNAP_LOGMARKER column
  values for CCD or PIT targets correctly based on source local
  time when run with LOGMARKERTZ=LOCAL parameter.
  5- The problem is resolved
  6- The problem should no longer occur after the fix.
  7- The problem should no longer occur after the fix.
  8- The problem should no longer occur after the fix.
  9- This issue is fixed.
  10-  Modify SQL Capture to fix this problem.
  11-  Q Capture will issue error message ASN7299E and deactivate
  the Q subscription if the table does not have rows for the
  'IBMQREPVERNODE' and 'IBMQREPVERTIME' versioning columns.
  

Temporary fix

Comments

APAR Information

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

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

  UI17567 UI17568 UI17569 UI17570

Modules/Macros

• ASNAAPP  ASNACMD  ASNACMP  ASNADMIN ASNADMSP ASNAFET  ASNAISO
  ASNAMAN  ASNAPPLY ASNAPRS  ASNAWPN  ASNBNDDR ASNBNDMU ASNBNDSR
  ASNCAP   ASNCCMD  ASNCCPWK ASNCDINS ASNCLP   ASNCLPAP ASNCLPB
  ASNCLPCL ASNCLPCM ASNCLPCO ASNCLPCT ASNCLPEV ASNCLPMS ASNCLPQA
  ASNCLPRM ASNCMPLD ASNCSCZ  ASNCTLZD ASNDADK  ASNDBCON ASNDB2CN
  ASNDB2SQ ASNDEDE  ASNDONE  ASNENUP  ASNENUS  ASNESES  ASNFIFI
  ASNFRFR  ASNITIT  ASNJAJP  ASNKOKR  ASNLOAD  ASNMCMD  ASNMDATA
  ASNMIGFB ASNMIGZD ASNMIG1D ASNMIG2C ASNMIG2S ASNMIG3C ASNMIG3S
  ASNMIG8  ASNMON   ASNMONIT ASNMPROC ASNMUPDT ASNM2V8  ASNNONO
  ASNPLPL  ASNPLXFY ASNPRUNE ASNPTBR  ASNQACMD ASNQAHKT ASNQAPAG
  ASNQAPP  ASNQAROW ASNQASUB ASNQBNDE ASNQBNDL ASNQBNDR ASNQBNDT
  ASNQBRWZ ASNQCAP  ASNQCCMD ASNQCTLZ ASNQDEFQ ASNQDEP  ASNQEXRP
  ASNQFALL ASNQFA10 ASNQFA95 ASNQFA97 ASNQJ001 ASNQJ002 ASNQLODZ
  ASNQMFMT ASNQMSTP ASNQMZV9 ASNQMZ10 ASNQMZ95 ASNQMZ97 ASNQM2V8
  ASNQPROF ASNQP2PA ASNQP2PI ASNQSPC  ASNQSPIL ASNQSPS  ASNQSTPA
  ASNQSTPC ASNQSTRA ASNQSTRC ASNQTOFF ASNQTON  ASNQXFMT ASNQ1001
  ASNRBASE ASNREG   ASNRURU  ASNSMZV9 ASNSMZ10 ASNSQLCF ASNSQLCZ
  ASNSTPA  ASNSTPC  ASNSTPM  ASNSTRA  ASNSTRC  ASNSTRM  ASNSVSE
  ASNS1001 ASNTDIFF ASNTDSP  ASNTDSQL ASNTRC   ASNTRCON ASNTRDMP
  ASNTRFLW ASNTRFMT ASNTROFF ASNUOW   ASNZHCN  ASNZHTW  ASNZOSCN
  ASN2BASE ASN2DBCN ASN2DB2C ASN2DB2Q ASN2SQLF ASN2SQLZ ASN2ZOSC
  CACINIZ
  

Fix information

• Fixed component name

  WS REPLICATION

• Fixed component ID

  5655L8800

Applicable component levels

• RA10 PSY UI17567

     UP14/05/08 P F405

• RA11 PSY UI17568

     UP14/05/09 P F405

• RA12 PSY UI17569

     UP14/05/09 P F405

• RA13 PSY UI17570

     UP14/05/09 P F405

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.