PM77090: MESSAGE DSNA679I IS NOT A VALID MULTI-LINE WTO

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Message DSNA679I is not a valid multi-line WTO. The message is
    is displayed spread over three lines and the third line issued
    as a separate message.
    DSNA679I  DSNA6BUF THE ADMIN SCHEDULER TT1AADMT CANNOT ACCESS
    TASK LIST
    SYSIBM.ADMIN_TASKS, REASON=
    SQLCODE -924, SQLSTATE 58006, 0001 0100 00F30018
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
    *                 users of the DB2 scheduler for               *
    *                 administrative tasks                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message DSNA679I is not written to the  *
    *                      console as a multi-line message. This   *
    *                      message is split and written as 2       *
    *                      single-line messages instead:           *
    *                                                              *
    *                       N ... DSNA679I  DSNA6BUF THE ADMIN     *
    *                             SCHEDULER DSNADMT CANNOT ACCESS  *
    *                             TASK LIST                        *
    *                       S ... SYSIBM.ADMIN_TASKS, REASON=      *
    *                       N ... SQLCODE -xxx, SQLSTATE yyyyy,    *
    *                             SYSIBM.ADMIN_TASKS               *
    *                                                              *
    *                      where                                   *
    *                      o the first part of DSNA679I is         *
    *                        a single-line message (log record     *
    *                        type 'N') followed by a continuation  *
    *                        line (log record type 'S')            *
    *                      o the second part of DSNA679I, which    *
    *                        contains the value of the REASON      *
    *                        token, is another single-line         *
    *                        message (log record type 'N')         *
    *                        which could also be followed by       *
    *                        a continuation line (log record       *
    *                        type 'S') if the value of the         *
    *                        REASON token is long and it           *
    *                        wraps                                 *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    The scheduler splits message DSNA679I into 2 parts, and invokes
    WTO to write each part as a single-line message.
    

Problem conclusion

  • The scheduler is modified to issue DSNA679I as a multi-line
    message as follows:
    
      M ... DSNA679I  DSNA6BUF THE ADMIN SCHEDULER DSNADMT
      D ... CANNOT ACCESS TASK LIST SYSIBM.ADMIN_TASKS,
      E ... REASON=SQLCODE -xxx, SQLSTATE yyyyy, SYSIBM.ADMIN_TASKS
    
    with log record types of 'M' (first line of a multi-line
    message), 'D' (data line of a multi-line message), and 'E'
    (end line of a multi-line message).
    
    If the REASON= line is longer than 71 characters, it is split,
    if possible, at a blank as follows:
      M ... DSNA679I  DSNA6BUF THE ADMIN SCHEDULER DSNADMT
      D ... CANNOT ACCESS TASK LIST SYSIBM.ADMIN_TASKS,
      D ... REASON=SQLCODE -xxx, SQLSTATE yyyyy,
      E ... locn.DSNADM.DSNA6DB2.contoken DSNRRSAF 03
    
    To make each line of DSNA679I clearer, DSNA679I is subdivided
    differently from how it was subdivided as two single-line
    messages. Therefore, any application that parses DSNA679I
    based on how this message was subdivided and displayed on the
    console must be modified.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM77090

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-14

  • Closed date

    2013-02-25

  • Last modified date

    2013-05-03

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

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

    UK91974 UK91975

Modules/Macros

  •    DSNA6BUF DSNA6ITK
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK91974

       UP13/04/27 P F304

  • R910 PSY UK91975

       UP13/04/27 P F304

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM77090

Modified date:

2013-05-03

Translate my page

Machine Translation

Content navigation