Re: V4R4M0 & NEWI problems

We are currently running backups off of GO SAVE which has an option to END 
*ALL networks, but before we start our Save, we ENDSBS *ALL.  This approach 
is taken because we have consultants who dial in on the ECS line, we just 
installed an external ethernet LAN, and a few users have PC ANYWHERE & other 
ways of dialing in to their office PCs from home.  I want to lock all of them 
out of BPCS during the backup, then control who can get in after it, if I am 
running dedicated BPCS tasks.

>  From: Dennis Munro <DMunro@badgerminingcorp.com>
>  
>  We are running ver.6.0.02plf, c/s, Mar'98 cum on an AS/400 model S20 with
>  dual processors, V4R4M0, & all the latest cum, database, hiper, y2k,
>  performance tools, & client access ptf's.
>  
>  As part of our "day end" process, I bring down IP as a means of keeping
>  people from being logged on while I do a backup of the system & BPCSF data
>  library.
>  
>  Since going from V4R2M0 to V4R4M0 this last weekend, I have been having
>  trouble with my production machine.  I was baby sitting it last night & was
>  able to determine that when I shut down TCP/IP, the NEWI daemons "peg" both
>  processors & the IP shut down takes about 1 hour and 45 minutes to end.
>  Looking at the job log, all I see is a blank time gap from 23:16:57 to
>  00:57:23 when nothing is logged.  When I start my "day end", I change the
>  job attributes to LOG(4 00 *SECLVL) LOGCLPGM(*YES).  What I did last night
>  after seeing the processors peg was to WRKACTJOB SBS(SUBSYSN) and kill the
>  two NEWI jobs that had the system running at over 100% utilized.  As soon 
as
>  I did that, the rest of my day end process continued normally.  Is there a
>  "better way" to stop all the daemons running?
>  
>  These same programs (BPCS & "day end" ) run on my test box (a single
>  processor 720) running the same software & ptf levels & it woks just fine.
>  Obviously, there is a difference someplace - but where.
>  
>  I wrote all these programs about 2 ½  years ago when we first started with
>  BPCS & IP.  Being a novice to both at the time, the way I chose to do it 
was
>  stop IP.  But I also stop the BPCS subsystem.  We do have a major VB
>  application that gets at the BPCS data & the only way I have to lock them
>  out is to bring down IP.

Al Macintyre  ©¿©
http://www.cen-elec.com MIS Manager Programmer & Computer Janitor
405 CD mixed mode V4R3
+---
| 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
+---