|
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.