Re: Tight loop - stopping the error

["Charles Wilt" <charles.wilt@xxxxxxxxx>]

I think Chuck provided a good alternative, but I thought I'd throw
this out there as another reason to use it.

While I don't know the internals of the OS, my first thought was your
original idea was a bad one simply because it seemed to me that the
original idea seemed recursive in nature.  Every send of the error
message invokes another one.

If you were talking about Windows, I wouldn't be surprised it it
crashed the system.  Even if IBM i doesn't crash, at some point, very
quickly, you'll hit a limit for the recursion.  Of course that error
might have trouble getting sent too, so who knows maybe you would
crash the OS. <grin>

If you use Chuck's suggestion of a loop around a CHKOBJ, it would seem
to me that any object would do, there's no reason to use the QSYSOPR
message queue.


HTH,
Charles

On Sat, Sep 6, 2008 at 12:13 AM, John Earl <john.earl@xxxxxxxxxxxxx> wrote:
> Here is an interesting problem.
>
> We're stress testing an application and need to generate and enormously
> large number of audit journal entries as quickly as possible.  "T" type
> entries are what we're after but really any entry type will do.  So if
> you have an idea how to do that, please chime in.
>
>
>
> Here is one idea that I had, but I don't know how to stop it once we
> begin.  Any ideas on this particular approach would be greatly
> appreciated.  Here is the plan:
>
> 1.      Create a User called "Fred"
> 2.      Give "Fred" *EXCLUDE authority to the QSYSOPR message queue.
> 3.      Have "Fred" submit a batch job that does a "SNDMSG 'Hello World'
> TOMSGQ(QSYSOPR).
>
> Because "Fred" has *EXCLUDE authority to QSYSOPR, this command will
> generate an 'T' 'AF' audit journal entry in QAUDJRN.  Because it is done
> in a batch job, the batch job attempt to throw and exception error
> message into QSYSOPR, but because "Fred" is still *EXCLUDED from message
> queue QSYSOPR, the process will generate another 'T' 'AF', and yet
> another error message headed for QSYSOPR, etc. etc. in  a very tight
> little loop.
>
> This seems like a good way to generate a ton of audit log entries, but
> the question is this:  How do you stop it before it runs away with your
> system?  Can anyone think of a way to interrupt this process?
>
> TIA,
>
> jte
>
>
> --
>
>
>
> John Earl, VP and Chief Technology Officer
>
> PowerTech:   253-872-7788
>
> Direct:          253-479-1408
>
> Mobile:          206-669-3336
>
> John.Earl@xxxxxxxxxxxxx
>
>
>
>
>
>
>
>
>
> Email is an excellent way to communicate material that is not time
> sensitive.  If your communication is of a more urgent nature, please
> call.
>
>
>
> ===========================
>
> This email message and any attachments are intended only for the use of
> the intended recipient named above and may contain information that is
> privileged and confidential. If you are not the intended recipient, any
> dissemination, distribution, or copying is strictly prohibited. If you
> received this email message in error, please immediately notify the
> sender by replying to this email message or by telephone and delete the
> message from your email system. Thank you.
>
>
>
> --
> 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.