BPCS question -- MIDRANGE-L

I am in this AM putting ptf's on my production system because no one else is
working & I am killing some time between IPL's.

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 machine 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 the code from my CL program starting BPCS:

/* 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)

Well, have a happy holidays to all on this list.  It is a learning
experience to be a part of this e-mail list.  

I hope to be out of here in a hour or so.  I have the cum, database, client
access, & Y2K ptf's to install.  The cum is done & took almost 2 hours to
finish.  The others are smaller & should not be as time consuming.

Thanks to all for your suggestions.

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 Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---