Re: CL Prompt for CALLPRC

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

Jon,

I have seen the same thing. Incredible that we have to put up with this 
nonsense with CL prompting! I could go on and on but will only say, 
_prompting_ _in_ _SEU_ _has_ _none_ _of_ _these_ _problems_. This is SO 
integral and basic that it MUST be fixed completely, IMO. There is no 
excuse I can think of that would allow these things to keep cropping up. 
The rules must have been published in the various design documents at one 
time - please, get those to the developers of the prompter. Yes, I know the 
prompter was based on the work of some open-source folks. PLEASE, release 
to them what they need.

I'm tired now!
Vern

At 01:15 PM 8/25/2005, you wrote:

> Jon:
>
> The CALLPRC command does not require a return value, but the prompter in
> WDSc does.  I have run into this before.  It may also have been
> mentioned in this list in the past.
>
> I recently loaded WDSc V6.0 and the same issue remains...the prompter
> will not accept a value of *NONE for the return value.  My solution is
> to provide a return variable, then manually remove it after the prompter
> creates the command.  IBM needs to properly prompt all commands.
>
> --Bruce Guetzkow
>
> --
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L) 
> mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.