|
Adrienne, If you have access to the source code that the jobs are running, it might be a lot simpler to call a custom module at start of job and also at job termination (both normal and any error condition). These modules can retrieve the data you require from the RTVJOBA command and write to your own customised log file. Downside is that you have to touch the source code of each job running that you want to track, but probably a lot easier than retrieving from QHST. Robin _____ From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Adrienne McConnon Sent: Monday June 19, 2006 14:11 To: cobol400-l@xxxxxxxxxxxx Subject: Re: [COBOL400-L] Best way to access QHST programatically Tom, I am relatively new to the iSeries and I appreciate your assstance. Thanks so much for your response. I noticed the documentation you directed me to was for V5R4 - we are still on V5R2 - does this make a difference? Also, all of our systems are batch-oriented, which is why I want to use the QHST log file - not the QHST queue. I want to simply start out accessing the QHST files and then selectively filtering messages based up[on job name, or rather partial job name. I am assuming I will need to first list and mergelog files to include logs for a few days. I want to retrieve and report all of the jobs that rean for client xxx (part of the job name) for the last 2 days and report the status of the job and maybe who submitted the job. I do not need to know the specifics of what the job entailed - more specifically whether it ran to completion successfully or not. Any comments, let me know - as I said I am new at this on the Iseries. Thanks, Adrienne -----Original Message----- From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of cobol400-l-request@xxxxxxxxxxxx Sent: Saturday, June 17, 2006 1:00 PM To: cobol400-l@xxxxxxxxxxxx Subject: COBOL400-L Digest, Vol 4, Issue 66 Send COBOL400-L mailing list submissions to cobol400-l@xxxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit http://lists.midrange.com/mailman/listinfo/cobol400-l or, via email, send a message with subject or body 'help' to cobol400-l-request@xxxxxxxxxxxx You can reach the person managing the list at cobol400-l-owner@xxxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of COBOL400-L digest..." Today's Topics: 1. Re: Best way to access QHST programatically (qsrvbas@xxxxxxxxxxxx) ---------------------------------------------------------------------- message: 1 date: Fri, 16 Jun 2006 19:13:28 -0400 from: qsrvbas@xxxxxxxxxxxx subject: Re: [COBOL400-L] Best way to access QHST programatically cobol400-l-request@xxxxxxxxxxxx wrote:
1. Best way to access QHST programatically (Adrienne McConnon) I am going to be writing a COBOL program to access/report on job
status'
in the QHST file. Anybody know if there is a better way to do this besides using the QMHRCVPM API ( receive program message). I have seen
documentation on the History Utility - but I have not been able to get that to function - is it a product that needs to be purchased? Anybody
have a sample or snipit of QHST accessing API's in COBOL?
Adrienne: There seems to be some confusion about QHST and how APIs might be used. First, the QHST message queue isn't a program message queue, so QMHRCVPM wouldn't be appropriate. Instead, for most message queues, you'd use QMHRCVM (receive NON-program messages). Unfortunately, the QHST message queue is a special case. You can't normally receive messages from it. It's restricted in that way. Also, if you _could_ receive messages from it, you might not want to because messages aren't kept in the QHST message queue for long in many cases. In some cases, messages might be there for only fractions of a second. The message data gets moved to the QHST log physical files automatically at intervals (more or less) and removed from the message queue. For general details, see: http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/r bam6/systl.htm or http://makeashorterlink.com/?V21262A4D Read that page carefully, especially the later parts that discuss how message data gets from the message queue to the log files. Your programming will be far easier once that page is understood. (And your programming will be _very_ difficult without it!) Tom Liotta -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 x313 Fax 253-872-7904 http://www.powertech.com __________________________________________________________________ Switch to Netscape Internet Service. As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register Netscape. Just the Net You Need. New! Netscape Toolbar for Internet Explorer Search from anywhere on the Web and block those annoying pop-ups. Download now at http://channels.netscape.com/ns/search/install.jsp ------------------------------ -- This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) digest list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/cobol400-l or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l. End of COBOL400-L Digest, Vol 4, Issue 66 ***************************************** -- This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/cobol400-l or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-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.