We had a similar circumstance. No one, other than the CFO & Controller, was allowed to deal with executive payroll. One time, the controller dropped a stack of checks and the operators said it was hilarious - he threw himself over the spillage like a soldier throwing himself over a live grenade to save his buddies.
Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Don Brown via MIDRANGE-L
Sent: Wednesday, June 12, 2024 1:22 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Don Brown <DBrown@xxxxxxxxxx>
Subject: Re: Is there a process that would allow me to take control of an interactive session?
The opposite to this is back in system 38 days.
An error occurred in the payroll for executives, production system.
Trying to fix the problem without access to production as we might see
something that we should not and being informed by the IT Manager of the
error and trying to fix on the test system.
Took quite a few goes but eventually found and fixed.
That is really working in the dark with a blindfold for good measure.
hahahah!!!!
Cheers
Don
From: "Jon Paris" <jon.paris@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 12/06/2024 06:05 PM
Subject: Re: Is there a process that would allow me to take control
of an interactive session?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
So you are OK if someone debugs in the payroll system and changes your
salary? (in a downward direction) ?
Of course, there will always be exceptional cases - but it should never be
the norm.
Jon P
On Jun 11, 2024, at 4:38 PM, 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.
--
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.
--
This email has been scanned for computer viruses. Although MSD has taken reasonable precautions to ensure no viruses are present in this email, MSD cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
--
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.
midrange.com
