Re: Embedded SQL inserts to wrong library

Interesting suggestion, Buck. I have been curious why this didn't
happen on the old server. However (and correct me if I'm wrong,
because I'm by no means an expert here), it doesn't seem to me like
this would be the case based on the results of the DSPJOB done by my
trigger. The job the trigger is being run in has the correct library
list and shows on the call stack the program containing the insert,
then QSQROUTE, QSQRUN3, QDBPUT, and finally the trigger program. This
makes me think everything is happening in the same job.

I may take your advice and see if anyone has anything to say on
WEB400; perhaps there are some special considerations in the CGI
environment.

Thanks,

Jacob Smallwood

On Wed, May 14, 2014 at 1:23 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 5/14/2014 11:47 AM, Jacob Smallwood wrote:

We call a CL program that accepts the client ID as a parameter, does a
CHGLIBL LIBL(QGPL QTEMP), then ADDLIBLE's the appropriate libraries.

I'm wondering if the CALL is running in a different job from the INSERT;
that is, the CALL properly sets the library list for JOB 111, but the
INSERT runs in job 222 and so is unaffected by that ADDLIBLE.

The point being that depending on the prior configuration, you may have
had fewer prestart jobs available, and as a result they might have been
reused more reliably. The new machine might have more prestart jobs,
and you may be ending up with two separate server jobs.

I myself don't usually handle library lists dynamically (like this). I
tie the library list to the user profile / job description. When the
caller authenticates as the test profile, it sees the test library list,
etc.

Further discussion might be better handled on the WEB400-L list because
the web folks may not have picked up on this as a web subject because of
the topic.

--buck
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.