MIMIX. Version 7.0 Using License Manager. Installation and Security Information for MIMIX Products

Transcription

1 MIMIX Version 7.0 Using License Manager Installation and Security Information for MIMIX Products

2 Published: September 2010 level Copyrights, Trademarks, and Notices Contents Who this book is for... 6 The MIMIX documentation set... 6 SNA and OptiConnect Support Discontinued... 7 Sources for additional information... 8 How to contact us... 9 Chapter 1 Preparing to install 10 Choosing a method of installing Understanding product naming conventions Software requirements for installing or upgrading INSMMX requirements for new installs System requirements Library considerations when installing products Considerations for changed command defaults Using best practices to set up a library list Setting up the system portion of the library list Procedure for adding libraries to the system library list Setting up the user portion of the library list Displaying a product s install history and installed fixes Working with MIMIX commands Chapter 2 Install process checklists 21 Checklist: new product installs Checklist: upgrading products Checklist: fix installs Chapter 3 Supporting procedures 26 Prepare your environment by ending products Installing products Starting the INSMMX tool when License Manager is not installed INSMMX restrictions for specifying the installation library (INSTLIB) Installing fixes Bring up your environment by starting products Setting up Vision Solutions Portal MIMIX Availability Manager post-install steps Adding or removing the Vision Solutions plug-in to IBM Systems Director Navigator Accessing the License Manager Main Menu Updating the installed products file Removing an installed product Chapter 4 Working with license keys 44 Information about license keys and identifiers Obtaining license keys through MIMIX Installation Wizard Manually obtaining and applying license keys using MIMIX Installation Wizard. 47 2

3 Obtaining license keys using UPDLICKEY command Obtaining license keys when using 5250 emulator to install Displaying maintenance expiration and license key information Changing or displaying license key expiration message defaults Chapter 5 General security considerations 53 Security for MIMIXOWN and MIMIXCLU user profiles MIMIX Monitor security considerations MIMIX Promoter security considerations Security for LAKEVIEW user profile Additional security considerations Multiple-system security considerations MIMIX Global security considerations User profile restrictions System security System security level Password level (QPWDLVL) system value Protecting your assets from unauthorized use Chapter 6 Vision Solutions-provided security functions 64 About the provided security functions Product authority Command authority Security for common functions Requirements for Run commands Authority level descriptions Changing product-level security Displaying authorities for authorized user profiles Changing product authority Using group profile support Group profile examples Granting a user authority to a product Revoking product authority for a user Displaying the authority level of MIMIX commands Changing command authority Changing the authority level for MIMIX commands Displaying commands known to License Manager Authority levels for commands Substitution values for command authority Chapter 7 Remote system support 95 Accessing Lakeview Technology support functions Configuring the Lakeview Technology support connection Starting Lakeview Technology support Disconnecting from Lakeview Technology support Ending the Lakeview Technology support connection Deleting Lakeview Technology support objects Appendix A About MIMIX Availability Manager 99 Introduction to MIMIX Availability Manager Introduction to MIMIX IntelliStart

4 Using MIMIX IntelliStart with MIMIX Availability Manager Using MIMIX IntelliStart as a standalone product Requirements for MIMIX Availability Manager System i software requirements Determining the JDK version and group PTF level Determining if Java is set up correctly MIMIX requirements MIMIX IntelliStart considerations when used as a standalone product PC requirements Setting time zones in the SystemDefault.properties file To change the SystemDefault.properties file To create the SystemDefault.properties file Enabling MIMIX Switch Assistant Changing prestart job settings for optimal performance iseries Access for Web Systems available to monitor Adding a system to the list of available systems Setting individual user preferences Selecting systems to monitor Selecting MIMIX installations to monitor Selecting data groups to monitor Confirming a MIMIX IntelliStart automatic synchronization Displaying audit status Interpreting audit results Performing MIMIX IntelliStart manual synchronization Logging in to MIMIX Availability Manager Your location is remembered Areas of the window in MIMIX Availability Manager Additional navigation and selection aids Other useful tips Becoming acquainted with status in MIMIX Availability Manager The Enterprise View - your status shortcut Status on the navigation bar Appendix B MIMIX Availability Manager troubleshooting and commands 124 Troubleshooting with MIMIX Availability Manager log files Troubleshooting possible error conditions Port not available Locks on files Cannot view any installations due to communication error Host database server not running Command prompter not working Communication errors Cookies Firewall Port connections Java Plug-in Disabling pop-up blockers HTTP 404 file not found Check the URL

5 Make sure MIMIX Availability Manager is running Non-MIMIX applets do not work Status in MIMIX Availability Manager is different than in 5250 emulator Setting the browser date format MIMIX Availability Manager commands Starting MIMIX Availability Manager Ending MIMIX Availability Manager Changing the port number used by MIMIX Availability Manager Retrieving data about the MIMIX Availability Manager Removing MIMIX IntelliStart Index 138 5

6 Who this book is for The Using License Manager book is for MIMIX operators who must use the installation and license key support provided by License Manager instead of using AutoValidate and the MIMIX Installation Wizard. This book is also for MIMIX administrators who need to set up system security and implement additional security features available through License Manager, or who need to maintain backward compatible releases of MIMIX Availability Manager. The MIMIX documentation set The following documents about MIMIX products are available: Using License Manager This book describes software requirements, system security, and other planning considerations for installing MIMIX software and software fixes. The preferred way to obtain license keys and install software is by using AutoValidate and the MIMIX Installation Wizard. However, if you cannot use them, this book provides instructions for obtaining licenses and installing software from a 5250 emulator. This book also describes how to use the additional security functions from Vision Solutions which are available for MIMIX products and commands through License Manager. Also, to support compatible previous releases, this book includes requirements and troubleshooting information for MIMIX Availability Manager. MIMIX Administrator Reference This book provides detailed conceptual, configuration, and programming information for MIMIX Enterprise and MIMIX Professional. It includes checklists for setting up several common configurations, information for planning what to replicate, and detailed advanced configuration topics for custom needs. It also identifies what information can be returned in outfiles if used in automation. MIMIX Global Operations This book provides high level concepts and operational procedures for MIMIX Global users in an IBM i cluster environment. This book focuses on addressing problems reported in status and basic operational procedures such as starting, ending, and switching. MIMIX Operations This book provides high level concepts and operational procedures for managing your high availability environment using MIMIX Enterprise or MIMIX Professional from a 5250 emulator. This book focuses on tasks typically performed by an operator, such as checking status, starting or stopping replication, performing audits, and basic problem resolution. Using MIMIX Monitor This book describes how to use the MIMIX Monitor user and programming interfaces available with MIMIX Enterprise or MIMIX Professional. This book also includes programming information about MIMIX Model Switch Framework and support for hardware switching. 6

7 SNA and OptiConnect Support Discontinued Using MIMIX Promoter This book describes how to use MIMIX commands for copying and reorganizing active files. MIMIX Promoter is available with MIMIX Enterprise only. MIMIX for IBM WebSphere MQ This book identifies requirements for the MIMIX for MQ feature which supports replication in IBM WebSphere MQ environments. This book describes how to configure MIMIX for this environment and how to perform the initial synchronization and initial startup. Once configured and started, all other operations are performed as described in the MIMIX Operations book. SNA and OptiConnect Support Discontinued With the release of MIMIX V7.0, MIMIX no longer supports configurations using SNA or OptiConnect for communications. The parameters are still available within MIMIX V7.0, however, this functionality will not be tested for MIMIX V7.0. Vision Solutions will only assist customers to determine possible workarounds with issues arising from the use of SNA or OptiConnect for communication in MIMIX V7.0. 7

8 Sources for additional information This book may refer to other published information. The following information, plus additional technical information, can be located on the IBM i and System i Information Center at: From the Information Center you can access IBM i topics, books, and redbooks. 8

9 How to contact us How to contact us For contact information, visit our Contact CustomerCare web page. If you are current on maintenance, support for MIMIX products is also available when you log in to Support Central. It is important to include product and version information whenever you report problems. Note: For information about remote system support, see Remote system support on page 95. 9

10 Preparing to install CHAPTER 1 Preparing to install The processes available for installing MIMIX software are the same regardless of whether you are installing MIMIX Enterprise, MIMIX Professional, or MIMIX Global. A typical MIMIX Enterprise installation includes MIMIX, MIMIX Monitor, and MIMIX Promoter. Similarly, a MIMIX Professional installation includes MIMIX and MIMIX Monitor. This chapter describes the necessary requirements and best practices that should be in place prior to installing products in your environment. The following topics are included: Choosing a method of installing on page 10 identifies available methods of installing software and describes benefits of the preferred method. Understanding product naming conventions on page 12 describes the significance of the software naming convention, such as , with respect to installing software. Software requirements for installing or upgrading on page 14 identifies the minimum requirements for installing this software version. INSMMX requirements for new installs on page 14 describes when an additional tool is needed when using the 5250 emulator processes for installing software. System requirements on page 15 identifies system values that need to be set on each system. Library considerations when installing products on page 16 identifies what should and should not be in the libraries associated with License Manager and MIMIX products. Using best practices to set up a library list on page 17 identifies how to set up the system and user portions of the library list when using MIMIX. Considerations for changed command defaults on page 16 describes the impact of changing default values for shipped commands. Displaying a product s install history and installed fixes on page 19 describes how to identify the level of currently installed software. Working with MIMIX commands on page 20 describes how to library-qualify commands. Choosing a method of installing The following methods of installing MIMIX software are available: MIMIX Installation Wizard 5250 emulator command line processes 10

11 Choosing a method of installing MIMIX Installation Wizard recommended: It is strongly recommended that you use the MIMIX Installation Wizard to install products. The MIMIX Installation Wizard provides a simple method for downloading, distributing, and installing products on a single system or to multiple systems simultaneously. In addition, the MIMIX Installation Wizard also does the following: Easily and automatically obtains and applies license keys via Vision AutoValidate. Automatically installs the Vision Solutions Portal server and MIMIX portal application. The server provides support for browser-based user interfaces to VIsion Solutions products which provide portal applications. The MIMIX Installation Wizard does not support installing into a library located on an independent ASP. For more information about requirements for using MIMIX Installation Wizard, see Support Central. If you cannot use the MIMIX Installation Wizard, this book (Using License Manager) provides secondary path procedures and supporting information for installing products using the 5250 emulator. The 5250 emulator processes will save the MIMIX portal application to the system but these processes do not install the Vision Solutions Portal server or make the application known to the server. 11

12 Understanding product naming conventions The terms and naming conventions used to identify the product provide a convenient means of referencing the level of software installed. Table 1 shows the naming convention in use. This convention is indicated by V.U.SP.FX(R). Table 1. Identifier Product naming convention for shipped software media Description Version number Update level Service pack (SP) Cumulative fixes Restricted fix V.U.SP.FX(R), where V is the version number. Example: (initial version 7 release) V.U.SP.FX(R), where U is the update level. Examples: (initial version 7 release) (first major update of version 7) V.U.SP.FX(R), where SP is the SP level. Examples: (first SP release for version 7) (sixth SP release for version 7.2) V.U.SP.FX(R), where FX is the cumulative fix level. Examples: (third cumulative fix for the fourth SP on version 7) (first cumulative fix for the sixth SP on version 7.2) V.U.SP.FX(R), where (R) is the restricted fix. For software media, restricted fixes are always associated with a service pack. Otherwise the field is left blank. Examples: R (third available restricted fix for the fourth SP on version 7) R (first available restricted fix for the sixth SP on version 7.2) Note: When viewing the Vision Solutions Installed Products display, R indicates that one or more restricted fixes have been applied to the indicated service pack level. Cumulative fixes for the service pack level may also be present. For example, R on this display indicates that the third cumulative fix as well at least one restricted fix for the fourth SP have been applied. The following are descriptions of product terminology used in version 7: Version number New version of a product. In order to install a product with a new version number, you must be current on maintenance. 12

13 Understanding product naming conventions Update level New functionality available within the current version. In order to install a product with a new update level, you must be current on maintenance. Service pack (SP) A collection of product changes that are packaged together for the purpose of distribution. Installing a service pack brings all products up to the specified level. An SP is released approximately once per month. Cumulative fixes Changes to a service pack that correct a specific problem. Additional fixes are cumulative to ensure that they are applied to the correct service pack and in the correct order. These fixes are released on an as-needed basis only. Restricted fix Changes to a specific service pack. Restricted fixes are not cumulative and may or may not be integrated into the next service pack. If two restricted fixes are available for the same service pack, the first restricted fix does not need to be applied before the second is installed. Restricted fixes are released on an as-needed basis only. Note: Restricted fixes require caution and should only be applied with assistance from a MIMIX CustomerCare representative. 13

14 Software requirements for installing or upgrading Table 2 identifies the software required in order to install version 7 MIMIX products for the first time or to upgrade MIMIX to version 7. Each system in the replication environment must have this software installed and be current with the recommended PTFs and service packs applied. Note: Upgrades to version 7 are supported from any version 6 service pack level. Table 2. Software requirements for version 7 Software Minimum level Notes IBM i IBM i 5.4 (V5R4M0) Required for new installs and upgrades License Manager (formerly License and Availability Manager) MIMIX Global (formerly Vision Cluster1) MIMIX Enterprise (formerly MIMIX ha1) MIMIX Professional (formerly MIMIX halite) MIMIX Promoter or above for upgrades or above for upgrades 3 1, 2 1. Upgrades are valid only when maintenance is current. Customers not current on maintenance will only be able to re-install the same version, update, and service pack level (V.U.SP) and install fixes for that level. See Displaying maintenance expiration and license key information on page Upgrades to version 7 require license keys that are for version 7. New installs of version 7 can be completed with no license keys present, although a valid license key is required before using any product. For information about obtaining license keys, see Working with license keys on page Version 7 of License Manager no longer includes software for installing MIMIX Availability Manager. License Manager supports MIMIX version 7 and earlier versions of MIMIX. However, MIMIX Availability Manager only supports monitoring MIMIX installations that are at version 5 or version 6. MIMIX Availability Manager does not support version 7 MIMIX installations. If you plan to continue using MIMIX Availability Manager for installations at earlier versions, you must install service pack or higher. For more information, see Requirements for MIMIX Availability Manager on page 103. INSMMX requirements for new installs The Install MIMIX (INSMMX) tool in License Manager is for users who are installing from a streamfile (STMF). The INSMMX tool simplifies the install process. If you will be using 5250 emulator processes to create a new installation of MIMIX on a system where License Manager is not yet installed, you must download the INSMMX STMF from Support Central and transfer it to your system. The installation procedures in this book describe how to make the INSMMX tool ready to use and when to use it. 14

15 System requirements System requirements Before you install a MIMIX product, you should determine what requirements you have for each system that will participate in the MIMIX network. If you use multiple MIMIX products, you need to determine the requirements of each product on each system that will participate in the MIMIX network. For every product, you need the following information: The system security level specified in the QSECURITY system value. This is important for products that function between systems when assessing security requirements. See System security level on page 62 for additional details. The QALWOBJRST system value must be set to *ALWPGMADP or *ALL in order for the software installation and fix installation processes to function correctly. The QLIBLCKLVL system value must be set to 1 on all systems used by MIMIX in order for MIMIX processes to complete successfully. 15

16 Library considerations when installing products Before installing products into a library, consider the following guidelines: Use topic Using best practices to set up a library list on page 17 to ensure your library list is set up properly. Only License Manager is allowed in the LAKEVIEW library. This library name cannot be changed. MIMIX Enterprise and MIMIX Professional cannot be installed in the same library. MIMIX Global can be installed in the same library as MIMIX Enterprise, MIMIX Professional, or in a library by itself. MIMIX dr1 cannot be installed in the same library as MIMIX Enterprise, MIMIX Professional, or MIMIX Global. Do not replicate libraries LAKEVIEW, MIMIXQGPL, VSI001LIB, any MIMIX installation libraries, any MIMIX data libraries, libraries in which Vision Director is installed, or the IFS location /visionsolutions/http/vsisvr. Note: MIMIX is the default name for the MIMIX installation library -- the library in which MIMIX Enterprise or MIMIX Professional is installed. MIMIX data libraries are associated with a MIMIX installation library and have names in the format installation-library-name_x, where x is a letter or number. Do not place user created objects or programs in the LAKEVIEW, MIMIXQGPL, or VSI001LIB libraries or in the IFS location /visionsolutions/http/vsisvr. This includes any programs created as part of your MIMIX Model Switch Framework. If you place such objects or programs in these libraries, they may be deleted during the installation process. Objects that are in these libraries must be placed in a different library before installing software.the one exception is that job descriptions, such as the MIMIX Port job, can continue to be placed into the MIMIXQGPL library. Only user created objects or programs that are related to a MIMIX installation should be placed within a MIMIX installation library or a MIMIX data library. Examples of related objects include user created step programs, user exit programs, and programs created as part of a MIMIX Model Switch Framework implementation. Considerations for changed command defaults Every command is replaced each time a version, update, or service pack (SP) upgrade of the product is applied. Also, if commands are included in cumulative fixes or restricted fixes, the installation process replaces the existing copy of the commands. As a result, any changes you make to default values of commands shipped with MIMIX products and License Manager are not preserved. The one exception to this is the MIMIX command in the product library. Installation processes preserve the value of the Assistance level (ASTLVL) parameter. 16

