ASAP 3.0 Client Manual

HP NonStop ASAP Client Manual Page 156 of 161
Example
HP developers must be able to define system entities in one EDL file, perhaps named
AsapSys.
Users must be able to define application entities in EDL files of your own, perhaps one
of which is named AsapApp.
Using this approach, INCLUDE statements let you modify application entity definitions
in AsapApp, and lets development organizations contain their system entity definitions
in AsapSys, without either group having to edit files belonging to the other.
These notions can be extended to include third parties.
Files can be brought together via wrapper EDL files:
$System.System.AsapEDL:
INCLUDE AsapSys;
INCLUDE AsapApp;
Include - Spanning Considerations
Two restrictions relate to INCLUDE statements:
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";