RE: Any Combination of Settings to Get one Large Contiguous Job L ogin V5R4

I do the same thing Rob suggests in WRKDBF's CLLE's to keep the joblog free
of extraneous, -expected- messages.

The key word here is "expected". In Rob's example, he does a DLTF command.
He is (hopefully!) expecting the file to not exist on occasion, thus he
removes the message. If he had expected the DLTF to -always- delete a file
I would expect he would not have removed the message as this condition would
be a problem he'd likely want to be informed of in the joblog.

If a message is considered "expected" and/or" normal", remove it and your
joblog will be left with only "unexpected" and/or "abnormal" messages.

Bill

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
Sent: Monday, July 07, 2008 8:53 AM
To: Midrange Systems Technical Discussion
Subject: Re: Any Combination of Settings to Get one Large Contiguous Job
Login V5R4


One of the main reasons that I started putting code in my programs to
remove messages that I processed. Here's a code sample:
MONMSG CPF9801 EXEC(DO) /* Object does not exist */
/* Remove message from cluttering joblog */
RCVMSG MSGTYPE(*NEXT) MSGKEY(*TOP) RMV(*YES) KEYVAR(&KEYVAR) +
MSGDTA(&DATA) MSGID(&MSGID)
EndDo

So, if your job does a lot of:
DLTF QTEMP/MYFILE
MONMSG CPF0000
Then change it to do:
DLTF QTEMP/MYFILE
MONMSG CPF2105 EXEC(DO) /* Object does not exist */
/* Remove message from cluttering joblog */
RCVMSG MSGTYPE(*NEXT) MSGKEY(*TOP) RMV(*YES) KEYVAR(&KEYVAR) +
MSGDTA(&DATA) MSGID(&MSGID)
EndDo

And your joblogs may be a LOT cleaner. This actually removed a thousand
or so pages from one joblog.
Notice that I also dropped the CPF0000 and replaced it with CPF2105. In
theory your DLTF may fail because of some other reason and I hate to
assume it was because the file wasn't there.

Rob Berendt