You may also find that IT Security and Audit personnel have another opinion about the importance of maintaining secure SAS information, if it involves Accounting/Chargeback or Cost Allocation data for your enterprise entities. And if you are forced down this path, it's important that everyone (maybe even including your information end-users) give their buy-in to the transformation (ideally in writing as in a documented project-execution plan), when considering information access, security and possibly admin learning-curve.
As Robert Bardos mentioned, SAS Institute (not just in North America, by the way) is taking license/contract negotiation more seriously for MSUs-based mainframe SAS licensing but I expect that it's going to need to come from your company/organization to determine what's a reasonable license fee for some "not to exceed" software usage limit. Sincerely, Scott Barry SBBWorks, Inc. > -----Ursprungliche Nachricht----- > FRASER, Brian > Gesendet: Dienstag, 22. Mai 2007 08:29 > > We have some management here with $$$$ in their eyes > wanting to stop the payment of our SAS mainframe licenses. > They want us to move all our SAS workload (including MXG) > onto a Unix box. > > Anyone out there done it? > > How painful was the experience? > > Does anyone have any experiences using the SAS clone WPS on the > mainframe? > http://www.minequest.com/WPS_Conversions.html > > Could we keep MXG without SAS and run it using WPS instead? > > <snip> > > But you must have SAS installed, and that is expensive. > > </snip> ---------------------------------------------------------------------- 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
