installationDir\egl\eclipse\plugins\ com.ibm.etools.egl.utilities_version\ dtd\eglcommands_5_1.dtd
The following table shows the elements and attributes supported by the DTD. The element and attribute names are case sensitive.
Element | Attribute | Attribute value |
---|---|---|
EGLCOMMANDS (required) | eglpath | As described in eglpath, the eglpath attribute identifies directories to search when EGL uses an import statement to resolve the name of a part. The attribute is optional and if present, references a quoted string that has one or more directory names, each separated from the next by a semicolon. The attribute is used only if the command EGLSDK is referencing the command file. If the command EGLCMD is in use, the value of eglpath is ignored; instead, import statements are resolved in accordance with the EGL project path, as described in Import. |
buildDescriptor (optional; you can avoid specifying this value if you are using a master build descriptor, as described in Build descriptor part) | name | The name of a build descriptor part that guides generation.
The build descriptor must be at the top level of an EGL build (.eglbld) file. Build descriptor options that you specify when invoking EGLCMD or EGLSDK take precedence over options in the build descriptor (if any) that is listed in the EGL command file. |
file | The absolute or relative path of the EGL file that contains
the build descriptor. Relative paths specified for EGLCMD are relative to
the path name of the Enterprise Developer workspace. Relative paths specified
for EGLSDK are relative to the directory in which you run the command. The path must be in double quotes if the path includes a space. |
|
generate (optional) | file | The absolute or relative path of the EGL file that contains
the part you want to process. Relative paths specified for EGLCMD are relative
to the path name of the Enterprise Developer workspace. Relative paths specified
for EGLSDK are relative to the directory in which you run the command. The path must be in double quotes if the path includes a space. If you omit the file attribute, no generation occurs. |
This section shows two command files. The results produced by either file are the same whether you use the EGLCMD command or the EGLSDK command, if you run the EGLSDK command in the directory where the EGL source files reside.
The following command file contains a generate command that uses the build descriptor myBDescPart to generate the program myProgram.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE EGLCOMMANDS PUBLIC "-//IBM//DTD EGLCOMMANDS 5.1//EN" ""> <EGLCOMMANDS eglpath="C:\mydata\entdev\workspace\projectinteract"> <generate file="projectinteract\myProgram.eglpgm"> <buildDescriptor name="myBDescPart" file="projectinteract\mybdesc.eglbld"/> </generate> </EGLCOMMANDS>
The next example contains two generate commands, both of which implicitly use a master build descriptor.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE EGLCOMMANDS PUBLIC "-//IBM//DTD EGLCOMMANDS 5.1//EN" ""> <EGLCOMMANDS eglpath="C:\mydata\entdev\workspace\projecttrade"> <generate file="projecttrade\program2.eglpgm"/> <generate file="projecttrade\program3.eglpgm"/> </EGLCOMMANDS>
Related concepts
Build descriptor part
Generation from the EGL Software Development Kit (SDK)
Generation from the workbench batch interface
Import
Related tasks
Generating from the EGL Software Development Kit (SDK)
Generating from the workbench batch interface
Generating in the workbench
Related reference
EGLCMD
EGL command file
EGL build path and eglpath
EGLSDK