HP 3000 Manuals HP 3000 Manuals
Nested EXECUTE
Executes a secondary REPORT ENTITY command that has been previously
created and stored by using a START/SAVE pair. You can only call this
command format from the SUB-REPORT keyword of the REPORT ENTITY command.
Note that no selection criteria is allowed for this reporting command.
Syntax
EX[ECUTE] report-name
;R[ELATIONSHIP-]T[YPE] = entity-type-name1
,entity-type-name2
[,entity-type-name3]
[,entity-type-name4]
[,entity-type-name5]
[,entity-type-name6]
[;R[ELATIONSHIP-]C[LASS] = relation-class-name]
[;S[OURCE-]P[OSITION] = source-position]
[;R[EPORT-]P[OSITION] = report-position]
.
Parameters
report-name Name of the stored report to be executed.
entity-type-name(N) Name of the entity type involved in the
relationship type.
relation-class-name Name of the relationship class.
source-position An integer (from 1 to 6) that specifies the
position in the RELATIONSHIP-TYPE list of the
entity type being reported in the primary report.
The entity type indicated must match the value
specified for ENTITY-TYPE in the primary REPORT
command.
The value defaults to the matching entity type
(specified in the REPORT ENTITY command) if the
type appears only one time in the list. If the
entity type appears more than once in the list, you
must enter a value to indicate the one desired.
report-position An integer (from 1 to 6) that specifies the
position in the RELATIONSHIP-TYPE list of the
entity type to be reported in the secondary report.
The entity type indicated must match the value
specified for ENTITY-TYPE in the secondary (stored)
REPORT command.
If the relationship type is binary (2-way), the
default is to the entity type that is not chosen as
the match for the source entity type. However,
for all relationships that are not binary
relationships, you must supply a value to indicate
which entity type is the desired report entity
type.
Description
This command allows you to retrieve data about an entity and then, by
following relationships in the dictionary, report on related entities.
Open Mode: Read-only, shared-update, or exclusive-update
Scope: DA scope or any scope that has read access to the data
being reported
Example
The following report consists of the attribute values of the
image-database sales and all the image-datasets that are related to it.
The image-database contains image-dataset relationship type is specified
as the path to be used to find the image-dataset that is associated to
the image-database sales. Note that neither SOURCE-POSITION nor
REPORT-POSITION are needed as the source entity type is unambiguous and
the specified relationship type is a binary one, respectively.
>REPORT ENTITY sales;
>>ENTITY-TYPE = image-database;
>>SUB-REPORT = (EXECUTE image-dataset-report;
>> RELATIONSHIP-TYPE = image-database,
>> image-dataset;
>> RELATIONSHIP-CLASS = contains.).
SALES
DATE-CREATED : 11/11/84 4:23 AM
DATE-CHANGED : 11/24/84 5:02 PM
SCOPE-OWNER : DA
SCOPE-CHANGED : DA
SENSITIVITY : PRIVATE
ID-NUMBER : 0
IMAGE-DATABASE-TYPE : IMAGE
2) CUSTOMERS
Entity-Type : IMAGE-DATASET
DATE-CREATED : 11/11/84 4:23 AM
DATE-CHANGED : 11/11/84 4:23 AM
SCOPE-OWNER : DA
SCOPE-CHANGED : DA
SENSITIVITY : PRIVATE
ID-NUMBER : 0
IMAGE-DATASET-TYPE : MANUAL
2) SUPPLIERS
Entity-Type : IMAGE-DATASET
DATE-CREATED : 11/11/84 4:23 AM
DATE-CHANGED : 11/11/84 4:23 AM
SCOPE-OWNER : DA
SCOPE-CHANGED : DA
SENSITIVITY : PRIVATE
ID-NUMBER : 0
IMAGE-DATASET-TYPE : MANUAL
2) ORDERS
Entity-Type : IMAGE-DATASET
DATE-CREATED : 11/11/84 4:23 AM
DATE-CHANGED : 11/11/84 4:23 AM
SCOPE-OWNER : DA
SCOPE-CHANGED : DA
SENSITIVITY : PRIVATE
ID-NUMBER : 0
IMAGE-DATASET-TYPE : DETAIL
2) STOCK
Entity-Type : IMAGE-DATASET
DATE-CREATED : 11/11/84 4:23 AM
DATE-CHANGED : 11/11/84 4:23 AM
SCOPE-OWNER : DA
SCOPE-CHANGED : DA
SENSITIVITY : PRIVATE
ID-NUMBER : 0
IMAGE-DATASET-TYPE : DETAIL
1 Entity(ies) Retrieved
>