PH08369: APPLY LATENCY ALERT MESSAGES FOR ZOS 11.4.0

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• New function: three new parameters have been added to the Q
  Apply IBMQREP_APPLYPARMS table (WARNTXLATENCY, WARNTXEVTS, and
  WARNTXRESET). Q Apply will use these columns to make the
  browser thread perform checks on committed and in-flight
  transactions to identify the transactions that are causing Q
  Apply to exceed latency.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1- All Q Capture customers                   *
  *                 2- All Q Capture customers                   *
  *                 3- All Q Capture customers                   *
  *                 4- All Q Capture customers                   *
  *                 5- All Q Capture customers                   *
  *                 6- All Q Capture customers                   *
  *                 7- All Capture customers                     *
  *                 8- SQL Apply users                           *
  *                 9- QApply users                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1- Q Apply ASN7224I message displays    *
  *                      an incorrect commit timestamp because   *
  *                      Q Capture sent Q Apply an incorrect     *
  *                      commit timestamp in a notification      *
  *                      message.                                *
  *                      2- Q Capture made an MQINQ call to      *
  *                      return the number of messages on a      *
  *                      queue and the call failed.              *
  *                      3- Q Capture REINIT of an active        *
  *                      subscription issues ASN7341W and does   *
  *                      not send a schema message to Q Apply.   *
  *                      4- Q Capture should check if the any    *
  *                      source table columns have field         *
  *                      procedures when it processes a          *
  *                      CAPSTART signal. Q Capture checks if    *
  *                      the source tables have any field        *
  *                      procedures at start or reinit time and  *
  *                      keeps this information in memory. If a  *
  *                      subscription for a source table with a  *
  *                      field procedure is activated, it is     *
  *                      handled as a table without field        *
  *                      procedures until Q Capture is recycled  *
  *                      or a REINIT is issued. This causes      *
  *                      incorrect data to be replicated or      *
  *                      published.                              *
  *                      5- Q Capture issues ASN7138W each time  *
  *                      it initializes a delimited              *
  *                      subscription that has a                 *
  *                      IBMQREP_SENDQUEUES message_codepage     *
  *                      that is not 1208.                       *
  *                      6- Q Capture prune positioned DELETE    *
  *                      statements are invalidated.             *
  *                      7- The capture log reader makes READS   *
  *                      calls for IFCID 306 that include a      *
  *                      request to convert returned log         *
  *                      records to the format for the table     *
  *                      space version in which the data was     *
  *                      written, but does not display an error  *
  *                      message if Db2 cannot convert the log   *
  *                      records.                                *
  *                      8- The user cannot identify the UTILID  *
  *                      used in ASNLOAD for a specific SQL      *
  *                      Apply instance.                         *
  *                      9- New function: three new parameters   *
  *                      have been added to the Q Apply          *
  *                      IBMQREP_APPLYPARMS table                *
  *                      (WARNTXLATENCY, WARNTXEVTS, and         *
  *                      WARNTXRESET). Q Apply will use these    *
  *                      columns to make the browser thread      *
  *                      perform checks on committed and         *
  *                      in-flight transactions to identify the  *
  *                      transactions that are causing Q Apply   *
  *                      to exceed latency.                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  1- Q Capture notifies Q Apply that it has published up to a
  commit LSN and commit timestamp, but sends an incorrect commit
  timestamp in the notification message.
  2- Q Capture IBMQREP_CAPMON XMITQDEPTH value should be -1 if an
  MQINQ Q DEPTH call fails.
  3- Q Capture REINIT should issue ASN7341W if the subscription
  STATE is 'L' and the subscription HAS_LOADPHASE is 'E'.
  4- Q Capture should check if the any source table columns have
  field procedures when it processes a CAPSTART signal.
  5- Q Capture should not issue ASN7138W.
  6- Q Capture runs a CONNECT RESET statement at the end of every
  prune cycle.  The CONNECT RESET invalidates the prune DELETE
  statement cursors.
  7- Capture should display a message if Db2 V12 cannot convert a
  log record and capture cannot decode the log record using its
  version information.
  8- It is difficult to associate an UTILID used in ASNLOAD user
  exit, especially when multiple SQL Apply instances are running.
  9- You can now set up apply latency warnings for Q Apply to
  help pinpoint individual transactions that are taking longer
  than desired to be applied to target tables. The WARNTXLATENCY
  parameter sets a threshold for apply latency (the time between
  getting transactions from the receive queue and applying them
  at the target). When the threshold is exceeded, Q Apply issues
  warning messages that help you determine which transactions are
  contributing to latency. On z/OSB., these messages go to the
  console. The WARNTXEVTS parameter sets a limit on the number of
  warnings and WARNTXRESET specifies a reset period. A message
  that identifies each table that is modified by the transaction
  is also issued. Q Apply also issues summary messages after each
  reset period to help with latency tracking.
  

