Re: Detecting when a user invoked strdbg

[Gavin Inman <midrangelist@xxxxxxxxxxxxxx>]

A good Change control process, including a CAB (change Approval Board), 
in addition to having a development only server and kick the developers 
off the production machine would solve most of your concerns.

Thanks,

Gavin..

On 5/28/2024 3:05 PM, Richard Schoen wrote:

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