PC Other Tables

LANSA supports most popular databases used in business at stable and supported versions. Refer to your LANSA supplier if you need exact details of what databases and versions are supported.

A PC Other table will always be imported into an RDMLX partition as an RDMLX Imported Tables. There is no option to import a PC Other table into an RDMLX partition as an RDML table. Furthermore, RDML field types will be converted to RDMLX field types. For example, alphanumeric fields become string fields.

When LANSA imports the table, it records the information required to connect to the database, which is then automatically used at execution time. These details may need to be altered. (Refer to Using DEFINE_DB_SERVER to modify connection details.)

• If LANSA cannot find a primary key defined for the table, it will import the first unique index (if any) it finds as the primary key.

• The Create RRNO Column flag must be set as appropriate for your application. Refer to Create RRNO Column.

• DateTime fields may require special handling. (Refer to Handling of Timestamp or DateTime columns.)

• It is strongly recommended that you do not import LANSA tables as PC Other tables. Refer to LANSA Tables loaded as Imported tables.

• SuperServer PSXX parameters cannot be used with local PC Other tables. (Refer to Using SuperServer with PC Other Tables.)

PC Other table data cannot be shipped with the Deployment Tool. If you need to ship data, you will need to write your own functions to insert or update the data as part of a package install. The Built-In Functions TRANSFORM_LIST and TRANSFORM_FILE may be appropriate. For further details, refer to Commands to execute in the LANSA Application Deployment Tool Guide.

Also See

LANSA Tables loaded as Imported tables

Using SuperServer with PC Other Tables

Using DEFINE_DB_SERVER to modify connection details

Database-specific Notes

RDML PC Other Table

RDMLX Imported Tables

Import Tables from IBM i in the Technical Reference Guide