Entering mixed case attributes

CEDA is often used in circumstances where the CICS system, or the particular terminals, are defined so that all input is folded (or translated) to upper case. However there are some resource definition attribute values which must be entered in lower case or mixed case, because their values must match those in other systems, where the use of lower case fields is commonplace.

Note: When upper case translation is active for a terminal, characters that appear in lower case as you type them are translated to upper case before CICS processes them.
CEDA knows that certain fields may be required in mixed case. When you use the CEDA input panels, upper case translation of the values entered in these fields does not occur, irrespective of the way upper case translation is specified for your terminal. These fields are marked (Mixed Case) on the CEDA input panels. Figure 1 shows an example:
Figure 1. The DEFINE panel for DJAR
 DJar         ==>
 Group        ==>
 Description  ==>
 Corbaserver  ==>
 Hfsfile      ==>
 (Mixed Case) ==>
              ==>
              ==>

The action of suppressing upper case translation, if it is active, applies to input on the CEDA panels, but it does not apply when values for these fields are supplied on the CEDA command line. If you need to enter mixed case values when you use CEDA from the command line, you must ensure that the terminal you use is correctly configured, with upper case translation suppressed.

So, for example, using a terminal which has UCTRAN set to cause upper case translation, If you enter:
CEDA DEFINE DJAR GROUP(ONE) CORBASERVER(TWO) HFSFILE(three) 
the result is HFSFILE THREE instead of the three that you intended.
If however you enter:
CEDA DEFINE DJAR GROUP(ONE) CORBASERVER(TWO)
and then supply the value three for HFSFILE using the panel, the result is as you intended.

CEDA has a help panel for mixed case input, see Figure 10