David,

Which user profile are you using from the PSDS?  The one located at position
254-263 or the one at position 358-367?  The one at 358 is the current user
profile and I believe it is the one you want.  Maybe it has QTMHHTP1 when
your program gets called.  I'm not totally clear on this but it seems like
the value at position 254 doesn't always reflect the current profile when a
job has performed a switch.  If you already useing the value at positon 358
then nevermind.

Scott Mildenberger

> -----Original Message-----
> From: David Gibbs [mailto:david@midrange.com]
> Sent: Thursday, January 16, 2003 1:16 PM
> To: web400@midrange.com
> Subject: [WEB400] Re: V4R5 Apache -- "Internal Server Error"
> 
> 
> "David Gibbs" <david=Zwy7GipZuJhWk0Htik3J/w@public.gmane.org> wrote in
> message news:5.2.0.9.2.20021229124527.031327f8@linux.midrange.com...
> > The programs seem to run OK ... except every other request 
> that is sent I
> > get a error 500 "Internal Server Error -- Cannot read script output
> pipe.".
> 
> Ok, I worked with IBM support on this a bit and I think we've 
> figured out
> what is happening.... although I'm kind of distressed about the cause.
> 
> My CGI program switches user handles so it can operate as the 
> authenticated
> user.  Here's the basic logic ...
> 
> 1. Program starts, user profile is QTMHHTTP
> 2. Retrieve current user from the PSDS and save it.
> 3. Switch to the user profile identified in the REMOTE_USER 
> environment
> variable.
> 4. Do work
> 5. Switch back to the saved user profile (QTMHHTTP)
> 
> This, however, does not work properly ... something about the 
> QTMHHTTP user
> not having the necessary authority to do a recv.  If, on the 
> other hand, we
> switch back to QTMHHTP1 instead ... our program works.
> 

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.