|
My experience has been on 6.1 Lawson, where I found that giving the Lawson subsystem its own memory pool was a great help. Apparently everything has changed on 7.2. I've heard horror stories about the changes to the architecture. If you haven't already, you might want to join the Lawson SysAdmin list on Topica. About 95% of the discussion is about the bloody hell involved in keeping Lawson's Unix/NT Oracle/SQL/Informix environment working. But there have been some discussions about AS/400 performance and tuning in between the complaints about being way behind the Unix version. Off list I'll send you a discussion from that list. An admin on 7.2 explains the issues she faced while trying to tune an AS/400 for the new GUI. -Jim James P. Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@dollargeneral.com> -----Original Message----- From: Berg, Dan [mailto:berg@scdatacenter.com] Sent: Friday, November 09, 2001 3:13 PM To: 'midrange-l@midrange.com' Subject: RE: AS/400-Lawson tuning We are currently running Lawson 7.2.2.x, It is definitely slower then 6.1.x (we upgraded earlier this year). If anyone has any Lawson-AS/400 tuning suggestions, I am always open to different approaches. I have tried many, some do make a difference. Thanks Dan -----Original Message----- From: Jim Damato [mailto:jdamato@dollargeneral.com] Sent: Friday, November 09, 2001 2:59 PM To: 'midrange-l@midrange.com' Subject: RE: Fast400 Value to iSeries community is less than zero Are you running Lawson 7.x or 6.x? We ran Lawson 6.x for quite a while. The GUI jobs ran out of a separate subsystem as Batch Immediate jobs. The GUI jobs basically ran a stack of C programs that called RPG application programs (no display files). Green screen Lawson ran a presentation manager program that accessed a display file and called the same RPG application programs. The application programs were designed to send feedback to either the green screen presentation manager or the GUI driver programs. There are also a bunch of database file members to define screen or GUI form layout. In 6.x the Lawson GUI did not consume Interactive CPW. I had heard that Lawson 7.x used some sort of screen scraper technique more in line with their Unix GUI, which is best described as supercharged Telnet. If this is true then Lawson's upgrade has further doomed their AS/400 customers. -Jim -----Original Message----- From: Berg, Dan [mailto:berg@scdatacenter.com] Sent: Friday, November 09, 2001 2:29 PM To: 'midrange-l@midrange.com' Subject: RE: Fast400 Value to iSeries community is less than zero We use our AS/400 to run several Lawson Apps with a GUI interactive interface. Isn't GUI supposed to bypass the interactive feature? Lawson's doesn't, but could use to. If IBM wanted to sell more AS/400's to Lawson customers, they should have Lawson turn that CFINT bit off. Then we might be able to lure some Unix customers over from the dark side. ;) Lawson already controls how many users can be signed on at one time and you have job priorities assigned to each job whether it is batch or interactive. So if a interactive job is limited by priority, why do you need CFINT too? Dan _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-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.
midrange.com
