When the option to create a new multilingual variable is chosen from the field control menu, a format like this example is displayed until the EXIT or CANCEL function key is used:
DC@P100801 Multilingual Variable - GGGG
Multilingual Variable . . . . . *MTXT___________________
Maximum Length . . . . . . . . ___
Initial public access . . . . . NORMAL (ALL, NORMAL, NONE)
*... ... 1 ... ... 2 ... ... 3 ... ... 4 ... ... 5 ... ... 6 ... ... 7
XXXXXXXXXX . . .
_________________________________________________________________
XXXXXXXXXX . . .
_________________________________________________________________
XXXXXXXXXX . . .
_________________________________________________________________
XXXXXXXXXX . . .
_________________________________________________________________
Fnn=Help Fnn=Exit Fnn=Cancel Fnn=Messages
|
|---|
|
Key in details of the new multilingual variable and press Enter.
Input Options
These input options apply to the creation (or amendment) of multilingual variables:
Special Note: This Facility uses Language "Grouping"
Standard LANSA language group processing means that any screen interaction may have to be repeated for each language group (if languages are used in the group). The group being processed is shown on the top of the example screen as GGGG, but when in use will have values:
LRTB | Left to right languages group. |
RLTB | Right to left languages group. |
DBCS | Double byte character set languages group. |
Multilingual Variable
Specifies the name of the multilingual variable:
- The first 5 characters are fixed to "*MTXT" and cannot be changed.
- This allows ready identification of multilingual variables.
- The rest of the name must be from 1 to 15 characters, contain no imbedded blanks, conform to IBM i & CPF valid name rules, and be unique within the current partition.
- Use a maximum of 3 characters for function key names as the input field on RDML commands is only 8 long.
- Develop and use naming standards for *MTXT variables.
- In packaged systems, use obscure prefixes to preserve uniqueness.
- Use as default value for fields in the dictionary, rather than direct RDML reference, is preferable when intention is to use as panel or report text. Improves cross referencing capabilities.
- Fields in the dictionary should have a naming standard too. It should equate to the naming standard used for the multilingual variable that is used as its default value.
- Most *MTXT references are "locked in" at compile time. Change of an *MTXT variable will require application recompile. This is where the field/default value/cross reference capability is most useful.
- Exception is use of *MTXT variables as message text. In this situation the derivation is dynamic, so no recompiles are required.
Maximum Length
Specifies the maximum length of multilingual variable.
- Range 1 to 78.
- No value specified should exceed length specified.
- In RLTB languages, length is from the right hand side.
- Includes shift characters in DBCS languages.
Initial Public Access
Mandatory, but always pre-filled to NORMAL. Allowable values are:
NORMAL | Other users can use this multilingual variable, but cannot change or delete its definition in/from the data dictionary. |
ALL | Other users can use this multilingual variable and can also change or delete its definition in/from the data dictionary |
NONE | Other users cannot use this multilingual variable, nor can they review, change or delete its definition in/from the data dictionary. |
XXXXXXXXXX ....
XXXXXXXXXX ... shows the language. On the line directly below specify the value that the *MTXT variable is to have when the specified language is being used.
- Keyed from right in RLTB languages.
- Include shift characters in DBCS languages.
- Do not exceed maximum length specified.
- Use upper and lower case characters as required.
- Where applicable, manually centering within the maximum length can be used.
- Center from left (within maximum length) for LRTB and DBCS languages.
- Center from right (within maximum length) for RLTB languages.