17 Using best practices to set up a library list Using best practices to set up a library list A library list contains a system portion and a user portion. When modifying a library list, following best practices ensures consistent and predictable results. Best practices dictate that specific libraries must exist in your system library list. Similarly, certain MIMIX-related libraries should not be kept within the system portion of the library list, while other MIMIX-related libraries should not be added to the user portion of the library list. Setting up the system portion of the library list Table 3 lists which libraries must be added to the system portion of the library list, and which libraries must not be added to the system portion. Table 3. Setting up the system portion of the library list Library Add to system portion Do not add to system portion Notes QSYS2 X QSOC X 1 MIMIX-installation-library X 2 LAKEVIEW QTEMP MIMIXQGPL X X X 1. Used for OptiConnect/400 only. 2. Indicates the library in which MIMIX is installed. Procedure for adding libraries to the system library list Do the following to add the appropriate library to the system library list: 1. On a command line, type WRKSYSVAL SYSVAL(QSYSLIBL). The Work with System Values display appears. 2. Type option 2 next to the QSYSLIBL system value and press Enter. The Change System Value display appears. 3. Add the appropriate library and Press Enter. Setting up the user portion of the library list Table 4 lists which libraries must be added to the system portion of the library list, and which libraries must not be added to the user portion of the library list. Table 4. Setting up the user portion of the library list Library Add to user portion Do not add to user portion Notes QTEMP X 17

18 Table 4. Setting up the user portion of the library list Library Add to user portion Do not add to user portion Notes LAKEVIEW X 1 MIMIXQGPL X 1 1. For these libraries, the best practice is to add the library to the job s library list as needed. Alternatively, you can qualify the command name with the library name when calling a command from within the library. 18

19 Displaying a product s install history and installed fixes Displaying a product s install history and installed fixes Do the following to determine the level of an installed product and identify any installed fixes: 1. From the License Manager Main Menu, select option 2 (Work with Products) and press Enter. See Accessing the License Manager Main Menu on page From the Vision Solutions Installed Products display, type a 13 (Display history) next to the product and library that you want and press Enter. 3. The Display MIMIX Product History display appears with a list of updates made to the product in the library. The updates listed identify when product updates were performed. 4. To check for when any fixes were installed, press F9 (Fixes). 5. The Work with Installed Fixes display appears with a list of fixes that have been applied to the product in the library indicated. To see when the fix was installed, press F11 (Date/Time). To see a description of a fix, type a 5 (Display Description) next to the fix you want and press Enter. 19

20 Working with MIMIX commands Several procedures in this document instruct you to use MIMIX commands. You must either library-qualify each MIMIX command or add the library to a library list from which all MIMIX commands will run in a given session. Library-qualifying a command - If you know the name of the MIMIX installation you want, you can use the name to library-qualify each command, as follows: Type the command library-name/mimix-command and press Enter. Adding a library to the library list - If you do not know the name of the MIMIX installation or would like to run multiple commands from a specific library in one session, do the following: 1. Type the command LAKEVIEW/WRKPRD and press Enter. 2. Type a 9 (Display product menu) next to the product in the library you want on the Vision Solutions Installed Products display and press Enter. 3. Until the session is ended or you exit from the product s main menu, you can run any MIMIX command for that installation without library-qualifying it first. 20

21 CHAPTER 2 Install process checklists This chapter provides checklists that guide you through the steps for different types of software installs using the 5250 emulator. MIMIX Installation Wizard recommended: These checklists and the installation procedures in this book (Using License Manager) are considered secondary path procedures. It is strongly recommended that you use the MIMIX Installation Wizard to install products. License Manager uses the same installation process for new installs, upgrades, and service packs. The naming convention reflects these in its V, U, and SP portions. During the installation process, all products in an installation library are refreshed. Cumulative and restricted fixes provide changes to correct a specific problem and are released on an as-needed basis only. They do not refresh the entire product, and are reflected by the FX(R) portion of the naming convention. For related information, see Understanding product naming conventions on page 12. The checklists included are: Checklist: new product installs on page 22 will guide you through the steps of installing a new installation of MIMIX. Checklist: upgrading products on page 24 will guide you through the steps to upgrade an existing MIMIX installation. Checklist: fix installs on page 25 will guide you through the steps of installing fixes for an existing MIMIX installation. 21

22 Checklist: new product installs If you cannot use the MIMIX Installation Wizard, follow this checklist to install products into a library on a system for the first time. For related information, see Understanding product naming conventions on page 12 and Software requirements for installing or upgrading on page 14. To perform a new install of a product, do the following on all participating systems: 1. Display the contents of the system library list by typing the command DSPSYSVAL SYSVAL(QSYSLIBL) and pressing Enter. Verify that the IBM-supplied library QSYS2 is in the system library list. If you are using OptiConnect/400, also verify that the QSOC library is in the system library list. If necessary, add the appropriate library to the system library list using Using best practices to set up a library list on page Refer to the Readme documentation associated with the release to which you are upgrading. Perform any special Before Installing instructions required. 3. Install a product from streamfile (STMF) or CD using the instructions in Installing products on page Refer to the Readme documentation associated with the release to which you are upgrading. Perform any special After Installing instructions required. 5. If you received cumulative or restricted fixes, install them using the instructions in Installing fixes on page After you have installed the products, sign off the system. 7. Sign back on to the system. 8. Do the following to secure your environment: a. To protect the system from misuse, turn on product-level security. Use the procedure Changing product-level security on page 70. b. Control access to products through the use of authorization levels for user profiles. Grant authority to user profiles as necessary using the procedure Changing product authority on page Configure the product according to the appropriate checklists in the MIMIX Administrator Reference book. 10. Start the product according to its startup procedures in the MIMIX Operations book. 11. Start the Vision Solutions Portal using Setting up Vision Solutions Portal on page If you use the Vision Solutions plug-in for the IBM Systems Director Navigator for i5/os you must end and restart the HTTP Administration Server. Check with your i5/os administrator before doing the following: a. End the server using the following command: ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) 22

23 Checklist: new product installs b. Confirm that all jobs in the QHTTPSVR subsystem have ended by using the command: WRKACTJOB SBS(QHTTPSVR) c. Start the server using the following command: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) d. Ensure that the ADMIN2 job in the QHTTPSVR subsystem is started before attempting to access the Vision Solutions plug-in. WRKACTJOB SBS(QHTTPSVR) 23

24 Checklist: upgrading products If you cannot use the MIMIX Installation Wizard, follow this checklist to upgrade products on a system. This checklist is valid for version, update, and service pack (SP) upgrades. For related information, see Understanding product naming conventions on page 12 and Software requirements for installing or upgrading on page 14. To upgrade a product, do the following on all participating systems: 1. Display the contents of the system library list by typing the command DSPSYSVAL SYSVAL(QSYSLIBL) and pressing Enter. Verify that the IBM-supplied library QSYS2 is in the system library list. If you are using OptiConnect/400, also verify that the QSOC library is in the system library list. If necessary, add the appropriate library to the system library list using Using best practices to set up a library list on page Refer to the Readme documentation associated with the release to which you are upgrading. Perform any special Before Installing instructions required. 3. Prepare for the upgrade by ending products using Prepare your environment by ending products on page Install the product on a system using the instructions in Installing products on page Refer to the Readme documentation associated with the release to which you are upgrading. Perform any special After Installing instructions required. 6. If you received cumulative or restricted fixes, install them using the instructions in Installing fixes on page After you have updated all the installations you want, sign off the system. 8. Sign back on to the system. 9. Do the following to secure your environment: a. To protect the system from misuse, turn on product-level security. Use the procedure Changing product-level security on page 70. b. Control access to products through the use of authorization levels for user profiles. Grant authority to user profiles as necessary using the procedure Changing product authority on page Start up your environment again using Bring up your environment by starting products on page

25 Checklist: fix installs Checklist: fix installs If you cannot use the MIMIX Installation Wizard, follow this checklist to apply fixes to your installed MIMIX products. Cumulative and restricted fixes are provided on an asneeded basis. A cumulative fix is also integrated into the next service pack (SP) for that product. License Manager provides the interface for working with fixes for all MIMIX products. Use the procedures in this section to install cumulative fixes and restricted fixes. Also refer to Understanding product naming conventions on page 12. To install a fix, do the following on all participating systems: 1. Refer to the Readme documentation associated with the release to which you are upgrading. Perform any special Before Installing instructions required. 2. Prepare for the upgrade by ending products. Use the procedure Prepare your environment by ending products on page Install the fix using Installing fixes on page Refer to the Readme documentation associated with the release to which you are upgrading. Perform any special After Installing instructions required. 5. After you have installed the fix, sign off the system. 6. Sign back on to the system. 7. Start up your environment again using Bring up your environment by starting products on page

26 Supporting procedures CHAPTER 3 Supporting procedures This chapter contains the procedures referenced by steps in the checklists for new installs, upgrades, and fix installs. Use these topics as directed by the checklist appropriate for your install type. The chapter also includes additional topics associated with adding or removing software. The following topics are included: Prepare your environment by ending products on page 27 describes how to end products before installing software. Installing products on page 28 describes how to install software using the 5250 emulator process. This process is used when installing or upgrading a version, update, or service pack. Installing fixes on page 33 describes how to install cumulative or restricted fixes using the 5250 emulator process. Bring up your environment by starting products on page 35 describes what to do to get MIMIX running again following a software install. MIMIX Availability Manager post-install steps on page 39 describes how to restart MIMIX Availability Manager to monitor earlier versions of MIMIX. Adding or removing the Vision Solutions plug-in to IBM Systems Director Navigator on page 40 describes what to do to have MIMIX Availability Manager available as a plug-in within or removed from the IBM Systems Director Navigator for i5/os console. Accessing the License Manager Main Menu on page 41 identifies how to access functions provided by License Manager. Updating the installed products file on page 42 describes how to correct the installed products file when directed to by a CustomerCare representative. Removing an installed product on page 43 describes how to remove an installation of a MIMIX product. 26

27 Prepare your environment by ending products Prepare your environment by ending products This procedure ends products for an installation and is required before upgrading or installing in an environment that currently has products installed. This procedure is valid whether you are installing from the MIMIX Installation Wizard or 5250 emulator. Use this procedure when you are instructed to by procedures in this book or when the MIMIX Installation Wizard prompts you to end MIMIX. If you have multiple product installations and License Manager is not already at the level being installed, the first installation updated will update License Manager as well. Because of this, you should end operations on all installations before installing. Do the following to prepare your environment for the install: Note: For related information about MIMIX commands, see Working with MIMIX commands on page Use the following command on the management system to end all system managers, journal managers, collector services, application groups, data groups, active audits and recoveries, the master monitor and all MIMIX monitors: installation-library/endmmx ENDOPT(*CNTRLD) Note: Based upon your environment and the parameters you specified, it may take some time for the ENDMMX command to complete. Ensure that all your jobs are ended before ending the MIMIX subsystem in Step Repeat Step 1 for each additional MIMIX installation. 3. If you are not using MIMIX to schedule audits, ensure that your scheduling mechanism does not start audits during the installation process. 4. If you use MIMIX Availability Manager, use the following command on any system which hosts an instance of MIMIX Availability Manager: LAKEVIEW/ENDMMXAM INST(name) where name is the name of the instance. The Vision-supplied default instance name is MIMIXAM. 5. Use the following command on all systems to end the MIMIX subsystem: ENDSBS SBS(MIMIXSBS) 27

28 Installing products If you cannot use the MIMIX Installation Wizard, use these procedures to install products from streamfile (STMF) or CD using the 5250 emulator. These steps are valid for new installs or upgrades. For related information, see Understanding product naming conventions on page 12. Starting the install process: Use Step 1 though Step 8 for all new installs and any upgrade (Version, Update, or SP). You only need to perform these steps once per install per system. Do the following: 1. Sign on to the system using the QSECOFR user profile or a user profile that has security officer classification and all special authorities. The end of the installation process automatically generates a job log. By signing on just before starting the installation, you limit the job log to only the installation process. 2. Load the installation media. Do one of the following: If installing from streamfile (STMF), skip to Step 4. If installing from CD, continue with Step Load the CD into the system s optical device. Using the name of the device from which you are installing for device-name, type the command LODRUN DEV(device-name) and press Enter to install it on your system. Then skip to Step Download the STMF for the software you will be installing. 5. Do one of the following to start the INSMMX tool for installing from a stream file: If License Manager exists on the system, type LAKEVIEW/INSMMX and press Enter. If License Manager is not installed on the system, follow the instructions in Starting the INSMMX tool when License Manager is not installed on page 31. You will be directed when to return to this procedure. 6. The Install MIMIX display appears. At the Stream file prompt, specify the name of the STMF you downloaded in Step At the Installation library prompt, most users will use the default value. For more information about this prompt and when other values are allowed, see INSMMX restrictions for specifying the installation library (INSTLIB) on page 31. Do one of the following: Accept the default value, *SELECT, and press Enter. Then continue with Step 8. Specify a library name and press Enter. No additional steps are required. When processing ends, a message is returned indicating success or failure. Installing the product: Use Step 8 through Step 14 to install a product on a system. 8. The Vision Solutions Common Install display appears with a list of products displayed. Do one of the following: 28

29 Installing products To install a new installation of MIMIX, type 1 (Install/upgrade) next to the *NEW line for MIMIX and press Enter. To upgrade an existing MIMIX product, type 1 (Install/upgrade) next to the existing product installation you want and press Enter. Note: When upgrading, only one product within an installation library should be selected for the upgrade. Selecting that product upgrades all products in the installation library. To install or upgrade only License Manager, type 1 (Install/upgrade) next to License Manager and press Enter. Note: You only need to select License Manager when it is the only software you want to install or upgrade. When products are installed or upgraded, License Manager is also installed or upgraded as needed. You do not have to enter a license key when installing only License Manager. 9. If the Vision Solutions License Agreement appears, it is recommended that you read through all pages. Press F16 to accept the agreement. Note: If you decline the agreement (F12), a cancellation message is displayed and you are returned to the Vision Solutions Common Install display. 10. If the License Key Failure display appears, follow the procedures in Obtaining license keys when using 5250 emulator to install on page 50 to get a License Key Package (LKP). Notes: If the LKP contains valid license keys for the product you are installing, the install process continues. If the license keys are not valid, the install process is cancelled. If you do not have version 7 license keys and are performing a new install, the New Install without License Keys display appears. Follow the options provided. Although you can obtain license keys before continuing the install or afterwards, a valid license key is required before attempting to use any product in the library. 11. The Install Lakeview Product (INSLKVPRD) display appears. Do the following: a. Confirm the value of the Product prompt. Note: If you selected a new or existing MIMIX product in Step 8 but the value *LICMGR appears, License Manager will be installed or upgraded first because either the installation process determined it was required or you also selected License Manager. Verify that the values of the prompts on this display are appropriate for License Manager. Pressing Enter will start the install. At the appropriate time, this display will appear again and then you can specify values for the MIMIX product. b. At the Installation library prompt, verify that the value is set correctly. The default library name for new installs is MIMIX. For License Manager, the library is LAKEVIEW. Note: If you will use an INTRA configuration for MIMIX, the name of the first 29

30 library can be up to 9 characters in length. For the second library, the name must be in the form nnnnnnnnni, where nnnnnnnnn is the name of the first library and I identifies it as INTRA. c. At the Keep current configuration data prompt, accept the default value *YES. Otherwise, specify the value you want. d. The value *CRTDFT appears in the Auxiliary storage pool ID prompt. This value uses the command default from the system command Create Library (CRTLIB) to specify the auxiliary storage pool (ASP) from which the system allocates storage for the library. If you need to use a different user ASP, specify the value you want. Note: License and Availability Manager must be installed in ASP1. e. To start the installation process, press Enter. 12. The system checks to see if there are locks on any objects. If locks are found, you will see message LVE1005 Product installation is in use. To determine which objects have locks, refer to message LVE1019 in the job log. 13. Depending on your choice for Step 8, you may see one of the following additional displays. If you selected to install multiple products, the Vision Solutions License Agreement for the next product is displayed. Return to Step 9. If you selected MIMIX but License Manager was installed as a prerequisite and the MIMIX license keys are not present, you will see the License Key Failure display. Return to Step 10 to obtain the keys and continue with the install. If you selected MIMIX but License Manager was installed as a prerequisite and the MIMIX license keys are present, you will see the Install Lakeview Product (INSLKVPRD) display. Return to Step 11 to specify the information for the MIMIX product. 14. When all of the selected products have been installed, the Vision Solutions Common Install display appears and completion message LMC0002 appears at the bottom of the display. For the installed or upgraded installation library, you will see one line on the display for each installed MIMIX product with valid license keys. If valid license keys are not present, you will see only one line for MIMIX until valid license keys are installed. 30

31 Starting the INSMMX tool when License Manager is not installed When using 5250 emulator processes for a new install of MIMIX when License Manager is not installed on the system, you must obtain the INSMMX tool. 1. If you have done so already, download the INSMMX STMF from Support Central and transfer it to your system. 2. From a command line, type the IBM command CPYFRMSTMF and press F4 (Prompt). 3. At the From stream file prompt, enter the name of the stream file you transferred in Step At the To file member or save file prompt, enter the following and press Enter: /QSYS.LIB/QTEMP.LIB/SAVF.FILE Note: This step converts the stream file to the QTEMP/SAVF save file. 5. Type the IBM command RSTOBJ and press F4 (Prompt). 6. At the Objects prompt, specify *ALL. 7. At the Saved library prompt, specify QTEMP. 8. At the Device prompt, specify *SAVF. 9. At the Save file prompt, specify SAVF in library QTEMP. 10. At the Restore to library prompt, specify QTEMP as the name of the library into which the objects should be restored and press Enter. This step restores all the objects from the save file. 11. Type QTEMP/INSMMX and press Enter. Continue with Step 6 in Installing products on page 28. INSMMX restrictions for specifying the installation library (INSTLIB) The Install MIMIX (INSMMX) command allows you to start the installation process for MIMIX software. When using this command, be aware of the following restrictions and conditions, which apply to the Installation Library (INSTLIB) prompt: Specifying the default, *SELECT, allows you to display the list of product libraries from which to select on the INSMMX command. You must choose this option if any of the following conditions apply: You are upgrading to a higher Version number (V) or a higher Update level (U). You are adding a new product to a library. You are installing a lower Service pack (SP) on an existing installation. You do not want to retain configuration data during the install. In this case, you must also specify KEEPCFG(*NO) for Step 11c in Installing products on page 28. Specifying a name for the installation library allows you to install the product update into the specified library without additional user intervention. This option is 31

