Birgitta,

Have you tried using the QIBM_CGI_LIBRARY_LIST environment variable in your
HTTP configuration? It adds the specified library/libraries to the HTTP
server library list automatically, e.g.:

SetEnv QIBM_CGI_LIBRARY_LIST "SRVPGMLIB1:SRVPGMLIB2:MYLIB"

I do this a lot, so my CGI programs will always work even if *LIBL was
specified for the *SRVPGM.

Rory

On Fri, Aug 26, 2011 at 10:55 AM, Charles Wilt <charles.wilt@xxxxxxxxx>wrote:

Birgitta,

It's called "early binding" for a reason. :) A link to the service
program is created at bind time, and resolved to a physical address
when the calling program is activated. From the ILE concepts:

"When ILE program A is activated, the following takes place:
v The service programs are located by using an explicit library
name or by using the current library list. This option is controlled
by you at the time the programs and service programs are created."

It seems to me that the CGI jobs weren't restarted when the CGI and/or
service program was recreated. Given that for performance reasons,
CGI programs are likely to run in a named activation, I can easily
imagine that the CGI program had the address of the original service
program and thus the MCH3401.

HTH,
Charles


On Fri, Aug 26, 2011 at 1:15 PM, Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:
Hi,

someone can explain the following situation.

I had to compile a CGI Program that calls procedures from a service
program.
This service program is located in a different library.
The service program is also located in a binding directory that is used
for
compiling the CGI program (H-Specs)

Until now everything worked great.

Yesterday the program was compiled (without problems), but as soon as it
get
called from an web application I got an "Internal Serve Error".
After searching through all available logs, I found out an MCH3401
(Service
Program could not be found) was sent.
The program was recompiled last time around a week ago. A modification in
a
procedure in the service program was made after.
So I also recreated the service program, recreated my program ... and
still
got the same error.

The program could be called from a command line without problems, that
means
the service program was found.

After a long search I found out the service program within the binding
directory was not specified with Library *LIBL.
I changed it to the library in which the service program is located.
... recreated everything ... and everything worked great.

... Is the library information stored somewhere in the caller
(service-)program so it is found and activated directly??????

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training
them
and keeping them!"


--
This is the RPG programming on the IBM i / System i (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.


--
This is the RPG programming on the IBM i / System i (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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.