|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Why not grant authority to these two objects to that IBM profile? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "David J. Smith" <dsmith@ais400.us> Sent by: web400-admin@midrange.com 12/19/2002 06:59 PM Please respond to web400 To: <web400@midrange.com> cc: Fax to: Subject: [WEB400] CGI and SQL Justin: I thought the same thing to be true, but on my system QTMHHTTP always seems to be the user ID executing the programs. That should not be an issue. The way our security is set up, no users have authority to any physical files. They have authority to programs and the programs in turn have authority to the files. In this case, the user QTMHHTTP has the authority to the program, its running and accessing other files, until it needs the system objects QSQRXLTR and QSQRLEX. For some reason the system is saying hey you have the program authority, but you can't run the SQL that's in the program. >This is kind of odd. I was under the impression that QTMHHTTP profile was >used to access web pages on the IFS and QTMHHTTP1 was the profile used to >execute the CGI programs. Does QTMHHTTP1 have authority to SLS? >Justin Houchin >Programmer and Web Developer >www.reliatek.com >justin@reliatek.com _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/web400 or email: WEB400-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
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.