RE: Monitor JobQs and OutQs -- MIDRANGE-L

I strongly discourage attempting to use spool files to convert into output 
files and then process that.  I've been burned too many times by IBM 
reformatting spool files with each new version.  Right after a new version 
is not a time to have to scramble to fix all the stuff that uses spool 
files.

For example, I used to use DSPSYSSTS OUTPUT(*PRINT) and then CPYSPLF that 
to a disk file.  But they kept shifting around the % system asp used.  And 
changing the U/M from MB to GB.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Jones, John \(US\)" <John.Jones@xxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/11/2005 02:11 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Monitor JobQs and OutQs






I did something like this. 

Mine looks at jobs in all active job queues (held queues are ignored),
CPU % busy, and concurrent interactive users.  It uses CL to gen the
splfs and parse them and a little QSH to gen the stats and net.data to
display them in a window.  The stats refresh automatically as does the
web page window.  The web page's title contains the info as well so even
if I can't see the window the current stats are in my task bar.

Really, it's not hard at all, is free, and uses a trivial amount of
resources.  Send me an email off-list and I can send you my (ugly)
source code.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Colin Williams
Sent: Wednesday, May 11, 2005 11:17 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Monitor JobQs and OutQs

Scott,

Do you need to spend any money on this? 

Just grow your own at home using the output from WRKOUTQ OUTQ(*ALL)
OUTPUT(*PRINT) and WRKJOBQ JOBQ(*ALL) OUTPUT(*PRINT).

You could probably do them both in an afternoon

cheers
Colin.W
 
http://as400blog.blogspot.com


-----Original Message-----
From: Scott Johnson [mailto:sjohnson@xxxxxxxxxxxxxxx]
Sent: 11 May 2005 17:11
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: Monitor JobQs and OutQs



We would like to monitor the number of jobs in JobQs and spools in
OutQs.
For 
JobQs we want to know if the number of jobs in a certain JobQ goes over
a 
specified number of jobs waiting to run. For OutQs it is a matter of if
the 
number of spools just keeps going up and does not go down.  I took a
quick
look 
at the Monitors in OpsNav, but did not see anything that would give me
what
I 
was hoping for.

So, does anybody have suggestions on vendors, software, and/or
utilities.
The 
cheaper the better.

Thanks,
    Scott J


-- 
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.

This e-mail has been sent by a company of Bertram Group Ltd, whose
registered office is 1 Broadland Business Park, Norwich, NR7 0WF. 
This message, and any attachments, are intended solely for the addressee
and may contain privileged or confidential information.  If you are not
the intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited and
may be unlawful.  If you believe that you have received this email in
error, please contact the sender immediately. Opinions, conclusions and
statements of intent in this e-mail are those of the sender and will not
bind a Bertram Group Ltd company unless confirmed in writing by a
director independently of this message. 
Although we have taken steps to ensure that this email and any
attachments are free from any virus, we advise that in keeping with good
computing practice the recipient should ensure they are actually virus
free.

-- 
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.




This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and 
then delete it.  If you are not the intended recipient, you must not keep, 
use, disclose, copy or distribute this email without the author's prior 
permission.  We have taken precautions to minimize the risk of 
transmitting software viruses, but we advise you to carry out your own 
virus checks on any attachment to this message.  We cannot accept 
liability for any loss or damage caused by software viruses.  The 
information contained in this communication may be confidential and may be 
subject to the attorney-client privilege. If you are the intended 
recipient and you do not wish to receive similar electronic messages from 
us in the future then please respond to the sender to this effect.

-- 
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.