IBM Support

PH11871: NEW FUNCTION FOR DB2 FOR Z/OS UTILITIES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • New Function for Db2 for z/OS utilities
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 for z/OS who need to write a                      *
    * Db2 diagnostic log record to trigger a                       *
    * data refresh on replicated objects.                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The REPAIR utility is enhanced to                            *
    * write a Db2 diagnostic log record                            *
    * which can be used to trigger a data                          *
    * refresh on replicated objects.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    A new REPAIR option, WRITELOG, to write a Diagnostic Log
    Record:
    
    >>REPAIR------------------------------------------------------>
    >+---------------------------------------------------------+-><
     |                   .------------------------.            |
     |.OBJECT. .LOG-YES. V                        |            |
     '+------+-+-------+-+-| locate block |-------+--+-+------+'
               'LOG-NO-' +-| set statement |---------+ 'CLONE-'
                         +-| dbd-statement |---------+
                         +-| level-id statement |----+
                         +-| versions statement |----+
                         +-| catalog statement |-----+
    |                    +-| system-pages statement |+
    |                    '-| write-log statement |---'
    
    |write-log statement option descriptions
    |>>-WRITELOG-------------------------------------------------->
    |>--TABLESPACE---+-------------+-table-space-name------------->
    |                'database-name'
    |>-TYPE-X'4400'--SUBTYPE-X'0083'--TEXT-X'-byte-string-'------<<
    
    |WRITELOG statement
    |Use the WRITELOG statement to write a Db2 log record. You
    |cannot specify CLONE with WRITELOG
    
    |       TABLESPACE  database-name.table-space-name
    |             Specifies the table space (and, optionally, the
    |             database to which it belongs) whose log record
    |             is to be written.
    |             database-name
    |                   Specifies the name of the database to
    |                   which the table space belongs. The default
    |                   value is DSNDB04.
    |             table-space-name
    |                   Specifies the name of the table space.
    
    |        TYPE  X'4400'
    |              Specifies that an alter or modify recovery log
    |              record is to be written
    
    |        SUBTYPE X'0083'
    |              Specifies that the add or alter column
    |              diagnostic log record (SCHEMA ALTER DIAGNOSTIC
    |              LOG RECORD as documented in DSNDQJ00) is to be
    |              written.
    
    |        TEXT  X'byte string'
    |              Specifies the content of the log record to be
    |              written (REPAIR WRITELOG will set the second
    |              bit of the 9th byte).
    
    IBM Knowledge Center is updated for these changes:
    http://www.ibm.com/support/knowledgecenter/SSEPEK
    

Problem conclusion

Temporary fix

Comments

  • REPAIR utility code is enhanced to support the new WRITELOG
    option to write a Db2 diagnostic log record.
    

APAR Information

  • APAR number

    PH11871

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-05-07

  • Closed date

    2019-09-11

  • Last modified date

    2019-10-01

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

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

    UI65271

Modules/Macros

  • DSNUGPRZ DSNUCBWL DSNFUDIR DSNUGPRV DSNUGPRT DSNFUDRE DSNUGUCA
    DSNUGTIS DSNUMSGE DSNUCBRP DSNUGDDN
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI65271

       UP19/09/26 P F909

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":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 October 2019