×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
James,
I'd guess so - one per file. I've not tried it. You might need to add code
to check that you're actually deleting the message you think, so it would
get more complex :-(
As an alternative, a while back I wrote a utility which got published in the
iSeriesNews Magazine about removing job log messages, where you could
specify which messages in the job log should be removed (selected by message
id, sending program, receiving program etc.). You might need membership to
see it -
http://systeminetwork.com/article/utility-cleans-unwanted-job-log-messages.
You could simply call that to remove every instance of CPF4011...
Rory
On Mon, Feb 23, 2009 at 10:03 AM, James Lampert <jamesl@xxxxxxxxxxxxxxxxx>wrote:
roryhewitt@xxxxxxxxx wrote:
A call to QMHRCVPM immediately after the file OPEN (if USROPN is
specified) does the trick. If the file is not USROPN, I'd guess a
call in your initialization processing would work...
Thanks.
Sounds like you've "been there, done that, got the T-shirt."
What if there are multiple non-USROPN files involved? Multiple QMHRCVPM
calls in the *INZSR?
--
James H. H. Lampert
Touchtone Corporation
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
