× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: NEWI Daemon & IPLing - Update
  • From: "Genyphyr Novak" <novakg@xxxxxxxx>
  • Date: Mon, 17 Jan 2000 10:32:26 -0600


-----Original Message-----
From: Dennis Munro <DMunro@badgerminingcorp.com>
To: 'BPCS Users' <BPCS-L@midrange.com>
Date: Sunday, January 16, 2000 11:37 AM
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
>
Hi Dennis,

There are several reasons this could be happening - the fact is that if you
have Newi version 2.2.65 (which is the version that the March 6002 cume
contained), then this authority is required. How you go about giving it out
is another question - there are many ways to grant this.

1. What authority does the profile who starts the job have on each system?
Is it possible you gave your V4R4 QPGMR more authority, such as *ALLOBJ?

2. Are the Newi versions the same on both systems (do some DSPPGM to compare
source dates).

3. If the user profile which starts the jobs does not have *ALLOBJ
authority, check the objects themselves (QSYGETPH and QWTSETP) to see if
they were made PUBLIC *USE or PUBLIC *CHANGE, in which case this would also
would have gotten around the problem for you, and would not require specific
authority to be set.
4. Do you have an authorization list set up on the 2 objects which is
granting authority to the profile which is starting this up?

There should be no difference in the way the operating system works, unless
those system objects were delivered with a different authority level on the
new release to begin with. However I checked our V4R4 system and the
authority that is required for PUBLIC on these 2 objects has not changed
with OS release level.

Thanks

Genyphyr Novak
SSA


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


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.