sysdump - Export System Definition
sysdump [-iemrupv] productline dumpfile [systemcode...]
Copy existing system definitions to a flat file, making it possible to import them to another product line.
The export function dumps information about the product line and creates a flat file that you can either load to a new product line or use to overwrite an existing product line. This utility delivers system definitions for a product line.
This utility is not suitable for creating a new product line or copying over an existing product line if you want that product line to be updatable with patches. For information on how to copy a product line that can be updated, see the "Product Line Copying" section of the Lawson Administration: Server Setup and Maintenance guide.
Program Option | Description |
---|---|
-i
|
Internal delivery. |
-e
|
Includes all element definitions in the product line, even if system code(s) are specified. |
-m
|
IBM Midrange. |
-r
|
Report Writer. |
-u
|
Lawson Environment. |
-p
|
Dump PGMCALL records. (The default is no PGMCALL records.) |
-n
|
Do not dump system key number records (the default is to dump them). |
-V
|
Display current dump version. |
At the command line, specify the information above.
- or -
-
From the Database Administration menu, choose Database Definition Export/Import.
-
From the Database Definition Export/Import menu, choose Export System Definition.
-
Specify or select the following data.
- Program Options
- Specify the letter of the system you want to export. Only the definitions owned by the specified system code(s) are dumped.
- Product Line
- The product line you want to export.
- Dump File Name
- The name of the file you want to dump to.
- System Code(s)
- System codes you want to export definitions for. Dumps all definitions owned by or
referenced by the specified system code(s). When used with the
-i
option, only the definitions owned by system code(s) are dumped.
-
Press Enter.
Note: Date, time, username, type, utility name and key field activities of this utility are logged in the %LAWDIR%\system\secadmin.log file.