Re: NEWI Daemon & IPLing - Update - DO NOT TRY IT -- BPCS-L

Hi Dennis,

What you say about the object authority change causing BPCS not to run is
simply NOT TRUE.

 You can change the authorities on those objects back to what you had them
this AM, and BPCS will work just fine. The reason BPCS was not running this
AM after your IPL is probably the following scenario:

1. Not only does the user that starts the daemon need authority to those 2
objects - it ALSO needs authority to each user profile who will use BPCS. I
doubt your QPGMR profile has sufficient authority overall to be the profile
to start the daemon. When you start the daemon manually - who runs it - not
QPGMR, right? Probably yourself, or someone who is copied from QSECOFR?

2. The daemon will unfortunately start up OK on 6002 if you have authority
to those two objects, even if you don't have enough authority to the user
profiles on the system who run BPCS. (OMS switches the daemon profile for
the user who is signing into BPCS, so there is no way around this authority
requirement).

3.The requirements for the OMS (Newi) daemon's authority are more fully
documented in the 6100 install instructions and in the 6004 July cumulative.
Likely it was not clearly documented in your install instructions because
6002 was, let's just say kindly - somewhat underdocumented in this area.

4. This is described in the Redbook as well, so you can certainly look at
chapters which describe OMS in the Redbook to become more clear on these
points.

5. Back to my original answer I posted on this subject. QPGMR and the
regular startup job QSTRUP is not the ideal vehicle to start this stuff,
unless you enjoy giving QPGMR *ALLOBJ authority (not a good thing to do!).

 Instead, use the startup to start TCP/IP. Put in a 5-10 minute delay. Then
start your BPCS subsystem. An autostart job in the BPCS subsystem should be
called to start your daemons and should be submitted by a user profile you
invent anew just for this purpose. Give it *ALLOBJ and give it Password
*NONE so that no one may hack with it.

6. I suggest you test this whole scenario on the weekend and get a normal
BPCS user profile and sign on and try it yourself too, rather than awaiting
the users to come in on the AM and not be able to get into BPCS.

If this does not help, I highly encourage you to open a Helpline call.
Thanks

Genyphyr Novak
SSA

-----Original Message-----
From: Dennis Munro <DMunro@badgerminingcorp.com>
To: 'BPCS-L@midrange.com' <BPCS-L@midrange.com>
Date: Monday, January 17, 2000 11:13 AM
Subject: RE: NEWI Daemon & IPLing - Update - DO NOT TRY IT


>To All, (BPCS 6.0.02, full C/S, Mar'98 cum, on an IBM S20
>running V4R2M0 for a production machine)
>
>After getting rolled out at 3:30 this morning because BPCS was not working,
>I take back what I did & said yesterday about  solving my IPLing problem &
>getting the NEWI daemon running automatically.  When I IPLed the system
>yesterday, I only checked to make sure the daemon was running & didn't even
>try BPCS to see if it would work - which didn't even cross my mind.
>
>Actually, IT MADE BPCS NOT WORK AT ALL!!!!!!!!
>
>After screwing around for a few hours this morning trying this & that, it
>finally made sense to undo the change I made to the QSYS/QSYGETPH object.
I
>just couldn't see what that would do to cause my problem so it was the last
>thing I tried.  I removed the *ALL authority from QPGMR for the
>QSYS/QSYGETPH object.   I then re-IPLed my machine, had the CL error occur
>(responded with an I) about QPGMR not having authority to the QSYS/QSYGETPH
>object, & started the NEWI daemon manually.
>
>Lo & behold, BPCS now works & I have people being productive today.
>
>So, whatever you do, DO NOT GIVE QPGMR *ALL AUTHORITY TO THE QSYS/QSYGETPH
>OBJECT.   IT WILL MAKE BPCS NOT FUNCTION!!!!
>
>So, I am back to raising the original question.  How do I get the NEWI
>daemon started AND have BPCS work???
>
>Anyone like to tackle the question????  I'm leaving my system alone.  When
I
>IPL, I just have to make sure the NEWI daemon gets started manually.  End
of
>screwing around.
>
>Dennis
>"One never notices what has been done; one can only see what remains to be
>done." -- Marie Curie
>"I love deadlines.  I especially like the whooshing sound they make as they
>go flying by."  Dilbert's Words Of Wisdom:
>
>Dennis Munro
>Badger Mining Corporation
>dmunro@badgerminingcorp.com <mailto:dmunro@badgerminingcorp.com>
>(920) 361-2388
>
>
> -----Original Message-----
> From: Dennis Munro [SMTP:DMunro@badgerminingcorp.com]
> Sent: Sunday, January 16, 2000 11:11 AM
> To: 'BPCS Users'
> Subject: NEWI Daemon & IPLing - Update
>
> To Genyphyr & Phil specifically & to the others on the list for your
>info,
>
> We are running BPCS 6.0.02, full C/S, Mar'98 cum, on an IBM S20
>running
> V4R2M0 for a production machine & an IBM 720 running V4R4M0 for a
>test/dev
> machine.
>
> I finally got in this weekend to IPL my V4R2M0 system after I gave
>QPGMR
> *ALL authority to the QSYS/QSYGETPH object.
>
> The IPL finally started the NEWI daemon - which it never has since
>putting
> on the Nov. 17, 1997 BPCS cum on.
>
> But I still am curious why I had to do this for V4R2M0 but not for
> V4R4M0???????
>
> V4R4M0 works just fine without the authority change.  Both machines
>have
> basically the same QSTRUP program and I have the same 300 second
>delay in
> the program immediately after starting up IP.
>
> V4R2M0 just needs the authority changed so the daemon will start.
>
> Dennis
>
> "One never notices what has been done; one can only see what remains
>to be
> done." -- Marie Curie
> "I love deadlines.  I especially like the whooshing sound they make
>as they
> go flying by."  Dilbert's Words Of Wisdom:
>
> Dennis Munro
> Badger Mining Corporation
> dmunro@badgerminingcorp.com <mailto:dmunro@badgerminingcorp.com>
> (920) 361-2388
>
> +---
> | 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
> +---
>+---
>| 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
>+---
>

+---
| 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
+---