Re: Is there a process that would allow me to take control of an interactive session?

James,
The deal with stopping debug on a production system is that you are allowed
to change the values of variables. I could a STRSRVJOB, set a breakpoint
in a payroll calculation job and change the payrate for me to $10,000/hr.
No trigger, audit journal or anything associated with that file would log
me as the culprit. And if I had done a CRTDUPOBJ on STRDBG they'd have a
devil of a time searching for use of that command.

On Tue, Jun 11, 2024 at 11:39 AM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

On 6/11/24 1:48 AM, Jon Paris wrote:

It is way worse than allowing debug in production.

I, for one, have never understood the objection to "allowing debug in
production." It is in a production environment that it is most important
to be able to verify (by single-stepping it through the critical lines
for a few records) that a program works as intended on the live data,
before turning it loose on an entire file.

And it's annoying to get my breakpoints in place for that, only to
discover that I'd forgotten to specify UPDPROD(*YES).

--
JHHL

--
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.