32 valid only when the following conditions apply: You are installing the same level or a higher level of a product. You do not have any license key issues that would prevent the install. It is acceptable to refresh all products within the installation library. 32

33 Installing fixes Installing fixes You can choose specific fixes to install or you can install all fixes from the media to the product library you specify. You must repeat this procedure for each system in the installation in which you need to apply the fix. Note: Before performing this procedure, complete the steps in Checklist: fix installs on page 25. Do the following to install a cumulative or restricted fix: 1. Sign off the system to ensure that library QTEMP is appropriately cleared and that the installation library does not exist in the library list of the job prior to running the command in Step Sign on the system using the QSECOFR user profile or a user profile that has the same security officer classification and all special authorities. 3. Load the installation media. Do one of the following: If installing from stream file (STMF), skip to Step 5. If installing from CD, continue with Step Load the CD into the system s optical device. Using the name of the device from which you are installing for device-name, type the command LAKEVIEW/INSMMX STMF( /QOPT/MIMIX/MIMIX.STM )and press Enter. Skip to Step Download and transfer the STMF to your system. 6. Type LAKEVIEW/INSMMX and press Enter. 7. The Install MIMIX display appears. At the Stream file prompt, specify the name of the STMF you downloaded in Step At the Installation library prompt, specify whether or not to display a list of libraries containing products from which you can select to install the product update. See the information provided in INSMMX restrictions for specifying the installation library (INSTLIB) on page 31. Do one of the following: Specify a library name and press Enter. In this case, no additional steps are required. A message is returned indicating success or failure. Specify the default, *SELECT and press Enter. Continue with Step The Vision Solutions Common Install display appears with a list of products displayed. 10. You should repeat the following steps for every product in the installation library for which the value FIXES appears in the Version on Media column. a. To select a product that has available fixes, type a 1 in the Opt column next to the product and library and press Enter. b. The Vision Solutions Fix Installation display appears with a list of the fixes available on the media. Type a 1 in the Opt column next to the fixes that you want to apply. 33

34 If the media contains a fix that is already installed, the value *YES appears in the Installed column. If the fix is not superseded by another fix, you can install the fix again. If the value *SUP appears in the Installed column, a fix is installed and has been superseded by another installed fix. You cannot reinstall a superseded fix. c. Press Enter. The items you selected are applied to all products in the library you selected. 11. After you have updated all desired installations with the fix, sign off the system. 12. Sign back on to the system. 34

35 Bring up your environment by starting products Bring up your environment by starting products Perform the following procedure after you have successfully installed products on all systems. This procedure is valid whether you are installing from the MIMIX Installation Wizard or 5250 emulator. Do the following to bring up your environment after the install: Note: For related information about MIMIX commands, see Working with MIMIX commands on page Use the following command to start the MIMIX subsystem on all systems: STRSBS SBSD(MIMIXQGPL/MIMIXSBS) 2. Ensure that your communications servers are started on all systems. Use the WRKACTJOB SBS(MIMIXSBS) to confirm that ports have been started by any autostart jobs. If necessary, start the servers. For example, use the following command for TCP: installation-library/strsvr HOST(system) PORT(nnnn) 3. On each installation, use the following command on the management system to start all system managers, journal managers, collector services, application groups, and data groups: installation-library/strmmx 4. Repeat Step 2 and Step 3 for each additional MIMIX installation. 5. As needed, make any known configuration changes on any installation that was upgraded. 6. If you use Vision Solutions Portal, do the following: a. To make the latest MIMIX portal application known to the VSP server, enter the command VSI001LIB/ADDVSIAPP. When the Add Vision Solutions App. (ADDVSIAPP) display appears, specify MIMIX in the Portal application prompt and press Enter. b. Start the Vision Solutions Portal server using the command: VSI001LIB/STRVSISVR Note: If the server has not been previously installed, use Setting up Vision Solutions Portal on page If you plan to continue to use MIMIX Availability Manager to manage installations running earlier versions, follow the procedures described in MIMIX Availability Manager post-install steps on page If you use the Vision Solutions plug-in for the IBM Systems Director Navigator for i5/os you must end and restart the HTTP Administration Server. Check with your i5/os administrator before doing the following: a. End the server using the following command: ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) b. Confirm that all jobs in the QHTTPSVR subsystem have ended by using the command: 35

36 WRKACTJOB SBS(QHTTPSVR) c. Start the server using the following command: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) d. Ensure that the ADMIN2 job in the QHTTPSVR subsystem is started before attempting to access the Vision Solutions plug-in. WRKACTJOB SBS(QHTTPSVR) 9. Check your MIMIX status using the information provided in the Using MIMIX book. 36

37 Setting up Vision Solutions Portal Setting up Vision Solutions Portal The Vision Solutions Portal server enables the use of portal applications for MIMIX and other Vision Solutions products. Portal applications provide enhanced web-based user interfaces to Vision Solutions products. Vision Solutions portal application packages are typically restored during the installation of Vision Solutions products. Notes: When the MIMIX Installation Wizard is used MIMIX is used to instal MIMIX, the Vision Solutions Portal (VSP) and the MIMIX portal application are automatically installed. You can use this procedure to start the server and set up your environment beginning at Step 4. When 5250 emulator processes are used to install or upgrade MIMIX, the VSP server is not installed even though the portal application has been restored on the system. You must use the Vision Solutions Portal Installation Wizard to install or upgrade the server. To install or upgrade the VSP server and start the Vision Solutions Portal, begin with Step 1. If you upgraded MIMIX and the existing version of Vision Solutions Portal is compatible, perform Step 3 through Step 6 to make the latest MIMIX portal application known to the server. The requirements for using the Vision Solutions Portal Installation wizard, as well as runtime requirements for using Vision Solutions Portal, are described in the Getting Started with Vision Solutions Portal book. Do the following: 1. Download the Vision Solutions Portal Installation Wizard from Support Central. 2. Use the VSP wizard to install or upgrade Vision Solutions Portal on the node you want. Note: Install the server on any IBM i node in your network that can communicate with the nodes where MIMIX is installed. Installing the server on a second node is recommended for high availability.the wizard installs the 7VSI001 LPP *BASE and option 13 into library VSI001LIB if they are not installed on the system. Vision Solutions Portal server software and product portal applications are stored on the system at IFS location /visionsolutions/http/vsisvr. 3. The MIMIX install process stored the MIMIX portal application on the system IFS location /visionsolutions/http/deploy. Do the following to make the MIMIX portal application known to the VSP server: a. Enter the command: VSI001LIB/ADDVSIAPP b. The Add Vision Solutions App. (ADDVSIAPP) display appears. At the Portal application prompt, type MIMIX. c. Press Enter. 4. Start the server using the command: VSI001LIB/STRVSISVR 37

38 The default port is Each instance of the server uses three consecutive ports. If you cannot use this port, go to the Getting Started with Vision Solutions Portal book instructions on changing the port number and other information. 5. Enter the following case-sensitive URL in your web browser to access the Log In page: 6. Log in using your IBM i user ID and password. After you have logged in, the portal opens to the Home page. 7. A default portal connection exists for the node on which you logged in. If you are hosting the VSP portal server on a different node than where MIMIX is installed, or if you want redundancy for your instance, do the following to configure additional portal connections: a. From the Portal Connections portlet, select Add. b. The Add Portal Connection dialog opens. Specify a name for the node used for this portal connection, the Host name or IP address of the node, the user ID to use to connect to the node, password preferences, and a description of the connection. Then click OK. 8. Configure an instance of MIMIX. From the Instances portlet, select Add. The wizard will prompt you to identify a portal connection, the MIMIX product library that you want to manage, and the instance domain. The instance domain defines the association between the portal connection and the nodes (system definitions (SYSDFN)) within the MIMIX product library. When the instance is added, you will see the instance name and status appear in the navigation area. For more information see the Getting Started with Vision Solutions Portal book. 38

39 MIMIX Availability Manager post-install steps MIMIX Availability Manager post-install steps If you use MIMIX Availability Manager to monitor earlier versions of MIMIX installations, perform this procedure to set up MIMIX Availability Manager after you have successfully installed MIMIX. 1. If necessary, change the default port setting. Use the procedure in the topic Changing the port number used by MIMIX Availability Manager on page Start MIMIX Availability Manager. See Starting MIMIX Availability Manager on page After installing and starting MIMIX Availability Manager, enter the following casesensitive URL in your web browser to open the Welcome page: 4. From the Welcome page, do the following: a. If this is a new install and you are using MIMIX IntelliStart, select Log In to MIMIX IntelliStart to begin using MIMIX IntelliStart. b. Select Log In to begin using MIMIX Availability Manager. This is only possible if MIMIX Availability Manager was previously installed at version If this is a new install, customize and enhance MIMIX Availability Manager as needed. It is recommended that you enable the MIMIX Switch Assistant and change your time zone properties. Use the subtopics provided in About MIMIX Availability Manager on page 99. Note: If you experience install-related problems after performing this procedure, see Locks on files on page 126. If ENDMMXAM was not run or completed prior to the install, residual locks may exist. 39

40 Adding or removing the Vision Solutions plug-in to IBM Systems Director Navigator Vision Solutions, Inc. provides a plug-in for the IBM Systems Director Navigator for i5/os. The Vision Solutions plug-in automatically appears as a task category under i5/os Management on the IBM Systems Director Navigator for i5/os console in release 6.1 or higher. When selected, a Vision Solutions tab opens within the console. Portlets on the Vision Solutions tab provide access to MIMIX Availability Manager and other information about installed MIMIX products from Vision Solutions. If you want to remove the plug-in from IBM Systems Director Navigator or re-install the plug-in if it was removed, do the following: 1. From the system on which you log in to IBM Systems Director Navigator, do one of the following: To remove the plug-in, enter the command: LAKEVIEW/RMVDIRVSIP To add the plug-in, enter the command: LAKEVIEW/ADDDIRVSIP 2. Check with your IBM i administrator before performing this step. The change to IBM Systems Director Navigator is effective the next time the HTTP Administration Server is started. To restart the server now, do the following: a. End the server using the command: ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) b. Start the server using the command: STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) 40

41 Accessing the License Manager Main Menu Accessing the License Manager Main Menu Do any of the following to access the License Manager Main Menu: Type LAKEVIEW/LICMGR and press Enter. Select option 31 (Product management menu) from the MIMIX Main Menu. 41

42 Updating the installed products file The installed products file is a file within License Manager that tracks what MIMIX products are installed on the system. If your MIMIX product libraries or License Manager are inadvertently deleted, a CustomerCare representative may direct you to perform this procedure. 1. Type the command LAKEVIEW/UPDINSPRD and press F4 (Prompt). 2. At the Library prompt, specify the name of the library you want to update or specify *ALL to update all product libraries on the system. 3. To start the update, press Enter. License Manager updates the list of products on the system and verifies that the product libraries in the installed product file exist. 42

43 Removing an installed product Removing an installed product The following describes how to remove a product from a system. This process removes the product from the library and removes any associated data libraries for the product. Notes: If you need a batch-capable command for this function, use the Delete Product (DLTPRD) command in the LAKEVIEW library. In any environment, you should delete the product from the associated library on each system. Do the following to remove an installed MIMIX product: 1. Before you remove a product, ensure that the product has been shut down. Refer to Prepare your environment by ending products on page 27 for a description of this operation. 2. Verify that all users have exited from the product interfaces, including menus, commands, and displays. 3. The library that you want to delete cannot be in the library list of any active user profiles if you intend to delete the library as well. Check the locks on the product library before you attempt to remove the product. 4. From the License Manager Main Menu, select option 2 (Work with Products) and press Enter. 5. The Vision Solutions Installed Products display appears. Type a 4 (Uninstall) next to the product library that you want to remove and press F4 (Prompt). 6. To delete the library as well as the product you selected, specify *YES at the Delete library prompt and press Enter. When deleting multiple products in a library, the last product removed deletes the library if *YES is specified. 7. The Confirm Uninstall of Product display appears. Press Enter to remove the product. 43

44 Working with license keys CHAPTER 4 Working with license keys License keys control which product functions you are able to use. Before you can configure any MIMIX product, you must enter a unique license key on each of the systems on which the product is installed. License keys can be obtained through the MIMIX Installation Wizard, the 5250 emulator installation process, or the Update License Keys (UPDLICKEY) command. The preferred method to use is the Vision AutoValidate through the MIMIX Installation Wizard, which allows you to easily and automatically obtain and apply license keys. All methods of obtaining license keys involve two basic processes. First, required system information is gathered and packaged into a License Request Package (LRP) and sent to the Vision Solutions portal. Second, the Vision Solutions portal generates a License Key Package (LKP), which is applied to your systems. When using Vision AutoValidate through the MIMIX Installation Wizard, these steps are automatically done for you. Note: If you are performing an upgrade to version 7, you must obtain license keys during the upgrade process. This chapter includes the following topics: Information about license keys and identifiers on page 45 identifies the two character product prefix used in license keys. Obtaining license keys through MIMIX Installation Wizard on page 47 describes how the wizard uses Vision AutoValidate to obtain and apply license keys. This topic also includes instructions for how to obtain license keys manually so they can be applied while using the MIMIX Installation Wizard. Obtaining license keys using UPDLICKEY command on page 49 describes an alternative method of obtaining and applying license keys through the 5250 emulator. Obtaining license keys when using 5250 emulator to install on page 50 describes how to obtains keys if you are installing using the 5250 emulator and the installation process indicates that you do not have a valid license key. Displaying maintenance expiration and license key information on page 51 describes how to see when your current maintenance agreement expires and when the product will stop working. Changing or displaying license key expiration message defaults on page 52 describes how to view or change the number of days at which MIMIX will begin sending warning messages that MIMIX license keys are about to expire. 44

45 Information about license keys and identifiers Information about license keys and identifiers To enable products or particular functionality within products, a 37-character license key is required. This applies in all cases: using AutoValidate to obtain license keys through the MIMIX Installation Wizard, updating license keys through the 5250 emulator installation process, or using the Update License Keys (UPDLICKEY) command. License keys begin with a product identifier followed by a set of characters and hyphens, for example: H1-nnnnnn-nnnnnn-nnnnnn-nnnnnn-nnnnnn. Hyphens are a required part of the license key when entering them. Table 5 provides a list of valid MIMIX product identifiers. Table 5. License key product identifiers Product identifier Name Description Notes H1 MIMIX Enterprise MIMIX Enterprise includes MIMIX, MIMIX Monitor, and MIMIX Promoter HT MIMIX Professional MIMIX Professional includes MIMIX and MIMIX Monitor C1 MIMIX Global Multi-management support. Requires either MIMIX Enterprise or MIMIX Professional. MC MIMIX Global - IASP Edition Support for switchable independent auxiliary storage pool (IASP) technologies. C3 MIMIX Global - SAN Edition Support for SAN high availability technologies. D1 MIMIX dr1 M4 MIMIX DB2 Replicator MIMIX DB2 Replicator is one of the two components of MIMIX 1 MO MIMIX Object Replicator MIMIX Object Replicator is one of the two components of MIMIX 1 MM MIMIX Monitor 1 MP MIMIX Promoter 1. These license keys are issued only when a subset of the MIMIX Enterprise or MIMIX Professional product is authorized. Most users will receive MIMIX Enterprise or MIMIX Professional license keys. 45

46 Table 6 provides a list of valid MIMIX feature identifiers. A feature is defined as functionality within a product that requires a unique and separate license key from the product in which it is contained. Table 6. License key feature identifiers Feature identifier Name Description MZ MIMIX Optimization Vision Director MIMIX Edition R3 MIMIX for SAP R/3 MIMIX for SAP R/3 for IBM Power TM Systems WQ MIMIX for MQ MIMIX for IBM WebSphere MQ 46

47 Obtaining license keys through MIMIX Installation Wizard Obtaining license keys through MIMIX Installation Wizard To prevent users from having to request and enter license keys manually, functionality within MIMIX Installation Wizard automatically obtains and applies new license keys through Vision AutoValidate. The MIMIX Installation Wizard uses Vision AutoValidate to collect the required system information and package it in a License Request Package (LRP). Using the MIMIX Installation Wizard to obtain and apply license keys requires the coordination between the system, MIMIX Installation Wizard, and Support Central. As such, it is possible that your environment may prevent these tools from working properly. Common restrictions include firewall issues or lack of an Internet connection. If Vision AutoValidate cannot complete, an error notification appears within the wizard and the process needs to be completed manually. Note: If you experience problems during this process, follow the instructions provided in Manually obtaining and applying license keys using MIMIX Installation Wizard on page 47. Manually obtaining and applying license keys using MIMIX Installation Wizard You must use this procedure in the event that Vision AutoValidate cannot complete through the MIMIX Installation Wizard. If Vision AutoValidate cannot complete, an error dialog appears. MIMIX Installation Wizard collects the required system information and packages it in a License Request Package (LRP) on your PC. MIMIX Installation Wizard then displays the location of this LRP that you need to upload to the Vision Solutions Portal. Do the following: 1. Make note of the LRP name displayed and transfer the file to a PC capable of communicating with the Internet. 2. On that PC, bring up the Vision Solutions portal at 3. Log in to the portal using your Support Central login information. 4. The LRP Upload page appears. At Upload License Request Packages, click Browse to navigate to the location of your LRP. 5. Select the LRP file and click Open. 6. Click Add. 7. At Generate License Keys, click Generate license keys to generate your LKP. 8. At Download License Key Package, click Download LKP to save the LKP to your PC. 9. Transfer the LKP from the PC where it was downloaded to the PC running the 47

