IBM Support

II10976: CHANGES TO DB2 MESSAGES AND CODES SC26-3268-00 THAT DID NOT MAKE V4.1 GA PUBS. CONTINUATION OF II09155, II10225, II10803.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • 5740xyr00 DB2 R410 V4 Continued in II09155,II10225,II10803
    This APAR documents changes to the DB2 Messages and Codes
    SC26326800 which did not make Version 4.1 GA pubs.
    ============================================================
    Version 4 Book Title: Messages & Codes
    Pages: 2-12
    Change Description:
    
             The following paragraph will be added to
             the Programmer Response for SQLCODE -122:
    
     Programmer Response:
    
       You can correct the statement by:
             - including the columns in the GROUP BY
               clause that are in the SELECT clause, or
             - removing the columns from the SELECT clause
       Refer to Chapter 5 of SQL REFERENCE for information
       about the use of GROUP BY clauses in SQL statements.
    ============================================================
    Version 4 Book Title: Messages & Codes
    Pages: 3-335
    
    Change Description:
    Modify the SSID under message DSNW050I to read:
       1-4 character DB2 subsystem name
    ============================================================
    Version 4 Book Title: Messages and Codes
    Pages: 3-335
    Change Description:
    
    In the "Explanation" section of message DSNX903E, change
    the description of the "name" parameter as follows:
    
        name      The name that was greater than 8 characters
                  in length
    ============================================================
    Version 4 Book Title: Messages and Codes
    Pages: 4-12
    Change Description:
    In the message explanation, add the following bullet to the
    existing bulleted list of causes:
    
    -TOD clock values are out of synch between systems in a
    Parallel Sysplex.
    
    In the user response section of the message add:
    
    If you are running data sharing, check the connectivity of
    the systems to the sysplex timers. The TOD clock values of
    all systems in the sysplex should all be within one
    microsecond apart unless a sysplex timer is malfunctioning.
    ============================================================
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II10976

  • Reported component name

    PB LIB INFO ITE

  • Reported component ID

    INFOPBLIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1997-12-22

  • Closed date

  • Last modified date

    1999-06-08

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
08 June 1999