RE: Ending TCP/IP, FTP jobs in QSYSWRK

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
>