MIMIX-specific security for MIMIXOWN and MIMIXCLU - Assure_DB2_Data_Monitor_(DB2MON) - Assure_Elevated_Authority_Manager_(EAM) - Assure_Encryption - Assure_Monitoring_and_Reporting_(AMR) - Assure_Secure_File_Transfer - Assure_Secure_File_Transfer_ - Assure_Secure_File_Transfer_PGP - Assure_Secure_File_Transfer_with_PGP - Assure_Security_Multi-Factor_Authentication_(MFA) - Assure_System_Access_Manager_(SAM) - Required_for_All_Modules - assure_ioptimize - assure_itera - assure_mimix - 10.0

License Manager for IBM i Products

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure Security > Assure Encryption
Assure Security > Assure DB2 Data Monitor (DB2MON)
Assure MIMIX™ Software
Assure Security > Assure Monitoring and Reporting (AMR)
Assure Security > Assure Elevated Authority Manager (EAM)
Assure Security > Assure Security Multi-Factor Authentication (MFA)
Assure Security > Assure Secure File Transfer with PGP
Assure Security > Assure Secure File Transfer
Assure Security > Required for All Modules
Assure iOptimize
Assure iTERA
Assure Security > Assure System Access Manager (SAM)
Version
10.0
Language
English
Product name
Assure
Title
License Manager for IBM i Products
Copyright
2023
First publish date
1999

In addition to the general requirements for TCP/IP, replication, auditing, and internal spooled files listed in Table 1, MIMIX has the following additional requirements for the MIMIXOWN and MIMIXCLU user profiles.

Procedures and step programs for application group operations 

In environments configured with application groups, replication is started, stopped, and switched at the application group level using procedures that run a series of step programs. These procedures and steps run under the MIMIXOWN user profile.

Model switch framework programs for switching 

In environments configured with data groups only, customized programs for switching the direction of replication through an implementation of MIMIX Model Switch Framework or MIMIX Switch Assistant run under the MIMIXOWN user profile.

Monitors 

MIMIX uses monitors for supporting functions. These monitors may be shipped with the product or created when needed. MIMIX also supports user-created monitors. All monitors run under the MIMIXOWN user profile which is shipped with special authority to all objects (*ALLOBJ).

*ALLOBJ authority is needed so that each monitor has access to all objects that it watches, such as journals and message queues. *ALLOBJ is also needed for access to the job scheduler and to any interface exit programs, condition programs, and event programs called by the monitor.

If 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.

 Files that have protected rows or columns 

In environments that have enabled permissions or masks on files to implement row and column access control (RCAC), the MIMIXOWN user profile must be an allowed user of the QIBM_DB_SECADM function on all systems within the MIMIX instance. All systems must be running IBM i 7.3 or higher.

Files with versioned relationships 

In environments that have defined versioned relationships between system-period temporal tables and history files, the MIMIXOWN user profile must be an allowed user of the QIBM_DB_SECADM function on all systems within the MIMIX instance. All systems must be running IBM i 7.3 or higher.

Temporary journaling environments 

Assure MIMIX Enterprise includes functionality that creates temporary journaling environments while copying or reorganizing active files. This activity can occur as part of replication or can be initiated manually from commands. Requests to copy or reorganize active files in this manner are submitted using the default job description for the MIMIXOWN user profile.

Assure Security product environment protected by MIMIX replication

In environments where MIMIX is configured to protect and switch your Assure Security environment, the MIMIXOWN user profile must be an allowed (*ALLOWED) user of the QIBM_DB_SECADM function on systems running IBM i 7.3 or higher.