MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » November 2006

Re: CL Program parm size change



fixed

Jeff,

Is it feasible to make a new version of the utility, with the *CHAR 10 
parameter, and gradually switch the calling programs to this new version?

That's what we do when a change in parameter (number, type, length, ... ) 
is too extensive to do in one sweep.

HTH,

Peter Colpaert
Application Developer
PLI - IT - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----



"Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/11/2006 15:02
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
CL Program parm size change






I have a command/cl utility where I need to change the size of the 1st 
parm
from *CHAR 7 to *CHAR 10.  This utility is pervasive, being called from 
283
places (yea, it's proved very useful <g>).

I cannot change the utility first because it will immediately break. 
(Trust
me on this, the current version of the utility uses the SPCVAL differently
than what the new version will.)

In my testing, it appears that I can call this utility command with the
calling program's variable being defined as *CHAR 10 (and the utility's
still being defined as *CHAR 7) and it works.  Therefore I could change 
all
283 locations as time permits, then change my utility.

Does this sound reasonable?

Thanks.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact