|
One problem we had with this was the QPGMR user profile that is
used during IPL did not have group authority to the SSA user
profile that owned all of the BPCS objects.
Tony Kleier
Robbins Inc.
akleier@robbinsfloor.com
|--------+----------------------->
| | <BPCS-L@midra|
| | nge.com> AT |
| | INTERNET-MAIL|
| | |
| | 12/28/1999 |
| | 08:58 AM |
| | |
|--------+----------------------->
>-----------------------------------------------------------|
| |
| To: "'BPCS Users'" <BPCS-L@midrange.com> AT |
| INTERNET-MAIL@ccMail |
| cc: (bcc: Anthony C Kleier/ROBBINSINC) |
| Subject: NEWI Daemon & IPLing |
>-----------------------------------------------------------|
I had put the following message on the Midrange e-mail list
Friday morning but forgot to also put it on the BPCS e-mail
list. Well, here it is.
<SNIP>
To all,
We are running BPCS 6.0.02, full C/S, Mar'98 cum, on an IBM S20
running V4R2M0. Since putting the Nov 17, 1997 BPCS cum on, I
have not been able to get one daemon to start up automatically
ONLY after IPLing my machine. Before installing this cum, I
could submit the job & all was fine. Since then I have to
start this one daemon manually after the IPL. Actually, I get
a CPF error that reminds me to start the daemon & I actually
don't remember what the CPF message number is. I worked with
one of the SSA help line people just to get the code below to
work for this daemon but never bothered to ask about the IPL
problem. We run 24/7 so IPLing is not something that happens
as often as it probably should & I kind of forget about the
problem - more of a nuisance than a problem.
The kicker is this. Since installing an IBM 720 test/dev
machine running V4R4M0 & copying all of BPCS to it, I do not
have to start this daemon manually after IPLing. What is
different between V4R2M0 & V4R4M0 (I suppose a lot & that makes
the question kind of dumb to ask) that would make this one
daemon behave differently? And is there something that I can
do to my production machine to fix my problem?
Both machines use the exact same CL to start BPCS and the
daemons it requires. I stop BPCS from running every night for
a backup & this same CL runs okay on the production machine.
It's okay for me but there just might come the day when I'm not
here when an IPL is performed (it's written down but will
somebody remember) & find out that BPCS won't work because one
of the daemons has not been started.
The following is part of the code from my CL program starting
BPCS:
/* Start TCP/IP Running
*/
STRTCP STRSVR(*YES) STRIFC(*YES)
MONMSG MSGID(TCP1A04)
DLYJOB DLY(300)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/* Set Up System To Start The BPCS's NEWI Daemon
*/
ADDLIBLE LIB(NEWILIB)
MONMSG MSGID(CPF2103)
/* This Was For Pre-Cum 11/17
*/
/* SBMJOB CMD(CALL PGM(NWID) PARM('9007')) +
*/
/* JOBD(NEWILIB/NWIJOBD)
*/
/* This Is For Cum 11/17
*/
NEWILIB/STRNWID PORT(9007)
JOBD(NEWILIB/NWIJOBD)
MONMSG MSGID(CPF3CF1)
RMVLIBLE LIB(NEWILIB)
MONMSG MSGID(CPF2104)
<SNIP>
Again, the kicker is that this daemon will not start up
automatically after an IPL but it works every night when BPCS
is stopped for a backup. Also, the same exact CL program runs
in both situations.
Anybody have a clue as to why? I will be changing my
production system to V4R4M0 sometime in the next two months so
the question is more for other people with the same problem
(are there any?????).
Thanks for any insight.
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
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.