ASAP 2.8 Client Manual

Entity Definition Language (EDL)
HP NonStop ASAP Client Manual—425263-004
6-32
EDL - INCLUDE Statement
Statement Spanning Restriction #1:
No single EDL statement can span multiple EDL files. You cannot begin a statement in
one file and complete it in another file. Any single EDL statement must be entirely
contained within a single EDL file.
Entity-Attribute Spanning Restriction #2:
No single Entity definition can span multiple EDL files. A specific Entity definition must
be entirely contained within a single file. This restriction refers not only to the Entity
statement but to all associated Attribute statements.
Thus both an Entity statement and all associated Attributes must be entirely contained
within one EDL file.
You cannot begin an entity definition in one file, and complete it in another file.
Include - Default Path/Subvol
The INCLUDE filename can either a fully qualified file name, or it can be a partially
qualified file name.
Examples
INCLUDE "C:\My Projects\ASAP\EDL\Asap2 Factory";
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";