|
Booth,
I noticed that you have /QSY.LIB instead of /QSYS.LIB. Is that a typo in the actual file, or just this e-mail? It could be the cause.
Also, you are using the older Order/Allow/Deny syntax here. Please check to be sure you are using this throughout the file. (If you use the newer syntax in some places, you should use it throughout.)
If neither of these help, please look at the error_log.xxxxx file. It will explain the cause of the 403 error. It generally will either be an issue with your conf file (bad alias, or failure to allow permission to that area) or else an authority error accessing the program. But, the log file will tell you specifically what it is.
-SK
On 9/25/2018 3:46 PM, Booth Martin wrote:
?? First, I saw no responses...? No idea why not.
Here is what I added at the end of the config file:
....
ScriptAlias /states /QSY.LIB/DVABRMD.LIB/STWEBSRVCR.PGM
<Directory /QSYS.LIB/DVABRMD.LIB>
Order Allow,Deny
Allow From All
</Directory>
I edited the authority for QTMHHTTP to have *all authority on DVABRMD. Same 403 failure message.
http://(IP address)/states
On 9/25/2018 3:16 PM, Bradley Stone wrote:
On Tue, Sep 25, 2018 at 2:48 PM Booth Martin<booth@xxxxxxxxxxxx> wrote:
(Asked onweb400@xxxxxxxxxxxx with no response. r affiliate link:Ah.. now that hurts, Booth.;) I see Kevin echoed my questions. I'd keep
http://amzn.to/2dEadiD
it on Web400 though.
Bradley "Nobody" Stone
www.bvstools.com
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.