I am attempting to run an SQL script from RDi (Database Development Perspective) that uses an INSERT INTO. I get the following error message:
MYFILE in MYLIB not valid for operation.. SQLCODE=-7008, SQLSTATE=55019, DRIVER=4.18.60
After researching this error, it seems very likely that my SQL statement is not running as COMMIT = *NONE. I confirmed that I can successfully execute this statement using RUNSQLSTM COMMIT(*NONE) from a command line. When I change the COMMIT option to COMMIT(*CHG) it fails for the same reason as listed above.
I tried adding an optional parameter to my Data Source connection property for autocommit = false, but this did not seem to help.
Any ideas how I can get execute an SQL statement from the RDi Database Development perspective when it contains an INSERT INTO?
MYFILE in MYLIB not valid for operation.. SQLCODE=-7008, SQLSTATE=55019, DRIVER=4.18.60
After researching this error, it seems very likely that my SQL statement is not running as COMMIT = *NONE. I confirmed that I can successfully execute this statement using RUNSQLSTM COMMIT(*NONE) from a command line. When I change the COMMIT option to COMMIT(*CHG) it fails for the same reason as listed above.
I tried adding an optional parameter to my Data Source connection property for autocommit = false, but this did not seem to help.
Any ideas how I can get execute an SQL statement from the RDi Database Development perspective when it contains an INSERT INTO?
Comment