HP 3000 Manuals HP 3000 Manuals
HP ALLBASE/SQL Messages
HP ALLBASE/SQL can detect errors at the following times:
* During generation of SQL logic blocks.
* While you are using the developer application.
* While an HP ALLBASE/4GL application is being run.
HP ALLBASE/4GL can display two different types of messages related to SQL
applications. Errors can be detected directly by HP ALLBASE/SQL or by
the HP ALLBASE/4GL-HP ALLBASE/SQL interface. All errors detected by the
HP ALLBASE/4GL-HP ALLBASE/SQL interface have error numbers between 60 000
and 61 000.
HP ALLBASE/4GL displays all error messages, except those that are
detected at run time, in the message window on the current screen.
If HP ALLBASE/SQL detects an error at run time, HP ALLBASE/4GL places the
text of the error message in the communication area field *ERROR, and
places the error number plus 100 000 in the communication area field
*IOSTATUS.
If the SQL command that caused the error does not contain an optional
error command, the text of the error message is displayed on the screen.
In some cases, a single SQL statement may cause more than one error
message. Under these conditions, the first error message and error
number are loaded into *ERROR and *IOSTATUS respectively at the time of
error detection.
If the SQL command contains an optional error command, the error handling
logic can invoke the SQLEXPLAIN command in an SQL logic block to retrieve
the text and number of the next error. The SQLEXPLAIN command returns
the text of the error to the *ERROR communication area field, and the
error number to *IOSTATUS. (Note that you cannot specify a host variable
with the SQLEXPLAIN command in an SQL logic block.)
The SQLEXPLAIN command returns a null string after the last error has
been returned.
Subtract 100 000 from the HP ALLBASE/4GL error message number to
determine the HP ALLBASE/SQL error message number. Refer to the HP
ALLBASE/SQL Message Manual for the causes and suggested remedial actions
for HP ALLBASE/SQL error messages.
HP ALLBASE/4GL-HP ALLBASE/SQL Interface Error Messages
The HP ALLBASE/4GL-HP ALLBASE/SQL interface can display the following
error messages.
60000 This application has no SQL database specified.
Error type message. The application is attempting
to access an HP ALLBASE/SQL database, but no
database environment has been specified on the
administrator application definition screen.
60001 Connecting to SQL database '<database name>'
Information type message. HP ALLBASE/4GL displays
this message when an application first accesses an
HP ALLBASE/SQL database. Once the application has
connected successfully to the database, the
connection is retained until the user terminates
the application.
60010 Unable to access SQL message catalog.
Error type message. HP ALLBASE/4GL has not been
able to find or access the HP ALLBASE/SQL message
catalog.
60011 You have an SQL transaction open, continue(y/n)[n]?
Query type message. You have tried to invoke HP
ALLBASE/QUERY while an HP ALLBASE/SQL transaction
is still open. If you enter Y, HP ALLBASE/4GL will
display error number 60012 to determine whether you
wish to commit the SQL transaction. If you enter
N, HP ALLBASE/4GL will cancel the action and HP
ALLBASE/QUERY will not be invoked.
60012 Do you want to perform an SQL COMMIT WORK (y/n)[y]
Query type message. Enter Y to terminate and make
permanent all HP ALLBASE/SQL work since the
previous explicit or automatic BEGIN WORK. If you
enter N, all of this work will be rolled back.
60110 Data storage warning - end of file: <filename>
Warning type message. This message occurs when a
FILE *NEXT command encounters the end of file for
the active set retrieved by a SELECT command. If
the SELECT command does not retrieve any records,
the first FILE *NEXT command returns this error
condition.
60112 Data storage error - record has not been read for
file: <filename>
Error type message. You cannot use the FILE logic
command to delete a record, and you cannot use the
WHERE CURRENT OF clause in an SQL logic block,
unless you read a record to position the cursor.
60150 The requested file operation cannot be performed on
SQL select lists
Error type message. You cannot modify records or
insert records in SQL select lists.
60151 The requested FILE *DELETE <filename> operation is
out of sequence or cannot be performed at this time
Error type message. To delete a record with a FILE
*DELETE command, you must:
* Use a SELECT command in an SQL logic block
to open a cursor.
* Use a FILE *NEXT command to position the
cursor on the record to be deleted.
60152 The requested FILE *FIRST <filename> operation is
out of sequence or cannot be performed at this time
Error type message. This message may be displayed
while HP ALLBASE/4GL is reporting from an HP
ALLBASE/SQL database. The start of report function
must include a SELECT command in a SQL logic block
to open a cursor, but it should not include a FILE
*NEXT command. The report generator issues an
implicit FILE *FIRST command when it starts
creating the report. (Note that the FILE *FIRST
command is not permitted in HP ALLBASE/4GL logic
blocks.)
60153 The requested FILE *NEXT <filename> operation is
out of sequence or cannot be performed at this time
Error type message. You must use a SELECT command
in an SQL logic block to open a cursor before you
can use the FILE *NEXT command.
60997 HP ALLBASE/4GL internal error - invalid SQL
table/select list operation.
Error type message. This is an internal HP
ALLBASE/4GL error condition. It should be
documented and reported to HP.