Re: Clean joblog

On 22/12/2009, at 7:50 AM, rob@xxxxxxxxx wrote:

Shouldn't this remove the one for C? Wouldn't C's be at the "top"?

No C's messages are the 3rd in sequence (presuming one escape message for each failed ADDLIBLE command and no other messages in the queue.

Job log should look something like:

*RQS CALL TESTPGM
*ESCAPE CPF2103 Library A already exists in library list
*ESCAPE CPF2103 Library B already exists in library list
*ESCAPE CPF2103 Library C already exists in library list

MSGTYPE(*NEXT) MSGKEY(*TOP) gets the first message in the nominated call stack queue. Since that's usually PGMQ(*SAME (*)) then it gets the first message from this OPM program call.

And if I have the MONMSG CPF2103 immediately after the ADDLIBLE C I can't
begin to fathom what message might be removed prior to it. I hate testing
on a several hour long program and prefer unit testing.

Possibly a completion message from a previous command or a diagnostic message from a previous failure where you only removed the escape message.

I'm willing to try something else though. What does your full RCVMSG look
like? Like, Mark Waterbury's?
RCVMSG PGMQ(*SAME (*)) MSGTYPE(*EXCP) MSGKEY(*NONE) +
WAIT(0) RMV(*YES)

Essentially the same.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------