Re: Is there a downside to using NODEBUGIO

Hi Buck -

On Fri, 17 Jun 2016 13:03:04 -0400, Buck Calabro
<kc2hiz@xxxxxxxxx> wrote:

On 6/17/2016 12:45 PM, Duane Scott wrote:

Hey, one thing at a time. No pushing. Baby steps.

I use a /copy for all of my h-specs for *PGM objects. *SRVPGM objects
get a different one. The point being that we set all of our program
options in one place, so things like this are easy to implement.

I had three, one for *SRVPGMs, one for *PGMs with ACTGRP(*NEW), and
one for *PGMs with ACTGRP(*CALLER).

(This was retrofitted onto existing software so I didn't use named
activation groups.

I'm deliberating using the past tense because as of the beginning of
May this software is no longer being used, and I'm retiring three
weeks from today. (It's a real retirement, not a shift to consulting
or anything, so I'll be dropping off these lists sometime thereafter.)

We'll tackle sub-procedures at a later date.

Another reason to use a /copy. When, in the future, you want to add a
binding directory to most (all) of your *PGMs, you change the /copy and
it's done everywhere.

Or in my case, the /copy members allowed me to easily remove a binding
directory that was no longer needed.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.