Re: Is there a downside to using NODEBUGIO

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 06/17/2016 12:41:14
PM:

----- Message from Tommy Holden <Tommy.Holden@xxxxxxxxx> on Fri, 17
Jun 2016 16:34:25 +0000 -----

To:

"RPG programming on the IBM i (AS/400 and iSeries)"

<rpg400-l@xxxxxxxxxxxx>

Subject:

RE: Is there a downside to using NODEBUGIO

Personally I'd opt for the H spec (or free format ctl-opt) method
that way if there's ever an OS upgrade or moving to a new system you
don't have to remember to change the command defaults again.

Thanks,
Tommy Holden

-----Original Message-----

. . .
. . .
. . .

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Roger Harman
Sent: Friday, June 17, 2016 11:29 AM
To: RPG programming on the IBM i (AS/400 and iSeries)

<rpg400-l@xxxxxxxxxxxx>

Subject: Re: Is there a downside to using NODEBUGIO

Have you thought about changing the command default?

If you do any customization to the system, you always have to be able to
redo it at a new release or system change, etc. Our System Administrator
has a single source member where he records all the customizations
(changed command defaults, outq customizations, etc.). Then at a new
release or if we get a new box, he just executes the one source member. He
also includes comments so the reason for a change can be documented as
needed.