Re: NEWI Daemon & IPLing

That one is easy and very well documented on OGS Online. In the April 
cumulative instructions it mentions you need to have authority to this 
object, and to one other (which escapes me at this moment - it is listed on 
OGS if you search for the object QSYGETPH, you will find some entries that 
list both.) 

You need to use a user profile which has authority to these objects when 
starting the daemon, plus which also has authority to the other user profiles 
on your system. That is because the daemon uses these AS/400 APIs to swap the 
daemon user profile with the user profile who is logging into BPCS as the 
user signs in. The authorities are checked when the daemon starts up. Check 
the user profile that your start up job is running under (generally QPGMR), 
and either give it *ALLOBJ or give it specific authority to those objects, 
and make sure it has authority to the user profiles who will sign into BPCS. 
Or, as many people do to avoid giving QPGMR too much authority, start TCP/IP 
in your startup program, use a DLYJOB of about 5-10 minutes as suggested by 
Phil in a prior note, and then do a separate STRSBS command to start up your 
BPCS subsystem. Make the daemon startup CL program an autostart job entry in 
your BPCS subsystem. When doing the autostart entry, run that job using a 
user profile that you create specifically for this purpose. Give that user 
profile *ALLOBJ authority, and make it's password *NONE so that users may not 
sign onto the system with that user ID. 
That should resolve your problems. 

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---