Problem conclusion

Temporary fix

Comments

• 1- Q Capture will send the correct commit timestamp in the
  notification message after it processes a STOP
  CAPTUREUPTO=LOGS_AVAIL_AFTER_DISASTER STOPAFTER DATA_APPLIED
  command.
  2- Q Capture IBMQREP_CAPMON XMITQDEPTH value should be -1 if an
  MQINQ call to return the number of messages on a queue fails.
  3- Q Capture REINIT will issue ASN7341W only if the
  subscription STATE is 'L' and the subscription HAS_LOADPHASE is
  'E'.
  4- Q Capture will check if the any source table columns have
  field procedures when it processes a CAPSTART signal.
  5- Q Capture REINIT will not issue ASN7138W.
  6- Q Capture will not run a CONNECT RESET statement at the end
  of every prune cycle.
  7- Capture will display ASN0748E if Db2 V12 cannot convert a
  log record and capture cannot decode the log record using its
  version information.
  8- Changed ASNLOAD to include the Apply Qualifier as part of
  the UTILID when invoking the DB2 cross loader.
  9- Users can use these three parameters to monitor long running
  transactions and ultimately find the target tables causing the
  issue.
  Note: ASNCLP has been updated from db2_v105fp11 s190414.
  

APAR Information

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

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

  UI63022 UI63023 UI63024 UI63025

Modules/Macros

•    ASNAAPP  ASNACMD  ASNACMP  ASNADMSP ASNAFET
  ASNAISO  ASNAMAN  ASNAPP   ASNAPPLY ASNAPRS  ASNAWPN  ASNBNDDR
  ASNBNDSR ASNBPXB  ASNCAP   ASNCATM  ASNCCDA  ASNCCDD  ASNCCMD
  ASNCCPWK ASNCDA   ASNCDD   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
  ASNMON   ASNMONIT ASNMPROC ASNMUPDT ASNNONO  ASNPLPL  ASNPRUNE
  ASNPTBR  ASNQACMD ASNQAHKT ASNQAPAG ASNQAPP  ASNQAROW ASNQASUB
  ASNQBNDE ASNQBNDL ASNQBNDR ASNQBNDT ASNQBRWZ ASNQCAP  ASNQCCDA
  ASNQCCDD ASNQCCMD ASNQCTLZ ASNQDEFQ ASNQDEP  ASNQEXRP ASNQFALL
  ASNQJ001 ASNQJ002 ASNQLODZ ASNQMFMT ASNQMSTP ASNQNMIH ASNQPROF
  ASNQP2PA ASNQP2PI ASNQSPC  ASNQSPIL ASNQSPS  ASNQSQLZ ASNQXFMT
  ASNQ1021 ASNQ1140 ASNRBASE ASNRURU  ASNSFALL ASNSQLCZ ASNSVSE
  ASNS1021 ASNTDIFF ASNTDSP  ASNTDSQL ASNTRC   ASNUOW   ASNVCD
  ASNVMON  ASNVREOR ASNVSQL  ASNV1021 ASNV1140 ASNZHCN  ASNZHTW
  ASNZOSCN ASN2BASE ASN2DBCN ASN2DB2C ASN2DB2Q ASN2SQLZ ASN2ZOSC
  

Fix information

• Fixed component name

  WS REPLICATION

• Fixed component ID

  5655L8800

Applicable component levels

• RB33 PSY UI63022

     UP19/05/23 P F905

• RB34 PSY UI63023

     UP19/05/23 P F905

• RB35 PSY UI63024

     UP19/05/23 P F905

• RB36 PSY UI63025

     UP19/05/23 P F905

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.