48 MIMIX Installation Wizard. 10. On the MIMIX Installation Wizard dialog, you are prompted for the location of the LKP you saved. The MIMIX Installation Wizard will validate and apply the license keys within the LKP and continue automatically if the license keys are valid. 48

49 Obtaining license keys using UPDLICKEY command Obtaining license keys using UPDLICKEY command The Update License Keys (UPDLICKEY) command provides an alternative method of obtaining and applying license keys through the 5250 emulator. Do the following: 1. On each system for which you want to obtain license keys, do the following: a. From the License Manager Main Menu, select option 1 (Update license keys) and press Enter. b. The Update License Keys (UPDLICKEY) command appears. Press Enter. c. The Update License Keys (UPDLICKEY) display appears, which describes how to obtain license keys. Make note of the LRP name displayed and transfer the file to a PC capable of communicating with the Internet. 2. On that PC, bring up the Vision Solutions portal at 3. Log in to the portal using your Support Central login information. 4. The LRP Upload page appears. At Upload License Request Packages, click Browse to navigate to the location of your LRP. 5. Select the LRP file and click Open. 6. Click Add. 7. At Generate License Keys, click Generate license keys to generate your LKP. 8. At Download License Key Package, click Download LKP to save the LKP to your PC. 9. Transfer the LKP from your PC to the system. It is recommended that you save it into the /VisionSolutions/LicenseKeys directory on your system. Make note of the full path name while saving. 10. Press F16 (Continue) on the Update License Keys wizard panel. The Apply License Keys (APYLICKEY) display appears. 11. At the LKP path and file name prompt, specify the location of the LKP file you saved in Step 9 and press Enter. The License Manager Main Menu reappears. 12. You should see message LVI0902 that indicates the change was complete. Note: If you see error message LVE100B, position the cursor on the message and press F1 (Help) to see information about the cause of the error. 49

50 Obtaining license keys when using 5250 emulator to install If you are performing an install using the 5250 emulator and you do not have a valid license key, the License Key Not Valid display appears. See Step 10 in Installing products on page 28. In this case, you will have to follow these instructions for obtaining and applying license keys. Do the following: 1. When the License Key Not Valid display appears, it describes how to obtain license keys. For each system on which the License Key Not Valid display appears during the install process, make note of the LRP name displayed and transfer the file to a PC capable of communicating with the Internet. 2. On that PC, bring up the Vision Solutions portal at 3. Log in to the portal using your Support Central login information. 4. The LRP Upload page appears. At Upload License Request Packages, click Browse to navigate to the location of your LRP. 5. Select the LRP file and click Open. 6. Click Add. 7. At Generate License Keys, click Generate license keys to generate your LKP. 8. At Download License Key Package, click Download LKP to save the LKP to your PC. 9. Transfer the LKP from your PC to the system. It is recommended that you save it into the /VisionSolutions/LicenseKeys directory on your system. Make note of the full path name while saving. 10. Press F16 (Continue) on the Update License Keys panel. The Apply License Keys (APYLICKEY) display appears. 11. At the LKP path and file name prompt, specify the location of the LKP file you saved in Step 9 and press Enter. The License Manager Main Menu reappears. 12. You should see message LVI0902 that indicates the license keys were applied successfully. Note: If you see error message LVE100B, position the cursor on the message and press F1 (Help) to see information about the cause of the error. 50

51 Displaying maintenance expiration and license key information Displaying maintenance expiration and license key information The Change License Key (CHGLICKEY) display allows you to display the product expiration date and maintenance expiration date from the license key. The product expiration date provides information about when the product will stop working and the maintenance expiration date is helpful when upgrading, as upgrades are only valid if you are current on maintenance. Do the following: 1. From a command line, type LAKEVIEW/CHGLICKEY and press F4 (Prompt). 2. The Change License Key command appears. Specify the value for the product or feature you want in the Product prompt. Press Enter. 3. The Expiration date and Maintenance expiration date are displayed for the license key for the product or feature. 4. The License key prompt displays the license key that was used for this product or feature. 51

52 Changing or displaying license key expiration message defaults Each MIMIX product is shipped with default values for notification of expiring license keys. To display or change the number of days that License Manager should begin sending warning messages about license key expiration, do the following: 1. From a command line, type LAKEVIEW/CHGLMMSG and press F4 (Prompt). 2. The Change License Manager Messaging display appears. Specify the value you want for the Product prompt and press Enter. 3. The Change License Manager Messaging display appears. The values displayed are the current settings for all libraries that contain this product. 4. To change the license key expiration message default values for all installation libraries containing the specified product, do the following: a. For the Enable message handling prompt, specify whether to send warning messages to the specified message queues when the license key is about to expire. b. For the Enable on new license key prompt, specify whether to enable message handling when the license key is updated. c. Specify the number of days before expiration to begin sending warning messages in the Days before expiration prompt. d. Specify the name and library of the primary message queue to which to send warning messages. e. Specify the name and library of the secondary message queue to which to send messages. If you do not want to have messages sent to a secondary message queue, specify *NONE and press Enter. 52

53 CHAPTER 5 General security considerations The following sections describe security provided within the IBM i operating system. Most commands run under the MIMIXOWN user profile, which is enabled with *ALLOBJ authority. It is important to pair IBM i security with the security functions provided by License Manager, as described in Vision Solutions-provided security functions on page 64. This chapter includes the following topics: Security for MIMIXOWN and MIMIXCLU user profiles on page 54 identifies the minimum security requirements for the MIMIXOWN user profile provided with MIMIX products. Security for LAKEVIEW user profile on page 59 identifies the minimum security requirements for the LAKEVIEW user profile provided with License Manager. Additional security considerations on page 60 identifies additional considerations for multi-system environments, special authority requirements for environments that use clustering support within MIMIX or MIMIX Global, and restrictions on user profiles. System security on page 62 describes considerations for the QSECURITY, QALWUSRDMN, and QPWDLVL system value. Protecting your assets from unauthorized use on page 63 describes additional practices that can help you protect your environment. 53

54 Security for MIMIXOWN and MIMIXCLU user profiles This information describes the minimum security requirements for the MIMIXOWN and MIMIXCLU user profiles provided with MIMIX products. Each enterprise is unique. Your enterprise may require exceptions to the information provided here. Note: The MIMIXCLU user profile is created when the first application group which specifies *CLU for the application group type is created. The MIMIXOWN user profile and the MIMIXCLU user profile are created with an initial menu of *SIGNOFF so that they cannot be used to sign on to the system, as well as a preset password so that it is consistent on all systems. The MIMIXOWN user profile owns all of the objects in the MIMIX library and has access to all the objects that make up each of the MIMIX products. All processes for MIMIX products run under the MIMIXOWN user profile. User interface objects, such as commands, command processing programs, display panels, menus, and help, have a public authority (*PUBLIC) of use (*USE). All product user interfaces are protected by the product-level security provided by Vision Solutions when that function is set to "On". The MIMIXOWN user profile and the MIMIXCLU user profile are created by default as a security officer class (*SECOFR) user profile with all special authorities, including all object authority (*ALLOBJ). The MIMIXOWN user profile needs this level of authority to access information needed for MIMIX products to perform their operations. The MIMIXOWN system directory entry is required for DLO replication and should not be removed. Note: *ALLOBJ authority is a very useful authority but it must be used with care because it leaves your system vulnerable to misuse. Protecting your assets from unauthorized use on page 63 describes considerations for changing this authority. Table 7 identifies the special authorities for user profiles and the operations for which the MIMIXOWN and MIMIXCLU user profiles require a special authority. 54

55 Security for MIMIXOWN and MIMIXCLU user profiles Table 7. Special Authority *ALLOBJ MIMIX operations that require special authorities MIMIX operations that require special authority In MIMIX DB2 Replicator this authority is needed to access all database files (*FILE) defined to MIMIX, including those defined for cooperative processing, and to create, delete, and alter a variety of object types used in replication. In MIMIX Object Replicator, if you replicate user profiles (*USRPRF objects) the MIMIXOWN user profile must have all the special authorities of the profiles being replicated. If you attempt to replicate a user profile that has a special authority not available to the MIMIXOWN user profile, MIMIX cannot grant the authority to the replicated profile, causing a failed request. This authority is needed for MIMIX Monitor, so that it has access to all objects that will be monitored, such as journals and message queues, the job scheduler, and any interface exit programs, condition programs, and event programs called by the monitor. See MIMIX Monitor security considerations on page 57. In MIMIX Promoter, the MIMIXOWN user profile is the default for submitting jobs, which may require the creation of temporary journaling environments. If you use another user profile to submit jobs see MIMIX Promoter security considerations on page 58. *AUDIT MIMIX Object Replicator requires *AUDIT authority on the MIMIXOWN user profile to change object auditing on defined objects to properly replicate them. Not required for MIMIX DB2 Replicator, MIMIX Monitor, or MIMIX Promoter. *IOSYSCFG Required for all MIMIX products if you are using TCP/IP as the transfer protocol between systems. Required for MIMIX Object Replicator if you are replicating line descriptions (*LIND), controller descriptions (*CTLD), device descriptions (*DEVD), or mode descriptions. (*MODD). Required for cluster resource service APIs, needed by MIMIXCLU. *JOBCTL *SAVSYS Required for all MIMIX products. MIMIX uses spooled files (*SPLF) in its processing and requires job control for spool file manipulation. Required for both MIMIX products. MIMIX DB2 Replicator uses save and restore operations in the processing of the SYNCDGFE command. MIMIX Object Replicator uses save and restore operations to replicate many object types. Not required for MIMIX Monitor or MIMIX Promoter. 55

56 Table 7. Special Authority *SECADM MIMIX operations that require special authorities MIMIX operations that require special authority Required for MIMIX Object Replicator if you are replicating user profiles (*USRPRF), documents (*DOC), or folders (*FLR). Not required for MIMIX DB2 Replicator, MIMIX Monitor, or MIMIX Promoter. *SERVICE Required for MIMIX Object Replicator if you are replicating user profiles (*USRPRF). Not required for MIMIX DB2 Replicator, MIMIX Monitor, or MIMIX Promoter. *SPLCTL Required for all MIMIX products. MIMIX uses spooled files in its processing. The following sections describe special authority considerations for specific MIMIX functions or when using MIMIX in certain environments. 56

57 MIMIX Monitor security considerations Monitors within MIMIX Monitor run under the MIMIXOWN user profile which is shipped with special authority to all objects (*ALLOBJ). When you create a monitor, the user profile creating that monitor must have authority to the interface exit program, condition program, or event program that is defined to the monitor MIMIX Monitor. *ALLOBJ authority is needed for MIMIX Monitor so that it has access to all objects that will be monitored, such as journals and message queues, the job scheduler, and any interface exit programs, condition programs, and event programs called by the monitor. If you are using MIMIX Switch Assistant or a MIMIX Model Switch Framework to switch the direction of replication and you changed the authority level of the MIMIXOWN user profile, the MIMIXOWN user profile needs to be granted explicit authority to the following: Any custom user programs. All MIMIX libraries to be switched. Any communications configurations to be switched. Change authority (*CHANGE) to the output queues of user profiles submitting switching commands so that MIMIX can write to spooled files. 57

58 MIMIX Promoter security considerations MIMIX Promoter requests to copy or reorganize a file are submitted using the default job description from MIMIXOWN. The MIMIXOWN user profile has *ALLOBJ authority. If you specify a different user profile when you submit copy or reorganize requests, consider the following: Does the user profile you will use for submitting copy or reorganize requests have adequate authority? If you change the job description, the user profile used to submit requests must have sufficient authority to work with the file and, if needed, to create and delete a journaling environment. For reorganize file requests, the submitting user profile must also have authority to reset object authorities and ownership. Will this user profile have access to products and functions to which it may not otherwise have authorization? You should set product-level security to "On" and limit user profile access through its authorization levels. 58

59 Security for LAKEVIEW user profile Security for LAKEVIEW user profile This information describes the minimum security requirements for the LAKEVIEW user profile provided with MIMIX products. Each enterprise is unique. Your enterprise may require exceptions to the information provided here. The LAKEVIEW user profile is created with an initial menu of *SIGNOFF so that it cannot be used to sign on to the system. The LAKEVIEW user profile owns all of the objects in the LAKEVIEW and MIMIXQGPL libraries and has access to all the objects that make up the License Manager product. User interface objects, such as commands, command processing programs, display panels, menus, and help, have a public authority (*PUBLIC) of use (*USE). All product user interfaces are protected by Vision Solutions product-level security when that function is set to "On". The LAKEVIEW user profile is created by default as a programmer class (*PGMR) user profile with selected special authorities, including all object authority (*ALLOBJ). Unless the user profile running the install has *ALLOBJ authority, the LAKEVIEW user profile needs this level of authority to access information needed for install operations. Notes: *ALLOBJ authority is a very useful authority but it must be used with care because it leaves your system vulnerable to misuse. Protecting your assets from unauthorized use on page 63 describes considerations for changing this authority. The following table identifies the special authorities and the operations for which the LAKEVIEW user profile requires a special authority: Table 8. Special Authority *ALLOBJ *SAVSYS MIMIX operations that require special authorities MIMIX operations that require special authority In License Manager this authority is needed to access all stream files required for installing updates to Lakeview products and the objects within the product libraries. Required for save and restore operations during installation of updates. 59

60 Additional security considerations If applicable, you should also address the security measures described in the following topics. Multiple-system security considerations When using MIMIX in a multiple-system environment, consider the following: Do user profiles also exist on the backup system? Do you want the user profiles enabled or disabled on the backup system? Do you plan to duplicate user profiles between systems? If you have the same user profiles on multiple systems in the MIMIX installation, the user profiles should have the same level of authority on each system. MIMIX Global security considerations When using MIMIX Global, the user profile used to run the application group exit program must exist on all nodes (systems) in the recovery domain and have *IOSYSCFG special authority. 60

61 User profile restrictions MIMIX cannot call any user exit program that is owned by one of the following user profiles. Because of this, you should ensure that your user exit programs are not owned by any of the following user profiles: Table 9. User profiles restricted from owning user exit programs User profile that is disabled QFNC QSNADS User profile with an expired password QGATE QSNX QAUTPROF QLPAUTO QSPL QCOLSRV QLPINSTALL QSPLJOB QDBSHR QMSF QSYS QDBSHRDO QNETSPLF QTCP QDFTOWN QNFSANON QTFTP QDIRSRV QRJE QTSTRQS QDOC QSECOFR 61

62 System security System security level You need to be aware of the following security considerations for the systems: You need to consider the security level as defined by the QSECURITY system value on each system. For any MIMIX product to function on a system with the security level set at 30 or above, you must have the QALWUSRDMN system value set to *ALL or have the product library and data library names added to the list of libraries for the system value. The installation process will add the product library and data library names to the system QALWUSRDMN value if it is not set to *ALL. Password level (QPWDLVL) system value IBM i supports the system value, password level (QPWDLVL). This system value does the following: Provides support for user profile passwords with a length of 1-10 characters, or for user profile passwords with a length of characters. Determines the forms in which the passwords are stored. Note: Changing the password level on the system requires careful consideration. If a system is configured for longer passwords and it communicates with other systems, then all the systems must be configured for longer passwords. Before you change this system value, you should be familiar with the information in "Planning Password Level Changes" in the Security section of the IBM i and System i Information Center at 62

63 Protecting your assets from unauthorized use Protecting your assets from unauthorized use You should use License Manager to turn on product-level security immediately after installing a MIMIX product. When product-level security is turned on, user profiles must be authorized to the MIMIX product through product-level security before they can access MIMIX functions. Then only users that have security access to a MIMIX product can use its functions. For example, if you did not use product-level security, an unauthorized user could create a journal monitor with MIMIX Monitor. The user could then receive partial information about journal transactions from a journal to which the user is not authorized. Without product-level security, an unauthorized user could also use License Manager to delete a MIMIX product installation. Removing *ALLOBJ authority from the LAKEVIEW user profile will degrade performance for all install-related processes because of the overhead of additional operating system authority look-ups. Removing *ALLOBJ authority may also cause product upgrades to fail if the LAKEVIEW user profile lacks the authority necessary to use the objects needed for updates or product installation objects. Removing *ALLOBJ authority from the MIMIXOWN user profile will degrade performance for all MIMIX processes because of the overhead of additional operating system authority look-ups. Removing *ALLOBJ authority may also cause files to go on hold and may cause failed requests if the MIMIXOWN user profile lacks the authority necessary to operate on the defined files and objects. If you have an extreme business need to remove *ALLOBJ authority, you have these options: For the MIMIXOWN user profile, add the QSECOFR user profile as the primary group profile. Because of the *ALLOBJ authority inherited from the QSECOFR user profile, this allows the MIMIXOWN user profile to access any objects for which it is not explicitly excluded. For the MIMIXOWN user profile, explicitly authorize every file and object used by the replication process on the source system and on the target system. For user journal-based replication, this includes every file on the source system from which transactions will be replicated, every file on the target system that will receive replicated transactions, and any libraries to which the object replication process replicates a file and defines the file for cooperative processing. For system journal-based replication, this includes every object on the source system that will be replicated, every library, folder, and directory (*LIB, *FLR, *DIR) on the target system that will receive replicated objects, and any library to which files are defined for cooperative processing. For the LAKEVIEW user profile, explicitly grant authorization to the LAKEVIEW user profile for every stream file for updates and all objects in each product installation library. 63

