The MUI issue shouldn't be a issue - it' just a matter of following the instructions in the MAPICS informationals. The MAPICS business partner should know about that and plan for that during the upgrade. The "gotcha" is the informationals discuss doing the CQIBMMUI call during a release upgrade. But, beware that a CUM can upset the MUI functionality. So, I always do the CQIBMMUI to set the OS/400 up when doing a release upgrade or a CUM. The MUI is good "magic" from MAPICS that provides cursor sensitive prompting, help text, and screen modification outside of the application code. So, I agree that IBM isn't at fault. The way I think of it is (from a application programmer view) - the MUI CQIBMMU call must fix the system domain stuff that is really called from within the application domain (MAPICS). That's why MAPICS wasn't allowed to run at greater than security level "30". BTW, I thought that MAPICS can now run at security level "40" now. Is anybody running above "30" with MAPICS? +--- | This is the MAPICS Mailing List! | To submit a new message, send your mail to MAPICS-L@midrange.com. | To subscribe to this list send email to MAPICS-L-SUB@midrange.com. | To unsubscribe from this list send email to MAPICS-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.