RE: Highlight line APAR now submitted to IBM for review

I guess we're being bitten by the "one size fits all" (or "one program fits
all") bug.

This behavior (taking another 4K for each macro execution) seems undesirable
for any user, regardless of the platform.  But I can also understand that
the designer didn't intend macros to be used on a line-by-line ("micro")
basis.

We agree line highlighting is a useful function, and I'm surprised it's not
a native (hard-coded) feature.  Macros and other soft-coding techniques are
nice to give a program personality, but at some point the designer has to
provide base functionality through hard-coding.

Is there a cross-hair function available?  Maybe I'll try that (unless it's
4K foe the vertical line and 4K for the horizontal line).

Thanks,
rf

-----Original Message-----
From: code400-l-admin@midrange.com [mailto:code400-l-admin@midrange.com]On
Behalf Of haklui@ca.ibm.com
Sent: Monday, April 08, 2002 10:35 AM
To: code400-l@midrange.com
Subject: RE: Highlight line APAR now submitted to IBM for review

Reeve:
     I'm with you; I like the feature too. We would like to provide a fix
as soon as we can. However, since CODE is using REXX/LPEX which is
essentially a different product, and we can see that it is almost
impossible to provide any service pack for the problem. We are still trying
to investigate if there is a work-around or alternative solution.



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




                    "Reeve Fritchman"
                    <reeve@ltl400.com>       To:
<code400-l@midrange.com>
                    Sent by:                 cc:
                    code400-l-admin@mi       Subject:     RE: Highlight line
APAR now submitted to IBM for
                    drange.com                review


                    04/05/2002 02:42
                    PM
                    Please respond to
                    code400-l





I think line highlighting /is/ useful, especially when working on a large
(21") CRT or in bad lighting conditions on a laptop.  I'd like it fixed
ASAP
for two reasons: (1) I like the function, and (2) I'd like to be able to
use
CODE/400 for more than two hours without a hang-up or lock.

-rf

-----Original Message-----
From: code400-l-admin@midrange.com [mailto:code400-l-admin@midrange.com]On
Behalf Of craigs@dekko.com
Sent: Thursday, April 04, 2002 10:00 AM
To: code400-l@midrange.com
Subject: Highlight line APAR now submitted to IBM for review

The source of the highlight line problem was finally found, explained in
detail by Hak Lui, and submitted to IBM as a request (APAR).  I noticed
that the CPU would spike to 100% and the memory would increase every time I
would go to another line.  Using detailed information, Hak Lui determined
that every lpex component macro command increases the memory by 4K.
Knowing what to look for, I was even able to cause my Windows NT PC to
start thinking awhile until I had to reboot.  Apparently, it will not be
fixed in this release in a service pack, which is fine since I don't think
too many people consider this really important anyway.  Thanks  for your
help Hak.

The following is a snip of a portion of the request sent to IBM:

Request Title:

The CODE/400 lpex component macro command should not increase memory by 4K.


Provide a detailed description of request (including unique usage):

Please change the CODE/400 Editor and Designer to not increase memory by 4K
every time an
lpex component macro command runs.  This is specifically causing problems
in the Extras ->
Highlight Line option of the Editor.  The problem occurs on every Windows
operating system
when the memory limit is reached and then the CODE/400 Editor either hangs
or closes.
Every time the cursor is placed on a different line, the macro highltln.lx
runs and
increases memory 4K.  So, if you are using the up and down arrow keys and
the page keys
a lot, CODE/400 locks up or closes after some time.  Obviously, this is the
main problem
since this is the main case where a macro being executed over and over will
cause major
system problems.  So, we would like to at least have the highlight line
problem fixed.
We do not have to use the highlight line option though and we do not
because it causes
hang ups, but it is a nice function.

Other related information:  (include problem number, if available)

Please read the below explanation sent to me by Hak Lui of IBM Toronto:
   by following what you have observed, I found that it was the macro call
which ate up memory. You can see this simply by entering something like
'macro colsedit on' on the command line; memory usage is incremented by 4K
for each macro issued. Since the macro highltln.lx is called for each line,
the usage adds up. Definitely, there is a memory leak in the lpex component
macro command. Could you please check with your support folk to open an
APAR to log this problem? Definitely, it will not be fixed in this release
as a service pack.

Thanks again,
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.


_______________________________________________
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.




_______________________________________________
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.