64 Vision Solutions-provided security functions CHAPTER 6 Vision Solutions-provided security functions You can take advantage of security functions provided by Vision Solutions to protect your MIMIX products and License Manager. These functions provide an additional level of security beyond that available with the IBM i. All MIMIX products use product authority as set through License Manager. You must take explicit action to set product authority to "On" for each product. It is recommended that you take advantage of this additional security. Any authorization levels that you set for specific user profiles to control access to a product or MIMIX command are not enabled when product authority for the product is turned Off. Product authority on page 66 provides an overview of product authority. Once product authority is in place, additional security measures must be addressed, including security for common functions, system security levels, password considerations, user profiles, and product-level security. This chapter includes the following topics: About the provided security functions on page 66 describes the authority levels of installed software and describes the additional product authority and command authority functions available through License Manager. This topic also includes tips for securing functions that are common to multiple MIMIX products as well as the Run commands (RUNCMD and RUNCMDS). Authority level descriptions on page 69 identifies the authority level which correspond to a security class that is assigned to product commands and functions. Changing product-level security on page 70 describes how to change productlevel security to enforce the additional security available in the product authority and command authority functions. When enabled, an administrator can limit access to License Manager and MIMIX products and can change the authority level of MIMIX commands. Displaying authorities for authorized user profiles on page 71 describes how to display a list of the user profiles that have been authorized to specific authority levels. Changing product authority on page 72 describes how to grant and revoke authority to a product for a user or a group of users. Displaying the authority level of MIMIX commands on page 76 describes how to display the authority level that is needed to run a MIMIX command when product authority is active. Changing command authority on page 77 describes considerations for and how to change the authority level of a MIMIX command while product-level security is in use. Displaying commands known to License Manager on page 79 describes how to 64

65 complete list of all commands known by License Manager, along with the product with which they are associated. Authority levels for commands on page 80 lists the commands and menu interfaces within MIMIX products that can be controlled with security functions provided by Vision Solutions. This includes the products in which the commands are available and the minimum authority level needed when you use the provided product authority or command authority functions. 65

66 About the provided security functions Product authority Command authority MIMIX products can take advantage of additional security functions for product authority and command authority. These functions are set through License Manager. MIMIX performs the following functions, automatically, during product installation: The user profile that is performing the installation is granted administrator (*ADM) authority. Users in the public access class (*PUBLIC) are granted display (*DSP) authority. Special user profiles for the product, such as the MIMIXOWN user profile, are granted management (*MGT) authority. After installation completes, you can use License Manager to make product and command authority changes. Your changes are not effective until product-level security is enabled through the Change Product Level Security (CHGPRDSEC) command. When enabled, product-level security enforces product and command authority. Note: These security functions are available through License Manager and are accessible only through 5250 emulator interfaces on the system. Product authority is a provided security function that allows an administrator to set or change the product authority level needed for a user profile or for public access to a specific MIMIX product. These authority levels are in addition to the standard IBM i security levels. Note: The QSECOFR user profile is not affected by the product authority function unless it is explicitly listed as a user within product authority. When product-level security is enabled, you can use the product authority function to do the following: Establish an authority level to access a product for the public access class (*PUBLIC). User profiles which are not explicitly assigned an authority level use this authority level when accessing the product. Control access to the functions that a user profile can access within a product by assigning one of several authority levels to that user profile. Explicitly authorizing a user profile to an authority level limits access to functions requiring authority up to and including that level. Exclude a user profile from accessing a product. Authorize user profiles to different security levels for different products in the same library. For example, a user may have one authority level for MIMIX Enterprise and another authority level for MIMIX Global. Command authority is a provided security function that enables you to change the authority level of specific MIMIX commands. When product-level security is enabled, 66

67 About the provided security functions you can use the command authority function to raise or lower the authority level for a command or to reset it to the shipped authority values. When you change the authority level of a command, it is changed for all products that use the command in all installations on the system. 67

68 Security for common functions MIMIX products can share common functions. Common functions make it easier for products in the same library to interact with each other. Common functions also require more careful consideration of your security needs when you use the supplied security functions for product authority and command authority. Common functions may give users access to functions within another product at a higher authority level than you intended. For example, you have a product library in which you have installed MIMIX Enterprise and MIMIX Global and you have valid license keys for both products. You set the public authority for MIMIX Enterprise to *DSP. You also turned on product-level security for MIMIX Global and gave user profile OPER1 *MGT authority to MIMIX Global. Both products use a common function, for purposes of this example call it ABC function, which requires *OPR authority to run. User profile OPER1 can access function ABC in MIMIX Enterprise because the function is common and OPER1 has *MGT authority to MIMIX Global in the same library which also uses function ABC. You need to carefully consider the authorization level you specify for public use of each product and consider setting all products within a library to the same authorization level. You should also determine which user profiles require access at specific authority levels. For more information about the minimum security level of the commands and interfaces in each product, see Authority levels for commands on page 80. Requirements for Run commands Two commands (RUNCMD and RUNCMDS) in MIMIX enable you to run commands on a remote system. MIMIX and MIMIX Monitor also use these commands internally. For these commands to function, you need to have the same user profile on the local system and the remote system and the password must be the same on both systems. When these commands are run internally, they are run under the MIMIXOWN user profile. 68

69 Authority level descriptions Authority level descriptions Each authority level corresponds to a security class that is assigned to the commands and functions in a product. The following figure shows how each authority level includes the capabilities of the associated security class and all lower security classes. Table 10. Authority level descriptions Authority Level Security Classes Included *ADM *MGT Administrator rights are required to create, change, or delete security classes for users. Management rights are required to create or change the configuration of the product. DSP OPR MGT ADM X X X X X X X *OPR Operational rights are required to control operation of the product, such as starting or stopping readers and reissuing failed requests. X X *DSP Display rights are required to use menus and DSPxxx functions. X *EXCL The user profile is excluded from using the product

70 Changing product-level security Product-level security is a provided security function that enforces the additional security available in the product authority and command authority functions. When enabled, an administrator can limit access to License Manager and MIMIX products using the product authority function and can change the authority level of MIMIX commands using the command authority function. For these authority levels to take affect, product-level security must be turned on. Notes: The user profile you use to perform this procedure must have *ADM authority to License Manager. Users running functions are not affected by a change until the next time they access a function that is protected by product authority. To display authorized user profiles for a product library, see Displaying authorities for authorized user profiles on page 71. For information about granting, revoking, or changing an authority level for a user profile, see Changing product authority on page 72. To change product-level security for one or more product libraries, do the following, or use the alternative process: 1. From the License Manager Main Menu, select option 2 (Work with Products) and press Enter. 2. The Vision Solutions Installed Products display appears. Type 30 next to the product libraries that you want and press Enter. 3. On the Change Product Level Security display, specify the value you want for product authority at the State prompt, then press Enter. Note: If you selected multiple product libraries in the previous step, you will see the Change Product Level Security display for each of the libraries you selected. Alternative Process: If you know the name of the product library or to change all products in the library, you can do the following: 1. From the License Manager Main Menu, select option 14 (Change product level security) and press Enter. 2. On the Change Product Level Security display, specify the type of product and the name of the library for which you want to change the security setting. To set security for all products in the library, specify *ALL for at the Product prompt. 3. At the State prompt, specify the value you want for product authority and press Enter. 70

71 Displaying authorities for authorized user profiles Displaying authorities for authorized user profiles For each product library, you can display a list that shows the user profiles that have been authorized to specific authority levels. Note: If the security officer profile (QSECOFR) is not explicitly granted a product level security setting, it will have all authority. To display product authority for one or more product libraries, do the following or use the alternative process: 1. From the License Manager Main Menu, select option 2 (Work with Products) and press Enter. 2. The Vision Solutions Installed Products display appears. Type a 5 (Display Product Authority) next to the product libraries that you want and press Enter twice. 3. The Display Product Authority display appears with a list of the user profiles that have been granted access to this product library. An X appears in the column for which the user profile has been authorized. The entry for *PUBLIC indicates the authority of all user profiles that are not explicitly listed. Alternative process: If you know the name of the product library you can display the product authority by doing the following: 1. From the License Manager Main Menu, select option 11 (Display Product Authority) and press Enter. 2. On the Display Product Authority display, specify the type of product and the name of the library you want. 71

72 Changing product authority You can control access to License Manager and MIMIX products through the use of authority levels. The installation process sets an authority level of *ADM for the installing user profile and sets an authority level of *DSP for *PUBLIC. User profiles that do not have an explicitly specified authority level will have the access authority as *PUBLIC. The procedures in this information enable you to set a different authority level for all explicitly listed user profiles and enable you to control access to function for specific user profiles by assigning an authority level. Using group profile support The following License Manager commands support using group profiles for product authority: Grant Product Authority (GRTPRDAUT) Revoke Product Authority (RVKPRDAUT) Group profiles are frequently used as security and customization tools. This makes it easier to set up and control access to MIMIX products using License Manager s product authority function. For example, you can use a group profile to authorize operators to a MIMIX product at the *OPR authority level. Note: To protect access to your MIMIX products and use the group profile support, product authority must be turned on for the products. When product authority is on and a user profile attempts to access a MIMIX function, License Manager checks for an entry in product authority. When a security entry exists for the user profile, access to the requested function is granted or denied based on the authorization set in the security entry. If the user profile is not specifically authorized through a security entry, License Manager checks the group profiles identified in the user profile and checks the *PUBLIC authority level. Access to the requested function is granted or denied based on the highest level identified in the group profiles and *PUBLIC authority. Group profile examples The following examples illustrate how the group profile support works with product authority. The authorization levels to MIMIX products are, in descending order, as follows: 1. *ADM (administrator) 2. *MGT (management) 3. *OPR (operator) 4. *DSP (display) 5. *EXCL (exclude) These examples use the following assumptions: *PUBLIC access has been granted *DSP authority to a MIMIX product Group profile GRPA has *ADM authority to the same product 72

73 Changing product authority Group profile GRPM has *MGT authority to the same product Group profile GRPO has *OPR authority to the same product Case 1: Default authority User profile USERA has no associated group profiles and does not have a specific security entry for the MIMIX product. USERA is granted *DSP authority to the product because that is the *PUBLIC authority level. Case 2: Specific user authority User profile USERB has no associated group profiles but there is a specific security entry for the product specifying authority level *EXCL for USERB. USERB is granted *EXCL authority (in this case, denied access to the product). Case 3: User in multiple groups (1) User profile USERC has no specific security entry, but is a member of both group profiles GRPA and GRPO. Because the highest authorization level for GRPA, GRPO, and *PUBLIC is the *ADM authority associated with group profile GRPA, USERC is granted *ADM authority to the MIMIX product. Case 4: User in multiple groups (2) User profile USERD has no specific security entry, but is a member of both group profiles GRPM and GRPR. Group profile GRPR does not have a specific security entry. Because the highest authorization level for GRPM and *PUBLIC is the *MGT authority associated with group profile GRPM, USERD is granted *MGT authority to the MIMIX product. Case 5: User in multiple groups (3) User profile USERE has no specific security entry, but is a member of both group profiles GRPQ and GRPR. Because neither of these group profiles has a specific security entry, USERE is granted *DSP authority (the *PUBLIC authority level) to the product. Case 6: Attempting to exclude a group of users User profile USERF has no specific security entry but is a member of group profile BADDY. There is a security entry for group profile BADDY which is set to *EXCL authority to the MIMIX product. Because the highest authorization level for BADDY and *PUBLIC is *DSP, USERF is granted *DSP authority to the MIMIX product. Users must be specifically excluded from using a MIMIX product. Granting a user authority to a product For your change to be effective, product-level security must be enabled. Note: To change the authority level for a user profile that already has been granted product authority, you must first revoke authority at the existing level. Then grant authority for the user profile at the desired level. To give a user profile authority to a product library, do the following or use the alternative process: 1. From the License Manager Main Menu, select option 2 (Work with Products) and press Enter. 2. The Vision Solutions Installed Products display appears. Type a 31 (Grant Product Authority) next to the product library you want and press Enter. 3. The Grant Product Authority display appears. Do the following: 73

74 a. At the User profile prompt, specify the name of the user profile for which you are granting authority. To set a default value for all user profiles, specify *PUBLIC. b. At the Authority Level prompt, specify the highest authority level that you want the user profile to access. Table 11 describes the valid values. Table 11. *ADM *MGT *OPR *DSP *EXCL Description of authority levels Authorization rights. Authorizes the user profile to function that can create, change, or delete security classes for users. This authorization level also has *MGT, *OPR, and *DSP rights. Management rights. Authorizes the user profile to function that creates or changes the configuration of the product. This authorization level also has *OPR and *DSP rights. Operational rights. Authorizes the user profile to function that controls the operation of the product, such as starting or stopping readers and reissuing failed requests. This authorization level also has *DSP rights. Display rights. Authorizes the user profile to use menus and other display functions. Exclude. This authorization level prevents the user profile from accessing the product. c. At the Minimum Lic. Mgr. auth. level prompt, specify the minimum authority level for the License Manager that the specified user profile should have. d. Press Enter, to grant authority to the user profile. Alternative process: If you know the name of the product library, you can do the following: 1. From the License Manager Main Menu, select option 12 (Grant product authority) and press Enter. 2. On the Grant Product Authority display specify the type of product and the name of the library to which you want to grant access. At the User profile prompt specify the name of the user profile to which you are granting authority and at the Authority level prompt specify the highest level you want the user profile to access. At the Minimum Lic. Mgr. auth. level prompt, specify the minimum authority level for the License Manager that the specified user profile should have 3. Press Enter to grant authority to the user profile. Revoking product authority for a user For your change to be effective, product-level security must be enabled. Do the following to revoke authority to a product for a specified user profile, or use the alternative process: 1. From the License Manager Main Menu, select option 2 (Work with Products) and press Enter. 74

75 Changing product authority 2. The Vision Solutions Installed Products display appears. Type a 32 (Revoke Product Authority) next to the product library you want and press Enter. 3. The Revoke Product Authority display appears. Do the following: a. At the User profile prompt, specify the name of the user profile for which you are revoking authority. b. At the Authority level prompt, specify the authority level that you want to revoke. c. Press Enter to revoke the authority level for the user profile. Alternative process: If you know the name of the product library, you can do the following: 1. From the License Manager Main Menu, select option 13 (Revoke product authority) and press Enter. 2. On the Revoke Product Authority display specify the type of product and the name of the library to which you want to revoke access. At the User profile prompt specify the name of the user profile from which you are revoking authority and at the Authority level prompt specify the level you want to revoke. 3. Press Enter to revoke the authority level for the user profile. 75

76 Displaying the authority level of MIMIX commands The Display Command Authority (DSPCMDAUT) command allows you to display the authority level that is needed to run a MIMIX command when product authority is active. You can display the authority level of a single MIMIX command or for all the commands in the MIMIX authority table. Note: When product authority is active, you must have *DSP authority to License Manager to run this command. To display the authority level for MIMIX commands, do the following: 1. From the command line, type DSPCMDAUT and press F4 (Prompt). 2. The Display Command Authority (DSPCMDAUT) display appears. At the Command prompt, specify the name of the MIMIX command for which you want to display the authority level. If you specify a generic name, you must include the first three characters. The value *ALL displays all the commands in the MIMIX authority table. If you specify *ALL, only the value *PRINT is valid for the Output prompt. 3. At the Detail prompt, specify the level of detail you want to include in the displayed or spooled output. The value *CHANGED displays only the commands whose authority levels have been changed since they were shipped with the product. The value *ALL displays all commands in the MIMIX authority table. 4. To create a spooled file that can be printed, specify *PRINT at the Output prompt. 5. To display the authority level, press Enter. 76

77 Changing command authority Changing command authority There may be times when it is necessary to change the authority level of a MIMIX command while product-level security is in use. For example, you may want to change the SWTDG command, which requires *OPR authority, to require *MGT authority instead. Command authority support enables you to change authorization to specific commands. Any changes that are made to authority for a command are effective when product-level security is activated for each product in which the command can be used. Command authority changes are retained when upgrades are performed on the system. The Change Command Authority (CHGCMDAUT) command allows you to modify the authority level of a MIMIX command when product-level security is in use. When product authority is active, you must have *ADM authority to License Manager to run this command. The authority levels for CHGCMDAUT, GRTPRDAUT, RVKPRDAUT, and CHGLICKEY cannot be changed. Note: Changes are effective for the products in all installation libraries on the system in which the command can be used. For example, you may have two installation libraries, where one contains MIMIX, and the other contains MIMIX, MIMIX Promoter, and MIMIX Monitor. If you change the Create System Definition authority from *MGT to a different value, this change is effective for all products in both installations and is enforced for the products which have enabled product-level security. Care must be used when changing command authority for commands that are used by multiple products. For example, you have a system with MIMIX products installed in three different libraries. Library A contains MIMIX licensed for MIMIX Enterprise. Library B contains MIMIX licensed for MIMIX Enterprise and MIMIX Global. You have enabled productlevel security for the products in libraries A and B. You have set up two group user profiles with product authority to control access to MIMIX functions in libraries A and B. One group has *OPR access and the other group has *MGT access. The members of the *OPR group are the same in both libraries, as are the members of the *MGT group. Library C contains MIMIX dr1 and you have not enabled product-level security for it. You have decided to use command authority to restrict authorization to the Start Lakeview TCP Server (STRSVR) and End Lakeview TCP Server (ENDSVR) commands to users with *MGT or higher authority. Because the command authority change is effective for every MIMIX product on the system but is only enforced for products that have enabled product-level security, the result of this decision will be: All users can use the STRSVR and ENDSVR commands from library C (MIMIX dr1) because command authority is not enforced when product-level security is disabled. Members of the group profile with *OPR authority in libraries A and B cannot use the STRSVR and ENDSVR commands because the command authority changed to a level higher than that to which their group is authorized. Members of the group profile with *MGT authority can run the STRSVR and ENDSVR commands in libraries A and B because their group has the appropriate authority. 77

