IBM Support

PI43178: SQLCODE -798 USING GENERATED ALWAYS AS (SESSION_USER)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The user is performing an EDIT of a DB2 table which has a column
    defined as:
    BEARB_SB2  VARCHAR(128)
    GENERATED ALWAYS AS (SESSION_USER)
    An  attempt to insert a row into such table causes the following
    DB2 error to be reported:
    DSNT408I SQLCODE = -798, ERROR:  A VALUE CANNOT BE SPECIFIED FOR
    COLUMN
             BEARB_SB2 WHICH IS DEFINED AS GENERATED ALWAYS
    DSNT418I SQLSTATE   = 428C9 SQLSTATE RETURN CODE
    DSNT415I SQLERRP    = DSNXOFF SQL PROCEDURE DETECTING ERROR
    DSNT416I SQLERRD    = -100  0  0  -1  0  0 SQL DIAGNOSTIC
    INFORMATION
    DSNT416I SQLERRD    = X'FFFFFF9C'  X'00000000'  X'00000000'
             X'FFFFFFFF'  X'00000000'  X'00000000' SQL DIAGNOSTIC
             INFORMATION
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Optim for z/OS users utilizing DB2 V11 integrated auditing   *
    * support functions introduced with APAR PM99683: "NEW         *
    * FUNCTION ON DB2 11 FOR Z/OS"                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * An attempt to process DB2 V11 tables which include columns   *
    * defined with integrated auditing support as introduced by    *
    * APAR PM99683: "NEW FUNCTION ON DB2 11 FOR Z/OS" may result   *
    * in SQL errors, for example DSNT408I SQLCODE = -798, ERROR:   *
    * A VALUE CANNOT BE SPECIFIED FOR COLUMN.                      *
    * In addition, incorrect JCL or DDL statements may be          *
    * generated while processing such tables.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply the provided fix.                                      *
    ****************************************************************
    Optim for z/OS did not support DB2 V11 integrated auditing
    support functions introduced with APAR PM99683: "NEW FUNCTION ON
    DB2 11 FOR Z/OS".
    

Problem conclusion

  • Optim for z/OS processing will be enhanced to add full support
    for DB2 V11 integrated auditing support functions introduced
    with APAR PM99683: "NEW FUNCTION ON DB2 11 FOR Z/OS".
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI43178

  • Reported component name

    OPTIM MOVE FOR

  • Reported component ID

    5655V0700

  • Reported release

    720

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-06-16

  • Closed date

    2015-07-06

  • Last modified date

    2015-08-03

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

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

    PI43179

Fix information

  • Fixed component name

    OPTIM MOVE FOR

  • Fixed component ID

    5655V0700

Applicable component levels

  • R720 PSY UI29153

       UP15/07/10 P F507

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

Document Information

Modified date:
03 August 2015