4 10 3 IBM i RDMLX Other Files

Visual LANSA

4.10.3 IBM i RDMLX Other Files

This facility is NOT to be used to load a LANSA file. Instead, export/import the definition you want to use into the new partition. Do not compile the file. Set the user's library to access the File and IO Module.

The following information pertains to RDMLX Other Files. For RDML Other Files, refer to Load the Definition of a File NOT Maintained by LANSA from the LANSA for i User Guide.

When loading an IBM i Other File for RDMLX, LANSA supports a much wider range of field types. For details on the various field types, refer to Field Types in the LANSA Technical Reference Guide.

Database columns will be skipped during the load if they meet the following criteria:

  • Type is Graphic, Vargraphic, DBCLOB with a non-Unicode CCSID. (Unicode CCSIDs are 1200 and 13488 for Graphic data.)
  • Type is Rowid, Decfloat, XML, or CLOB with CCSID 1208.

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

As IBM i Other Files never have their external definition changed by LANSA, additional columns to support LOBs are never added. (Refer to No additional LOB columns.)

On Windows and Linux, IBM i Other Files are treated as if they are LANSA Files. Some IBM i Other Files that have features not supported by LANSA Files may not build or execute correctly on Windows and Linux.

Also See

Load Other File in the Technical Reference Guide

How BLOB and CLOB columns are handled by RDMLX Other Files

Ý 4.10 Load Other File