78 If product-level security is enabled for MIMIX dr1 in library C, only members of the group profile with *MGT authority can run the STRSVR and ENDSVR commands in library C. Changing the authority level for MIMIX commands The shipped authority level of each command is identified in Authority levels for commands on page 80. Do the following to change the authority for a MIMIX command: 1. From the command line, type LAKEVIEW/CHGCMDAUT and press F4 (Prompt). 2. The Change Command Authority (CHGCMDAUT) display appears. At the Command prompt, specify the name of the MIMIX command for which you want to change the authority level. If you specify a generic name, you must include the first three characters. The value *ALL resets all MIMIX commands to their original security setting. If you specify *ALL, you must specify *DFT for the Authority prompt. In this case, only the value *PRINT is valid for the Output prompt. 3. At the Authority prompt, specify the minimum authority level needed to use the command. Use F1 (Help) in this field to see descriptions of the possible values. 4. To create a spooled file that can be printed, specify *PRINT at the Output prompt. 5. To change the authority level, press Enter. 78

79 Displaying commands known to License Manager Displaying commands known to License Manager You can use the Display Command Authority (DSPCMDAUT) command to display the complete list of all commands known by License Manager, along with the product with which they are associated. This list can be helpful when working with productlevel security. Do the following: 1. From the command line, type LAKEVIEW/DSPCMDAUT press F4 (Prompt): 2. The Display Command Authority command appears. At the Command prompt, select *ALL. 3. At the Detail prompt, select *ALL. 4. At the Output prompt, select *PRINT. This value is required when *ALL is specified for the Command prompt. 5. Press Enter. A successful message is issued. 6. To view the resulting list of commands, type the following on a command line and press Enter: WRKSPLF 7. The Work with All Spooled Files display appears. Next to the LMDSPCMDL file, type 5 (Display) and press Enter. 8. The Display Spooled File display appears, showing the current list of all commands known to License Manager. 79

80 Authority levels for commands Table 12 shows the commands and menu interfaces within MIMIX products that can be controlled with security functions provided by Vision Solutions. The left side of the table indicates the products in which the commands are available; to use the command from within a product, you must first have a valid license key that includes the product. The right side of the table shows the minimum authority level needed for the command when you use the provided product authority or command authority. Before using this information, you should note that: Product-level security must be enabled to enforce your choices for product authority and command authority. The product authority function does not apply to the security officer user profile (QSECOFR). As long as valid license keys exist, the QSECOFR user profile can perform all functions. This allows the security officer to access a product when all other user profiles are excluded from access. Commands that are not listed are not protected by product authority and cannot be modified with command authority. All users with *ADM authority to a product in a library have access to the grant and revoke authority commands (GRTPRDAUT and RVKPRDAUT) for that instance of the product. These users have the ability to grant and revoke authority to that product even though they do not have *MGT authority to License Manager. Be aware of the security considerations for commands and interfaces that are used by more than one product in the same library. When you have multiple products in the same library, in each product, you should set command authority to use the same product-security level. This is also true of product level authority to commands for individual user profiles. Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. *ADM *MGT *OPR *DSP MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only O=Obj only Monitor b X X ABOUT X U ADDDGDAE X O ADDDGDLOE X U ADDDGFE X U ADDDGFEALS X O ADDDGIFSE X O X ADDDGOBJE X

81 Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. *ADM *MGT *OPR *DSP MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only Monitor b O=Obj only X ADDDIRVSIP X X X ADDDTARGE c X X ADDEXITPGM X X ADDMMXDMNE d X X X ADDMONINF X X X X X ADDMSGLOGE X X X ADDNFYE X X X ADDNODE X X X ADDPRCE X U ADDRJLNK X X X ADDSTEP X X X ADDSTEPMSG X X X ADDSTEPPGM X X ADDSWTDEVE X X APYLICKEY X X X BLDAGENV X X X BLDCLUOBJ X X BLDJRNENV X X CFGLKVSPT X X X CHGAGDFN X X X CHGCLUOBJ X X CHGCMDAUT X X CHGDG X U CHGDGDAE X X X CHGDGDFN X O CHGDGDLOE X U CHGDGFE X U CHGDGFEALS X O CHGDGIFSE X O X CHGDGOBJE X X CHGDGRCV X X CHGDTARGE X

82 *ADM *MGT *OPR *DSP Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only O=Obj only Monitor b X CHGJRNDFN X X CHGLICKEY X X CHGLMMSG X X CHGMMXAM e X X X CHGMMXCLU X X X CHGMONINF X X X CHGMONOBJ X X X CHGMONSTS X X X CHGNODE X X X CHGNODSTS X X X CHGPRCDFN X X X CHGPRCE X X CHGPRDLIB X X CHGPRDSEC X U X CHGPRMGRP X X X CHGPROC X X X CHGPROCSTS X U CHGRJLNK X X X CHGSTEP X X X CHGSTEPMSG X X X CHGSTEPPGM X X CHGSWTDEVE X X CHGSWTDFN X X X CHGSWTFWK X X X X X CHGSYSDFN f X X X X X CHGTFRDFN X X X CHGUPSAVL X X X CHGUPSCFG X X X CHGUPSMSG X X CHKDGFE X X X CHKR3PRF X X X CHKSWTFWK X

83 *ADM *MGT *OPR *DSP Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only O=Obj only Monitor b O CLRCNRCCH X X CLRDGRCYP X X X CLOMMXLST X X CMPDLOA X X CMPFILA X X CMPFILDTA X O CMPIFSA X O X CMPOBJA X X CMPRCDCNT X O CNLDGACTE X X X CNLPROC X U X CPYACTF X X X CPYCFGDTA X U CPYDGDAE X X X CPYDGDFN X O CPYDGDLOE X U CPYDGFE X O CPYDGIFSE X O X CPYDGOBJE X X CPYJRNDFN X X X CPYMONOBJ X X X CPYPRCDFN X X X CPYPRCE X X X CPYPROC X X X X X CPYSYSDFN X X X X X CPYTFRDFN X X CPYTOECS X X X CRTAGDFN X U CRTCRCLS X X X CRTDGDFN X U CRTDGTSP X X CRTJRNDFN X

84 Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. *ADM *MGT *OPR *DSP MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only Monitor b O=Obj only X CRTMMXAM e X X X CRTMMXCLU X X X CRTMMXDFN X X X CRTMONOBJ X X X CRTPRCDFN X X X CRTPROC X X CRTSWTDFN X X X CRTSWTFWK X X X X X CRTSYSDFN f X X X X X CRTTFRDFN X O CVTDG X X CVTLKVSTMF X X X DLTAGDFN X U DLTCRCLS X X X DLTDGDFN X U DLTDGTSP X X DLTJRNDFN X X DLTJRNENV X X DLTLKVSPT X X DLTMMXAM e X X X DLTMMXCLU X X X DLTMONOBJ X X X DLTPRCDFN X X DLTPRD X X X DLTPROC X X DLTSWTDFN X X X DLTSWTFWK X X X X X DLTSYSDFN X X X X X DLTTFRDFN X U DMLOGOUT X X X DSPAGDFN X O DSPPATH X

85 Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. *ADM *MGT *OPR *DSP MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only Monitor b O=Obj only X DSPCMDAUT X X DSPCOLSRV X X DSPCPYDTL X U DSPDGDAE X X X DSPDGDFN X O DSPDGDLOE X U DSPDGFE X U DSPDGFEALS X O DSPDGIFSE X X DSPDGIFSTE X O X DSPDGOBJE X X DSPDGOBJTE X X X DSPDGSTS X X DSPDTARGE X X DSPJRNDFN X X DSPJRNSTC X X X X X DSPMMXMSGQ X X X DSPMONINF X X X DSPMONOBJ X X X DSPMONSTS X X X DSPNODE X X X DSPPRCDFN X X X DSPPRCE X X DSPPRDAUT X U DSPRJLNK X X DSPSWTDEVE X X DSPSWTDFN X X DSPSWTSTS X X X X X DSPSYSDFN X X DSPSYSINF X X X X X DSPTFRDFN X X X DSPUPSSTS X

86 *ADM *MGT *OPR *DSP Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only O=Obj only Monitor b X X ENDAG X X X X ENDCOLSRV X X X ENDDG X U ENDJRNFE X X ENDJRNIFSE X X ENDJRNMMX X X ENDJRNOBJE X X ENDLKVSPT X X X X X ENDMMX g X X ENDMMXAM e X X X ENDMMXMGR X X X ENDMON X X X ENDMSTMON X U ENDRJLNK X X X X ENDSVR X X ENDSWT X X ENDSWTSCN X X X EXPMONOBJ X X X EXPPRCDFN X X X X X X X EXPPRDINF X X FORMBR X X FOROBJ X X GRTPRDAUT X X X X X X X GRTPRDAUT X U HLDDGLOG X X X HLDMON X X X IMPMONOBJ X X X IMPPRCDFN X X INSMMX X X X INZR3SWT X X LICMGR X X X LODAG X

87 *ADM *MGT *OPR *DSP Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only O=Obj only Monitor b U LODDGDAE X O LODDGDLOE X U LODDGFE X U LODDGIFSTE X O X LODDGOBJE X U LODDGOBJTE X X X LODDTARGE X X LODLKVFIX X X LODSWTDEVE X X X X X MIMIX X X MIMIXPRM X X MMUPSMENU X U MMXSNDJRNE X X X MOVCLUMSG X X X OPNMMXLST X X X OVRSTEP X X PRDMGT X X RGZACTF X U RLSDGLOG X X X RLSMON X O RMVDGACTE X U RMVDGDAE X O RMVDGDLOE X U RMVDGFE X U RMVDGFEALS X O RMVDGIFSE X X RMVDGIFSTE X O X RMVDGOBJE X X RMVDGOBJTE X X RMVDIRVSIP X X X RMVDTARGE X X RMVMMXDMNE d X

88 *ADM *MGT *OPR *DSP Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only O=Obj only Monitor b X X RMVMMXNOD X X X X X RMVMSGLOGE X X X RMVNODE X X X RMVPRCE X U RMVRJCNN X U RMVRJLNK X X X RMVSTEP X X X RMVSTEPMSG X X X RMVSTEPPGM X X RMVSWTDEVE X X X RNMDGDFN X X RNMJRNDFN X X X RNMMONOBJ X X X RNMPRCDFN X X X RNMPROC X X X RNMSTEPPGM X X X X X RNMSYSDFN X X X X X RNMTFRDFN X X X RQSPRCECFM X X RTVAPYSTS X U RTVDGDAE X X X RTVDGDFN X X X RTVDGDFN2 X O RTVDGDLOE X U RTVDGEXIT X U RTVDGFE X X RTVDGIFSTE X O X RTVDGOBJE X X X RTVDGSTS X X RTVJRNDFN X X RTVJRNSTS X X RTVMMXAM e X

89 *ADM *MGT *OPR *DSP Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only O=Obj only Monitor b X X RTVMMXLSTE X X X RTVPRCDFN X X X RTVPRCE X X X RTVPROC X X RTVPRMGRP X U RTVRJLNK X X X RTVSPSTS X X X RTVSTEP X X X RTVSTEPMSG X X X RTVSTEPPGM X X X X RTVSWTFWK X X X X X RTVSYSDFN X X X RTVSYSSTS X X X X X RTVTFRDFN X O RTYDGACTE X X X RSMPROC X X X X X RUNCMD X X X X X RUNCMDS X X X RUNMON X X X RUNPRCE X X X RUNPROC X X X RUNRULE X X X RUNRULEGRP X X X RUNSWTFWK X X RVKPRDAUT X X X X X X X RVKPRDAUT X X SAVCFGDTA X X X SETAPPCDE X O SETDGAUD X U SETDGEXIT X U SETDGFE X X SETDGIFSTE X

90 *ADM *MGT *OPR *DSP Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only O=Obj only Monitor b X SETDGOBJTE X X SETDGRCYP X X SETEXTPCY X X SETIDCOLA X X X X SETLCLSYS X X X SETODASTS X X X SETMMXPCY X X SETSWTSRC X X X SNDCLUOBJ X O SNDNETDLO X O SNDNETIFS X O X SNDNETOBJ X X X STRAG h X X X X STRCOLSRV X X X STRCVTAG X X X STRDG X U STRJRNFE X X STRJRNIFSE X X STRJRNMMX X X STRJRNOBJE X X STRLKVSPT X X X X X STRMMX g X X STRMMXAM e X X X X X STRMMXMGR X X X STRMON X X X STRMSTMON X U STRRJLNK X X X X STRSVR X X STRSWT X X STRSWTSCN X X X SWTAG X X SWTDG X

91 Authority levels for commands Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. *ADM *MGT *OPR *DSP MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only Monitor b O=Obj only X X SWTR3PRF X X SYNCDG X O SYNCDGACTE X U SYNCDGFE X O SYNCDLO X O SYNCIFS X O X SYNCOBJ X X X TSTPWRCHG X X UPDINSPRD X X UPDLICKEY X X X UPDUPSAVL X X X X X VFYCMNLNK X U VFYDGDAE X U VFYDGFE X U VFYJRNFE X X VFYJRNIFSE X X VFYJRNOBJE X U VFYKEYATR X X X WRKAG X X X WRKAUD X X X WRKAUDHST X X X WRKAUDOBJ X X X WRKAUDOBJH X U X WRKCPYSTS X U WRKCRCLS X X X WRKDG X O WRKDGACT X O WRKDGACTE X U WRKDGDAE X X X WRKDGDFN X O WRKDGDLOE X U WRKDGFE X 91

92 Authority levels for commands *ADM *MGT *OPR *DSP Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only O=Obj only Monitor b U WRKDGFEALS X U WRKDGFEHLD X O WRKDGIFSE X X WRKDGIFSTE X O X WRKDGOBJE X X WRKDGOBJTE X U WRKDGTSP X X X WRKDTARGE X X WRKIFSREF X X WRKJRNDFN X X X WRKMMXSTS X X X WRKMON X X X WRKMONINF X X X X X WRKMSGLOG X X X WRKNFY X X X WRKNODE X X X WRKPRCDFN X X X WRKPRCE X X WRKPRD X X X WRKPROC X X X WRKPROCSTS X X WRKRCY X X WRKRJLNK X X X WRKSPSTS X X X WRKSTEP X X X WRKSTEPMSG X X X WRKSTEPPGM X X X WRKSTEPSTS X X WRKSWT X X WRKSWTDEVE X X X X X WRKSYS X X X X X WRKSYSDFN X 92

93 Authority levels for commands Table 12. Commands and menu interfaces available by product, showing their shipped minimum authority level settings when the provided security functions are used. *ADM *MGT *OPR *DSP MIMIX Enterprise or MIMIX Professional MIMIX for MIMIX License Command and Menu Minimum Authority Level Replication MIMIX MIMIX Promoter SAP/R3 Global a Manager Interfaces U=DB only Monitor b O=Obj only X X X X WRKTFRDFN X a. Includes licenses for MIMIX Global, MIMIX Global - IASP Edition, and MIMIX Global - SAN Edition unless otherwise noted. b. MIMIX Promoter is not included with MIMIX Professional. c. Supported values for the resource group type (TYPE) parameter vary depending on which license keys are present. When MIMIX Enterprise or MIMIX Professional is licensed, the supported types are *DTA and *PEER. When MIMIX Global - IASP Edition is licensed, the supported types are *DEV, *LUN, *PEER, and *XSM. When MIMIX Global - SAN Edition is licensed, the supported types are *DEV, *GMIR, *LUN, *PEER, *PPRC, and *XSM. d. Supported for MIMIX Global - IASP Edition or MIMIX Global - SAN Edition licenses only. e. MIMIX Availability Manager commands are included for backward compatibility only. MIMIX Availability Manager can only be started on systems that were at version 6 service pack or higher before version 7 of License Manager was installed. f. A license for MIMIX Global (C1) requires either a MIMIX Enterprise or a MIMIX Professional license. g. This command is not protected by product level security. Authority to use this command is controlled by the product level security assigned to any commands used by this command. h. Supported values for the resource group (TYPE) parameter vary depending on which license keys are present. When MIMIX Enterprise or MIMIX Professional is licensed, the supported types are *APP, *DTA, and *PEER. When MIMIX Global - IASP Edition is licensed, the supported types are *DEV, *LUN, *PEER, and *XSM. When MIMIX Global - SAN Edition is licensed, the supported type are *DEV, *GMIR, *LUN, *PEER, *PPRC, and *XSM. Substitution values for command authority Table 13 is only needed if you change authority to individual commands using the Change Command Authority (CHGCMDAUT) command. When you change the command authority for any of these commands, you need to specify the value shown in the Substitution Entry column for the Command (CMD) parameter. Table 13. Change command authority substitutes Command DLTDGDFN RTVDGDFN Substitution Entry DLTDGDFN2 RTVDGDFN2 93

94 Table 13. Change command authority substitutes Command RTVPRCDFN RTVPRCE SETLCLSYS WRKDGDAE WRKDGDFN WRKDGDLOE WRKDGFE WRKDGOBJE WRKJRNDFN WRKMSGLOG WRKPRCDFN WRKPRCE WRKPRD WRKSYSDFN WRKTFRDFN Substitution Entry RTVPRCDFN2 RTVPRCE2 SETLOCSYS WRKDGDAE2 WRKDGDFN2 WRKDGDLOE2 WRJDGFE2 WRKDGOBJE2 WRKJRNDFN3 WRKMSGLOG2 WRKPRCDFN2 WRKPRCE2 WRKPRD2 WRKSYSDFN2 WRKTFRDFN2 94

