ASAP 2.8 Client Manual

Entity Definition Language (EDL)
HP NonStop ASAP Client Manual—425263-004
6-30
EDL - DATA Statement
Default: NULL
Example
AT TranCount METRICRULE "#1"
STATEPAIR YES STATERULE UseStateGraphState
TYPEDATA REAL64;
AT TranRate METRICRULE "#1/S" FORMAT F10.2
STATEPAIR YES STATERULE UseStateGraphState
TYPEDATA REAL64;
EDL - DATA Statement
The EDL includes a DATA statement that facilitates entity prototyping, testing, and
demonstration. The DATA statement lets you associate data with an entity declaration.
The DATA statement lets availability, statistics, and performance information be
included as part of the EDL source file for an entity. DATA statements can be
automatically generated along with entity definitions when the FILE… EXPORT EDL
function is selected from the ASAP Browse window. This capability is useful for saving
the environment, as well as prototyping what if scenarios. The DATA statement lets any
type of data be imported into the ASAP Client.
The layout of the DATA statement syntax is a what-you-see-is-what-you-get
composition that mirrors the desired result:
DATA entity-name
heading1 heading2 heading3 ...
-------- -------- --------
\col1dat col2data col3data ...
\col1dat col2data col3data ...
...
..
; -- semicolon terminates statement
Considerations
•
Each record after the DATA statement is stored in the ASAP object cache for the
entity specified as entity-name.
•
The DATA statement must be terminated with a semicolon after the first record that
does not begin with a backslash.
•
Column widths are determined by the number of dashes in the heading for each
column.
•
Data record attribute properties must align with the corresponding dashes
character underlining headings. Data records represent the contents of attribute
data columns. If columns are not aligned, data is truncated to fit under the column
definitions.