Re: Monitoring for MSGW -- MIDRANGE-L

20yrs of experience

vs.

1yr of experience 20 times...

Charles

On Fri, Sep 23, 2016 at 10:51 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

Folks,

Get over this fascination with outputting to spool files and converting
the spool files to a disk file and then processing that.
Crack open a book, STFW, something. Learning something new won't kill
you.
Think "API".

Problems with the spool file to disk file concept:
- processor and disk I/O inefficient.
- details are much more limited on spool files vs what is available via
the APIs
- jobs blow up when you reach max spool file entries per job.
- And the biggest reason? Read the Memo to User for ANY release and you
will see:
Output(*PRINT) changes
Release to release Output(*PRINT) considerations
Applications specifying OUTPUT(*PRINT) to generate spooled output from
commands must be able to
tolerate changes to the record layout in the spooled file. From release to
release, commands that support
that option can add, change, or remove records from the output. Any
application that has a dependency
on the record layout for a specific command might have to change.

I've had print format changes bite me in the butt when supporting multiple
releases and long ago stopped doing this.

Ok, with me coming unglued let me say this. In 15 minutes I am taking off
early for the day. This half day of "vacation" will find me:
- helping set up a going away party at my MIL for her son who is taking a
distant position for ministering
- helping with a concession stand for Unified Track. A team composed of
boys and girls with mental challenges and partners from general education.
Last time I helped them involved me going to the regional burn center.
- helping with a concession stand for football boosters
- football game
- getting there late to the camporee for boy scouts.

I'll feel better next week. Out.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: Kurt Anderson <Kurt.Anderson@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/23/2016 10:36 AM
Subject: RE: Monitoring for MSGW
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Hi Paul,

Mike Wills has some code on github for looking for MSGW jobs. It does so
by generating a spool file of all active jobs and parsing the file.
https://gist.github.com/MikeWills/8549554

I took this approach, though heavily modified it. Our system will send an
email out to the appropriate people and will send an email every 12 hours
if the MSGW isn't addressed.

This method does generate a TON of FIN spool files which will eventually
cause the program to error. In this case I monitor for that error and
have the job resubmit itself if that condition is met.

Kurt Anderson
Lead iSeries Developer - Application Development, Service Delivery
Platform

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Paul Bailey
Sent: Thursday, September 22, 2016 9:43 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Monitoring for MSGW

Hi,

I've been tasked with finding a way to notify relevant people the moment
when *any* job goes into the MSGW status. The notification has to tell
those people which job is in the MSGW status, when it entered that status
and what the MSGID is (I also don't want to spam them with
notifications!).
I am not interested in notifying anyone about jobs in the QSPL subsystem,
but apart from that I want notification for any batch or interactive job
on the local machine requiring a user's response to a message.

I've put together a small routine that loops forever using the QUSLJOB API
which works (thanks to Eric Pell), but I'd prefer a different approach
because continuously reading the job list over and over just seems like an
awkward way to do what I want. Is there a way to have a program called (or
dtaq/file added to) when any job in the system goes into the MSGW status?
Trigger, or exit point, etc?

Any tips, ideas, web searches I may have missed?

-Paul.

PS Eric Pell's code, an adjustment to code from "jamief", can be found
here:
http://www.code400.com/forum/forum/tips-techniques-tools-
announcements/tips-for-the-iseries-as400/1227-use-the-
qusljob-api-to-whip-thru-wrkactjob?p=51441#post51441

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.