Based on your prestart settings, you can then schedule to capture how many you’re processing at intervals with this command (automate in a CLP, etc.):
DSPACTPJ SBS(QUSRWRK) PGM(QZDASOINIT) OUTPUT(*PRINT)
You may need to do DSPACTPJ SBS(QUSRWRK) PGM(QZDASOINIT) and take option F13 to reset your statistics.
You can then trend your data of peaks and valleys vs. DSPLOG.
Just a thought.
----- Original Message -----
From: "Mike Cunningham" <mike.cunningham@xxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, June 14, 2011 9:04:35 AM
Subject: RE: QZDASOINIT start/stop logging
Did that already. That will show a log of connections made but does not tell me when there were insufficient QZDASOINIT jobs to service a request and more needed to start and see of that need to start more correlates with when a user reports they can't get connected
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, June 14, 2011 8:35 AM
To: Midrange Systems Technical Discussion
Subject: Re: QZDASOINIT start/stop logging
This mailing list archive is Copyright 1997-2019 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