Re: Does the recommendation against variable names starting with SQL apply to constants?

[Rory Hewitt <rory.hewitt@xxxxxxxxx>]

Duane,

My solution to this is to change only the copybook (and include a comment to
the effect that 'X0' has been changed to a new value) and the program that
I'm compiling. When other programs that use the old cX0 are recompiled they
will fail and the developer will figure out what happened and change that
program. Hopefully they will know where cX0 is defined and will go there and
see that it was previously changed.

Or not... :)

Rory

On Fri, Sep 3, 2010 at 10:34 AM, Christen, Duane
<Duane.Christen@xxxxxxxxxx>wrote:

> I think, and I may be wrong here, but the reason that David added the long
> named constant instead of replacing it, was that the constant was defined in
> a copy book and used in multiple modules. Which may make it a non-trivial
> task to replace the cXO constant name with the long name.
>
> Duane Christen