• Subject: RE: Alert job owner of QSYSOPR message?
  • From: Walden Leverich <walden@xxxxxxxxxxxxxxx>
  • Date: Thu, 2 Jul 1998 08:37:56 -0400

Rob,

Nice program. I'd make just two comments.

1) Can you post SNDMSGGRP? This looks like a cool command to have. I
assume it sends the message text to a list of people identified as a
"group" maintained in some database somewhere. Cool.

2) It won't affect you here, because the user space is small, but on
large user spaces always initialize the userspace to x'00' unless you
NEED another initial value. OS/400 always creates the user space with an
initial value of x'00' and then changes every byte if you use a initial
value other than x'00'. I just tried it on a 620 and the blank
initialize took 14 seconds and the x'00' was subsecond on a 15 meg
userspace.

-Walden

-----Original Message-----
From: Rob Berendt [mailto:rob@dekko.com]
Sent: Tuesday, June 30, 1998 2:11 PM
To: MIDRANGE-L@midrange.com
Subject: RE: Alert job owner of QSYSOPR message?


I have another job that monitors subsystem QBATCH on a routine basis and
every 15 minutes it sends a message out to a select group of people for
each job that is stuck.  You could probably modify this to suit your
needs.
 There is some other stuff in there about certain jobs not running that
should be that you could trash if you want to.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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 [javascript protected email address].