RE: Detecting when a user invoked strdbg

I questioned that as well. Honestly, my first thought was an old Dilbert cartoon.

Pointy-Haired Boss offers a cash bonus for every bug found & fixed.
Everyone is super excited.
Wally says "I'm going to write me a new minivan this afternoon".



-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Richard Schoen
Sent: Tuesday, May 28, 2024 12:05 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Detecting when a user invoked strdbg

That just made me think of something......

Why does it matter if they do STRDBG and how often ?

Maybe I missed something there 😊

Regards,
Richard Schoen
Web: http://www.richardschoen.net/
Email: richard@xxxxxxxxxxxxxxxxx

----------------------------------------------------------------------

message: 3
date: Tue, 28 May 2024 14:22:06 -0400
from: Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
subject: Re: Detecting when a user invoked strdbg

Thx Richard, but only until the dev's catch on and start doing qsys/strdbg.

thanks

Jay

On Tue, May 28, 2024 at 1:12?PM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
wrote:

This might be a hammer approach, but I did this with the SIGNOFF
command a looong time ago.

Create your own wrapper version of STRDBG and put in place ahead of
QSYS in the library list, but have it call the STRDBG from QSYS.

Then you could create your own log every time STRDBG gets called.

That could probably work for the green screen, but not sure where else
you need to call STRDBG from.

Regards,
Richard Schoen
Web: http://www.richardschoen.net/
Email: richard@xxxxxxxxxxxxxxxxx

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.