Re: SQL Filling Job Log

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Kurt

A couple crazy ideas - how about adding a watch for these messages? 
STRWCH is the command, if you've not looked at it before.

My thought is, you can delete a message that just arrived, I would think.

Each watch can be set for up to 5 message IDs, and you can specify 
generic message IDs.

When any of the messages appears on the job log or some other place 
specified, the watch program is called. You get to do what you need to then.

Jobs that are being watched can also be specified with generic values.

I don't know - maybe!

Another idea is to bracket the job with the technique of walking through 
all messages between the SNDPGMMSG with message key. It could be done 
for only the programs with SQL processing. Again, unwanted messages can 
be received with DLT(*YES). Again, you'd need to know the message IDs 
you want not to see.

HTH
Vern

On 6/7/2013 12:13 PM, Gary Thompson wrote:
> Yea, that's what I *thought* I had been able to do - hopefully someone else helps with this
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Anderson, Kurt
> Sent: Friday, June 07, 2013 11:09 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: SQL Filling Job Log
>
> *No suppresses SQL messages from going to the job log when STRDBG is not active.
>
> I'm trying to find a way that I can (ideally optionally) suppress SQL messages from going to the job log when STRDBG is active.
>
> In my test I processed 130k records which resulted in 70k inserts.
> The old job log was 40 pages.
> Now, there are 483 job logs that are 338 pages, plus one final job log that is 21,394 pages.  That's a total of 184,648 pages.
>
> -Kurt
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
> Sent: Friday, June 07, 2013 11:56 AM
> To: Midrange Systems Technical Discussion
> Subject: RE: SQL Filling Job Log
>
> Kurt.
> You are right on target.  From *memory* I think *NO for that setting should suppress . . . HTH
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.