4 1 Technical Considerations and Warnings

LANSA Open System Utilities

4.1 Technical Considerations and Warnings

  • Processes must be compiled. It is impossible to invoke a LANSA process using this method if the OS/400 object for the process does not exist.
  • No library list manipulation is performed. The library list must be correct. That is, these libraries must be included in the library list:
  • LANSA Program Library
  • LANSA Data Library
  • Partition module library
  • Partition data library (optionally)
  • Any LANSA functions that are executed using this method must be created with FUNCTION OPTIONS(*DIRECT).
  • These procedures are not available for processes and/or functions that require parameters, other than working lists or data structures.
  • In the case of multilingual partitions, the user defined setup program will also need to perform any overrides for message files.

    That is, LANSA Message file DC@M01 may need to be overridden to the appropriate version. (e.g. French may use DC@M01FRA). Refer to the LANSA Multilingual Application Design Guide for further information about the type of processing that is necessary.
  • It is not recommended that Function Routing be used with this method of running LANSA applications. When LANSA is invoked normally by use of the LANSA command, the Function Routing Table is loaded during the LANSA initiation and is available until LANSA is terminated. If you use this method of calling LANSA applications, the Function Routing Table will not have been loaded for you.
  • All steps and guidelines must be considered when using this method to execute LANSA processes or functions.
  • All examples provided are in RPG/400 or Control Language. This is not a restriction. User defined programs that use this method to execute LANSA applications can be written in any language available in OS/400.
  • These procedures are not available for RDMLX functions. To achieve the equivalent functionality, code a "wrapper" RDML function that uses the same FUNCTION statement and simply calls the RDMLX function. If the original RDMLX function is using the RCV_DS to receive a data structure, refer to Note 3 in 4.6.1 Data Structures.

Warnings:

  • No security checking is performed.
  • The environment for the application is your responsibility. LANSA no longer has any control, your user defined 3GL program is in control.