Versions Compared

Old Version 4

changes.mady.by.user user-2c621

Saved on

compared with

New Version Current

changes.mady.by.user Fabiola Arias Navia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If the flag *IMPREFFLDNOPROP is in system data area DC@OSVEROP, the input and output attributes will not be protected but will still be updated if the reference field is changed. This is to provide compatibility with previous versions. For more information, refer to Version Dependency Data Area DC@OSVEROP.

Reference fields are mostly used to specify an attribute that is common to many similar fields. For example, a shipping company deals with many different types of ports, so they could define a field called PORT as an alphanumeric field of 5 characters.

...

Optional. If not specified defaults to either alpha (type A) or numeric (type P or S) system default values. Further information on output attributes is contained in DEFINE Parameters and OVERRIDE Parameters in the Technical Reference.

...

Attribute

Description / Comments

A

P

S

GRN

Display with color green.

Y

Y

Y

WHT

Display with color white.

Y

Y

Y

RED

Display with color red.

Y

Y

Y

TRQ

Display with color turquoise.

Y

Y

Y

YLW

Display with color yellow.

Y

Y

Y

PNK

Display with color pink.

Y

Y

Y

BLU

Display with color blue.

Y

Y

Y

BL

Display blinking.

Y

Y

Y

CS

Display with column separators.

Y

Y

Y

HI

Display in high intensity.

Y

Y

Y

ND

Non-display (hidden field).

Y

Y

Y

SREV

Store in reverse format. This is a special attribute provided for bidirectional languages. Refer to the LANSA Multilingual Application Design Guide.

Y

N

N

SBIN

Store in binary format. This special attribute is provided for fields that need to contain embedded packed or signed fields. Refer to the Use of Hex Values, Attributes, Hidden/Embedded Decimal Data in the LANSA Application Design Guide.

Y

N

N

Urxx

User Defined Reporting Attribute. Provides access to DDS statements for printer files. Refer to User Defined Reporting Attributes.

Y

Y

Y

HIND

HINDI Numerics. Display using HINDI numerals. Refer to Hindi Numerics for details.

N

Y

Y

CBOX *

Check Box

Y

N

N

RBnn *

Radio Button

Y

N

N

PBnn *

Push Button

Y

N

N

DDxx *

Drop Down

Y

N

N

Attributes marked with * represent the field with the corresponding GUI WIMP construct. Refer to Guidelines, Hints, and Tips in GUI WIMP Constructs for more information.

...

*Normally only PBCN and PBCE would be specified as output attributes. Refer to the IBM i SAA/CUA Implementation in the LANSA Application Design Guide for details of these attributes.

...

Optional. If not specified defaults to either alpha (type A) or numeric (type P or S) system default values. Further information on input attributes is contained in DEFINE Parameters and OVERRIDE Parameters in the Technical Reference.

...

Attribute

Description / Comments

A

P

S

AB

Allow to be blank.

Y

Y

Y

ME

Mandatory entry check required.

Y

Y

Y

MF

Mandatory fill check required.

Y

Y

Y

M10

Modulus 10 check required.


Y

Y

M11

Modulus 11 check required.


Y

Y

VN

Valid name check required.

Y



FE

Field exit key required.

Y

Y

Y

LC

Lowercase entry allowed. If you do NOT set this attribute, refer also to PC Locale uppercasing requested in Review or Change a Partition's Multilingual Attributes

Y



RB

Right adjust and blank fill.

Y

Y

Y

RZ

Right adjust and zero fill.

Y

Y

Y

RL

Move cursor right to left.

Y

Y

Y

RLTB

Tab cursor right/left top/bottom Valid in SAA/CUA partitions only. Affects all screen panels in function.

Y

Y

Y

GRN

Display with color green.

Y

Y

Y

WHT

Display with color white.

Y

Y

Y

RED

Display with color red.

Y

Y

Y

TRQ

Display with color turquoise.

Y

Y

Y

YLW

Display with color yellow.

Y

Y

Y

PNK

Display with color pink.

Y

Y

Y

BLU

Display with color blue.

Y

Y

Y

BL

Display blinking.

Y

Y

Y

CS

Display with column separators.

Y

Y

Y

HI

Display in high intensity.

Y

Y

Y

ND

Non-display (hidden field).

Y

Y

Y

RA

Auto record advance field

Y

Y

Y

SREV

Store in reverse format. This is a special attribute provided for bidirectional languages. Refer to the LANSA Multilingual Application Design Guide.

Y

N

N

SBIN

Store in binary format. This special attribute is provided for fields that need to contain embedded packed or signed fields. Refer to the Use of Hex Values, Attributes, Hidden/Embedded Decimal Data in the LANSA Application Design Guide.

Y

N

N

HIND

HINDI Numerics. Display using HINDI numerals. Refer to Hindi Numerics for details.

N

Y

Y

CBOX

Check Box

Y

N

N

RBnn

Radio Button

Y

N

N

PBnn

Push Button

Y

N

N

DDxx

Drop Down. Represents the field with the corresponding GUI WIMP construct. Refer to Guidelines, Hints, and Tips in GUI WIMP Constructs for more information.

Y

N

N

...

* Normally only PBCN and PBCE would be specified as output attributes. Refer to the IBM i SAA/CUA Implementation in the LANSA Application Design Guide for details of these attributes. Note also that only one color can be specified for a field. Use of colors may affect other attributes. Refer to IBM manual Data Description Specifications for details. Keywords that should be reviewed are CHECK, COLOR and DSPATR.

...

Optional. However, use of edit codes for all numeric fields (type S or P) is strongly recommended. Edit codes supported under this version of LANSA are shown in Standard Field Edit Codes in the Technical Reference Guide.

...

In other words, all field names and all alias names must form a unique list of names. The alias name facility is provided primarily for installations that use the COBOL or PL/1 programming languages. Refer to the specific IBM-supplied program reference manuals for the use of the ALIAS keyword. Name must conform to field naming conventions like the field name. COBOL or PL/1 language naming conventions are NOT checked.

...

Using *DIRECT has positive performance benefits, but when a prompting function is to be invoked this way it must use the FUNCTION OPTIONS(*DIRECT) command. Refer to CALL Comments / Warnings and FUNCTION Examples in the Technical Reference Guide for details of direct mode invocation of functions. A "prompt request" is made against a field when the user positions the screen cursor into a field, on its label, or on one of its column headings, and then uses the PROMPT function key. Normally the prompt function key is F4, but it may be assigned differently on your system.

...

If the reference field's prompt process/function is changed, any of the fields referring to it which have the same prompt process/function (before the referenced field is changed) also have their prompt process/function updated.

For technical details of Prompt_Key Processing please refer to the Technical Reference Guide. For examples of prompting processes and functions please refer to What Happens When the PROMPT Key is Used in the LANSA Application Design Guide.

...