ASAP 2.8 Client Manual

Entity Definition Language (EDL)
HP NonStop ASAP Client Manual—425263-004
6-31
EDL - INCLUDE Statement
Applies to: Client
Default: Null
Example
DATA CPU
Node Num Cpu Stats Op Dateymd Time CpuType Et Bsy QL Disp
-------- --- --- ----- -- ---------- ----- ------- --- --- -- ----
\CENTDIV 051 00 Up 2 1999/12/21 20:48 K10000 1 3 0 51
\CENTDIV 051 01 Up 2 1999/12/21 20:48 K10000 1 5 0 97
\CHITOWN 153 00 Up 2 1999/12/21 20:47 K1000 1 3 0 22
\CHITOWN 153 01 Up 2 1999/12/21 20:47 K1000 1 2 0 19
\WINE 242 00 Up 2 1999/12/21 20:48 K1000 1 2 0 18
\WINE 242 01 Up 2 1999/12/21 20:48 K1000 1 1 0 8
\DOME 245 00 Up 2 1999/12/21 20:48 S70000 1 2 0 158
\DOME 245 01 Up 2 1999/12/21 20:48 S70000 1 1 0 57
\ISLAND 249 01 Up 2 1999/12/21 20:47 K2000 1 2 0 22
\ISLAND 249 02 Up 2 1999/12/21 20:47 K2000 1 1 0 12
\ISLAND 249 03 Up 2 1999/12/21 20:47 K2000 1 0 0 3
;
EDL - INCLUDE Statement
The INCLUDE statement lets you include multiple EDL files. This statement lets you
distribute EDL information across multiple files, thus letting you separate entity
definitions among various organizations and companies.
INCLUDE filename ;
Applies to: Client and Server
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: