Re: Logging when child-server jobs start and end -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Logging when child-server jobs start and end
From: rob@xxxxxxxxx
Date: Fri, 3 Jun 2011 09:03:21 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Some good suggestions are flowing in. Keep in mind, that, when you do an
ENDSBS *ALL *IMMED just how many calls, etc, do you expect to be allowed
to happen by watches, etc when the client server jobs? I suspect little
to none.

Then again, if someone's downtime processes include this:
ENDSBS *ALL *IMMED
wait on QSYSOPR
change qhstlogsiz to minimum
delete qhst* files
You may end up losing some information also.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 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.