95 CHAPTER 7 Remote system support This section describes how to use the electronic access to remote support functions provided within License Manager. These capabilities, known as the Lakeview Technology Support function, use remote system support to assist you with problem determination for License Manager and MIMIX products. Vision Solutions CustomerCare representatives can access your system over a switched point-to-point connection using Systems Network Architecture Distribution Services (SNADS). You can send and receive information between your system and the Vision Solutions support system. This chapter includes the following topics: Accessing Lakeview Technology support functions on page 96 describes how to configure and start the remote support connection. Disconnecting from Lakeview Technology support on page 98 describes how to end the remote support connection and delete configuration objects used by remote system support. 95

96 Accessing Lakeview Technology support functions Use Lakeview Technology support when you are asked to do so by your MIMIX product provider or by a Vision Solutions CustomerCare representative. To use remote system support, you must configure the connection and start the support. Typically, you will use the ECS line and modem already installed on your system. Configuring the Lakeview Technology support connection Do the following to configure the connection for remote system support: 1. From the License Manager Main Menu, select option 21 (Configure Lakeview support) and press Enter. 2. The Configure Lakeview Support display appears. Your Lakeview Technology Support representative can assist you in providing the following information: a. At the Local connection ID prompt, specify the value to use to connect to the CustomerCare system. b. At the Resource name prompt, specify the hardware resource name to which the modem you plan to use is connected. You can find this name in the line description for the QESLINE. c. At the Station address prompt, specify the station address to use for the connection. d. At the Connection number prompt, specify the telephone number to dial to connect to the CustomerCare system. Typically CustomerCare will initiate the connection and this line is left blank. e. Press F10 (Additional parameters). f. At the Initial connection prompt, indicate which system initiates the connection. Specify *DIAL to initiate the connection. Specify *ANS to have the CustomerCare system initiate the connection. g. At the Force create prompt, indicate whether to force creation of configuration objects needed to establish the connection. 3. When you complete your selections, press Enter to configure the connection. Starting Lakeview Technology support Do the following to start Lakeview Technology Support: 1. From the License Manager Main Menu, select option 22 (Start Lakeview support) and press Enter. Note: If you have not configured Lakeview Support, you will be prompted to provide the configuration information. 2. You can now send or receive network distributions from the CustomerCare system using Systems Network Architecture Distribution Services (SNADS). Network distributions that you send to the CustomerCare system should be sent 96

97 Accessing Lakeview Technology support functions to User ID LKVECS at Address LAKEVIEW. Network distributions sent to your system from CustomerCare are sent to User ID LKVECS. 97

98 Disconnecting from Lakeview Technology support Disconnecting from Lakeview Technology support consists of ending the connection and deleting the configuration objects used by the connection. Ending the Lakeview Technology support connection Ending the connection to Lakeview Technology support varies off the communications line, controller, and device configuration objects used by remote system support. Do the following to end the connection: 1. From the License Manager Main Menu, select option 23 (End Lakeview support) and press Enter. 2. On the End Lakeview Support display, specify a value for the Forced end of active sessions prompt and press Enter. The value *NO does not force the ending of all sessions that may be active on the Lakeview Technology Support configuration objects. Deleting Lakeview Technology support objects Delete the configuration objects used by remote system support when you no longer need the connection to the Lakeview Technology Support system. Do the following to delete the configuration objects: From the License Manager Main Menu, select option 24 (Delete Lakeview support) and press Enter. If you want to start Lakeview Technology support again, you will have to reconfigure the connection. 98

99 APPENDIX A About MIMIX Availability Manager MIMIX Availability Manager offers an intuitive, easy to use interface which significantly enhances your ability to check the status of version 5 or 6 MIMIX replication environments. Important! Vision Solutions Portal replaces MIMIX Availability Manager for MIMIX version 7 and higher. MIMIX Availability Manager only supports versions 5 and 6 of MIMIX. If you have used MIMIX Availability Manager, be aware of the following: Version 7 of License Manager no longer includes software for installing MIMIX Availability Manager. MIMIX IntelliStart is still included, as are commands to support running previously installed versions of MIMIX Availability Manager. If you plan to continue using MIMIX Availability Manager for installations at earlier versions, a service pack is required. Before you install or upgrade License Manager to version 7, you must install service pack or higher on the server where MIMIX Availability Manager is installed as well as on the systems to be monitored. Both Vision Solutions Portal and MIMIX Availability Manager use port 8410 as the default port number. If you use both products, you cannot use the same default port number for each product. You can also use MIMIX IntelliStart as a standalone product. It is strongly recommended that you use the version 6 MIMIX Installation Wizard when installing MIMIX Availability Manager. The installation process automatically creates a default MIMIX Availability Manager named MIMIXAM on the local system and assigns a default port number of This section includes the following topics: Introduction to MIMIX Availability Manager on page 100 Introduction to MIMIX IntelliStart on page 100 Requirements for MIMIX Availability Manager on page 103 Setting time zones in the SystemDefault.properties file on page 108 Enabling MIMIX Switch Assistant on page 109 Changing prestart job settings for optimal performance on page 109 iseries Access for Web on page 109 Systems available to monitor on page 110 Setting individual user preferences on page 110 Confirming a MIMIX IntelliStart automatic synchronization on page 112 Performing MIMIX IntelliStart manual synchronization on page 114 Logging in to MIMIX Availability Manager on page 116 Areas of the window in MIMIX Availability Manager on page

100 About MIMIX Availability Manager Becoming acquainted with status in MIMIX Availability Manager on page 121 Introduction to MIMIX Availability Manager MIMIX Availability Manager is a simplified graphical user interface for managing MIMIX installations across your enterprise once your environment is configured. It provides a high level, at-a-glance view of the health of your MIMIX enterprise as well as a summary for each installation that includes: current replication status, status of the last switch and last audit, summaries of audit status and compliance, as well as access to recoveries, notification details, services, monitors, policies, and command history. MIMIX Availability Manager is specifically designed to make managing your MIMIX installations easier and provide an even greater level of switch-ready confidence. Contextual online help is available within the MIMIX Availability Manager product to assist you in setting your preferences and completing tasks. MIMIX Availability Manager also includes MIMIX IntelliStart, a wizard that guides you through the initial planning, modeling, configuration, and deployment of your MIMIX environment prior to starting MIMIX Availability Manager. Introduction to MIMIX IntelliStart MIMIX IntelliStart is a wizard to guide you through the initial planning, modeling, and configuration of your MIMIX environment. MIMIX IntelliStart is automatically installed when MIMIX Availability Manager is installed. MIMIX IntelliStart can also be used as a standalone product by downloading it from Support Central. MIMIX IntelliStart consists of six phases. When using MIMIX IntelliStart as a standalone product, you can complete the phases up to the Deployment phase. The Deployment and Start phases require a MIMIX installation on both the source system and target system. MIMIX IntelliStart consists of six key phases: Interview - Important information regarding your environment, availability goals, and user contacts is collected. Discovery - Automatically seeks out and identifies the elements of your system that should be replicated under best practices for MIMIX. A recommended list of these elements is then provided for your review. If you wish, you can manually select the data to be replicated. IT Analysis - Evaluates your environment and isolates communication bandwidth needs that should be addressed in order to ensure peak replication performance. Modeling - Uses consultant-level expertise to determine the most effective and efficient means of configuring items for replication. Deployment - Automatically configures the MIMIX installation for peak performance based upon the results of the previous phases. Start - Guides you through the final steps that will start your HA environment, 100

101 Introduction to MIMIX IntelliStart including the initial synchronization which ensures that data is the same on each system. Using MIMIX IntelliStart with MIMIX Availability Manager MIMIX IntelliStart is automatically installed when MIMIX Availability Manager is installed. Follow the procedures in this section to install and start MIMIX Availability Manager. When you open the MIMIX Availability Manager Welcome page for the first time, select to login to MIMIX IntelliStart. The wizard will step you through the phases to configure a MIMIX installation. Online help within MIMIX IntelliStart is available to assist you. If you previously used MIMIX IntelliStart as a standalone product, the following must be completed before installing MIMIX Availability Manager and continuing with the MIMIX IntelliStart Deployment phase: 1. You must have logged out of the MIMIX IntelliStart standalone version used. 2. You must perform the end MIMIX Availability Manager procedure. See Ending MIMIX Availability Manager on page 134. For more information, see MIMIX Availability Manager post-install steps on page 39. Using MIMIX IntelliStart as a standalone product You can use MIMIX IntelliStart as a standalone product from the web. You can complete the first four phases of MIMIX IntelliStart which result in a recommended configuration model for your environment. The information gathered during the MIMIX IntelliStart planning and modeling phases can later be used to configure your MIMIX installation before logging in to MIMIX Availability Manager. To use MIMIX IntelliStart as a standalone product do the following: 1. You should receive a licence key for MIMIX IntelliStart from your MIMIX Services representative. The Services representative sends the license key in a file attached to an Save the license key file to your preferred location. Do not change the filename. The first time you log in to MIMIX IntelliStart, you are required to register the license using this license key. You will need to access this file containing the license key. 3. Download MIMIX IntelliStart and follow the prompts in the MIMIX IntelliStart installation wizard. You can choose to have the wizard automatically start required services for you, or you can choose to manually start these services. If you choose to manually start required services, you will need to follow the steps in Starting MIMIX Availability Manager on page 134. Note: MIMIX IntelliStart copies the license key from the location you specified. This may take a few moments. Online help within MIMIX IntelliStart is available to assist you. You can only complete the first four phases, Interview, Discovery, IT Analysis, and Modeling using MIMIX IntelliStart as a standalone product. If you decide to pursue a MIMIX environment, the 101

102 About MIMIX Availability Manager following must be completed before installing MIMIX and completing the MIMIX IntelliStart configuration phases: 1. You must have logged out of the MIMIX IntelliStart standalone version used. 2. You must perform the end MIMIX Availability Manager procedure. See Ending MIMIX Availability Manager on page

103 Requirements for MIMIX Availability Manager Requirements for MIMIX Availability Manager MIMIX Availability Manager has additional requirements for IBM i software, MIMIX software, and PC software, as described in this topic. System i software requirements In an environment running MIMIX Availability Manager, each system has one of two roles: The server system is the main system on which the MIMIX Availability Manager is installed and run. The monitored systems are the systems that the server system observes and reports status. In some environments, the server system is also a monitored system. Table 14 and Table 15 list the specific software components that must be installed on your system, depending on the role they play in your environment. The software requirements for the monitored systems are a subset of those for the server system. Before you install the prerequisite software, make sure you know your system s name or TCP/IP address. Also, ensure that Java is set up correctly on your system. See Determining if Java is set up correctly on page 105. Table 14 lists requirements for systems running the IBM i 5.4.release Table 14. IBM i V5R4 - System requirements for MIMIX Availability Manager and MIMIX IntelliStart Prerequisite Licensed Programs Minimum required Where to install Notes 5722SS1 *BASE - i5/os operating system V5R4 Server system Monitored systems Option 12 - Host Servers Option 30 - QShell Interpreter Base operating system level Base operating system level Server system Monitored systems Server system JC1 *BASE - IBM Toolbox for Java Base operating system level 5722JV1 *BASE - IBM Developer Kit for Java (JDK) Base operating system level Server system Server system 2 Option 7- Java Developer Kit 5.0 Base operating system level Server system IBM PTFs 3 103

104 Table 14. IBM i V5R4 - System requirements for MIMIX Availability Manager and MIMIX IntelliStart Prerequisite Licensed Programs Minimum required Where to install Notes Notes: 1. For more information, see 2. To determine your version, see Determining the JDK version and group PTF level on page To see the latest IBM PTF requirements, visit 03.ibm.com/servers/eserver/support/iseries/index.html. Table 15 lists requirements for systems running the IBM i 6.1.release. Table 15. IBM i V6R1 - System requirements for MIMIX Availability Manager and MIMIX IntelliStart Prerequisite Licensed Program Minimum required Where to install Notes 5761SS1 *BASE - i5/os operating system IBM i V6R1 Server system Monitored systems Option 12 - Host Servers Option 30 - QShell Interpreter Base operating system level Base operating system level Server system Monitored systems Server system JC1 *BASE - IBM Toolbox for Java Base operating system level 5761JV1 *BASE- IBM Developer Kit for Java (JDK) Base operating system level Server system Server system 2 Option 7 -Java Developer Kit 5.0 Base operating system level Server system IBM PTFs 3 Notes: 1. For more information, see 2. To determine your version, see Determining the JDK version and group PTF level on page To see the latest IBM PTF requirements, visit 03.ibm.com/servers/eserver/support/iseries/index.html. Determining the JDK version and group PTF level Use this procedure to determine which version of the IBM Developer Kit for Java (JDK) is installed on your system. On the command line, do the following: 1. Type GO LICPGM and press Enter. 104

105 Requirements for MIMIX Availability Manager MIMIX requirements 2. Type a 10 on the command line to display the licensed programs that are installed on this system and press Enter. 3. Ensure that the Java Developer Kit 5.0 licensed program is installed. 4. Press F11 to display the operating system release level. 5. Press F11 again to display the product option. 6. Ensure that product option 7 is installed for the Java Developer Kit 5.0 licensed program. 7. Ensure the Java group PTF level is current on your system. Determining if Java is set up correctly Use this procedure to determine if Java is correctly set up on your system. On the command line, do the following: 1. Type QSH CMD('java -Djava.version=1.5 Hello') 2. If your Java setup is correct, you will see results similar to the following: java version "5.0" Java 2 Runtime Environment, Standard Edition (build 5.0_08-b02) Classic VM (build 5.0, build JDK-5.0, native threads, jitc_de) Press ENTER to end terminal session. Hello World Press ENTER to end terminal session. 3. Press Enter to end the session. Table 16 lists the MIMIX components required to operate the MIMIX Availability Manager. Table 16. MIMIX requirements for MIMIX Availability Manager and MIMIX IntelliStart Prerequisite Software Level Where to Install Notes License Manager (formerly License and Availability Manager) MIMIX Enterprise or MIMIX Professional (formerly MIMIX ha1 or MIMIX halite, respectively) version 6 or higher Server system Monitored systems version 6 Monitored systems The system running the Run Switch Framework (RUNSWTFWK) command during a switch. 1, 2, 3 4, 5 105

106 Table 16. MIMIX requirements for MIMIX Availability Manager and MIMIX IntelliStart Prerequisite Software Level Where to Install Notes Notes: 1. MIMIX Availability Manager can be installed on a system with or without MIMIX. On systems without MIMIX, you must install version 6 of License Manager. MIMIX Availability Manager does not support MIMIX version 7. If you plan to continue using MIMIX Availability Manager to monitor version 5 or 6 MIMIX installations, a service pack is required before installing version 7 of License Manager. Install service pack or higher on server system for MIMIX Availability Manager as well as on the systems to be monitored. 2. It is recommended that MIMIX Availability Manager be installed on more than one system. 3. MIMIX IntelliStart must be installed on the source system. This is especially important if you are using MIMIX IntelliStart as a standalone product. See MIMIX IntelliStart considerations when used as a standalone product on page These prerequisites are also required for MIMIX Switch Assistant. 5. A license key for MIMIX Enterprise (H1), MIMIX Professional (HT), or MIMIX Monitor (MM) is also required. MIMIX IntelliStart considerations when used as a standalone product PC requirements If you previously used MIMIX IntelliStart as a standalone product, do the following before installing MIMIX Availability Manager and completing the MIMIX IntelliStart configuration phases: Log out of the MIMIX IntelliStart standalone version used. End MIMIX Availability Manager. See Step 4 in Prepare your environment by ending products on page 27. Resume MIMIX IntelliStart with the Deployment phase once your installation is ready. Table 17 lists the minimum requirements for any client PC running the MIMIX Availability Manager. Table 17. PC requirements for the MIMIX Availability Manager and MIMIX IntelliStart Prerequisite Minimum required Notes Browser Internet Explorer 6.0 or above, Firefox or above, Mozilla 1.7 or above, Netscape 7.0 or above Java Plug-in Version 5.0 or above 1 Java Script Must be enabled Cookies Must be enabled 2 Pop-up blockers Must be disabled 3, 4 106

107 Requirements for MIMIX Availability Manager Table 17. PC requirements for the MIMIX Availability Manager and MIMIX IntelliStart Prerequisite Minimum required Notes Notes: 1. To determine whether your Java Plug-in is at the correct level, see the topic in Command prompter not working on page Set the cookie configuration option to Allow per-session cookies (not stored) and Allow cookies that are stored on your computer. 3. See Disabling pop-up blockers on page Alternatively, you can allow pop-up blockers on the MIMIX Availability Manager server and port. 107

108 Setting time zones in the SystemDefault.properties file The Java user.timezone property specified in the SystemDefault.properties file defaults to Greenwich Mean time (GMT). In order for notification entries and message log information to appear correctly in MIMIX Availability Manager, change the SystemDefault.properties file to reflect your time zone. If the file does not already exist, you will need to create it. Use the Work with Time Zone Desc (WRKTIMZON) command to determine the system time zone. If the file does not exist, you must create it. It is recommended that you perform the following on all systems that you intend to monitor with MIMIX Availability Manager. Minimally, perform these procedures on the system on which the MIMIX Availability Manager server resides. To change the SystemDefault.properties file If the SystemDefault.properties file exists, do the following to change it as necessary: 1. On a command line, type the following and press Enter: wrklnk '/QIBM/UserData/Java400' 2. On the Java400 directory, select option On the SystemDefault.properties file, select option Change or add the user.timezone property as required. This property has the following syntax: user.timezone=<time_zone> For example, central time zone appears as: user.timezone=cst For a list of supported values, see 5. Press F2 to save the setting. 6. Press F3 to exit. 7. To have the change take effect, end and restart the web server. Use the procedures in Ending MIMIX Availability Manager on page 134 followed by Starting MIMIX Availability Manager on page 134. To create the SystemDefault.properties file Do the following: 1. On a command line, type the following and press Enter: edtf '/QIBM/UserData/Java400/SystemDefault.properties' 2. Change or add the user.timezone property as required. This property has the following syntax: user.timezone=<time_zone> 108

