Re: CMD Validity Program Oddity

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Hi Brian

I have a feeling it is about the order things are called - as a test, 
you might actually put in a choice program and see whether that is 
before or after the validity checking program - I forget, and it's been 
quite awhile.

Cheers
Vern

On 6/11/2018 8:50 AM, Brian Garland wrote:
> I have a CMD with a validity checking program that does it's own prompting
> to override the value of a parameter.  I'm doing it this way because I do
> not like the way CHOICE(*PGM) works.
>
> If I type the command and press ENTER things work correctly.   If I type
> the command and press F4 the value is not actually replaced.
>
> I've stepped through the flow in debug and can see the value being set in
> the validity checking program, but then when the processing program is
> called the parameter was reset to the default.
>
> I've been able to reproduce it on both 7.1 and 7.3.  Is this a known issue
> OS issue?
>
> Maybe I'm just lucky it works with ENTER.