HP 3000 Manuals HP 3000 Manuals
Execute Messages (1750-1799)
1750 MESSAGE Both ENTITY and RELATIONSHIP keywords cannot be specified (SDERR
1750)
CAUSE As the underlying report is either a REPORT ENTITY or a REPORT
RELATIONSHIP, only one of the ENTITY/RELATIONSHIP keywords can
be specified.
ACTION Reissue the command deleting the unneeded keyword clause.
--------------------------------------------------------------------------------------
1751 MESSAGE Could NOT retrieve the report named ! (SDERR 1751)
CAUSE Cannot retrieve the specified report.
ACTION Refer to the associated error and correct the indicated problem.
--------------------------------------------------------------------------------------
1752 MESSAGE A ! command cannot be issued after a REPORT command (SDERR 1752)
CAUSE The specified command (CONFIGURE or FORMAT) cannot be placed
after the REPORT command in a stored report.
ACTION Use the EDIT REPORT command to move the indicated command to
before the REPORT command (or to delete it completely if there
is already one before the REPORT command).
--------------------------------------------------------------------------------------
1753 MESSAGE Cannot issue two ! commands (SDERR 1753)
CAUSE Two of the specified commands (CONFIGURE, FORMAT, or REPORT) are
not allowed in the same stored report.
ACTION Use the EDIT REPORT command to delete one of the indicated
commands.
--------------------------------------------------------------------------------------
1754 MESSAGE ! is an invalid command in a stored report (SDERR 1754)
CAUSE The specified command is invalid in a stored report.
ACTION Use the EDIT REPORT command to remove the invalid command.
--------------------------------------------------------------------------------------
1755 MESSAGE The keyword is incompatible with the report type (SDERR 1755)
CAUSE Either the ENTITY keyword is specified and the stored command is
a REPORT RELATIONSHIP or the RELATIONSHIP keyword is specified
and the stored command is a REPORT ENTITY.
ACTION Reissue the command with the keyword corresponding to the stored
command.
1756 MESSAGE Source and indicated entity-types do not match for report !
(SDERR 1756)
CAUSE The entity type of the REPORT command and the entity type
specified by the SOURCE-POSITION keyword are not the same.
ACTION Revise the REPORT command so that the specified source entity
type matches the entity type of the REPORT command.
--------------------------------------------------------------------------------------
1757 MESSAGE SOURCE-POSITION required as is > 1 match for report ! (SDERR
1757)
CAUSE There are two or more possible position matches for the source
entity so the SOURCE-POSITION keyword must be specified.
ACTION Reissue the command with the SOURCE-POSITION keyword specified.
--------------------------------------------------------------------------------------
1758 MESSAGE Source entity-type is NOT in the relationship-type for report !
(SDERR 1758)
CAUSE The RELATIONSHIP-TYPE to be followed does not involve the source
ENTITY-TYPE.
ACTION Revise the relationship type to be followed so that it involves
the source entity type.
--------------------------------------------------------------------------------------
1759 MESSAGE REPORT-POSITION required as > 2 entity-types for report !
(SDERR 1759)
CAUSE A 3-way (or more) relationship is being followed to the nested
report. Accordingly, the REPORT-POSITION keyword is required.
ACTION Reissue the command with the REPORT-POSITION keyword added.
--------------------------------------------------------------------------------------
1760 MESSAGE Error while retrieving entities for report ! (SDERR 1760)
CAUSE Encountered an error while retrieving the entities to be used
for the nested report.
ACTION Refer to the associated error and correct the problem indicated.
--------------------------------------------------------------------------------------
1761 MESSAGE Illegal REPORT-POSITION value given for report ! (SDERR 1761)
CAUSE The REPORT-POSITION specified in the indicated report is not
legal (there is no such position in the relationship type to
follow).
ACTION Change the REPORT-POSITION to a value that is present in the
relationship to be followed.
1762 MESSAGE Stored and indicated entity-types don't match for report !
(SDERR 1762)
CAUSE The entity types in the REPORT command and the stored report do
not match.
ACTION Revise the REPORT command so the entity types match or specify a
different stored report with the correct entity type (create one
if needed).
--------------------------------------------------------------------------------------
1763 MESSAGE Error found in stored report ! (SDERR 1763)
CAUSE An error was encountered while processing the indicated report.
ACTION Refer to the associated error and correct the indicated problem.
--------------------------------------------------------------------------------------
1764 MESSAGE Report and Source position cannot be the same for report !
(SDERR 1764)
CAUSE The same position was specified for both SOURCE-POSITION and
REPORT-POSITION.
ACTION Reissue the report with the position values updated so they are
not both the same.
--------------------------------------------------------------------------------------
1765 MESSAGE The stored report must be a REPORT ENTITY (SDERR 1765)
CAUSE For nested EXECUTEs, the stored report must be a REPORT ENTITY
while in this case it is a REPORT RELATIONSHIP.
ACTION Change the report chained to so that the chained report is a
REPORT ENTITY.