IBM Support

PM92321: HEX FORMAT BEHAVES DIFFERENTLY THAT LHEX AND CHAR FORMATS WHEN "CAPS INITIALLY ON" IS CHECKED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If in 0.6 Edit options, "CAPS initially ON" is checked, then
    in CHAR or LHEX mode, if one character is changed from lower
    case to uppercase, then all characters in the record are
    uppercased. When in HEX mode, only the changed character is
    uppercased, not the entire record. The behavior should be the
    same between the format modes.
    

Local fix

  • As HEX format should behave the same as CHAR and LHEX, users
    can switch to CHAR or LHEX to get the expected behavior.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All File Manager users                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. When editing data in HEX mode        *
    *                      without a template, and the CAPS ON     *
    *                      option is in effect, only those         *
    *                      characters which are changed are        *
    *                      uppercased.                             *
    *                      2. When editing data in LHEX mode       *
    *                      without a template, and the CAPS ON     *
    *                      option is in effect, the record will be *
    *                      uppercased when a change is made the    *
    *                      the record.                             *
    ****************************************************************
    * RECOMMENDATION: Apply the provided PTF.                      *
    ****************************************************************
    

Problem conclusion

  • 1. When editing data in HEX mode without a template, and the
    CAPS ON option is in effect, the record will be uppercased when
    a change is made to the record unless that change is made to the
    hexadecimal representation of the data.
    2. When editing data in LHEX mode without a template, and the
    CAPS ON option is in effect, the record will not be uppercased
    when a change is made to the record unless that change is made
    to the hexadecimal representation of the data.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM92321

  • Reported component name

    FILE MANAGER Z/

  • Reported component ID

    5655W6800

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-07-03

  • Closed date

    2013-07-23

  • Last modified date

    2013-08-02

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

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

Modules/Macros

  • FMN0LVL
    

Fix information

  • Fixed component name

    FILE MANAGER Z/

  • Fixed component ID

    5655W6800

Applicable component levels

  • RC10 PSY UK95967

       UP13/07/25 P F307

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":"C10","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSXJAV","label":"File Manager for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C10","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 August 2013