IBM Support

PK10070: UCTRAN=YES CAUSING CEDA RDO DEFINITIONS TO BE FOLDED TO UPPER CASE WHEN THEY SHOULD NOT.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If CEDA is defined with a PROFILE that has UCTRAN(YES) then the
    Mixed Case fields are translated to upper case.  CEDA is
    supposed to recognize that certain fields in RDO definitions are
    case sensitive, and not automatically fold everything to upper
    case.  UCTRAN setting in PROFILE or TYPETERM should not have any
    affect on this.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Altering mixed case attribute values    *
    *                      within CEDA can cause lowercase         *
    *                      characters to be uppercased ( folded ). *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The CEDA transaction has been modified to use a profile with
    UCTRAN set to YES. If a mixed cased attribute for a resource
    definition is then altered, from within a CEDA panel, any
    lowercase characters in the new value are being uppercased.
    Lowercase characters should not be folded when mixed case
    attribute values are altered from within CEDA. A similar
    problem could happen with DEFINE.
    
    Additional Keywords: TCTEOPT2 TCTETUCT DFHCICST
    

Problem conclusion

  • DFHEIN01 has been changed so that the profile UCTRAN is set off
    while the CEDA transaction is active. This will ensure mixed
    cased attributes values are not uppercased when altered to
    contain lowercase characters.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK10070

  • Reported component name

    CICSTS 3.1 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2005-08-08

  • Closed date

    2005-09-30

  • Last modified date

    2006-11-03

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

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

    UK07733 PK34000

Modules/Macros

  •    DFHCUCA  DFHCUCAB DFHCUCAC DFHCUCAN DFHEIDSD
    DFHEIN01 DFHEIN22 DFHEIN23 DFHEMT23 DFHESP01 DFHESP22 DFHESP23
    

Fix information

  • Fixed component name

    CICSTS 3.1 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R400 PSY UK07733

       UP05/10/05 P F510

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"3.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 November 2006