MVSFORUMS.com

[ironponygrl]

i'm working on a legacy mainframe system written in COBOL, CICS and Natural. I find many places in this old system where a cursor is opened then fetched into a working storage table and closed. Usually its not a lot of data, just like all the rows for a single individual. is there still a reason to do this kind of processing? doesnt scrollable cursors take care of any previous issues?

[kolusu]

ironponygrl,

If you are reading the data from the cursor and moving into a working storage table then I think it has to do with LOCKS and avoiding deadlocks. You probably are working with the uncommitted data in your working storage. If it is a batch process, I believe you quickly fetch the data from the table usually at midnight and then release the lock so that other applications or online systems can perform their updates.

Having said if you just want to read the uncommitted data, you can get around it by simply specifying WITH UR on the cursor.

[ironponygrl]

thanks K, I think that whats going on is just really old technique that can be accomplished in another way