SQL/MX 2.x Messages Manual (H06.04+)

Utility Messages (20000 through 23099)
HP NonStop SQL/MX Messages Manual—540498-003
17-92
Effect. The MODIFY operation fails.
Recovery. None. Contact your service provider.
SQL 20731
Cause. The MODIFY command includes a COMMIT BEFORE timestamp clause,
and the MODIFY processing did not reach commit phase before the specified
timestamp. Note that the timestamp is checked at two points during processing: at
the time the MODIFY command is first parsed and again when MODIFY is ready to
begin commit phase.
Effect. The MODIFY operation fails.
Recovery. If the timestamp check failed at the beginning of the commit phase,
perform a RECOVER command to undo partial processing. Then, retry the MODIFY
operation with a timestamp sufficiently in the future.
SQL 20732
Cause. The MODIFY command includes a COMMIT AFTER timestamp clause, and
the timestamp specifies a time that is more than 30 days in the future.
Effect. The MODIFY operation fails.
Recovery. Correct the COMMIT AFTER clause to use a time within 30 days of the
present, and resubmit.
SQL 20734
Where error number is the returned file system number.
Cause. When processing COMMIT BEFORE or COMMIT AFTER clauses, the
MODIFY command encountered an error number from the CONVERTTIMESTAMP
Guardian procedure when converting the current time to local civil time.
Effect. The MODIFY operation fails.
Recovery. See the Guardian Procedure Calls Reference Manual topic
CONVERTTIMESTAMP Procedure for the meaning of error number and possible
recovery actions.
20731 The time given in the BEFORE clause has already passed.
20732 The time given in the AFTER clause is more than 30 days
in the future.
20734 Error error number was returned by CONVERTTIMESTAMP
while trying to obtain local civil time.