Re: QZDASOINIT and Persistent Programs

Good point.  However I wonder about the implementation.  Let's say, for 
performance sake, that his SQLRPGLE stored procedure doesn't normally set 
on LR.  Now, he's getting ready to put in a new version.  Then he would 
have to have every client call the stored procedure with a special option 
that says shut 'er down.  I would see that would be a bit hairy to 
implement.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Mike_Bramley@xxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/10/2004 04:02 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: QZDASOINIT and Persistent Programs







ref:
"We've found that if we change the stored procedure (SQLRPGLE program) on
the AS/400, the VB programs don't seem to pick up on it right away. They
seem to keep using the old version -- maybe until a system IPL, maybe
until the Domino server reboots"

if these jobs behave like conventional jobs.
can you change the stored procedures to recognise an instruction to  'do
end of program processing (seton *INLR)  and exit (return)'?
Then pass that instruction when you want to end the active invocation of
the old stored procedure. Then the next time the stored procedure is 
called
the new version will be picked up.

Regards
Mike





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