IBM Support

PM56294: REPLICATION SERVER PROGRAMS STARTED WITH TERM=Y STOP WITHOUT A DISPLAYING A MESSAGE IF THE DB2 SUBSYSTEM IS NOT ACTIVE.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Replication Server programs started with the parameter TERM=Y
    stop without displaying any message if the Db2 subsystem is not
    active.
    Replication Server programs should display some sort of message
    before stopping in the case of the Db2 subsystem being stopped.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 1- Customers getting exceptions and having   *
    *                 doubly byte column names with '?' character  *
    *                 2- Q Apply                                   *
    *                 3- Q and SQL Replication customers.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1- Q Apply dumps in                     *
    *                      generateSQL4Exceptions - while trying   *
    *                      to generate SQL text                    *
    *                      2- Q Apply with a mixed EBCDIC          *
    *                      application codepage may receive SQL    *
    *                      errors when applying to target tables   *
    *                      with column names containing            *
    *                      multi-byte characters.                  *
    *                      3-  z/OS Replication programs started   *
    *                      with TERM=Y stop without displaying an  *
    *                      error message if the DB2 subsystem is   *
    *                      not active.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1- Q Apply does not handle double byte column names that have
    '?' character even if it is within shift-out and shift-in
    bytes.
    2- Q Apply may receive SQLCODE -107 when trying to apply to a
    target table and Q Apply is running in a mixed EBCDIC
    application codepage. When constructing SQL statements to be
    run against the target database it escapes certain special
    characters such as double quote and single quote. Multi-byte
    characters may contain the hex value of a double quote or
    single quote causing Apply to escape this character. However,
    this invalidates the column name leading to the SQL error when
    the statement is run.
    3-  Replication programs started with TERM=Y should display an
    error message before they terminate because the DB2 subsystem
    is not active.
    

Problem conclusion

  • 1- Q Apply exception reporting code has been fixed to tolerate
    special characters that are marked within 0x0E(shift_out) and
    0x0F(shift-in) bytes
    2- If multi-byte characters are used in column or table names
    they must be shifted-out and shifted-in in order to determine
    whether or not multi-byte characters are processed. Q Apply
    does not try to escape bytes matching double or single quotes
    when processing byte patterns shifted-out and shifted-in.
    3- Replication programs will display "ASN0678E The program is
    terminating because the DB2 subsystem "subsystem name" is not
    active." if they are started with TERM=Y and the DB2 subsystem
    is not active.  Replication programs will display "ASN0679E The
    program is terminating because the DB2 subsystem "subsystem
    name" had been started in restricted access mode." if they are
    started with TERM=Y and the DB2 subsystem was started in
    restricted access mode.
    

Temporary fix

Comments

  • *********
    *HIPER *
    *********
    Qapply crashes with ABENDS0C4 trying to create SQL text
    which involves double byte character set values.  A
    question mark '?' was contained within a shift-out,
    shift-in chararacter stream but Qapply would try to
    substitute the ? with a value from the SQLDA.
    The remaining parsing of the SQLDA would be incorrect and
    resulted in the ABENDS0C4.  Qapply was changed to
    handle the appearance of ? in the SO/SI string.
    

APAR Information

  • APAR number

    PM56294

  • Reported component name

    WS REPLICATION

  • Reported component ID

    5655L8800

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-01-18

  • Closed date

    2012-02-06

  • Last modified date

    2012-03-08

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

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

    UK75961 UK75962 UK75963 UK75964

Modules/Macros

  •    ASNAAPP  ASNACMD  ASNADMSP ASNAPPLY ASNCAP
    ASNCCMD  ASNDBCON ASNLOAD  ASNMCMD  ASNMIG8  ASNMON   ASNPLXFY
    ASNQACMD ASNQAPP  ASNQAROW ASNQCAP  ASNQCCMD ASNQDEP  ASNQLODZ
    ASNQMFMT ASNQXFMT ASNRBASE ASNTDIFF ASNTRC   ASNZOSCN ASN2BASE
    ASN2DBCN ASN2ZOSC
    

Fix information

  • Fixed component name

    WS REPLICATION

  • Fixed component ID

    5655L8800

Applicable component levels

  • R910 PSY UK75961

       UP12/02/14 P F202

  • R911 PSY UK75962

       UP12/02/15 P F202

  • R912 PSY UK75963

       UP12/02/14 P F202

  • R913 PSY UK75964

       UP12/02/14 P F202

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":"910","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
08 March 2012