Try replacing your READ's with READL's, or using TRANS(). In order to
preserve the integrity of the transaction, Universe requires certain
lock levels to be used within SQL transactions. If I remember
correctly, both READL and TRANS will work, as will SQL selects.
Jeff Marcos wrote:
Hi all,
We're experimenting with the Uni JDBC software and have come across an
issue.
***************
java.sql.SQLException: Program "CREATE.MP.LOG": Line 36, FATAL: The
locks necessary for database operations at the current isolation level
(2) are not held by this process.
***************
The program mentioned (in the error) is initiated via a file index. We
were just trying to write to a file (using Java & JDBC) which contains
an index, that calls a program CREATE.MP.LOG. The program works fine in
basic code both interactively and phantoms.
The program contains OPEN's, READ's and initialisation of variables in a
common block. I believe the line in question is an OPEN statement. Its
difficulty to tell due to a high number of includes in the code. Line 36
doesn't necessarily mean line 36. Line 36 refers to (via VLIST) a
complete section of code in the include.
Universe Version : 10.1.14
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
