ultra
usage: ultra export <target-jar-file> | import <source-jar-file> |list [-v, --verbose] [-h --historic-only]
When you make changes to an ultra format, historic formats a stored on the system. However, these are not included when you perform a system export. You can use the ultra
command to export both current and historic ultra formats from one system and import them as historic formats in another. This is useful when the target system must be able to handle e g persisted runtime data that is consistent with a previous version of an Ultra format.
Option | Description |
---|---|
[ -v --verbose ] | Use this option for detailed output from the |
[ -h --historic-only ] | Use this option to only include historic formats in the export. This option is not applicable for the |
export
Use the export
 command to write Ultra formats on the system to disk. These will be stored in a JAR file that contains the Ultra class definitions.Â
Example - Exporting Ultra formats
mzsh <username>/<password> ultra export /home/user/mz/ultra/ultraexport.jar
Note!
The export command cannot overwrite an existing export file.
Import
Use the import
command to import Ultra formats from disk. For each Ultra format (class) in the specified JAR file, the command will perform the import if the format is not already present in the Code Server. If a format in the JAR file is historic or not does not matter during import, since it will be considered historic in the target system.
List
Use the list
 command to list Ultra formats on the system.
Return Codes
Listed below are the different return codes for the ultra
command:
Code | Description |
---|---|
0 | Will be returned if the command was successful. |
1 | Will be returned if the command could not be interpreted, e g if a option that does not exist has been entered. |
2 | Will be returned if the input file is not found or if the output file already exists. |
Â