Generally, a file is not maintained by LANSA if it was created by, and belongs to, an application created outside of LANSA.
If such a file (frequently referred to as an OTHER file) needs to be accessible within the LANSA system, the definition must be loaded into LANSA. At the same time, any alterations to the definitions must be prohibited from within LANSA, as this could affect the system which is maintaining it.
The facility to "Load/re-load external file definitions" is designed specifically to handle these files.
You need to be sure of:
3.19.1 What Happens When a File Definition Is Loaded (or Re-Loaded)?
3.19.2 When Should a File Definition Be Loaded (or Re-Loaded)?
3.19.3 The Steps to Loading Definition of File Not Maintained by LANSA
3.19.4 Elect whether or not to Make Logical File Accessible
3.19.5 Review Messages that Result from Attempted Load
When you create a new file definition via the "Create new file definition" prompt (accessed from the file control menu) you must specify whether the file being defined is to be NOT maintained by LANSA by specifying "OTHER". (The alternative is that the file is to be maintained by LANSA by specifying "LANSA".)
Note: You must specify *OTHER_DATETIME and *OTHER_VARCHAR options if the OTHER files that you want to made known to LANSA contain:
For more information about these options, refer to OTHER file I/O modules in Compile and Edit Settings in the Review System Settings.
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 list to access the File and IO Module.
