RE: QZDASOINIT and Persistent Programs

Mike,

It sounds like your VB program is running in an activation group that
doesn't get reclaimed.  Since the QZDASOINIT jobs are running in QSERVER
I take it they are batch interactive jobs (BCI).  If you start the
subsystem where QZDASOINIT is defined as a pre-start job you can control
the number of uses a job has.  Starting subsystem QUSRWRK or QSYSWRK
will make QZDASOINIT jobs prestart jobs.

Before starting the subsystem though you will want to change the number
of uses for the prestart jobs.  Use command CHGPJE to change the
pre-start job's settings.

        CHGPJE SBS(subsystemName) +
      PGM(QSYS/QZDASOINIT)      +
      USER(*SAME)               + 
      STRJOBS(*SAME)            +
      INLJOBS(NumberYouThinkIsProper)  +
      TRESHOLD(NumberYouThinkIsProper) +
      ADLJOBS(NumberYouThinkIsProper)  +
      MAXJOBS(NumberYouThinkIsProper)  +
      JOB(*SAME)    +
      JOBD(*SAME)   +
      MAXUSES(1)    +
      WAIT(*SAME)   +
      POOLID(*SAME) +
      CLS(*SAME *SAME *SAME *SAME)

-----Original Message-----
From: midrange-l-bounces+gary.monnier=powertech.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+gary.monnier=powertech.com@xxxxxxxxxxxx] On
Behalf Of Michael Naughton
Sent: Thursday, September 09, 2004 6:10 PM
To: Midrange Systems Technical Discussion
Subject: QZDASOINIT and Persistent Programs


Hi everyone,

I'm having trouble coming up with a catchy description of this problem,
so
here's the scenario:

We have a VB and Lotus Domino programs that call stored procedures on
our
AS/400. The jobs (QZDASOINIT) run in QSERVER with the user name of the
DSN
we're using for the ODBC connection.

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 (we don't do this very often, and
everything is in production, so it's a little hard to run extensive
tests).

Has anyone else experience with this? Is there a way to stop this from
happening (i.e. to recompile the program the program on the AS/400 and
have the stored procedure recognize it [maybe use UPDPGM instead?]). In
the spirit of RTFM, I'd be  happy to, if someone could point me to where
the FM might be found. . . . :-)

Thanks very much for any help

Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@xxxxxxxxxxxx

--
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.