The command has several forms, and the last section in this topic gives reference details for any form.
If you are using a command file, use the following form of the EGLCMD command:

The following examples assume that you are starting java EGLCMD in the directory that includes the command file:
java EGLCMD "commandfile.xml"
java EGLCMD "myCommand.xml"
-sqlID myID -sqlPassword myPW
-destUserID myUserID -destPassword myPass
java EGLCMD "/MyProject/MyCommands/Command1.xml" -data "c:\myWorkSpace"
java EGLCMD "/MyProject/MyCommands/Command1.xml"
-data "myWorkSpace"
-sqlID myID -sqlPassword myPW
-destUserID myUserID -destPassword myPass
Place the content for a given command on a single line. If your command file is in another directory, you must add the path to the command file name.
If you are generating a main part and its associates and are not using a command file, use the generate subcommand:

Here is an example, which belongs on a single line:
java EGLCMD generate
-generateFile "/MyProject/EGLSource/my/pkg/myProg.egl"
-data "myWorkSpace"
-buildDescriptorFile "/MyProject/EGLSource/myProject.eglbld"
-buildDescriptorName myBuildDescriptor
If you are generating by part and are not using a command file, use the generatePart subcommand:

java EGLCMD generatePart
-data "myWorkSpace"
-project "MyProject"
-part "test.my.pkg.program1"
-buildDescriptorFile "/MyProject/EGLSource/myProject.eglbld"
-buildDescriptorName myBuildDescriptor
java EGLSDK generatePart
-data "myWorkSpace"
-project "MyProject"
-part "test.my.pkg.*"
-buildDescriptorFile "c:/myBuild.eglbld"
-buildDescriptorName myBuildDescriptor
java EGLCMD generatePart
-data "myWorkSpace"
-project "MyProject"
-part "MyRecords.myRecord"
-buildDescriptorFile "/MyProject/EGLSource/myProject.eglbld"
-buildDescriptorName myBuildDescriptor
If you are deploying output and are not using a command file, use the deploy subcommand:

java EGLCMD deploy
-data "myWorkSpace"
-deployDescriptorFile "/MyProject/EGLSource/myDeploy.egldd"
Do not specify an asterisk (*) in place of a file name because, if you do, only the alphabetically first deployment descriptor is processed, and the command ends with an error.
Here are additional details, in alphabetical order:
A build descriptor option that you specify when invoking the EGLCMD command takes precedence over the same build descriptor option in the build descriptor (if any) that is referenced in the EGL command file. The options that are only in the EGLCMD command or only in the build descriptor are also in effect at generation time.
Embed the path in double quotation marks.
If you do not specify this value, the EGL generator searches for the master build descriptor.
If you do not specify this value, the EGL generator searches for the master build descriptor.
Please note that debugging information is never included in the generated output, even if you specify a debug build descriptor.
/MyProject/MyCommands/Command1.xml
Embed the path in double quotation marks.
The command file must be in your workspace before you run the EGLCMD command. If the command file is not in the workspace, use the Eclipse import process to import the file and then rerun the EGLCMD command.
If you do not specify a value, the command accesses the Eclipse default workspace.
Embed the path in double quotation marks.
Embed the path in double quotation marks. You can specify either the name of the file or an asterisk (*), which represents all EGL deployment descriptors in the path.
Embed the path in double quotation marks.
The symbolic parameters that you specify when invoking the EGLCMD command take precedence over the same-named symbolic parameters in the build descriptor (if any) that is referenced in the EGL command file. The parameters that are only in the EGLCMD command or only in the build descriptor are also in effect at generation time.