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.