× 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: MAPICS XA6 at QSECURITY level 40
  • From: "Shaw, David" <dshaw@xxxxxxxxxxx>
  • Date: Thu, 20 Jul 2000 13:20:19 -0400


Forwarded by moderator for Gernot Langle:

*********************************************

"Leland, David" wrote:

>
>
> Anyone running MAPICS XA6 at level 40 security?  I sent an e-mail to
> MAPICS asking if this was possible.  They say it is but it's not
> recommended.  Haven't heard back from them as to why it's not.
>
> Dave

You may want to read informational download SH13924 (see below).
****************************************************************************
*****

SH13924
MAPICS MUI FOR XA RELEASE 6
07/13/2000 CURRENT
06/14/2000 PREVIOUS
06/09/2000
06/08/2000
-----------------------------------------------------------------------
PURPOSE:  Information on MAPICS User Interface (MUI) for XA Release 6
          RISC systems only.  CISC is no longer supported.
-----------------------------------------------------------------------
TABLE OF CONTENTS

o  Tips and Notes
o  Current XAR6 MUI PTFs

***********************************************************************
TIPS AND NOTES
--------------

* REQUIREMENTS
  For XAR6 the operating system must be OS/400 V4R3 or higher.
  Additionally, the following IBM PTFs and APIs must be applied:

  IBM Product ID:  5769SS1

     V4R3              V4R4
     SF61366           SF61374
     SF61371           SF61378


  Required IBM API objects QDDDUPDF and QWSACCDS are packaged with
  MAPICS objects in AMALIBx because they were created by IBM for
  MAPICS.

* NEW FUNCTIONALITY
  Functional and visible changes to MUI XAR6 are few; however, under
  the covers the architecture has major enhancements to allow MUI to
  run at security level 40 if needed.  Running at security level 30
  is still the recommended preference.

  Please DO NOT apply any OLD versions of MUI PTFs to XAR6.

  MUI for XAR6 has major changes in over 100 programs.  It should not
  be necessary run CQIBMMUI on XAR6 because of architecture changes
  and new IBM APIs.

  The STRMUI command can now be assigned for individuals or interface
  codes; this means that MUI may be operational for some users and not
  for others.

  A new sequence number field has been added within MUI to provide user
  sequencing of the order the fields appear in; maintain this field in
  the "Notes - Identify an Object" display that appears when using "I"

  on the Objects to display identifiers in the "Notes - Objects" screen
  from the heading "Object", under "Note", which is reached by using
  the ADMMUI command from a command line.

* MUI PERFORMANCE CONSIDERATIONS
  Performance can be improved by turning off MUI screen design.  This
  can be accomplished by changing the APPTXT file records at position
  238 from INTERFACE(*YES) to INTERFACE(*NO) for each application.

  Starting in position 206 of the APPTXT file, the MUI commands look
  like this:
            STRMUI HELP(F1 *UNUSED *ALWAYS) INTERFACE(*YES)
                   HOTKEY(HOME MAIN_MENU) MENU(*MAIN_MENU) MENU(*NONE)


* OPERATING SYSTEM PTFS/UPGRADES
    Currently OS/400 changes should not result in the need to 'reset'
    MUI as previous levels did; this means, as noted above, that the
    CQIBMMUI program should no longer be required.

* OS SECURITY LEVEL REQUIREMENT
    MUI will now allow the AS/400 to run at a security level of 40 or
    lower; there may, however, be other reasons to run at a level of
    30 as per previous releases, and you should check the requirements
    for all applications and third-party programs you are running.

    To verify the security level of your system, do the following:

       DSPSYSVAL QSECURITY

    If needed, use the following command to change the system security
    level as appropriate (in the following example '30' is used):

       CHGSYSVAL SYSVAL(QSECURITY) VALUE('30')
       ** Important note - the system must be re-IPLed for the above
                           change to take effect.


* SPECIAL NOTES CONCERNING THE APPLY OF MUI PTFs

  a.)  When applying MUI PTFs, be sure to use either the AMAPICS or
       QSECOFR user profile, or a profile with *ALLOBJ authority.

  b.)  MUI PTFs MUST be applied directly to the AMALIBx (where 'x'
       is your environment designator).  They CANNOT be applied to
       any other library, even if that library is ahead of AMALIBx in
       the library list.  MUI uses its own library list and will only
       work from AMALIBx.

  c.)  Before applying a MUI PTF, be sure to verify there are NO locks
       against the AMALIBx.  To check for locks, run the following:

             WRKOBJLCK OBJ(QSYS/AMALIBx) OBJTYPE(*LIB)

       If this command shows ANY locks against AMALIBx, either end the
       job(s) or have the user sign out of MAPICS.

  d.)  After applying MUI PTFs, sign completely off the AS/400 then
       sign back on.  Upon signing into MAPICS again, MUI will be
       restarted thereby allowing the newly applied MUI PTFs to be in
       effect (the first person into MAPICS after applying a MUI PTF
       will experience a slightly longer startup time).

  e.)  After applying MUI PTFs, the ownership of the MUI modules may be
       changed to QDFTOWNER.  Verify that all modules affected by the
       PTF are owned by AMAPICS (use the DSPOBJAUT command; if needed,
       use the CHGOBJOWN command to change owner to AMAPICS).

***********************************************************************
CURRENT XAR6 MUI PTFs
---------------------

  MUI PTFs for RISC System
  ------------------------

        SH40962

***********************************************************************
PTF SUMMARY
-----------

SH40962  Conglomerated PTF containing all MUI HELP and LOOKUP records.
         Please be advised, this PTF is EXTREMELY large.  Only those
         users experiencing error "EXTERNAL HELP FILE COULD NOT BE
         OPENED" when pressing F1 for HELP on a field and/or a pop-up
         window stating "THERE IS NO WINDOW ASSOCIATED WITH THIS FIELD"
         when pressing F4 for LOOKUP need to download/apply this PTF.

--
Gernot Langle
PARAS Solutions, Inc.
http://www.parassolutions.com
mailto:glangle@parassolutions.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.