RE: Removing Job Log Messages -- RPG400-L

My bad, Vern. This article does apply. A thousand apologies. ;) Although I'm still debating whether or not the solution is right for my high-volume processing environment. For example, if I process 60 million records, I'd be essentially writing to the job log 60 million times, then removing it 60 million times, just to get the message key. Ideally, we only ever have a couple thousand duplicates we're concerned with. (Although in the last batch, we had 3.8 million which is why the Sender's Copy became an issue.)

I'll do some testing to see just how much of an impact the extra steps would be.

Thanks!
Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt Anderson
Sent: Friday, June 25, 2010 9:38 AM
To: 'RPG programming on the IBM i / System i'
Subject: RE: Removing Job Log Messages

Hi Vern,

Thanks for the link. Looks like it has to do with program-to-program message sending and using the message key. I'm trying to capture a system message.

Yesterday I thought it'd be ok to have that lone Sender Copy message, but as I learned today, it's still too much. Our client gives us a huge chunk of data and says, "Here." Well, 100,000+ were duplicates and caused our job to bomb b/c we don't wrap the job log. To get this through I will wrap the job log, but it would be ideal to remove this system message.

Thanks,
Kurt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Thursday, June 24, 2010 4:36 PM
To: RPG programming on the IBM i / System i
Subject: Re: Removing Job Log Messages

Kurt

IBM put out a knowledge base article that might help you here. I don't
know if it works with Sender Copy, but it might be worth a look.

The title is "*Receiving Messages from the Joblog after the Program Is
off the Callstack"*

And a link to it is *http://tinyurl.com/d4a6xx*

The article has examples in C and in CL - easily enough fitted to RPG.

HTH
Vern

On 6/24/2010 4:09 PM, Kurt Anderson wrote:

I created a service program called $RemoveProcedureJobLogEntries().
It will attempt to remove all messages generated by the calling procedure using the QMHRMVPM API by using the *ALL remove code. Unfortunately, this isn't capturing the "SENDER COPY." I understand why it's not - in looking at the job log, all of the other messages are TO the Module& Procedure (which I have specified in the API call), but SENDER COPY does not have this information.

So I'm left wondering, how can I remove this message as well? Ultimately, I'm happy with what the API does for me already, but it would be nice to remove this message as well.

Full information about the message I want to remove:
CPF5026 Sender copy 30 06/24/10 10:37:31.651168 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key not allowed for member EQNFMTPP.
Cause . . . . . : An output or update operation on member EQNFMTPP failed
because of a duplicate key in member EQNFMTPP file EQNFMTPP in library
KJA9LIB. Recovery . . . : See previously listed message CPF5009 to
identify the record with the duplicate key. Then change the key value so
that each key is unique and try your request again. Possible choices for
replying to message . . . . . . . . . . . . . . . : C -- The request is
canceled. I -- The request is ignored.

And for the record, this error is handled by the program, so I don't want the job log to be potentially bogged down by it (there are other things in the job log we'd rather see w/o having to work our way through this stuff).

Thanks,
Kurt Anderson
Sr. Programmer/Analyst
CustomCall Data Systems