Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1554
  • Last Modified:

iSeries Journal Receiver Monitoring

I have a passing knowledge of CL and some of the journal-related commands on the IBM iSeries machines.  We are using V6R1.  My assignment is to find a way to measure how long journal receivers are lasting before they are filled and closed.  If entries are filling the receivers too quickly, we may have a runaway job, which we need to kill and investigate.

Can I run some combination of queries, workfiles, data areas and system commands in a CL program to do the following?

1) Get the output for WRKOBJ OBJ(*ALL/TPS*) OBJTYPE(*JRNRCV) into a workfile.
2) Loop through those objects and pass the receiver numbers to DSPJRNRCVA JRNRCV([number from workfile]).
3) Save the receiver number, attach date and time and detatch date and time to another workfile.

The commands I have looked at so far do not all allow *OUTFILE output, so with my limited abilities I can't even say if this technique is possible.  Thanks in advance for any assistance.
0
Alan Varga
Asked:
Alan Varga
  • 2
  • 2
1 Solution
 
stevebowdoinOwnerCommented:
Here is what I believe.  I have not proven it.
If you have the system manage your journal receivers, it will CHGJRN from time to time.  If you have a “run-a-way” job, this may happen frequently.

There is an exit point for CHGJRN “QIBM_QJO_CHG_JRNRCV”.  You can find it with WRKREGINF.  You could write a CLP and add it as an exit program via an 8 then a 1.

See https://pic.dhe.ibm.com/infocenter/iseries/v6r1m0/topic/apis_web/jc.pdf page 160.

You may want to have your exit program send a message or an email (SNDDST) every time a journal changes.

If you elect to continue on the path you are on, use:
DSPOBJD OBJ(journallib/*ALL)              
        OBJTYPE(*JRNRCV)          
        OUTPUT(*OUTFILE)          
        OUTFILE(yourworklib/yourworkfile)

This will create a PF you can read to check how many and the creation dates of the receivers.

The exit program method is by far cooler.

Steve
0
 
Gary PattersonVP Technology / Senior Consultant Commented:
Steve's exactly right - use the QIBM_QJO_CHG_JRNRCV exit point.  Your exit program will get called automatically whenever a receiver is detached for any reason and will be passed the journal receiver name and the time it was detached.    You then just grab the receiver's creation date, for example in CL, use RTVOBJD CRTDATE().

Now you know how fast the receiver filled and can make your notification decision based on whatever criteria you like.

http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_61/apis/xchgrcv.htm

Points to Steve, please - I'm just agreeing with him since he was a little tentative.
0
 
Alan VargaAccess DeveloperAuthor Commented:
Thanks guys!  I will defer using the exit point until phase 2, but to get up and running quickly the DSPOBJD command gives me exactly what we're looking for.

I can create a CLP to run hourly which will replace a workfile, then run a query and display the results showing the open, close and lifespan of journals.  If the timespans are too short and too many journals are being created, that will be the indicator of trouble we are looking for.

The query is as simple as:
select  ODOBNM,
        ODCDAT,
        ODCTIM,
        ODLDAT,
        ODLTIM
from SUPPORT.AVJRN
where ODOBNM like 'TPSRCV%'

Open in new window

Alan
0
 
Alan VargaAccess DeveloperAuthor Commented:
I appreciate having a couple of options to address my situation.  I've used EE for a wide range of PC-software and -hardware issues, but this is the first time I've asked a question for a mainframe.  I will certainly tap this valuable knowledge again.

Thanks again to both posters!
0
 
Gary PattersonVP Technology / Senior Consultant Commented:
Not that it matters much, but AS/400 / iSeries / Power is not a mainframe.  Same severs are used to run Linux and AIX. We used to call them "midrange systems".  Now we pretty much just call them servers.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now