Looked at that solution a few years ago. Of course, the root problem is SAS trying to put itself out of business.
Even so, the difficulty in automating and scheduling the process added a lot of human intervention. Human beans ain't cheap. For a scenario where MXG was used for research and ad hoc, then, yes, hands down a winner. But for situations where MXG actually generated and distributed reports to a number of people, I am not so sure. My $0.02, and there have been a few trivial technology advances in the last decade or so ;-) -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ron and Jenny Hawkins Sent: Wednesday, July 13, 2005 3:13 PM To: [email protected] Subject: Re: Another - Another One Bites the Dust Hands up all of you that have successfully migrated your SAS/MXG applications from MVS to Windows and saved money. Hands up those of you that believe it is now costing more? The MXG PDB is a classic example of an application that can be successfully moved from mainframe to a windows or Unix and provide a better TCO along with improved performance, function and productivity. In fact, if I was asked to develop an MXG PDB from scratch for a site I wouldn't even consider using MVS. A reasonable server class desktop, with XP Professional and some FC connections to SAN storage would be a better and cheaper way to go in almost all cases. Ron ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
