Re: CL Prompting

["SamL" <lennon_s_j@xxxxxxxxxxx>]

----- Original Message -----
From: <craigs@dekko.com>
To: <code400-l@midrange.com>
Sent: Monday, October 14, 2002 1:50 PM
Subject: CL Prompting


>
> Sam,
> Even with WDSC 4.0 SP2, certain CL commands like CRTLIB,
ADDLIBLE, CALL,
> ...., do not pop up in the STRCODE session like you would expect
but use
> local GUI.  I think this is true for most versions of CODE/400
but I cannot
> remember when CL GUI prompting became included with CODE/400.
Enabling
> extras by typing "EXTRAS ON" (then opening CODE/400) will show
Extras -> CL
> GUI Prompting.  Although, checking this option will allow all CL
commands
> to be prompted in GUI, unchecking this option will still keep the
> previously mentioned commands as local GUI even though you would
expect and
> want them in the STRCODE session.

I wonder if this involves a distinction between trying to run the a
CL command (e.g. EDTLIBL) in the command window and prompting the
command just to get the syntax right but not actually executing it
when writing a CL program?

With program writing, I find the GUI less effective that green
screen prompting, but I can live with it, since I still can do most
of my CL stuff in green screen and I tend to use prompting heavily.

I haven't tried something like EDTLIBL or CALL in the command
window.

Sam