Hi, Rob:
Using CL variables (&name) certainly bypasses some validity checks at
compile-time.
But, if those validity checks failed at compile time when the values
were "hard-coded", won't they also fail at runtime, when the values in
those variables (&name) are substituted into the command and the system
attempts to process that command?
In other words, when you ultimately try to run this CL program on the
target system, will it not also fail the same validity checks? =-O
Mark
> On 2/20/2013 10:56 AM, rob@xxxxxxxxx wrote:
In case my emails came out of order to you also, Paul's reply was perfect
and is now implemented.
Rob Berendt
