Important considerations
This section provides important information that you need to consider before manually copying source files and metadata between product lines.
-
Programs can be copied from UNIX to Windows and from Windows to UNIX.
-
Windows and UNIX programs cannot be copied to an IBM i system.
-
The source and destination product lines must be the same release version.
-
Source and target can be on the same machine but must be in different environments.
-
The user performing the copy process must have security privileges to run the metadump and metaload utilities.
There are two types of files needed to transfer a program to another product line: source code files and metadata files.
Source code files are located in %LAWDIR%\productLine\systemCodesrc.
| This section provides an overview of the copy process. These are the processes Program source code file | Description |
|---|---|
|
programcodePD |
Contains the procedure source code. |
|
programcodeWS |
Contains the working storage source code. |
|
programcode.scr |
Contains the screen definition source code. |
|
programcode.rpt |
Contains the report definition source code. |
| programcode.cfg | For report programs, this file provides optional configuration parameters for printing. For online programs, this file provides a way to set up data record caching. |
Metadata files are located in %LAWDIR%\productLine\metadata\systemCodemeta.
| Program metadata file | Description |
|---|---|
| Program code metadata | This is the program definition created through pgmdef. Programs cannot have a "Run Type" of 'Prototyped' if they are to be copied to another product line. |
| Work file metadata | You can determine if a program includes work files by using workdef. |
| Message metadata | This metadata defines the messages contained in msgmnt for the program. |
| Menu metadata | This data is maintained in menudef. Batch programs have one *.mnu file. Online programs have a *.mnu file for each of screen. |