IBM Support

PM03341: USE OF SYSLGRNX INVALID WITH ANY MEMID > 9

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the SYSLGRNX option of LAT
    (i.e., Misc Flags not = 'X'), the product will not deal properly
    with any member whose ID (i.e., its MEMID) is greater than 9.
    The REPORT utility generates the MEMID in displayable
    hexadecimal, but the product treats it as decimal. This causes
    an internal mismatch, resulting in potential incorrect results
    from use of SYSLGRNX. Workaround is to bypass SYSLGRNX
    (i.e., set Misc Flags=X) if site has more than 9 members in a
    data sharing group.
    

Local fix

  • Bypass SYSLGRNX (set Misc Flags = X) if site has more than 9
    members in a data sharing group
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using the SYSLGRNX option of LAT   *
    *                      (i.e., Misc Flags not = 'X'), the       *
    *                      product will not deal properly with     *
    *                      any member whose ID (i.e., its MEMID)   *
    *                      is greater than 9. The REPORT utility   *
    *                      generates the MEMID in displayable      *
    *                      hexadecimal, but the product treats it  *
    *                      as decimal. This causes an internal     *
    *                      mismatch, resulting in potential        *
    *                      incorrect results from use of SYSLGRNX. *
    *                      Workaround is to bypass SYSLGRNX        *
    *                      (i.e., set Misc Flags=X) if site has    *
    *                      more than 9 members in a data sharing   *
    *                      group.                                  *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM03341

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-12-11

  • Closed date

    2010-02-01

  • Last modified date

    2010-03-01

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

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

Modules/Macros

  •    ALAZT550
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R310 PSY UK54054

       UP10/02/13 P F002

  • R320 PSY UK54055

       UP10/02/13 P F002

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310"}]

Document Information

Modified date:
12 April 2021