× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Upgrading to V4R4
  • From: Bryan Burns <burnsbm@xxxxxxxxxxxxxxxxxxxx>
  • Date: Mon, 14 Feb 2000 17:17:33 -0600
  • Organization: Echo, Inc.

According to MAPICS, Inc. none of their versions can run at level 40 right 
now.

I submitted a question to their response line via e-mail regarding this 
issue  just last week and here was their response:


"At this point XAR5.5 is not compliant with security level 40, this will 
change.
I do not have a target date at this time.  XAR6 should be compliant with 
this security level when it is available and XAR5.5 will become compliant 
with this security level via PCM in the future."

This kind of surprised me because it seems that the AS/400 security experts 
think we should all be at level 40 and here we have an ERP system that 
cannot even run at 40!

BTW, we have 5.5 in a test environment and it seems to all be working OK, 
even help text.




Bryan Burns
Echo, Inc.

-----Original Message-----
From:   Kandel, Ed [SMTP:ekandel@CONEDRIVE.TEXTRON.com]
Sent:   Wednesday, February 09, 2000 3:36 PM
To:     MAPICS-L@midrange.com
Subject:        RE: Upgrading to V4R4

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: 
dshaw@spartan.com
+---

+---
| 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: dshaw@spartan.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.