109 Enabling MIMIX Switch Assistant For example, central time zone appears as the following: user.timezone=cst For a list of supported values, see 3. Press F2 to save the setting. 4. Press F3 to exit. 5. To have the change take effect, end and restart the web server. Use the procedures in Ending MIMIX Availability Manager on page 134 followed by Starting MIMIX Availability Manager on page 134. Enabling MIMIX Switch Assistant To use MIMIX Switch Assistant functions available through MIMIX Availability Manager, you must have a configured MIMIX Model Switch Framework and have it identified in your installation policies. If you do not have a configured switch framework, contact your Certified MIMIX Consultant. See the additional information about setting policies for switching within online help in MIMIX Availability Manager or in the MIMIX Operations book. Like all MIMIX Availability Manager operations, MIMIX Switch Assistant submits commands in batch. As a result, if your default switch framework uses exit programs that perform interactive steps, switch steps may appear to run indefinitely. The best, long-term solution is to evaluate the switch exit programs called by the switch framework and make the necessary updates to remove any actions that require a user response during the switch process. Otherwise, procedures for checking and responding to pending inquiry messages during the switch are provided in the online help for MIMIX Availability Manager. Changing prestart job settings for optimal performance Prestart jobs are batch jobs that run before a program on a remote system sends a program start request. The QSQSRVR and QZDASOINIT prestart jobs provide JDBC access to system resources that your Java applications request. For optimal performance, these jobs must have adequate memory and activity levels when they are needed. To ensure this, you should increase the number of prestart jobs and add the jobs to a memory pool that is not used by other jobs. To add these jobs to a dedicated memory pool, see Working with the prestart jobs in Java and WebSphere Performance on IBM iseries Servers. iseries Access for Web iseries Access for Web is a alternate command interface to the command prompter used by MIMIX Availability Manager. Installing it is optional. iseries Access for Web enables you to access a system from a web browser using standard Internet 109

110 protocols. iseries Access for Web is a set of servlets that run on IBM i Java Virtual Machine (JVM) and generate HTML output to a browser. Two methods of configuring iseries Access for Web are possible. Only the first method is supported by MIMIX Availability Manager. This method allows you to configure a pair of servers on each system that will use iseries Access for Web. To configure iseries Access for Web (5722XH2), refer to the IBM redbook, Note: Ignore chapter 2.5 of the redbook, which describes the unsupported method for configuring iseries Access for Web. For related information, visit the iseries Access for Web homepage at 1.ibm.com/servers/eserver/iseries/access/web/. Systems available to monitor The first time you use MIMIX Availability Manager, the system on which the MIMIX Availability Manager server is installed is available to view. If you used MIMIX IntelliStart to create and deploy a MIMIX configuration, only one system may be identified to MIMIX Availability Manager. The other systems in the configuration must be identified so that you can monitor them. You can do this through Administration Preferences. In addition, the first time that users log in to MIMIX Availability Manager, they must use Preferences to select the systems they want to monitor from the available list. Adding a system to the list of available systems Do the following: 1. Click Preferences. 2. From the Preferences window click Administration. 3. Select i5/os Systems from the Preferences Defaults area in the navigation bar. 4. From the i5/os Systems window, at the System prompt, type the name of the system. Click Add. 5. Click Save. 6. To close the window, click Close. 7. To exit preferences, click Return. Setting individual user preferences Each new user of MIMIX Availability Manager must set preferences after logging in the first time. MIMIX Availability Manager will prompt you to select preferences for systems, installations, and data groups when the necessary selections have not yet been made. 110

111 Setting individual user preferences You must select systems before you can select installations that exist on a system. Similarly, you must select installations before you can select data groups in an installation. Once these and any other preference selections are saved, the information is retained for use in subsequent sessions. Selecting systems to monitor Do the following: 1. Click Preferences. 2. From the Preferences area in the navigation bar, select i5/os Systems. 3. From the i5/os System Preferences window, select the system you want from the list of available systems and click Add. 4. When you have added all the systems you want, click Save. Selecting MIMIX installations to monitor MIMIX Availability Manager can monitor installations that are running earlier levels of MIMIX. For example, version 6 of MIMIX Availability Manager supports monitoring installations that are running version 5 of MIMIX. MIMIX installations running version 7 cannot be monitored with MIMIX Availability Manager. Do the following: 1. Click Preferences. 2. In the navigation bar, select Installation from the Preferences area. Then select the system you want from the i5/os Systems area. 3. From the content area of the Installation Preferences window, select the installation you want from the list of available installations and click Add. 4. When you have added all the installations you want, click Save. Selecting data groups to monitor Do the following: 1. Click Preferences. 2. From the Preferences area in the navigation bar, select Data Group. Then select the system you want from the i5/os Systems and the installation from the Installations area. 3. From the content area of the Data Group Preferences window, select the data group you want from the list of available data groups and click Add. 4. When you have added all the data groups you want, click Save. 5. To exit preferences, click Return. 111

112 Confirming a MIMIX IntelliStart automatic synchronization The automatic synchronization option in the Start phase of MIMIX IntelliStart starts a series of audits that synchronize the data to be replicated and is shown in the Audit Summary window. These audits perform comparisons and synchronize items for which differences are detected. The automatic synchronization process will make several attempts at synchronization before reporting that difference as not recovered. When the audit jobs complete, MIMIX is automatically started. Automatic synchronization starts multiple audits for each data group. For each data group, automatic synchronization starts the following rules: #OBJATR, #DGFE, #FILATR, and #FILATRMBR are run sequentially in one job #IFSATR and #DLOATR are run sequentially in one job To ensure that your MIMIX environment runs smoothly, check the results of these audits for any items that are not recovered and take action to synchronize them. Displaying audit status You can view audit status from either interface. From MIMIX Availability Manager, do the following: 1. Select the installation you want from the navigation bar. 2. Select Audit Summary from the navigation bar. 3. The Audit Summary window shows all audits for the data groups that are selected for viewing for the installation. Check the following: Icons next to the Rule column indicate overall audit status. The State column indicates the current state of audit activity. The Results column summarizes the result of the last audit. Click Help to see descriptions of values for these fields and icons. 4. To view additional details, select the Details action and click. From a 5250 emulator, do the following: 1. Do one of the following to access the Summary view of the Work with Audits display: From the MIMIX Intermediate Main Menu, select option 6 (Work with audits) and press Enter. Then use F10 as needed to access the Audit summary view. Enter the command: installation-library/wrkaud VIEW(*AUDSTS) 2.Check the value shown in the Audit Status column. Press F1 (Help) for a description of status values. 3. To view additional information about an audit, use option 5 (Display). 112

113 Confirming a MIMIX IntelliStart automatic synchronization Interpreting audit results When viewing results of audits, the starting point is the Audit Summary window. You may also need to view the output file or the job log, which are only available from the system where the audits ran. In most cases, this is the management system. Additional detailed information about resolving audit problems and displaying the job log for an audit is available within MIMIX Availability Manager online help. 113

114 Performing MIMIX IntelliStart manual synchronization This procedure uses MIMIX AutoGuard to ensure that your environment is ready to start replication. Shipped policy settings for MIMIX allow audits to automatically attempt recovery actions for any problems they detect. You should not use this procedure if you have already synchronized your systems using the Synchronize Data Group (SYNCDG) command or the automatic synchronization method in MIMIX IntelliStart. The audits used in this procedure will: Verify that journaling is started on the source and target systems for the items you identified in the deployed replication patterns. Without journaling, replication will not occur. Verify that data is synchronized between systems. Audits will detect potential problems with synchronization and attempt to automatically recover differences found. Do the following: 1. Check whether all necessary journaling is started for each data group. Enter the following command: (installation-library-name)/dspdgsts DGDFN(data-group-name) VIEW(*DBFETE) On the File and Tracking Entry Status display, the File Entries column identifies how many file entries were configured from your replication patterns and indicates whether any file entries are not journaled on the source or target systems. If your configuration permits user journal replication of IFS objects, data areas, or data queues, the Tracking Entries columns provide similar information. 2. Use MIMIX AutoGuard to audit your environment. To access the audits, enter the following command: (installation-library-name)/wrkaud 3. Each audit listed on the Work with Audits display is a unique combination of data group and MIMIX rule. When verifying an initial configuration, you need to perform a subset of the available audits for each data group in a specific order, shown in Table 18. Do the following: a. To change the number of active audits at any one time, enter the following command: CHGJOBQE SBSD(MIMIXQGPL/MIMIXSBS) JOBQ(MIMIXQGPL/MIMIXVFY) MAXACT(*NOMAX) b. Use F18 (Subset) to subset the audits by the name of the rule you want to run. c. Type a 9 (Run rule) next to the audit for each data group and press Enter. 114

115 Performing MIMIX IntelliStart manual synchronization Repeat Step 3b and Step 3c for each rule in Table 18 until you have started all the listed audits for all data groups. Table 18. Rules for initial validation, listed in the order to be performed. Rule Name 1. #DGFE 2. #OBJATR 3. #FILATR 4. #IFSATR 5. #FILATRMBR 6. #DLOATR d. Reset the number of active audit jobs to values consistent with regular auditing: CHGJOBQE SBSD(MIMIXQGPL/MIMIXSBS) JOBQ(MIMIXQGPL/MIMIXVFY) MAXACT(5) 4. Wait for all audits to complete. Some audits may take time to complete. Then check the results and resolve any problems. You may need to change subsetting values again so you can view all rule and data group combinations at once. On the Work with Audits display, check the Audit Status column for the following value: *NOTRCVD - The comparison performed by the rule detected differences. Some of the differences were not automatically recovered. Action is required. View notifications for more information and resolve the problem. Note: For more information about viewing audit results and resolving reported problems is available within MIMIX Availability Manager online help. 115

116 Logging in to MIMIX Availability Manager The first time you log in to MIMIX Availability Manager, you could see one of several windows. If you are logged in to the available systems and there are problems, you will see the system and installation with the highest severity problem. If there are no problems on any of the systems in view, you will see the Enterprise view. If you did not log in to any systems when you logged in to the server, you will see the Login window for the first system. Log in to the system so you can continue. You may be prompted to select an installation. For many windows, you can adjust the amount of information displayed by changing preferences. You can change preferences at any time. Many tasks can be performed in the main window. Some tasks launch a new window while leaving the main window active. You can easily close the new window by using the Close button. Your location is remembered Once you visit a location, MIMIX Availability Manager remembers that you were there. For example, say you viewed notifications for installation ABC, then viewed data group status for installation XYZ. The next time you return to installation ABC, MIMIX Availability Manager will display the notifications. When you select a system in the Enterprise view, your location is reset. You will be taken to the most severe problem. If there are no problems, you will be taken to the first data group on the Data Group Status page. If you are not logged in to the system, you will be taken to the Login window for that system. Areas of the window in MIMIX Availability Manager MIMIX Availability Manager uses a similar layout for every window, shown in Figure 1. The primary elements of every window are: Title bar - The title bar includes buttons for accessing online help. It also includes navigational buttons, as needed, to close a secondary window or return to the previously viewed window. Navigation bar - The vertical navigation bar is both a navigational tool and a highlevel status indicator. Labeled areas within the navigation bar enable access to specific areas such as systems, installations, and details. The selections available may be relative to other selections in the navigation bar. For example, the installations available to select are dependent on the system selected. When used in order from top to bottom, labeled areas help you to narrow a selection until the desired information appears in the content area. Status icons quickly identify areas with potential problems. See Status icons - overview on page 119. Note: Some windows may not have the bar or selected areas of the navigation bar. 116

117 Areas of the window in MIMIX Availability Manager Content area - The content area changes based on your selections in the navigation bar. Typically, your location is identified in the summary at the top and corresponds to selected items in the navigation bar. Many windows display information in list form below the Toolbar. The Toolbar, when available, provides access to functions that are relevant to the displayed information. Figure 1. Basic window layout The content area of the Data Group Status window has a unique layout, shown in Figure 2. For this window, a portion of the content area is used as a selection list. The 117

118 data group selected is highlighted in gray and its summary status is displayed to its right in the gray-highlighted area. Figure 2. Unique content area layout for the Data Group Status window. Additional navigation and selection aids Navigation within the MIMIX Availability Manager is simple and predictable. Elements such as the navigation bar, buttons, filters, and drop-down lists, function consistently throughout the interface with few exceptions. Flyover help - Flyover help provides the first level of information about a problem or item and often identifies a predetermined action. This type of help is available for most status icons, buttons, and actions. To see flyover help, hover over the interface element with your mouse pointer. In many cases, clicking on the element will take an action that is indicated by its flyover help. For example, flyover help for a problem action button indicates what action is available; clicking on the button takes you to a command that will resolve the problem or takes you directly to the correct window where you can see the error and take steps to resolve the problem. Status icons - Icons always represent status. Each icon has a unique shape and color combination. Many status icons are also links which provide a shortcut to a predetermined action or additional information. Flyover help identifies both the status 118

119 Areas of the window in MIMIX Availability Manager and the action that will occur when clicked. The following provides an overview of common status icons: Status icons - overview Status Action required Unknown Partially Active Ended Switching Attention Unknown (No icon) Active Disabled Description An error occurred. Immediate user action is required. Some or all status information is unavailable. Immediate user action is required. Processes are changing state or some processes are active while others are ended. User action may be required. All processes have ended normally due to a user request. User action is necessary to restart the processes. One or more data groups is in the process of switching which system is used as the source for replication. User action may be necessary. A warning condition exists that is either automatically correctable or is a non-critical condition. User action may be necessary. The status is unknown because collector services is not active. User action is necessary to start collector services. Processes are active. The process has been disabled. Underlined text - Text that is underlined when you hover over it can be used to navigate to a predetermined area. Flyover help indicates the action. Clicking on underlined text can take a predefined action, display additional selection criteria, such as another navigation area, or change the content in the content area. Selecting listed items with checkboxes - Several windows contain lists from which you can select multiple items to act upon with actions available in the toolbar. Checkboxes next to each item allow selection. A checkbox at the top of a list next to a heading allows selection or deselection of all items in the list at once. Once items are selected, you can use any of the Selected buttons from the toolbar. Selecting actions from drop-down lists - Drop-down lists provide available actions for an item. The location of the drop-down list determines the scope of its available actions. In summary area - When a drop-down list appears in the summary area at the top of a window, its actions apply to all the items on the window. With some notable exceptions, such as starting all or ending all data groups, the actions can affect data groups that may not be visible from MIMIX Availability Manager. Online help notes these exceptions. Next to an item - When a drop-down list appears next to an item, its actions apply to only that item. These drop-down lists cannot be used in conjunction with checkboxes. In some cases, the recommended best action is the default action for the item and can vary from item to item in the list. In a toolbar - Drop-down lists available in toolbars are for filtering. The available 119

120 Other useful tips actions can be used to filter the content displayed. Ellipses - Actions that will prompt a command in another window or confirmation box before occurring are always followed by an ellipsis (...). Filtering - Filter buttons on the toolbar and not associated with a drop-down list offer a larger set of filtering criteria. Clicking the Filter button displays a Filter window, from which you can specify filter criteria for items within the current window. Actions that can cause changes to your MIMIX environment always have confirmations. Other actions such as displaying more information do not have confirmations. Buttons can appear in the toolbar or within areas of a window. They may include a graphic, text, or both. Buttons are always gray. When selecting an action that prompts a command, MIMIX Availability Manager preselects values on the command based on the item you selected. For example, selecting the action to start system managers from the Services window will prompt the Start MIMIX Managers command and will preselect system managers (*SYSMGR) in the appropriate field. 120

121 Becoming acquainted with status in MIMIX Availability Manager Becoming acquainted with status in MIMIX Availability Manager MIMIX uses the priority assigned to status values to ensure that Items with the highest priority, those for detected problems or situations that require attention, are reflected on the highest level of each user interface. Additional detail and lower priority items can be viewed by drilling down to the next level within the interfaces. In MIMIX Availability Manager, the highest level is the Enterprise View window. MIMIX Availability Manager is designed so that problems or actions that require attention are easily detected. From any window in the interface, you can quickly see if problems exist. Status values are prioritized and those requiring immediate attention or intervention have icons to draw your attention. Additionally, these statuses are bubbled up to the next higher window all the way up to the Enterprise View. Where appropriate, items are sorted to ensure that the highest severity item is at the top of the list. The Enterprise View - your status shortcut The Enterprise view, Figure 3, provides at-a-glance recognition of where problems exist and their severity. Systems are listed based on their status from left to right, with the most severe problems listed first. Figure 3. Enterprise View showing a problem. Status on the navigation bar The navigation bar provides a quick high level indication of where problems exist and their severity. Default settings list systems and installations in an order based on their 121

122 status, with the most severe problems listed first. Regardless of which detail you are currently viewing, the navigation bar always reflects current status for all of the systems and installations visible in your session. Figure 4 shows how a problem in data groups and auditing are also reflected at the installation and system level. Without viewing a different detail window, you can see that there is a problem with a data group in installation DEMO1 on system AS01 and that there are audits approaching out of compliance and either running or waiting to run. Figure 4. Problem areas are represented by icons in the navigation bar. Figure 5 shows how the severity of the problem is reflected in the content area as well as the navigation bar. The data group with the problem is identified in the list. Also, the Summary area identifies the cause of the problem and an appropriate action for 122

123 Becoming acquainted with status in MIMIX Availability Manager resolving it. Displaying details from the Summary area provides access to additional information about replication activity and problems. Figure 5. A problem reflected on the Data Group Status window. 123