Re: Prompting for CL commands is broken in Code/400 V4

Jim

I agree that the "old" way is a lot faster. I much prefer the STRCODE
servers for lots of stuff - definitely seem more stable.

Vern

At 10:39 AM 12/18/2002 -0700, you wrote:

Vern,

I did not have GUI prompting turned on in the extras, because I did not
want to use GUI prompting.  I like the old (I know!) way.  I can find
prompts faster.

I turned on GUI prompting and - I now get GUI CL prompt.  It does not use
the server I set up because it asked me to signon to the 400 again.
(another reason I don't like GUI prompting.)  I would like to have my old
way back!

Jim

> Jim
>
> Is it possible you have turned on GUI CL prompting?
>
> Vern
>
> At 07:34 AM 12/18/2002 -0700, you wrote:
>>(Posted on the WDSC list, but no response there)
>>
>>Greetings!
>>
>>I have had CL prompting fail several times from the Code/400 editor.  I
>> am using a 5250 emulation session (PCOMM V5.6 build 20020814)  and a
>> STRCODE server session.  I initiate the edit of a CLLE source member
>> from WRKOBJPDM with the following command:
>>
>>/* Evoke Code/400 in Edit Mode */ CALL PGM(QDEVTOOLS/EVFCFDBK)
>> PARM('37' 'Y' 'JIM' '<LOCAL> CODEEDIT "<>&L/&F(&N)"')
>>
>>The editor presents the source to me as normal.  When I prompt a CL
>> command the editor uses the 5250 screen, but I don't see the prompt
>>information.  The 5250 session hangs, and I never see that server
>> session again (until I reboot).  I have to kill the Communication
>> Daemon, All 5250 jobs, the interactive session on the AS/400 (excuse me
>> - iSeries 400), hold my nose, and give a pint of blood.
>