File Name:

DC@FPS, LX_FPS

Description

This table defines the property settings associated with a Visual LANSA component in some specified context. For example, when the owner component type is 1 (member), then information in this table defines the property settings associated with a memebr component in the current component definition.
Note that the sequence number is required because a property value can be longer than the 20 bytes allocated to store it.   

Implemented in:

7.50 / H4

LANSA for i Library:

<<dtalib>>

Visual LANSA Collection:

LX_DTA

Field Name Prefix:

FPS, XPS

Required for Run Only System?

Yes

LANSA for i Logical Views

Name

Use

Keys/Description/Comments

LX_FPSV1

Read

FPSP_I, FPSCID, FPSCTX,  FPSOCU, FPSPTU, FPSSEQ

LX_FPSV2

Update

Same as LX_FPSV1.

Visual LANSA Database Index

Name

Unique?

Columns

LX_FPS_PRIM

Y

XPSP_I, XPSCID, XPSCTX, XPSOCU, XPSPTU, XPSSEQ

Record Layout

Key

Field Name

Description

LANSA for i Type

Visual LANSA Type

Comments

1

P_I

Partition Identifier

A 3

CHAR(3)


2

CID

Component Class Identifier

A 10

CHAR(10)


3

CTX

Context Identifier

P 7,0

LONG


4

OCU

Owner Component Name (Uppercase)

A 20

CHAR(20)

See the Notes

5

PTU

Property Name (Uppercase)

A 20

CHAR(20)


6

SEQ

Property Value Sequence

P 7,0

LONG


1-4   Sequence number

5-5   0 = more records in sequence
         9 = last or only record of sequence

6 - 7   Length of value in record


VAL

Property Value

A 20

STRING(20)



EXP

Expression Attributes

P 9,0

LONG



FE1

Future Expansion Field 1

P 7,0

LONG



FE2

Future Expansion - Field 2

A 10

CHAR(10)


Notes

When saving property settings for the Owner component, OCU will be the same as CID.

The EXP column will be used to save a Visual LANSA collection of flags that will assist the restore process when Visual LANSA uses the Cross Reference tables to restore a component. The Expression Attributes contain flags that indicate how Visual LANSA is to interpret the Property Value.

The property value may be longer than 20 characters and will be split into several records. It can contain DBCS. When checking in/out, if DBCS,  the whole value must be assembled and processed as one string in the same manner as RDMLX.