|
Charles,
I actually have job accounting running, not sure if 100% accurate.
If all user profiles were set correctly, that would ensure interactive
jobs.
Not sure how to handle system jobs QZDASSINIT, QZHQSSRV, etc. that are
servicing that application.
Other question is can you setup job accounting to have sub groups.
I'm not sure if this could be done accurately, because the same user
profile could run a job from different groups
BRC Interfaces
BRC Order Entry
BRC Payments
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Wednesday, May 21, 2014 8:33 AM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries Message Monitoring, auto actions, and pager (email)
notifications
If you mean can different jobs have different accounting codes, then sure.
IIRC, the job accounting code get's its initial value from the user
profile and/or job description.
But it can be changed within a job using Change Accounting Code
(CHGACGCDE) command
Look here
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzaks/rzaksmanagejobaccounting.htm
Charles
On Tue, May 20, 2014 at 9:59 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx
wrote:
Charles,for.
Implementing multiple monitors, with different filters, resulting in
different actions based on 1st digit of userprofile.
Bytware support has been excellent.
I'm still looking for something, possibly Job Accounting, to group
jobs by application.
Below are the 4 options for filters.
Can Job Accounting have sub categories?
I've never worked with job accounting.
Job . . . . . . . . . . *ALL
User . . . . . . . . . CVG*
Program . . . . . . . . *ALL
Accounting code . . . . *ALL
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt via MIDRANGE-L
Sent: Friday, May 16, 2014 12:26 PM
To: Midrange Systems Technical Discussion
Subject: Re: iSeries Message Monitoring, auto actions, and pager
(email) notifications
You can define multiple monitors with different include/exclude
filters so that you can page different groups.
Assuming you've got support, Bytware should be able to help you get
what you want.
Charles
On Fri, May 16, 2014 at 12:00 PM, Steinmetz, Paul via MIDRANGE-L <
midrange-l@xxxxxxxxxxxx> wrote:
I currently use MPLUS for monitoring, for the most part all ok.
However, my manager no longer wants everyone to get all the alerts.
(I have one group, contains manager, admin, 2 operators, and 4
programmers, total of 8) My thought is to still allow all messages
to go to the group, using the MPLUS monitor default pager.
For those messages that should NOT go to the entire group, I will
either send individual pages or create new groups as needed (Groups
are preferred, sending to individuals is frowned upon).
We run multiple 3rd party apps, manager would like only the messages
for that app to go to the programmers for that app.
The problem is you can't configure the same message monitor to go to
different pagers based on something??.
At this point I'm looking at userprofile to determine who should get
the message, but this may not work.
I wish could see the V7R2 monitoring capabilities, I'm wondering
how much could be done with V7R2 base that I'm currently using MPLUS
http://archive.midrange.com/midrange-l.I'm also entertaining other solutions.--
Any thoughts from the group?
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
--
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 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
--
--
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 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 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
