Re: CL prompter problems still abound

Hi Vern,

I have opened APAR SE18053 for this problem.  The fix target is 5.1.2.4
As Don previously mentioned, 5.1.2.3 was for only one specific high
severity memory/caching issue and therefore contained no CL fixes.

Unfortunately calling QCAPCMD will not parse a command (which is the code
that generates the message you describe) in a way that the parser can use
so that parameters can be prefilled with specified values.

Thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab




wdsci-l-bounces@xxxxxxxxxxxx wrote on 12/13/2004 11:16:51 PM:

> What is the status on fixes to the CL prompter? I am at 5.1.2.3 build
> 20041201_1502.
>
> I still get a message that MSGID is not a valid parameter for the
following
> statement:
>
> IF &ERRORSW SNDPGMMSG MSGID(CPF9999) MSGF(QCPFMSG) MSGTYPE(*ESCAPE)
>
> But this is completely valid, and SEU does just fine.
>
> Things like this make me very wary of using WDSC for CL editing. There
are
> just 'way too many problems with this prompter. It would be slower, maybe
-
> maybe not - but how about doing a call to QCAPCMD or equivalent until
this
> gets done right. Or, at least, get that code and make sure the same thing

> happens. It's been right for years - seems as if someone is doing this
from
> scratch, or from what they see and not from what has been established.
> PLEASE!!!
>
> Regards
> Vern