RE: SQL vs V5R1 and service woes

["Alexei Pytel" <pytel@xxxxxxxxxx>]

I think changing library list is a clue.
SQL might be using an old ODP cached from a previous invocation and lands
into wrong library.
You might experiment with CLOSQLCSR parameter in SQL precompiler command.

    Alexei Pytel

"No one can beat unbeatable"





                    rob@dekko.com
                    Sent by:                  To:     midrange-l@midrange.com
                    midrange-l-admin@mi       cc:
                    drange.com                Subject:     RE: SQL vs V5R1 and 
service woes


                    09/11/2001 03:39 PM
                    Please respond to
                    midrange-l






Latest on this issue.

First of all, this is a multi program application.  One program uses SQL to
read a field in this file (VDLINE) to determine which division makes that
part.  It uses a GROUP BY the division field.  Then it takes this division
number, bounces it against a CL program which does a ADDLIBLE of that
divisions particular file library.  (Later the appropriate RMVLIBLE is
done).  Then it calls a SQLRPGLE program to post from the VD* files into
the PL* files.  Calling these last two programs once for each division
found in the first program.
Works on V4R5.
Works great on the first round.
Fails on succeeding rounds.  The failure is deemed to be because of how
imbedded SQL, under V5R1, fails to properly handle the new libraries.
Something about QDT and/or ODP.

Currently we got bounced back from Consult line to Support Line.  Oh well,
Support line is starting to see the light...


Rob Berendt

==================
If we can't stop, let alone get justice for, the destruction of a US
warship (the Cole),
how we going to handle the events of Sept 11, 2001?

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.