IBM Support

PI72077: ADD RUN TIME PARAMETER SENDER_ADDRESS FOR ASNMON

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • When receiving emails, some email servers need a valid sender
    address, otherwise the email may be blocked/filtered.  This
    address can be set by env variables on luw, but can not be set
    on Z/os, on Z it is set to be hostserver@ASNMON by default.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 1- All Q Apply customers.                    *
    *                 2- User can not receive alerts email sent    *
    *                 by ASNMON.                                   *
    *                 3- All Capture customers.                    *
    *                 4- Agricultural Bank of China                *
    *                 5- SQL Apply users                           *
    *                 6- ASNTDIFF on z/OS                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1- Q Apply message ASN0569E does not    *
    *                      reveal what caused the Q Apply thread   *
    *                      to terminate abnormally.                *
    *                      2- When receiving emails, some email    *
    *                      servers need a valid sender address,    *
    *                      otherwise the email may be              *
    *                      blocked/filtered.  This address can be  *
    *                      set by env variables on luw, but can    *
    *                      not be set on Z/os, on Z it is set to   *
    *                      be hostserver@ASNMON by default.        *
    *                      3- Capture ignores transactions using   *
    *                      a filter based upon the authorization   *
    *                      ID, authorization token, or plan name   *
    *                      it extracts from the begin transaction  *
    *                      log record.  If capture stops after a   *
    *                      transaction for different tables        *
    *                      commits and before it reads all rows    *
    *                      of the ignored transaction, capture     *
    *                      warm start will read and not ignore     *
    *                      the ignored transaction rows having     *
    *                      RBA/LRSN's that are higher than the     *
    *                      commit RBA/LRSN of the unrelated        *
    *                      transaction.  Capture should ignore     *
    *                      the transaction after it extracts       *
    *                      transaction authorization ID,           *
    *                      authorization token, and plan name      *
    *                      from DB2 V11 and DB2 V12 commit log     *
    *                      records.                                *
    *                      4- Customer runs load dummy to many     *
    *                      tables concurrently at source system.   *
    *                      Apply shows very poor performance.      *
    *                      5- Too many ASN8999D messages are       *
    *                      issued when using TOLERATE_LSN_TRUNC=Y  *
    *                      6- Customer got -601 sql error when     *
    *                      restart a failed ASNTDIFF job.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1- Q Apply message ASN0569E should display the system or DB2
    completion code that terminated the Q Apply thread abnormally.
    2- The sender address should be modifiable.
    3- Capture should correctly extract transaction authorization
    ID, authorization token, and plan name from DB2 V11 and DB2 V12
    commit log records so that it is able to ignore transactions
    that do not have a begin transaction log record.
    4- When Apply receives loaddummy schema message, browser stops
    reading RECVQ and invokes load utility to do loaddummy. The
    actual time cost of load utility is 1 min, which leads to bad
    apply performance when customer runs loaddummy to many tables
    concurrently.
    5- One ASN8999D message is issued for each member in the set in
    each subscription cycle when TOLERATE_LSN_TRUNC=Y is in use.
    6- Customer got -601 sql error when restart a failed ASNTDIFF
    job. ASNTDIFF will drop GTT(global temporary table) table when
    stops. But when tdiff job crushed, a dirty GTT table will be
    created. That's why we sees -601 error when recreating GTT
    table.
    

Problem conclusion

Temporary fix

Comments

  • 1- Q Apply message ASN0569E will be changed to display the
    system or DB2 completion code that terminated the Q Apply
    thread abnormally..
    2- The default sender value in z for ASNMON alerts is
    asnmon@server_name.  A new optional run time parameter
    SENDER_ADDRESS is added to ASNMON for users on z to specify
    sender address for alerts.
    
    //ASNMON   EXEC PGM=ASNMON,REGION=0M,
    // PARM='/monitor_server=SSTR monitor_qual=MONQUAL
    //             sender_address=EC13@YAHOO.COM'
    
    3- Capture will correctly extract transaction authorization ID,
    authorization token, and plan name from DB2 V11 and DB2 V12
    commit log records so that it is able to ignore transactions
    that do not have a begin transaction log record.
    4- With this fix, spill Agent invokes load utility when doing
    loaddummy. Browser can continue reading RECVQ when spill Agent
    is doing loaddummy.
    5- Changed Apply not to issue any ASN8999D message
    6- Try to delete existing GTT table if ASNTDIFF got -601 when
    creating the GTT table.
    

APAR Information

  • APAR number

    PI72077

  • Reported component name

    WS REPLICATION

  • Reported component ID

    5655L8800

  • Reported release

    A21

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-09

  • Closed date

    2016-12-13

  • Last modified date

    2017-01-03

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

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

    UI43315 UI43316 UI43317 UI43318

Modules/Macros

  •    ASNACMD  ASNADMSP ASNAPPLY ASNAPRS  ASNCAP
    ASNCCMD  ASNCLPAP ASNCLPCL ASNCLPCM ASNCLPCO ASNCLPMS ASNCLPQA
    ASNCTLZD ASNMCMD  ASNMON   ASNMUPDT ASNQACMD ASNQAPAG ASNQAPP
    ASNQASUB ASNQBRWZ ASNQCAP  ASNQCCMD ASNQCTLZ ASNQDEP  ASNQEXRP
    ASNQLODZ ASNQMFMT ASNQSPIL ASNQXFMT ASNQ1021 ASNRBASE ASNS1021
    ASNTDIFF ASNTDSP  ASNTRC   ASN2BASE
    

Fix information

  • Fixed component name

    WS REPLICATION

  • Fixed component ID

    5655L8800

Applicable component levels

  • RA21 PSY UI43315

       UP16/12/22 P F612

  • RA24 PSY UI43316

       UP16/12/22 P F612

  • RA25 PSY UI43317

       UP16/12/22 P F612

  • RA26 PSY UI43318

       UP16/12/22 P F612

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDP5R","label":"InfoSphere Replication Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A21","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 January 2017