ASAP 3.0 Client Manual

HP NonStop ASAP Client Manual Page 157 of 161
INCLUDE Asap2App;
INCLUDE Asap2Sys;
INCLUDE $SYSTEM.SYSTEM.ASAPEDL;
INCLUDE Asap2App;
INCLUDE Asap2Sys;
When filename is partially qualified, the default path or subvolume for that file is the
same as the path or subvolume of the parent file that included the INCLUDE
statement. For example, if a file $SYSTEM.SYSTEM.ASAPEDL contains INCLUDE
statements with simple file names, those INCLUDE files have a default subvolume of
$SYSTEM.SYSTEM, which is the same as the parent EDL file name.
INCLUDE $SYSTEM.SYSTEM.ASAPEDL;
INCLUDE Asap2Sys;
INCLUDE Asap2App;
Path or subvolume inheritance lets related INCLUDE files be grouped or moved
together without embedding fully qualified file names.
File Names With Special Characters, or Embedded Blanks
If a filename includes special characters or blanks, it must be enclosed in double
quotes. For example: INCLUDE "C:\My Projects\ASAP\EDL\Asap2 Factory";
Included EDL file names do not have to have the .EDL extension in the INCLUDE
statement.
File Names Limited to 40 Characters
An include filename is limited to a total of 40 characters in length.
Statement Termination
INCLUDE statements, like any other EDL statements, must be terminated with a
semicolon.
This example shows how to use the INCLUDE statement to distribute entity definitions
across multiple files:
$System.System.AsapEDL:
INCLUDE AsapSys;
INCLUDE AsapApp;
$System.System.AsapSys:
INCLUDE AsapCpu;
INCLUDE AsapDisk;
INCLUDE AsapExpand;
$System.System.AsapApp: