Re: CL Prompting in WDSC

Hi August,

This appears to be a bug in the CL prompter.  I will fix it for our next
release.

Thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab
(905)413-2750                          tie line: 969-2750         Fax:
(905)413-4850




wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/26/2004 01:59:20 PM:

> Does anyone know of a way to keep explicitly keyed "default" values from
> being removed after prompting on a command?
>
> Case in point...
>
> SAVLIB     LIB(&SAVLIB) DEV(&TAPDEV) +
>              ACCPTH(*YES) OUTPUT(*OUTFILE) +
>              OUTFILE(QTEMP/SAVERR) INFTYPE(*OBJ)
>
> The default value for INFTYPE is "*OBJ".  If I prompt on this command in
> SEU, the explicitly coded *OBJ will remain in the command when I return
> from the prompting screen.  If, however, I prompt in WDSC, it is assumed
> that any default values should be omitted.  This is not a true
> assumption in our environment.  In this particular case, *OBJ was
> explicitly coded to indicate that a conscious decision was made to
> include object level messages in the output file - as opposed to just
> accepting the default, whatever that may be.
>
> Obviously, I'm not suggesting that all default values should be
> shown...I'm simply suggesting that if the value was present prior to the
> prompting, it should remain when you return from the prompting window.
>
> Thanks in advance for any suggestions or advice,
>
>
> August Fassler
> Lead Programmer/Analyst
> Sporlan Valve Company
>