RE: Ending TCP/IP, FTP jobs in QSYSWRK

Jim,

I have been doing a nice shutdown of all my IP services and host servers 
before ending all subsystems for *MANY_MOONS now.  You are right on the mark, 
the more complicated your environment is, the more important to implement 
this.

Since doing this I have not had something hang or had problems restarting 
services after an ENDSBS *ALL *IMMED.  Good luck!

Regards,

Mike Shaw

  
> QTFTPxxxxx jobs are set to logging level 4 0 *NOLIST, and they generate 2
> page job logs.
> 
> I'm surprised that ENDSBS *ALL *IMMED, which is supposed to end all jobs
> *IMMED as well, causes jobs to hang out for so long.  I suppose these SAVE
> menu programs are just "serving suggestions", and we're supposed to RTFM to
> work out the real steps for our particular environments.  QMNSRBND does seem
> like a neat piece of code, but I wonder if IBM really endorses ENDSBS *ALL
> *IMMED alone for bringing down the system in complex environments.  For
> example, we bring down Domino gracefully before going to ENDSBS.
> 
> I'll be taking Sean's advice.
> 
> Much thanks to all.
> 
> -Jim
> 
> -----Original Message-----
> From: Jim Franz [mailto:franz400@xxxxxxxxxxxx]
> Sent: Monday, November 24, 2003 4:00 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Ending TCP/IP, FTP jobs in QSYSWRK
> 
> 
> Are you by any chance getting extremely large job logs on these jobs?
> jim
> 
> 
> >              Jim Damato
> > We're not running SAVE menu option 21.  We've set up custom procedures so
> > that we can break up the SAVLIB *NONSYS portion of the full save and split
> > it out to three 3590's.  We execute ENDSBS *ALL *IMMED then the operators
> > wait for the restricted state before continuing on with various SAV*
> > commands.  According to QHST these QTFTPxxxxx jobs take 25 - 90 minutes to
> > end.
> >
> > I'm not sure what you're saying.  Would repeated ENDSBS *ALL *IMMED
> > commands
> > bring down the jobs in QSYSWRK any faster than the single execution we're
> > performing?
> >
> > -Jim
> >
> 
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>