Re: qpgmr auth for qstrup to start http

Mine starts up just fine.  Out httpd.conf file has *PUBLIC *NONE and
QTMHTTP and *R.  QPGMR is user class *PGMR and has special authorities
*JOBCTL & *SAVSYS.

We do have HTTP set to auto-start in CHGHTTPA in addition to the entries
in QSTRUP; perhaps the autostart is what gets the job done.


John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Jim Franz
Sent: Thursday, September 21, 2006 3:45 PM
To: WEB400@xxxxxxxxxxxx
Subject: [WEB400] qpgmr auth for qstrup to start http

Continueing my saga - starting the http server is failing for an
authority halt on file www/xxxx/conf/httpd.conf
The QSTRUP pgm has STRTCPSVR   *HTTP   XXXX
I do not want profile QPGMR to have *allobj (or is this how everyone
does this?), 

The odd thing is I have this working on one machine, but not another. 
Both at V5R3 same cume & groups.
Have checked auth on www/ and it's directories and all have same auth. 
Have been down the checklist in Info Center chapter for User profiles
and required authorities for HTTP server. 

jim franz
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To
post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.



This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in the future then please respond to the sender to this effect.