Re: Commit in DB2/MVS

[John Sayre <John_Sayre@GAP.COM>]

John Sayre@GAPINC
10/01/98 02:22 PM
We do commits inside loops with DB2 regularly. If we don't save the values
where we are
    (let $oldempl=&emplid   for example)
   the cursor is closed and restarts at the top, processing the same rows
it just did. Forever.


There is a DB2 option 'With Hold' that you issue when you declare the
cursors which keeps you at the same row
when the cursor is reopened.





Please respond to SQR-USERS@USA.NET

To:   Multiple recipients of list SQR-USERS <SQR-USERS@list.iex.net>
cc:    (bcc: John Sayre/SB/GAPINC)
Subject:  Commit in DB2/MVS




Any help would be greatly appreciated.

I am using DB2 version 4 and SQR version 4 on windows NT and MVS
mainframe.
I have an sqr program that issues a commit after x number of records are
processed.
When I run it on the NT/Client it runs ok, when I run it on the MVS
server it abends after the commit is executed.  The commit is actually
working, but it seems to blow up on a select after the commit.   The
program runs ok on MVS with the 'commit' commented out.  This is a
conversion program that will load a large volume of data and needs to do
a commit periodically.

Has anyone else run into this???


DSN      ENDED DUE TO ERROR+
 SYSTEM ABEND CODE 04E   REASON CODE 00E7000C  PSW 077C100087713180
ASIDS:  HOME
1LSCX041 **** ERROR ****
         ABEND occurred in line  1020 of    SQ043(SQ048)  ,offset 000390

         Program terminated by operating system. ABEND code = S04E
         A non-C or system routine was running at the time of ABEND