Re: CL GUI prompting haunting programmers -- CODE400-L

Craig:

I found out that for certain CL commands such as CRTLIB, ADDLIBLE,CALL...,
CODE is using local GUI in the STRCODE session. This might be the reason
why help is not working. I agree the inconsistency in this behaviour.
However, I don't know if we can provide any solution for this in the
current release now.  I need to investigate this.


Hak Lui
AS/400 AD, IBM Canada Ltd.
e-mail: haklui@ca.ibm.com


craigs@dekko.com@midrange.com on 01/09/2002 11:04:29 AM

Please respond to code400-l@midrange.com

Sent by:  code400-l-admin@midrange.com


To:   code400-l@midrange.com
cc:
Subject:  CL GUI prompting haunting programmers


CL GUI prompting is causing old GUI prompts that haunt us when we want to
keep it behind the curtain.  It even haunts us in two completely different
PC's and cases which are:
1. When we have installed CL GUI prompting but have it disabled.  ("Extras"
-> "CL GUI prompting" unchecked).
    Seen on WinNT 4.0 and Win2000 with WDT400 service pack 4.
2. When we have not installed CL GUI prompting from
http://www-4.ibm.com/software/ad/wdt400/support/codesupport.html.
    Seen on Win2000 and possibly WinNT 4.0 with WDT400 service pack 3.01
and service pack 4.

The problem is the same in both cases.  When prompting certain CL commands
like ADDLIBLE, CALL, etc, an old GUI prompt pops up when we want the prompt
in the STRCODE session.  We cannot get help on this type of prompt and we
would like to be able to prompt these commands to the STRCODE session like
OVRPRTF, DLTOVR, etc.  A long time ago, I installed CL GUI prompting to my
WinNT PC but noticed when CL GUI prompting was disabled, certain commands
still popped up in GUI but were old and help did not work.  I completely
uninstalled CL GUI prompting and then I thought I could see them in the
STRCODE session but that defeated the purpose of having CL GUI prompting.
Then I reinstalled the CL GUI prompting and enabled it, which shows the
more current GUI prompt and allows help.  I didn't worry about it and kind
of forgot about it for months, thinking my case was just different and that
no one really cared about STRCODE prompting anyway.  Then recently someone
else wanted help on a GUI prompt who had never even installed GUI prompting
on their PC.  I saw this old GUI prompt and they did not even have the
CLGUIF4.LX file in their Extras folder.  They were on WDT400 service pack
3.01 Windows 2000 but I saw a PC without CL GUI prompting installed with
the same problems on WDT400 service pack 4 on Windows 2000.  The person on
WDT400 service pack 4 on Windows 2000 had the problem when CL GUI prompting
was installed but was disabled.  They also had the problem when
uninstalling CL GUI prompting and reinstalling service pack 4.  He
reinstalled service pack 4 because at the time the files were backed up
from the install, he was on service pack 2, so he did not want to have
files back in service pack 2.  That got me thinking then that this bug must
have gotten incorporated into a service pack and could now be a widespread
error even now on service pack 4.  I haven't seen anyone mention a problem
so I am not sure if this apparent bug is limited to us or is widespread.
If I cancel the old GUI prompt, I get a message that says, "Unable to
access CL host prompting or help".  This brings up another question.  Are
there plans to merge CL GUI prompting with a service pack?  It seems like
this should be in a service pack instead of having files backed up that
might now be at an old service pack.  In any case, we would still like to
be able to have CL prompts switch to the STRCODE session instead of an old
GUI prompt.
Any help would be greatly appreciated.

Thanks,
Craig Strong

_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.