Page History
...
- RDML objects may be exported and imported between partitions without restriction.
- RDMLX objects may be exported from a partition enabled for RDMLX and imported into another partition enabled for RDMLX.
- RDMLX objects may not be imported in an RDML partition.
- An IBM i export which contains a mixture of RDML and RDMLX objects may be imported into an RDML partition. The RDML objects will be imported. The RDMLX objects will not be imported. They will be reported with a warning message. For example,
Definition of field STD_DATEX was not successfully exported and so it cannot be imported.
A Report Is Produced Which Details Each Step of the Export Job
The report takes the form of a series of messages that are listed on the report. Each message has a unique identifying number, a type (completion, warning or fatal), and a line of text that describes what event took place.
...
When the export job is submitted from a workstation, a summary message will be sent back to the workstation at job completion indicating the number of completion, warning, and fatal messages issued by the job (as per the summary lines at the end of the export report).
...
The format of tapes / disks used varies with the source (i.e. exporting) and target (i.e. importing ) system types. Currently, only the IBM i IBM i is supported for exports via tapes as per the following table:
Source System | Target System | Format Of Data On Tape / Disk |
|---|---|---|
IBM i | IBM i | Operating system save restore |
Transfer of Programs in Compiled Form
...
As such, all the logic used by LANSA to import fields, files, processes, and functions has been designed so that it can be easily re-run with no specific actions required by the importer other than to start the job executing again.
...
This data area, which is created after some LANSA operations complete, can be accessed by other programs to test the result of the attempted export operation.
Refer to the DC@RESLT Data Area for details of this data area and what it contains.
...
Clearly mark all tapes with 'Import will delete source code'.
| Anchor | ||||
|---|---|---|---|---|
|
To reduce the amount of time taken to investigate and re-run an export job in error, limit the size of export lists where ever possible, for example when exporting a whole partition set up a separate export list for each object type opposed to one export list for the whole partition:
LIST01 | All fields in a partition |
LIST02 | All files in a partition |
LIST03 | All processes and functions in a partition |
To avoid large export lists it is recommended that you set up and run numerous medium-sized export jobs opposed to 1 very large export job.
...
Since the LANSA export/import facilities support the transfer of non-LANSA objects between systems, you may specify user-defined IBM i IBM i operating system commands which can be executed as part of the import job. Typical examples would be the transfer of objects such as message files, non-LANSA created database files, and programs.
This is an example of the types of commands that would most likely be executed before and after an import of these non-LANSA objects:
...