Long Transaction with Logging OFF ???

We have a database with logging turned off (read-only system). In an ESQL-C program, we are executing a very large open cursor statement (reading 10's of millions of rows and returning 10's of thousands). When we execute the program we get a -458 (long transaction cancelled). My understanding is that with logging turned off for a database that this kind of thing should not happen !?!?!? Why is it filling up the log ??? What can I do (increasing the size of the logs is not desireable since that seems like a 'band-aid' type of solution) ??? I tried changing LTXHWM and LTXEHWM to 95 and 98 % and that allowed it to run longer, but it still bit the dust. tia, Bill =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ /*** / ***\\ Hewlett-Packard Company / \\ / Colorado Springs ITC /* / \\ /**\\ /***\\ / \\/ \\ Phone: TN/(719) 590-3402 / \\ \\ Fax: " " 590-3596 / Bill Border \\ \\ EMail: border@cs.itc.hp.com / MVS Technical Support Mailstop: C103G