M
Member 310024
Guest
I don't believe the answer to this question is as simple as it may appear.
I have a COBOL/DB2(IBM mainframe) program and the declare cursor returns +000. However the subsequent attempt to open that cursor,returns a +100. When I do a close cursor, the program aborts with a -501 error which of course means trying to close a cursor that isn't open. However, another thing is that I don't want the program to abort on the -501, I want it to just continue, but it's not the -501 that my question is really about, it's the +100 on the open that has me baffled. The explanations I have about +100 is that it referes to a fetch update delete or query of a table, but I'm doing an OPEN CURSOR when I get it. There is actually a record in the table that meets the SELECT statement in the DECLARE CURSOR (WITH HOLD) code, but should that even matter?
I have a COBOL/DB2(IBM mainframe) program and the declare cursor returns +000. However the subsequent attempt to open that cursor,returns a +100. When I do a close cursor, the program aborts with a -501 error which of course means trying to close a cursor that isn't open. However, another thing is that I don't want the program to abort on the -501, I want it to just continue, but it's not the -501 that my question is really about, it's the +100 on the open that has me baffled. The explanations I have about +100 is that it referes to a fetch update delete or query of a table, but I'm doing an OPEN CURSOR when I get it. There is actually a record in the table that meets the SELECT statement in the DECLARE CURSOR (WITH HOLD) code, but should that even matter?
