You are on page 1of 67

Read This First

Version 8.1 Service Pack 8.1.13.00


MIMIX version 8.1.13.00 includes all relevant changes to earlier level 8.1 service packs, 8.0.17.00, and
earlier levels of version 8.0.
Prerequisites:
• The minimum level required for the IBM i operating system is IBM i 6.1.
• Upgrades to MIMIX version 8.1 require version 8.1 license keys and are supported from any MIMIX
version 8.0 service pack (8.0.01.00 or higher).
• MIMIX portal application version 8.1.13.00 is the minimum version required to manage MIMIX
8.1.13.00 instances and later.
• MIMIX portal application version 8.1.13.00 requires Vision Solutions Portal (VSP) version 3.1.03.00
or higher.

Supported installation processes


This document supports:
• Installing or upgrading the product, its portal application, and VSP on systems running IBM i using
the MIMIX Installation wizard for IBM i. The wizard is recommended and supports standard and
custom install options.
• Pre- and post-install instructions for installing the product using native user interface command
processes. Actual install instructions can be found in the Using License Manager book.
To see requirements for using the wizard, click the More Info link from the wizard’s Welcome panel.
Note: The MIMIX portal application requires VSP 3.1, which is installed by the MIMIX Installation
Wizard. The first time you install VSP version 3.1 on a system, you must also upgrade portal
applications for any other products to a level compatible with VSP 3.1. If you cannot upgrade a
product’s portal application, you may need to install a separate VSP server. For more
information, see “VSP 3.1 compatibility with product portal applications” on page 3.

Action required
This document provides service pack installation instructions for all supported installation media.
Required Document Section
“Before installing the service pack” on page 5
“Installing the service pack on IBM Power Systems” on page 9
“After installing the service pack instructions” on page 12

Important changes
You should be aware of the following information before you install this service pack. Also check the
Before Installing and After Installing sections for potential configuration changes.
Enhancements
Enhancement to the Virtual Switch (SWTVRT) procedure . . . . . . . . . . . . . . . . . . . . 18
Support for copying VSP configuration between servers . . . . . . . . . . . . . . . . . . . . . 19

MIMIX and Vision Solutions are registered trademarks and iOptimize, MIMIX Availability, MIMIX Enterprise, MIMIX Global, and
MIMIX Professional are trademarks of Vision Solutions, Inc. AIX, AS/400, DB2, eServer, i5/OS, IBM, iSeries, OS/400, Power,
PowerHA System i, and WebSphere are trademarks of International Business Machines Corporation. All other trademarks are
the property of their respective owners.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 1
To see a list of fixes included with this service pack, see “Fixes included in service pack 8.1.13.00” on
page 18.

Features in MIMIX version 8.1


The following is a cumulative list of all behavior changes and enhancements released in version 8.1,
since inception. The list is sorted alphabetically.
Behavior changes
Automatic problem detection and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Changed behavior for OBJONTGT policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Changes to support for unconfirmed entries in synchronous remote journaling
environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Compatibility of VSP with product portal applications . . . . . . . . . . . . . . . . . . . . . . . . 65
Exclude from Replication action cleans up library exception selection rules . . . . . . 36
Fewer delayed activities for locked objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Product portal application compatibility with VSP 3.1 . . . . . . . . . . . . . . . . . . . . . . . . . 3
VSP 3.1 requires 64-bit Java . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Enhancements
Automatic problem detection and recovery enhancements . . . . . . . . . . . . . . . . . . . . 55
Automatic resolution of deadlocks caused by long-running open commits . . . . . . . . 35
Customizable procedure for performing backup operations . . . . . . . . . . . . . . . . . . . 60
Enhanced support for excluding IFS objects using wildcard characters . . . . . . . . . . 21
Enhancement to the Virtual Switch (SWTVRT) procedure . . . . . . . . . . . . . . . . . . . . 18
Improvements for reconnecting an instance within a subscription . . . . . . . . . . . . . . 29
Improvements to Data Protection Reports and actions for configuring from VSP . . 47
Improvements to RJ Link threshold reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
MIMIX DR supports virtual failover and priority auditing . . . . . . . . . . . . . . . . . . . . . . 50
MIMIX Installation Wizard now supports Windows® 8.1 and Windows® 10 . . . . . . . 66
More access to file selection rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
More accurate status displayed on Data Group Details and Activities portlet
during an outage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
New retrieve commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
New value to decrease retention time before cleanup of completed DG activity
entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Object auditing level of cooperatively processed *DTAARA and *DTAQ objects
no longer changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Subscriptions support sending traps to SNMP management applications . . . . . . . . 26
Subsystem description (*SBSD) replication enhancement . . . . . . . . . . . . . . . . . . . . 32
Support for copying VSP configuration between servers . . . . . . . . . . . . . . . . . . . . . 19
Support for environments running IBM i 7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Support for integration with SNMP management applications . . . . . . . . . . . . . . . . . 24
Support for MIMIX-managed foreign key constraints on target node . . . . . . . . . . . . 61
Support for omitting content of *DTAARA and *DTAQ objects from system
journal replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Support for virtual switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Understanding correction activity in your MIMIX environment video . . . . . . . . . . . . . 45
Viewing and comparing details of replicated objects . . . . . . . . . . . . . . . . . . . . . . . . . 50

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 2
VSP 3.1 compatibility with product portal applications
Vision Solutions Portal (VSP) version 3.1 is included with this service pack. If you use default options in
the installation wizard for the product, the wizard automatically installs or upgrades VSP and deploys the
product portal application on all systems in the installation.
The first time VSP version 3.1 is installed on a system, you must upgrade any other portal applications
on the same system to a level that is compatible with VSP version 3.1. Table 1 lists compatible portal
applications. Portal applications that cannot be upgraded to meet the compatibility requirements with
VSP 3.1 will require a VSP server that remains at version 3.0.
VSP and portal applications for MIMIX and iOptimize can be upgraded without having to upgrade their
associated products on the IBM i platform.
Note: Product portal applications can connect to and manage multiple instances of their products.
The product instances to which some of the product portal applications connect may be at
different versions. For example, a MIMIX 8.1 portal application can be used to connect to and
manage MIMIX 8.1 and MIMIX 8.0 instances. For more information, see the Vision Solutions
Portal (VSP) User’s Guide.
Action required:
• Ensure product portal applications are at a compatible version for the version of VSP included with
this service pack. See Table 1. You can use a products’ installation wizard and select the “portal
application” option to upgrade a portal application.
• If you are using VSP 3.0 on a Windows platform that does not support 64-bit applications, VSP 3.1
cannot be installed on that Windows server, be aware of the following:
– If you are using only MIMIX or iOptimize portal applications on the VSP server, you can either
install VSP 3.1 and the portal applications on a supported Windows server, or you can continue to
use VSP 3.0 and your existing portal application but you will not have access to product
enhancements implemented solely through the latest portal application interfaces.
– If you are using VSP 3.0 on a Windows platform where the Double-Take for AIX 5.0 portal
application is installed along with the MIMIX or iOptimize portal application, you need to install
VSP 3.1 and the MIMIX or iOptimize 8.1.11.00 or higher portal applications on a different
Windows server. The Double-Take for AIX 5.0 portal application is not supported on VSP 3.1.
For more information about requirements for installing VSP 3.1 on a Windows server, see the More Info
document for the Vision Solutions Portal (VSP) 3.1 & Portal Application Installation Wizard for
Windows®.

Table 1. Compatibility of supported product portal applications and VSP.

Product VSP server VSP server


Portal Application version 3.1 version 3.0

MIMIX 8.1 8.1.11.00 or higher Only 8.1.01.00 through 8.1.10.00

MIMIX 8.0

iOptimize 8.1 8.1.11.00 or higher Only 8.1.01.00 through 8.1.10.00

iOptimize 8.0

Double-Take for AIX 5.0

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 3
Superseded
This service pack includes the contents of the following superseded service packs. If you do not already
have the following service packs installed, their contents are also installed when you install service pack
8.1.13.00. To see highlights and additional fixes for a superseded service pack, click on the link.
8.1.12.00 - Highlights and fixes
8.1.11.00 - Highlights and fixes
8.1.10.00 - Highlights and fixes
8.1.09.00 - Highlights and fixes
8.1.08.00 - Highlights and fixes
8.1.07.00 - Highlights and fixes
8.1.06.00 - Highlights and fixes
8.1.05.00 - Highlights and fixes
8.1.04.00 - Highlights and fixes
8.1.03.00 - Highlights and fixes
8.1.02.00 - Highlights and fixes
8.1.01.00 - Highlights and fixes

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 4
Installation Instructions
Before installing the service pack
If you run iOptimize™ on systems or LPARs in your MIMIX installation, we strongly recommend that you
upgrade iOptimize at the same time as your MIMIX .
Note: MIMIX and iOptimize service pack cycles are coordinated for concurrent release. When there are
no fixes for iOptimize for a service pack, there will be no iOptimize product download posted for
that release level. iOptimize service packs will continue to be numbered to correspond with the
MIMIX service pack releases.
Step 1 through Step 8 identify areas that may require modifications to your MIMIX environment before
you install the service pack.
1. It is strongly recommended that you apply the latest IBM PTFs associated with IBM i releases as
they pertain to your environment. The Check IBM PTF (CHKIBMPTF) command is available as a
downloadable stream file available from Knowledgebase article 45894. It is also included in License
Manager when the service pack is installed. You only need to download the separate stream file if
you want to check the latest PTFs before installing. Instructions for downloading and using the
command are also included in the article. The knowledgebase article lists all of the recommended
PTFs for each IBM i release for which Vision supports products and replaces the recommended PTF
list previously available from Support Central. The article and command are updated regularly with
the latest information.
The CHKIBMPTF command runs on a single system and checks it for the Vision-recommended
PTFs. Run the command on all systems where you have installed or plan to install a supported
version of MIMIX, iOptimize, or iTERA. The command generates two QPRINT outputs. One output
file lists the status of only the PTFs that require attention or corrective action. The other output file
lists all the recommended PTFs and their status on the system. You can use the release-specific PTF
list in the knowledgebase article to link to PTF cover letters for additional details about a PTF.
• To check PTFs before installing the service pack, download the command from the
knowledgebase article and follow the instructions in the article to run command.
• To check PTFs after installing the service pack, use the command LAKEVIEW/CHKIBMPTF.
Resolve any issues found.
2. Move any user-created objects or programs in libraries LAKEVIEW, MIMIXQGPL, or VSI001LIB or
in the IFS location /visionsolutions/http/vsisvr to a different location before installing this
service pack. Any user-created objects or programs, including programs created as part of MIMIX
Model Switch Framework, in these locations will be deleted during the installation process. Job
descriptions, such as the job description used by the MIMIX Port job, can continue to be placed into
the MIMIXQGPL library.
3. Ensure that only user-created objects or programs related to a product installation exist within the
product’s installation library or a data library. Examples of related objects for MIMIX products include
user-created step programs, user exit programs, and programs created as part of a MIMIX Model
Switch Framework implementation.
4. If you run other products that use the same journals on the same systems as MIMIX, such as
MIMIX® Share™, iOptimize™, or MIMIX® Director™, there may be considerations for journal
receiver management. For details, see “Interaction with other products that manage receivers” in the
MIMIX Administrator Reference book.
5. Certain types of information must not be replicated. Check and change your configuration if

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 5
necessary so that the following information is not replicated:

Table 1.Data to exclude from MIMIX replication

Data Category Type Do Not Replicate

Application Temporary objects or files You may not need to replicate temporary files, work
Environment files, and temporary objects, including DLOs and
stream files. Evaluate how your applications use such
files to determine if they need to be replicated.

System Libraries IBM-supplied libraries, files, and other objects for


Environment System i, which typically begin with the prefix Q.

User profiles System user profiles, such as QSYSOPR and


QSECOFR

MIMIX Libraries LAKEVIEW


Environment (and contents) MIMIXQGPL
MIMIX product installation libraries
MIMIX data libraries - for example, mimix_0 and
mimix_1.
MXIWIZ*
#mxjrn* (MIMIX journal libraries)
VSI001LIB
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.

IFS directories /LakeviewTech


(and contents) /VISIONSOLUTIONS

User profiles LAKEVIEW


MIMIXOWN
MIMIXCLU

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 6
Table 1.Data to exclude from MIMIX replication (Continued)

Data Category Type Do Not Replicate

iOptimize If iOptimize is installed on the same system or in the same partition as MIMIX, do not
Environment replicate the following:

Libraries IOPT
(and contents) IOPT71
IOPTSPLARC
IOPTOBJARC
Note: IOPT is the default name for the iOptimize
installation library -- the library in which iOptimize is
installed. iOptimize data libraries are associated with
an iOptimize installation library and begin with the
default name.

Authorization lists IOAUTLST72


IOAUTLST71

User profiles IOPTOWNER


and corresponding message ITIDGUI
queues VSI001LIB

Device description VSINSVRT

IFS directories /VISIONSOLUTIONS


(and contents) /VisionISOImages

MIMIX Director For MIMIX Director, 8n is the release level. For example, n=1 in release 8.1. If MIMIX
Environment Director is installed on the same system or in the same partition as MIMIX, do not
replicate the following:

Libraries (and contents) ITID8n


IDSPLARC8n
IDOBJARC8n

Authorization lists IDAUTLST8n

User profiles and ITIDOWNER


corresponding message ITIDGUI
queues VSI001LIB

Device description VSINSVRT

IFS directories /VISIONSOLUTIONS


(and contents) /VisionISOImages

6. Library QTEMP cannot be in the system portion of the library list. Use this command to access
options to display and change the list:
WRKSYSVAL SYSVAL(QSYSLIBL)
Note: MIMIX requires other system value settings for operation, and will change some system
values to required values. This may include system values that affect system security and
can occur when MIMIX is started following software installation. For more information, see
the More Info document for the MIMIX Installation Wizard or the MIMIX Administrator
Reference book.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 7
7. Review Technical Alerts which can be found at Support Central in the Notifications section of the
Customer Care page. From Support Central, choose Customer Care > My Product >
Notifications.
8. If required, perform the following actions, before installing, that are necessary for your environment.
The actions are listed below by service pack. It is necessary to perform any special instructions
provided for 8.1.13.00, as well as the following actions for service packs that are not yet installed.
(You can skip actions for service packs already installed on your systems.)

8.1.04.00
An IBM PTF may need to be installed on your systems . . . . . . . . . . . . . . . . . . . . . .45
8.1.06.00
Install IBM PTFs if running IBM i OS 7.3 on any of your systems, . . . . . . . . . . . . . .39
8.1.11.00
Ensure product portal applications are compatible with VSP when installing . . . . . . .3

IMPORTANT: When preparing to upgrade to version 8.1, do not make changes to your configuration
between when you shut down MIMIX and when you start the upgrade process. Any changes made
between shut down and starting the upgrade will be lost.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 8
Installation Instructions
Installing the service pack on IBM Power Systems
MIMIX Installation Wizard strongly recommended
The wizard provides a simple method for downloading, distributing, and installing version 8.1 products
on a single IBM Power™ System or on multiple Power Systems simultaneously. The wizard supports a
standard option which streamlines the installation process, and a custom option which provides more
control for more complex environments. The wizard also uses Vision AutoValidate™ to automatically
obtain and apply license keys and installs (or upgrades, when needed) the Vision Solutions Portal (VSP)
server and the MIMIX portal application. If you select to not shut down VSP when upgrading, updates to
the server are not installed and the latest version of the MIMIX portal application is not made available
for use.
The MIMIX Installation Wizard does not support installing into a library located on an independent ASP.
To see requirements for using the wizard, click the More Info link from the wizard’s Welcome panel or
access them in a PDF from Support Central.

If you cannot use the MIMIX Installation Wizard in your environment, do the following:
1. Download the streamfile for the service pack.
2. Use instructions in the Using License Manager book to end the existing MIMIX environment
and to install or upgrade command-based processes from the native user interface.
The native user interface processes do not install or upgrade VSP; however, the “After
Installing” section of this document describes how to update the VSP server.
3. Return to the “After Installing” section of this document for any post-install actions for this
service pack.

For standard upgrades, after the upgrade completes the wizard automatically starts the MIMIXSBS
subsystem and port jobs on the upgraded nodes. Data protection reports are also started if they were not
previously run on an upgraded node. By default, MIMIX is automatically started, but you can specify No
to start MIMIX yourself.
For custom upgrades, default values result in the same behavior after the wizard completes as
described above for standard upgrades. However, if you specify No for the Start MIMIX replication
choice in a custom upgrade, you also have the option to automatically start the MIMIXSBS subsystem
and port jobs on the upgraded nodes. If you specify No to prevent automatically starting these
processes, you must manually start the MIMIXSBS subsystem and port jobs on the upgraded nodes
before manually starting MIMIX.
For new installs, the number of nodes on which you are installing significantly affects wizard activity.
• For a new two-node instance of MIMIX, the wizard partially configures MIMIX, and simplifies startup
so you can complete your configuration using VSP on an IBM i platform. The wizard prompts you for
information it uses to create basic product configuration. The wizard also starts the MIMIXSBS
subsystem, port jobs, data protection reports, and the VSP server on both nodes. By default, MIMIX
is automatically started, but you can specify No to start MIMIX yourself.
• For any other number of nodes, only the software is installed. Configuration and start up activities
must be performed manually when the software installation completes.
Requirements for new two-node installs: You must provide information about both nodes and identify
which node is the primary node. The wizard uses this to create system definitions which define the
nodes (Node 1 and Node 2) to MIMIX and creates a transfer definition for communication between the

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 9
nodes. The node identified as the primary node will have its system definition assigned the role of a
network (*NET) node. The other node will have its system definition assigned the role of a management
(*MGT) node. These assignments occur even in environments licensed for multiple management nodes.
The transfer definition is created with the name PRIMARY. You must provide the following:
• MIMIX node (SYSDFN) - The names specified will be used for the system definitions. If values are
displayed, they are from the nodes you logged in to on previous panels in the wizard.
• IP address or host name - The values displayed are from the nodes you logged in to in previous
panels in the wizard. Values can be either a mixed-case host alias name up to 256 characters in
length or a TCP address (nnn.nnn.nnn.nnn).
• Port - Identifies the port number that MIMIX will use to communicate with the node. The default value
is port 50410.
• Primary node - Select which node will be the primary node in the installation. The Primary node
identifies the source for replication activity. The node selected should be where your business runs.
The default is the node identified as Node 1.
To use the wizard do the following:
1. If you haven’t already, download the MIMIX Installation Wizard for this service pack from Support
Central. There is an executable (.exe) file for each product download, which contains the MIMIX
Installation Wizard as well as the actual product update.
2. Run the wizard.
Note: The wizard will instruct you when to end MIMIX. When directed to end MIMIX, perform Step 3
through Step 9.
If you have multiple installations of MIMIX, the first installation updated will update License
Manager. Because of this, you should end MIMIX on all installations before installing.
3. Use the following command on a management system to end replication processes, audits, and
supporting processes for the MIMIX installation:
installation-library/ENDMMX ENDOPT(*CNTRLD)
Note: Based on 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 continuing. For
optimal availability, do not end the remote journal links as part of ending MIMIX.
4. Repeat Step 3 for each additional MIMIX installation.
5. If you are not using MIMIX to schedule audits, ensure that your scheduling mechanism does not start
audits during the installation process.
6. If running iOptimize on any system in your MIMIX installation, specify the iOptimize installation library
name to end iOptimize using the following command:
installation-library/ENDID *ALL
7. If you are using Vision Solutions Portal (VSP), end the VSP server on the system where it runs. This
prevents object locking issues that can interfere with the install process when subscriptions are used
or when VSP users are logged in.
• If the VSP server runs on an IBM i platform, use the following command:
VSI001LIB/ENDVSISVR
• If the VSP server runs on a Windows platform, from the Windows Start menu, select
All Programs > Vision Solutions Portal > Stop Server and click Stop Server.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 10
8. End the port jobs on all systems. Use the End Lakeview TCP Server command on each system:
installation_library/ENDSVR HOST(host_name) PORT(port_number)
where host_name is the host name or address and port_number is the port number or alias
defined in the transfer definition for the system on which you are running this command.
9. Ensure that all MIMIX jobs are ended before performing this step. Use the following command
on all systems to end the MIMIX subsystem:
ENDSBS SBS(MIMIXSBS) OPTION(*IMMED)

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 11
Installation Instructions
After installing the service pack instructions
The steps you need to perform after installing vary depending on whether there are special instructions
for this service pack that apply to your environment, whether you used commands or the MIMIX
Installation Wizard to install, and choices you made within the wizard.

Post-install actions for this service pack, all install methods


This section applies regardless of how you installed this service pack and provides links to topics in this
document that describe changes within the service pack that may require modifications to your MIMIX
environment after you install. Even new installations should check this list for potential required actions.
.

After installing, perform any of the following actions that are necessary for your environment. The
instructions are listed by service pack. It is necessary to perform any special instructions provided for
8.1.13.00, as well as the following actions for service packs that were not installed when you started this
process. (You can skip special instructions for service packs previously installed on your system.)
8.1.01.00
If using RUNBACKUP procedure, customize BACKUPAPP step before use . . . . . .61
8.1.11.00
Set up and configure SNMP support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

After a new two-node install


Note: For any new install on more than two nodes (or on 1 node only), use the instructions in “After a
wizard new install (3+ nodes) or a command-based install or upgrade” on page 13.
The wizard started the VSP server, the MIMIX subsystem, port jobs, and data protection reports on all
nodes. If you used the default value, the wizard also started MIMIX (STRMMX command). To access
VSP to continue configuring MIMIX, do the following:
1. Check the special instructions above for details of any actions required after installing new
environments.
2. If the installation wizard is still open, click the Launch VSP button on the Summary panel to open a
browser window.
If the wizard is not open, use the following URL in the address bar of your web browser, specifying
the IP address or host name where the VSP server is installed and the configured port. The default
port is 8410.
http://server:port
3. Log in using your IBM i user ID and password.
4. If you are the first person to log in, portal connections and an instance that connects to your new
installation are created. Otherwise, follow the instructions in the Enterprise Status portlet in the Home
folder, to configure portal connections and an instance.
5. If necessary, start MIMIX using the Start MIMIX action from the Nodes portlet on the Summary page.
6. Select the instance. Instructions in the Application Groups portlet on the Summary page direct you
how to start completing your configuration using the Data Protection Reports portlet on the Analysis
page. For more information, see online help for the Data Protection Reports portlet.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 12
Installation Instructions
After upgrading an existing installation
If you used the wizard’s standard upgrade option or its default values in the custom upgrade option, the
wizard started the VSP server, the MIMIXSBS subsystem and port jobs on all upgraded nodes, and
MIMIX replication processes (STRMMX command) for the installation. The wizard also started data
protection reports if they had not previously been run on a node. Do the following:
1. As needed, do the following:
a. Make any known configuration changes on any installation that was upgraded. Check the post
install instructions above for details.
b. Update your Runbook. For more information about the Runbook, contact your certified MIMIX
consultant.
2. If the installation wizard is still open, click the Launch VSP button on the Summary panel to open a
browser window to access Vision Solutions Portal.
If the wizard is not open, use the following URL in the address bar of your web browser, specifying
the IP address or host name where the VSP server is installed and the configured port. The default
port is 8410.
http://server:port
3. Log in to VSP using your IBM i user ID and password.
4. Check MIMIX status. All supporting processes on all nodes and all replication processes should be
active. Do one of the following:
• From VSP, check status on the Summary page of an instance that connects to the product library
you upgraded.
• From the native user interface, check status on either the Work with Application Groups display,
or the Work with Data Groups display. For more status instructions, see the MIMIX Operations
book.
5. If necessary, start MIMIX using the Start MIMIX action from the Nodes portlet on the Summary page.
6. If you use Vision Solutions Portal (VSP) on a Windows® server, you need to manually update that
environment using an additional wizard and the instructions in “Optional VSP and MIMIX Portal
Application on Windows” on page 16.

After a wizard new install (3+ nodes) or a command-based install or upgrade


Use these instructions if you used the MIMIX Installation Wizard for a new install on 3 or more nodes, on
only 1 node, or if you used commands within the native user interface on IBM i to install or upgrade.
The following steps must be performed after successfully installing on all systems:
1. Use the following command to start the MIMIX subsystem on all systems:
STRSBS SBSD(MIMIXQGPL/MIMIXSBS)
2. If performing a new installation, configure MIMIX from the management system using the “Checklist:
New remote journal (preferred) configuration” in the MIMIX Administrator Reference book.
3. Ensure that your communications servers are started on all systems. Use the command
WRKACTJOB SBS(MIMXSBS) to confirm that jobs have been started by any autostart jobs. If
necessary, start the servers. For example, use the following command for TCP:
installation-library/STRSVR HOST(host_name) PORT(port_number)
where host_name is the host name or address and port_number is the port number or alias
defined in the transfer definition for the system on which you are running this command.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 13
4. On each installation, use the following command on the management system to start all system
managers, journal managers, collector services, application groups, data groups, monitors including
the master monitor, the MXSCHED job, and the MXCOMMD job:
installation-library/STRMMX
5. Repeat Step 3 and Step 4 for each additional MIMIX installation.
6. As needed, do the following:
a. Make any known configuration changes on any installation that was upgraded. Check the special
instructions above for details.
b. Update your Runbook. For more information about the Runbook, contact your certified MIMIX
consultant.
7. Check MIMIX status using the information provided in the MIMIX Operations book. To check status
from VSP, you may need to complete the remaining steps to ensure VSP is up to date first.
8. Use Step 8 through Step 13 to ensure your VSP environment on IBM i is current and active.
• If you used the wizard, default options ensured that VSP was installed at a level compatible with
the latest portal application for the product and started VSP on all nodes. Skip to Step 12 to
access a browser and log in.
• If you used native user interface commands for a new installation or the first upgrade to a version
8.1 service pack, continue with Step 9.
• If you used native user interface commands for an upgrade when VSP version 3.1 was already
installed, skip to Step 10 to make the latest portal application available to the VSP sever.
• If you use VSP on a Windows® server, you need to manually update that environment using an
additional wizard and the instructions in “Optional VSP and MIMIX Portal Application on
Windows” on page 16.
9. Command line install processes (found in the Using License Manager book) do not install or upgrade
the VSP server, and do not make the server aware of the latest portal application. Use either of these
methods to install VSP on systems running IBM i:
• Recommended method - Use the MIMIX Installation Wizard and select the option “MIMIX portal
application only”. This will also install the VSP server as needed to support the portal application.
• Alternate method - If you cannot use the wizard, use the VSP stream file installation method
documented in the Using License Manager book.
10. Make the portal application known to the server using the command:
VSI001LIB/ADDVSIAPP APP(MIMIX)
If the command fails with message VSE100A, you must upgrade the VSP server to a compatible
level before you can use the latest portal application available. Choices for installing are identified
in Step 9.
11. Start the server using the command:
VSI001LIB/STRVSISVR
Note: The default port is 8410. Each instance of the server uses three consecutive ports. If you
cannot use this port, change the port using instructions in the Vision Solutions Portal (VSP)
User’s Guide book.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 14
12. If the installation wizard is still open, click the Launch VSP button on the Summary panel to open a
browser window.
If not, use the following URL, specifying the IP address or host name where the VSP server is
installed and the configured port. The default port is 8410.
http://server:port
13. Log in using your IBM i user ID and password.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 15
Installation Instructions
Optional VSP and MIMIX Portal Application on Windows
This section provides optional instructions for installing Vision Solutions Portal and the MIMIX portal
application on a supported Windows® server. Support Central provides an executable (.exe) file for the
Vision Solutions Portal (VSP) 3.1 & Portal Application Installation Wizard for Windows® for each MIMIX
service pack.This wizard installs version 3.1 of Vision Solutions Portal and the MIMIX portal application
on a supported Windows server.
Notes:
• This wizard does not install the MIMIX product on any platform. You must still install the product
updates in this service pack using the service pack installation instructions. For more information,
see “Action required” on page 1.
• The first time you install version 3.1 of Vision Solutions Portal on a Windows server, you must
upgrade any other portal applications on the VSP server to a compatible level. For more information,
see “VSP 3.1 compatibility with product portal applications” on page 3.

Before installing on Windows


Before running the Vision Solutions Portal (VSP) 3.1 & Portal Application Installation Wizard for
Windows, do the following:
1. VSP 3.1 can only be installed on Windows servers that support 64-bit applications. Customers
whose servers do not meet this requirement must continue to use VSP 3.0.
2. Ensure that your client workstation meets the minimum requirements for using this wizard. The user
who runs this wizard must have administrator privileges for the system on which it is run. Either
Windows® 7, Windows® 8, Windows® 8.1, Windows® 10, Windows® 2008 R2, or Windows Server®
2012 R2 is required. For a complete list of wizard requirements, see the More Info link in the wizard’s
Welcome panel or on the download page in Support Central.
3. To improve performance of the wizard, close other applications before starting the wizard.

Installing on Windows
Default options in this wizard for Windows will shut down the VSP server if necessary. This affects
access to all instances running on the server, including those connecting to other products. Do the
following:
1. If you haven’t already, download the Vision Solutions Portal (VSP) 3.1 & Portal Application
Installation Wizard for this service pack.
2. Run the wizard.
Installed Location: Version 3.1 of Vision Solutions Portal can only be installed on a 64-bit Windows®
operating system. VSP server software and product portal applications are stored on the system in
\Program Files\VisionSolutions\. When the server is upgraded to VSP 3.1, if VSP 3.0 is
installed in \Program Files (x86)\VisionSolutions\, the installation wizard will delete VSP
from the (x86) path up to and including the \VisionSolutions folder.

After installing on Windows


If you used defaults, the wizard started the VSP server. If necessary, start the server. From Windows,
click the Start menu and point to All Programs. Locate and point to Vision Solutions Portal, then Click
Start.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 16
Log in to VSP using your Windows user ID and password.
For more information about using VSP on a Windows server, see the Vision Solutions Portal (VSP)
User’s Guide.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 17
Highlights Version 8.1 Service Pack 8.1.13.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Enhancement to the Virtual Switch (SWTVRT) procedure


For MIMIX 8.1.13.00 instances and higher, all Virtual Switch procedures of the type *SWTVRT
will have two separate steps for the actions of waiting for virtual switch recovery to complete and
enabling constraints for a data group. This will provide a higher level of visibility to the completion
of processing for each action.
Detail for the changes in MIMIX 8.1.13.00 and later are:
• A new step MXCKRCYCMP checks for virtual switch recovery to be completed. The step is
automatically added to existing procedures and is also included in newly created procedures
of a *SWTVRT type.
• The existing step MXENBCSTV is changed to now only enable all foreign key constraints if
the data group is not configured to manage constraints. The step is automatically updated in
existing procedures and is included with this change in newly created procedures of a
*SWTVRT type.
MIMIX instances earlier than 8.1.13.00 will continue to have only the MXENBCSTV step that has
both actions of waiting for virtual switch recovery to complete and enabling constraints for a data
group.
(MXHA-24166)

Fixes included in service pack 8.1.13.00


This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.17.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-15962 When changing the Scheduled day parameter for the SETMMXSCD command to
*ALL, the value in the Scheduled time parameter will now be retained.
MXHA-23932 Data group tracking entries will no longer be removed when a clear pending start
is requested for the data group.
MXHA-24122 A message will now be displayed in the job log of the step program running on a
local system indicating that a remote step program has been called along with the
fully qualified remote job name.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 18
MXHA-24138 F-CB journal entries for database statistics are no longer replayed for files using
*KEYED replication. This prevents an endless loop in bi-directional replication
environments.
MXHA-24153 Step programs working with physical file constraints will no longer attempt any
processing for data groups that are not defined for database replication.
MXHA-24158 Journal receivers are now deleted correctly on the target system when it is the
target for multiple data groups that all have the same journal receiver prefix.
MXHA-24198 An apply session will no longer end abnormally with MCH3203 while processing
an update for files using keyed replication.
MXHA-24202 Data group file entries for files that have been moved or renamed are now
updated correctly for disabled data groups that are associated with active data
groups in the same data resource group.
MXHA-24215 The message queues for the MXSYSMGR and MXCFGJRN MIMIX internal
journals will now be set to wrap when they are full.
MXHA-24265 The Directories (#IFSATR) priority audit will no longer fail with error LVE0101
(error number 3524).
MXHA-24305 MIMIX now correctly creates work libraries in the correct ASP when a command
default is changed for the CRTLIB command.
License Manager
MXHA-23832 License Summary now displays the correct information for iOptimize instances.
MXHA-24217 Triggers are now properly handled for LM3400P during License Manager upgrade
processing.

Vision Solutions Portal


Vision Solutions Portal version 3.1.03.00 is included with MIMIX service pack 8.1.13.00.

Support for copying VSP configuration between servers


Customers who require a duplicate copy of their primary VSP server for redundancy or balancing
work load can now use commands to export the VSP configuration to a file on one server and
import it to VSP on another server that is running the same service pack level of VSP. The VSP
servers can be on different hardware platforms (IBM i or Windows).
• The Export VSP Server Config. (EXPVSICFG) command will export configuration for VSP
and deployed portal applications to a .zip file on the local system. The file name reflects the
service pack level of VSP on the system and the date that the file was created. You must
manually transfer the file to the system where you want to import it.
• The Import VSP Server Config. (IMPVSICFG) command will import a configuration file to the
VSP server on the local system if the VSP service pack level on the local system is the same
as that where the configuration file was created. The VSP server on the local system must be
ended before running this command. The IMPVSICFG command replaces any existing
configuration on the local VSP server and does not retain any local customization. Any
imported configuration for a portal application that is not deployed to the local VSP server is
not available for use until after the portal application is deployed to the local VSP server.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 19
The EXPVSICFG and IMPVSICFG commands exist for IBM i and Windows on systems running
VSP 3.1.03.00 or higher. For more information about what configuration information is exported
and how to use these commands, see topic “Requirements for a highly available VSP
environment” in the Vision Solutions Portal (VSP) User’s Guide.
(STR-3531)

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.1.03.00 includes all relevant changes to earlier VSP 3.1 service packs,
all relevant fixes in 3.0.22.00 or earlier levels of version 3.0, and the following:

STR-5293 The Windows versions of the expvsiinf and resetpwd tools now run correctly when
VSP is installed on a Windows server.

8.1.13.00 © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 20
Highlights Version 8.1 Service Pack 8.1.12.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Enhanced support for excluding IFS objects using wildcard


characters
In directory selection rules (data group IFS entries) that exclude objects from replication, MIMIX
now supports the ability to specify asterisks (*) embedded within the identified object name and
interpret the asterisks as wildcard characters. Exclude rules that specify asterisks in positions
other than the last character of the object name will now act as filters to exclude objects that
would otherwise be selected by include rules which specify only a trailing asterisk. This is a
change in behavior for how rules are processed.
Prior to upgrading to 8.1.12.00 or higher, asterisks used anywhere except as the last (trailing)
character of an object name within directory selection rules (IFS entries) were interpreted as
literal characters, not wildcards. If any such directory rules exist prior to upgrading, asterisks
embedded within names will be considered advanced generic names. After upgrading to
8.1.12.00 and starting MIMIX, any directory rules (IFS entries) with advanced generic names are
identified, and processing behavior changes as follows:
• MIMIX sends a notification from the source system of each data group in which embedded
asterisks were found within directory selection rules (IFS entries). The notifications are
identified as originating from Install in the Notifications portlet and the Work with Notifications
(WRKNFY) display. From the portlet in VSP, you can use the Selection Rules action for the
notification to view the directory rules for that data group.
• From VSP, the Directories tab of the Selection Rules window displays an informational
icon next to the Replication column for rules with advanced generic names. From the native
user interface, the Work with DG IFS Entries display (WRKDGIFSE) displays either
*INCLD(A) or *EXCLD(*A) for any occurrences of names with embedded asterisks found
during the upgrade.
• Processing of directory selection rules occurs as follows:
– Embedded asterisks within generic names in exclude rules (IFS entries) for directories are
considered wildcard characters. When a directory is being evaluated for processing, an
exclude rule with an advanced generic name is processed only after finding the most
specific match to an Include rule with a basic generic name. Then, a match to an
advanced generic name will exclude the object.
– Embedded asterisks within generic names in exclude rules (IFS entries) for directories or
directory content that existed prior to upgrading are now considered wildcard characters.
After upgrading, embedded asterisks can only be specified in exclude rules. When

8.1.12.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 21
creating or changing exclude rules from VSP, an informational icon is displayed in the
Exclude Selection Rules dialog or Selection Rules Details dialog. After upgrading to
8.1.12.00 or higher, when a directory or an object in a directory is being evaluated for
processing, an exclude rule with an advanced generic name is evaluated only after finding
the most specific match to an Include rule with a basic generic name. Then, a match to an
advanced generic name will exclude the directory or object.
For examples of implementing generic names in exclude selection rules, changes to the
processing order of precedence, and other details, see the Using MIMIX from Vision Solutions
Portal book or the MIMIX Administrator Reference book.
(MXHA-22397)

Fixes included in service pack 8.1.12.00


This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.17.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-18273 Multiple uses of SYNCDGFE on two or more members of the same file no longer
results in lock conflicts, job failures or files left in a ‘damaged’ condition (LVE3308
and CPF326B).
MXHA-23782 Updates to the journal status of object tracking entries for disabled data groups is
now done more consistently. This will prevent unnecessary notifications.
MXHA-23829 Performance of the IFS auditing has been enhanced to use fewer system
resources.
MXHA-23843 Users are no longer allowed to change the host name or IP address in a transfer
definition while system manager jobs are active.
MXHA-23857 SYNCDGACTE no longer fails with MCH1202 when syncing a *LIB object.
MXHA-23862 Recovery counts are now reported correctly on WRKDG outfiles for *OBJ only
data groups.
MXHA-23929 The data provider is now correctly set when both nodes’ roles are listed as
*BACKUP.
MXHA-23973 Starting an application group will no longer switch data groups that do not have a
source system that matches the primary node for the application group.
MXHA-24005 Journal status for data group object tracking entries is now updated on the remote
system more consistently.
MXHA-24010 MIMIX will now correct a failed APM status even if APM has been disabled.
MXHA-24018 IFS objects that are moved from a non-replicated directory to a replicated
directory will no longer remain in *RLSWAIT in environments that replicate data
among three or more systems.
MXHA-24033 Recovery time for IFS exceptions such as those generated during a virtual switch
has been improved.
MXHA-24048 The MIMIX system manager processing in multi-management environments has
been changed to eliminate the CPF5034 duplicate key error messages for
MXMBRTRKL1.

8.1.12.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 22
MXHA-24059 Recoveries initiated from exceptions generated for files with long record lengths
will no longer result in the file going to *HLDERR, and files with LOB fields will now
be successfully repaired.
MIMIX Portal Application
MXHA-23647 Instance Policies and Policy Summary actions are now available in the global
menu on the Application Groups portlet.
MXHA-23792 The Last Started column is now used as the secondary sort order when sorting on
columns in the Procedures portlet in VSP, allowing you to see your most recent
procedure runs at the top of the portlet.

Vision Solutions Portal


Vision Solutions Portal version 3.1.02.00 is included with MIMIX service pack 8.1.12.00.

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.1.02.00 includes all relevant changes to earlier VSP level 3.0 service
packs.

8.1.12.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 23
Highlights Version 8.1 Service Pack 8.1.11.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Support for integration with SNMP management


applications
The MIMIX portal application at 8.1.11.00 or higher supports SNMP as a subscription event
action. For more information, see “Subscriptions support sending traps to SNMP management
applications” on page 26.

New value to decrease retention time before cleanup of


completed DG activity entries
The create or change system definition (CRTSYSDFN or CHGSYSDFN) commands have a new
value of zero (0) days that can be configured for the parameter Keep data group history (days)
(KEEPDGHST). The new value of zero (0) days allows you to decrease the retention time before
the cleanup of completed data group activity entries (DGACTE) is performed. Additionally, the
frequency that the cleanup job runs has been increased to occur more often than daily only.
An example of when the value of zero (0) days can be useful is for environments that process a
large number of QAUDJRN journal entries by processed by system journal (object) replication
and have experienced OBJSND fails with a Message LVE0102.
(MXHA-23824)

Fixes included in service pack 8.1.11.00


This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.17.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-22543 Improved journal verification for environments with rapid create and delete activity
of files in order to reduce the possibility of orphan data group file entries on the
target node.
MXHA-23636 For IFS object-based replication, the recovery of IFS attribute changes identified
by the Directories (#IFSATR) audit will no longer attempt a Start Journaling IFS
Entries (STRJRNIFSE).

8.1.11.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 24
MXHA-23696 File attribute (#FILATR) audit will no longer show an incorrect value for the object
attribute when the attributes were not retrieved due to a lock on the object.
MXHA-23789 Improved performance in system manager when processing high volumes of
changes to configuration files (particularly DG file entries changes when the File
Data (#FILDTA) audit runs).
MXHA-23845 Virtual switch with an associated MQ data group no longer fails in step program
MXCKDGEAPY (Checks if applies and APM are ended, max 1 hour).
MXHA-23847 The Object Attribute (#OBJATR) audit will complete with differences when
comparing subsystem descriptions where the subsystem description is not found
on one of the systems.
MXHA-23848 Replication status for data groups associated with a switchable IASP in a non-
cluster enabled application group now report status correctly.
MXHA-23854 Improved performance of the SYNC jobs initiated by database apply for IFS
objects moved from non-replicated directories to replicated directories.
MXHA-23916 Journaled data areas and files are now successfully recovered when restored on
the target system.
MXHA-23950 Performance is improved for the IFS attributes priority audit for object-replicated
IFS objects when a large number of directories are involved.
MIMIX Portal Application
MXHA-23822 The Object Correction Activity window no longer shows entries for deleted IFS
objects that were previously displayed due to journaling issues.
MXHA-23922 Data group compliance, when running an audit that was previously out of
compliance, will now be properly summarized in the audit compliance column
(Audits Cply) as Out of Compliance (indicated by a red x) in the Data Groups
portlet on the Data Groups tab.

Vision Solutions Portal


Vision Solutions Portal version 3.1.01.00 is included with MIMIX service pack 8.1.11.00.

VSP 3.1 requires 64-bit Java


To better support using VSP when managing large numbers of instances or active users, VSP
version 3.1 is shipped with this service pack and is delivered as a 64-bit capable software
distribution. On 64-bit Windows servers, VSP 3.1 can take advantage of more resources
available to the Java runtime environment (JRE) in 64-bit environments.

VSP on an IBM i server


Default choices in the MIMIX Installation Wizard will automatically install VSP 3.1 on the servers
where the MIMIX product is installed. To operate VSP on System i servers, those systems
require a compatible version (5770-JV1 or 5761-JV1) of IBM Developer Kit for Java (*BASE) and
either Option 14 (Java SE 7 32 Bit) or Option 15 (Java SE 7 64 Bit). Option 15 is strongly
recommended.

8.1.11.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 25
The Start Vision Solutions Server (STRVSISVR) and End Vision Solutions Server (ENDVSISVR)
commands are changed to default to 64-bit Java. If you are running with only the 32-bit Java
option installed, you will need to specify JVM(*IBM32) on these commands to start or end the
VSP server in a 32-bit Java environment.
If you have MIMIX and iOptimize portal applications deployed on the same VSP server on a
System i server, you must upgrade both portal applications on the VSP 3.1 sever to service pack
levels that are compatible with VSP 3.1. For more information, see “VSP 3.1 compatibility with
product portal applications” on page 3.

VSP on a Windows server


VSP 3.1 can only be installed on Windows servers that support 64-bit applications. The Vision
Solutions® Portal (VSP) 3.1 & Portal Application Installation Wizard for Windows® includes and
installs the 64-bit Java 7 (7u60) runtime environment needed for VSP operation on supported
Windows servers.
Customers who need 32-bit distributions of VSP due to existing hardware or software constraints
must continue to use VSP 3.0. Also, customers with the Double-Take for AIX portal application
and either the MIMIX or iOptimize portal application deployed on an existing VSP 3.0 server must
maintain a separate VSP server at 3.0 because the AIX portal application is not compatible with
VSP 3.1. For compatibility details, see “VSP 3.1 compatibility with product portal applications” on
page 3.
(STR-5127)

Subscriptions support sending traps to SNMP


management applications
Through its Subscription interfaces, VSP 3.1 supports integrating notifications about events that
occur in VSP-managed instances into your existing Simple Network Management Protocol
(SNMP) management software. VSP includes software that allows it to act as an SNMP agent
that sends notifications (traps) to the SNMP manager on behalf of product instances for which
appropriate SNMP support is available. VSP and portal applications that support SNMP
notifications provide MIB files on the VSP server when VSP is installed or upgraded. VSP does
not support querying or controlling VSP or product instances from SNMP management
applications.
The MIMIX portal application at 8.1.11.00 or higher supports SNMP as a subscription event
action.
Action required. If you want to use SNMP support, some initial setup is required. The MIB files
for VSP and the MIMIX portal application must be made available to your SNMP management
application in its expected location. Also, the VSP administrator must configure SNMP policies
with the appropriate SNMP version, the host name or IP address of the SNMP management
application and its port for receiving notifications (traps), as well as authentication details. After
the initial setup is complete, you can create or change subscriptions to specify SNMP, email, or
both as event actions. For detailed instructions, see these topics in the Vision Solutions Portal
(VSP) User’s Guide:
• Setting up SNMP support
• Configuring subscriptions for automatic monitoring

8.1.11.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 26
The list of “Events available for MIMIX” within online help for the Subscription Events portlet
identifies the OID for the SNMP trap associated with each event.
(STR-3070)

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.1.01.00 includes all relevant changes to earlier VSP level 3.0 service
packs.

8.1.11.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 27
Highlights Version 8.1 Service Pack 8.1.10.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Fixes included in service pack 8.1.10.00


This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.16.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-23043 The Directories (#IFSATR) audit and Compare IFS Attributes (CMPIFSA)
command will now audit UDFS directories for data group IFS entries containing
trailing generics at the root level (e.g., /udfsdir*).
MXHA-23422 During a virtual switch, the Access Path Maintenance (APM) status will now
indicate Virtual switch test (*VRTSWTTST) instead of Stopped (*INACTIVE). This
will result in correct rolled-up status of Virtual switch test (*VRTSWTTST) on the
Application Groups and Data Groups portlet when no other more severe errors
are present.
MXHA-23449 The MIMIX replication manager job now correctly handles exceptions caused by
logical files being restored on the target system of a data group.
MXHA-23648 When gathering node role information, step programs now perform retries when
encountering timing issues with system manager jobs.
MXHA-23701 MIMIX system manager will now distribute notifications that are not associated
with a data group from management systems to network systems.
MXHA-23776 Journal analysis will no longer fail with LVE3955 error code MS when there are
more than 9,999 DGFEs.
MXHA-23783 Start data group requests no longer hang after a system definition has been
updated.
MXHA-23799 File Member Attributes (#FILATRMBR) audit will no longer attempt to recover
members that are missing on the target for files that have a DGOBJE configured
with OMTDATA(*FILE).
MXHA-23830 Object Apply (OBJAPY) now correctly replicates subsystem description attributes
that contain blanks.
MXHA-23836 Object Apply (OBJAPY) now correctly handles disabling triggers for a file handled
via object replication.

8.1.10.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 28
MIMIX Portal Application
MXHA-23323 MIMIX now supports the ability for a user other than the subscription owner to
reconnect an instance. See “Improvements for reconnecting an instance within a
subscription” for details.
MXHA-23505 Activity entries for objects in third-delay/retry processing now appear as active
recoveries within VSP and can be seen in the Object Correction Activity window
as well as in the Recoveries tab of the Audits, Recoveries and Notifications portlet
for a selected data group.
MXHA-23657 The MIMIX portal application has improved the error handling when a
communication problem exists with the primary portal connection being used to
monitor VSP subscriptions for an instance.
MXHA-23665 The Data Group Started event will now be triggered again when upgrading VSP
from 8.1.09.

Vision Solutions Portal


Vision Solutions Portal version 3.0.22.00 is included with MIMIX service pack 8.1.10.00.

Improvements for reconnecting an instance within a


subscription
Within VSP, any user who is a subscriber to a MIMIX instance and is not the subscription owner
can now attempt to reconnect the monitored instance when the “Instance cannot be monitored”
event occurs. VSP now provides a Reconnect action in the Subscriptions portlet for a
subscription that detected the “cannot monitor instance” event. The email notification for the
event includes recovery text identifying how to access the Reconnect action. This capability is
available for MIMIX subscriptions when the 8.1.10.00 MIMIX portal application is deployed on the
VSP server.
Previously, only the group owner or instance owner could re-establish the connection. If not re-
established within five minutes, the subscription effectively became disabled. This could occur
after the product was ended for scheduled maintenance or because of a problem.
(MXHA-23323, STR-5026)

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.0.22.00 includes all relevant changes to earlier VSP level 3.0 service
packs.

8.1.10.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 29
Highlights Version 8.1 Service Pack 8.1.09.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Fixes included in service pack 8.1.09.00


This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.16.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-23036 Object replication of a user profile no longer fails with CPF4AA7 or CPF4AC2
when the same restrictive password rules are in effect on both the source and
target systems.
MXHA-23511 IFS replication performance is now improved when name mapping is not used.
MXHA-23529 Frequently updated records that become unsynchronized are now correctly
replicated, audited (#FILDTA), and compared (CMPFILDTA) in data groups with
journals configured to minimize entry specific data (MINENTDTA) for files.
MXHA-23535 Database apply job no longer fails with CPF0001 when attempting to synchronize
IFS objects with names longer than approximately 200 characters.
MXHA-23545 Target journal inspection no longer reports an exception when a Delete on Target
operation is performed for a *DEVD which is not within the replicated namespace
based on attributes.
MXHA-23588 #FILDTA audit and CMPFILDTA will now correctly report a file as *NE (not equal)
when file has exceeded the deleted record threshold and one file has more trailing
records than the other file.
MIMIX Portal Application
MXHA-23467 Subscription emails for partially stopped data group are no longer issued when
processes are still in the process of ending.

8.1.09.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 30
Vision Solutions Portal
Vision Solutions Portal version 3.0.21.00 is included with MIMIX service pack 8.1.09.00.

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.0.21.00 includes all relevant changes to earlier VSP level 3.0 service
packs and the following:
STR-5118 Trailing spaces are now removed when creating portal connections in VSP. This
allows the portal connections to be used in an instance.

8.1.09.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 31
Highlights Version 8.1 Service Pack 8.1.08.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Subsystem description (*SBSD) replication enhancement


Object replication processes will now attempt to apply transactions for replicated subsystem
descriptions (*SBSD) regardless of the status of the subsystem on the target node. If the
subsystem on the target node is active when the apply occurs, the change to the subsystem
description does not take effect until the subsystem on the target node is ended and restarted.
Previously, replication activity for *SBSD objects always failed if the subsystem on the target
node was active.
(MXHA-22313)

Fixes included in service pack 8.1.08.00


This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.15.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-22920 SYNCDGFE METHOD(*ATR) will no longer fail with CPD3213 when
synchronizing attributes for a partitioned table (or any SQL type file).
MXHA-23029 The database reader (DBRDR) job will no longer end with MCH5804 and
LVE0103 updating the name tracking file in environments with high database level
activity.
MXHA-23079 Object replication now checks journaling start time for data areas and data queues
to determine if data base replication is handling the create operation.
MXHA-23080 The database reader job will now store the last starting point if an ENDDG is
requested before it completes loading of the IFS configuration.
MXHA-23269 Setting USRDFNOBJ(*NONE) for print devices on the source will now replicate
correctly to the target.
MXHA-23273 Remote journals will no longer be ended by the ENDDG command if ending of the
data group was not successful.
MXHA-23294 When comparing attributes of file members (CMPFILA CMPLVL(*MBR)
command) and the File Member Attributes (#FILATRMBR) audit will no longer fail
with MCH0601 if files are deleted while the audit is processing them.

8.1.08.00 (Included with 8.1.10.00) © Copyright 1999, 2016 Vision Solutions, Inc. All rights reserved. 20
MXHA-23319 CPYDGDFN now provides TORSCGRP(*DFT) to better select default value
based on which part of the data group name is changing on the copy.
MXHA-23332 The virtual switch procedure will no longer attempt to disable triggers on logical
files.
MXHA-23394 Data resource group name is now properly resolved when *DFT is specified when
creating or changing a data group definition and the data resource group with the
same name as the data group already exists.
MXHA-23404 Database apply (DBAPY) job will no longer end abnormally with MCH3601 when
processing an incomplete D-CG (Change File) journal entry for a file that is on
hold.

MIMIX Portal Application


MXHA-22228 The Object Correction Activity window in VSP no longer shows files in Compare
repair status.
MXHA-23070 The description for the MXSBMAUD step of the Virtual Switch procedure now
states that it runs on a specific system.

Vision Solutions Portal


Vision Solutions Portal version 3.0.20.00 is included with MIMIX service pack 8.1.08.00.

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.0.20.00 includes all relevant changes to earlier VSP level 3.0 service
packs and the following:
STR-5086 When using Google Chrome, you can now scroll the list of data groups in the
drop-down menu on the Arrivals and Backlog portlet.
STR-5087 Updated encryption algorithms are now used when using HTTPS for accessing
VSP running on an IBM i having the latest Java PTF groups applied.

8.1.08.00 (Included with 8.1.10.00) © Copyright 1999, 2016 Vision Solutions, Inc. All rights reserved. #
Highlights Version 8.1 Service Pack 8.1.07.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Support for omitting content of *DTAARA and *DTAQ


objects from system journal replication
MIMIX now supports omitting the content of *DTAARA and *DTAQ objects configured for system
journal replication. This provides greater flexibility to configure replication of only what is needed
on the target node and is similar to existing support for omitting content for *FILE objects. This
support is not configured by default for new or upgraded installations.
To support configuration, the following possible values have been added to the Content to omit
field in the Include Library and Objects dialog, the Selection Rule Details dialog (for a library-
based object), and to the Omit content (OMTDTA) parameter on the ADDDGOBJE,
CHGDGOBJE, and LODDGOBJE commands.
• Data area changes (*DTAARA) - Operations that change the content (data) or the text
description of a data area are omitted from replication.
Note: When this value is specified, MIMIX skips all T-ZC journal entries for data areas
selected by the rule and will not change the object auditing value of those data areas
to *CHANGE or *ALL during replication, during a start request, or as the result of the
using SETDGAUD command.
• Data queue changes (*DTAQ) - Operations that change the content (data) of a data queue
are omitted from replication. Operations that affect only data queue attributes, such as
changing the text description, are replicated.
The new values are also supported in the Omit content values (OMTDTA) field of the
MXDGOBJE outfile for the WRKDGOBJE command.
Audit results and comparison commands will report the attributes associated with the omitted
content as *EC (equal configuration) even though the attributes are different between systems.
Omitting content and cooperative processing are mutually exclusive techniques. Both techniques
cannot be specified in the same selection rule (data group object entry). To use this capability to
omit content, it is better to configure it in a selection rule that specifies either the specific object
type or a specific or generic object name instead of in a rule that selects all object types and
names. For more information about how to configure to omit content, see the MIMIX
Administrator Reference book or the Using MIMIX from Vision Solutions Portal book.
(MXHA-22345)

8.1.07.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 34
Object auditing level of cooperatively processed *DTAARA
and *DTAQ objects no longer changed
MIMIX no longer changes the object auditing value of *DTAARA and *DTAQ objects identified by
selection rules (data group object entries) that are configured for cooperative processing through
the user journal. This prevents extra journal entries from being logged in the QAUDJRN (system)
journal that are not needed by MIMIX. This behavior is now consistent with how cooperatively
processed *FILE objects are handled. This change may also reduce the amount of CPU used by
all object send processes when determining whether or not to process entries in receivers for the
QAUDJRN journal, and may reduce the amount of storage used by those receivers on the
source system.
For existing environments that previously configured extra selection rules (data group object
entries) with an Object auditing (OBJAUD) value of *NONE for journaled *DTAARA and *DTAQ
objects in order to prevent extra entries in the QAUDJRN journal, those rules are no longer
necessary and can optionally be removed.
(MXHA-22347)

Automatic resolution of deadlocks caused by long-running


open commits
User journal replication processes now automatically detect and attempt to correct conditions
where the database reader (or send process) and database apply processes have deadlocked
due to a long-running commit cycle. When MIMIX detects a deadlock, it attempts to automatically
clear the condition by checking the user journal transactions not yet processed by the database
reader for the commit or rollback operation and releasing the commit cycle on the target node
accordingly so that apply processing can continue. The apply process issues message LVI0905
to indicate that the commit cycle was resolved on the target node.
If MIMIX is configured for delayed (*DLY) commit mode, a subset of objects in a commit cycle
that MIMIX processed to clear a deadlock may be automatically identified for selection in
prioritized auditing.
If MIMIX cannot clear the deadlock condition, the condition is reported as follows:
• Message LVE311D in the message log identifies the job that started the long commit cycle
and indicates that user action is needed for the application to either commit or rollback the
commit cycle.
• In VSP, the Information icon and a message which includes a link to the job log appear at
the top of Apply Details area of the DB Statistics tab on the Data Group Details and Activities
portlet.
• In the native user interface, the value *DLK is displayed in the Open Commit column on view
1 of the Data Group Database Status display (DSPDGSTS command).
• An event is triggered and sends an email notification for users who have a subscription
configured within VSP that includes this event. This is a new event that is automatically
added to existing subscriptions during the installation process. This event is also part of the
default set of events that are added when a new subscription is created.
• The MXDGSTS outfile (WRKDG command) identifies a backlog condition that could not be
automatically resolved. The DBAOPNCMT field now supports values of *YES, *NO, and

8.1.07.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 35
*DLK. Also the following fields have been added to identify the job associated with the long
commit cycle: CMTJOBNAME, CMTJOBUSER, CMTJOBNUM. These fields are blank if a
deadlock condition does not exist.
Once the commit cycle has been resolved, MIMIX will be able to automatically clear the deadlock
condition.
(MXHA-22348)

More accurate status displayed on Data Group Details and


Activities portlet during an outage
When a MIMIX instance loses connectivity between the source and target servers, the Data
Group Details and Activities portlet within VSP will now display the last known information from
the node that is not communicating on the DB Statistics and Object Statistics tabs. A red
message at the top of the portlet indicates which node is not available and indicates that the last
known information is displayed in gray. The last known information can be useful during
unplanned switches that may occur during server outages. The last known information may also
be displayed because the port server for a node is stopped or there is some other
communications problem between the nodes.
Previously, no data was displayed in the portlet in VSP when an instance could not communicate
with the source or target server.
(MXHA-22392)

More access to file selection rules


When viewing selection rules for a library selected from the Data Protection Reports portlet, you
can now use the File Selection Rules action to view the file selection rules configured for the
library. When accessed in this way, the File Selection Rules window does not allow using the
New Include action.
(MXHA-22875)

Fewer delayed activities for locked objects


For *DTAARA and *DTAQ objects identified for cooperative processing, you may see fewer
occurrences of delayed status values for data group activity entries associated with T-CO
(create) transactions for those objects. If journaling attributes are inherited, the activity entry
status is changed to Completed by Ignoring (CI) without entering the delay/retry cycles while
waiting for the lock to be freed.
(MXHA-22346)

Exclude from Replication action cleans up library


exception selection rules
When the Exclude from Replication action is selected for a library listed on the Libraries tab of the
Data Protection Reports portlet or from the Replicated Objects window, the selected library and

8.1.07.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 36
its contents are excluded from replication and all exception rules for objects and files in the library
are removed. Replication processes for the affected resource groups or data groups will use the
resulting changes after they are stopped and restarted. Previously, exception rules, such as rules
that included a specific object or file within the library, were not affected by the exclude action.
Note: This change does not apply to the Exclude from Replication action when used from the
Documents or Folders tab.
(MXHA-19530)

Fixes included in service pack 8.1.07.00


This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.15.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-22989 Virtual switch recovery no longer fails with error codes CPD435F and LVE3DAA
by attempting to disable triggers from user copies of QAQQINI files.
MXHA-23048 Management (*MGT) system definitions now can only be renamed
(RNMSYSDFN) from the system to be renamed and Network (*NET) system
definitions now can only be renamed from a *MGT system that it communicates
with as specified in the MGTSYS setting.
MXHA-23054 Performing the SYNCDGFE or SYNCOBJ command on a file with system triggers
will now correctly map the trigger program library when library name mapping is
being used.
MXHA-23061 MXREPMGR will no longer loop trying to recover record level exceptions for
blocks of records with invalid starting RRNs (relative record numbers) which
previously prevented step MXENBCSTV in a virtual switch procedure from
completing.
MXHA-23074 Replication of an object change via save/restore processing will now correctly
maintain the object's owner and its authorities.
MXHA-23075 DBAPY will no longer end abnormally with MCH3601 after replaying a D-TC
(create trigger) journal entry.
MXHA-23078 Object apply no longer fails with CPD0084 when replicating objects of type
*EXITRG.
MXHA-23100 Constraints containing blanks, single quotes, and/or double quotes are now
correctly disabled and enabled during a virtual switch.
MXHA-23115 The replication manager job (MXREPMGR) will now limit the journal entries read
when performing source data capture for record level exceptions.
MXHA-23241 Libraries audit (#OBJATR) and CMPOBJA will no longer fail with MCH3601.
License Manager
MXHA-23245 License Manager upgrade no longer fails due to QSHELL issues in environments
using CCSID 5026.

8.1.07.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 37
Vision Solutions Portal
Vision Solutions Portal version 3.0.19.00 is included with MIMIX service pack 8.1.07.00.

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.0.19.00 includes all relevant changes to earlier VSP level 3.0 service
packs and the following:
STR-5049 Unused license information is now removed from the VSP license database when
the Retrieve Licenses global action command is used from the License Summary
Window.

8.1.07.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 38
Highlights Version 8.1 Service Pack 8.1.06.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Support for environments running IBM i 7.3


This version of MIMIX supports replication between systems running the IBM i 7.3 operating
system. However, there is an issue between systems running different operating system levels,
described in more detail below. Additionally, there may be new IBM capabilities in IBM i 7.3 that
MIMIX does not yet fully support.
Known restriction: A known issue identified in IBM APARs SE64667 and SE64928 affects
environments that perform replication between systems running different operating system
levels. When one of the systems is running IBM i 7.3 and the other system is running IBM i 7.2 or
IBM i 7.1, events that add triggers (D-TC journal entries) cannot be properly replicated. IBM has
released fixes to address the issue. The CHKIBMPTF tool has been updated with these PTFs.
Action required: Regardless of the known restriction, if any system in your MIMIX environment
is running IBM i 7.3, you must install required IBM PTFs on that system before installing or
upgrading the product on that system. PTFs may also be needed on the systems running earlier
releases of the operating system. See Step 1 in “Before installing the service pack” on page 5 for
instructions on using the CHKIBMPTF tool.
(MXHA-22343)

Fixes included in service pack 8.1.06.00


This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.14.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-17395 Target journal inspection (TJI) will now issue one notification per day per user
when the system definition restart time (RSTARTTIME) is *NONE.
MXHA-19903 OBJRTV and STSSND jobs will no longer get stuck when activity entries are
removed prematurely.
MXHA-21554 CPYDGDFN command added parameter TORSCGRP to allow specifying the
data resource group entry in which the new data group will participate. Possible
values are *FROMDGDFN (default), *NONE, or the name of a data resource
group entry.

8.1.06.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 39
MXHA-22786 Priority audits are run based on correct time intervals, and no longer run in
response to when a scheduled audit runs or when the audit schedule is changed.
MXHA-22882 Objects with exceptions that are excluded from configuration will no longer be
selected by the prioritized Libraries (#OBJATR) audit.
MXHA-22922 System manager jobs now start successfully when dealing with very large
sequence numbers.
MXHA-22926 System manager remote journals will now be correctly restarted using the
secondary transfer definition IP address if the primary IP address is not available.
MXHA-22937 Target journal inspection will no longer issue a notification for journal entry B-FC
(IFS object forced).
MXHA-22938 Performance was improved for the selection of objects for the #OBJATR Priority
Based Audit.
MXHA-22940 DSPDGSTS merged view will now only color the currently used transfer definition
blue.
MXHA-22970 Priority audits will now correctly audit objects that were previously reported as
existing only on the target system.
MXHA-22972 Data group configuration entries in multi-management environments are now
propagated to disabled data groups correctly.
MXHA-22994 Database apply (DBAPY) will no longer try to recover objects being moved from a
non-replicated directory to a directory that is replicated by object replication.
MXHA-23035 Upgrades to version 8.1 no longer fail with CPF5009 duplicate key error on
DM2100P file.
MIMIX Portal Application
MXHA-22810 Object in error count on the Data Groups portlet is now updated when data group
status is refreshed in VSP.
MXHA-22921 The Compare Object Details from Nodes window now shows the object size
correctly for large objects.
MXHA-22932 Object names with certain special characters (variant) are now correctly handled
and displayed in the Data Protection Reports when the parent library, directory, or
folder is selected to be ignored by VSP.
MXHA-22935 When the Object only on target action policy is set to Do Not Recover, the Object
Correction Activity window now correctly reports (when appropriate) “Not
recovered due to policy Object only on target.”
MXHA-23028 Failed data area poller status now correctly cleared in VSP when all data area
entries (configuration) have been removed.

8.1.06.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 40
Vision Solutions Portal
Vision Solutions Portal version 3.0.18.00 is included with MIMIX service pack 8.1.13.00.

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.0.18.00 includes all relevant changes to earlier VSP level 3.0 service
packs and the following:
STR-5005 VSP is now able to allow users having embedded spaces in the User ID to add
instances for deployed portal applications.

8.1.06.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 41
Highlights Version 8.1 Service Pack 8.1.05.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

New retrieve commands


Four new commands were added to provide methods to programmatically retrieve status for
Application groups, Nodes, Procedures, and Steps. They are:
• Retrieve Application Group Status (RTVAGSTS) - allows the retrieval of status for an
application group.
• Retrieve Node Status (RTVNODSTS) - allows the retrieval of node status for the specified
application group, resource group, and node.
• Retrieve Procedure Status (RTVPROCSTS) - allows the retrieval of status about the most
recent run of a procedure for a specified application group, resource group, and node
(procedure may be in progress).
• Retrieve Step Status (RTVSTEPSTS) - allows the retrieval of status for a step within the most
recent run of a specified procedure.
For each retrieve command, see its help for more detail.
The OPNMMXLST command has also been updated. OPNMMXLST command provides the
ability to open a list of specified MIMIX definitions or data group entries for use with the MIMIX
retrieve commands. The changes include:
• TYPE parameter - A new type of request value of *STEPSTS was added to the TYPE
parameter. *STEPSTS opens a list of status for all the steps of the specified procedure and
application group, or for the started on node. *STEPSTS is for use with the new Retrieve Step
Status (RTVSTEPSTS) command.
• STRONNODE parameter - When specifying parameters on the OPNMMXLST command, a
new STRONNODE parameter is valid only when the value of TYPE is *STEPSTS. It allows
specifying the node on which a procedure run was started.
• PROC parameter - When specifying parameters on the OPNMMXLST command, the PROC
parameter is valid when the value of TYPE is *STEP or *STEPSTS.
• AGDFN parameter - When specifying parameters on the OPNMMXLST command, AGDFN
parameter is valid with the value of TYPE is *PROC, *STEP, or *STEPSTS.
(MXHA-67)

8.1.05.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 42
Fixes included in service pack 8.1.05.00
This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.14.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-22115 The Work with Notifications (WRKNFY) display no longer results in CPF6A9D or
CPF6A15 when F13=Repeat processing is done.
MXHA-22734 The Work with Notifications (WRKNFY) and Work with Recoveries (WRKRCY)
displays now properly subset by data group system 1 or system 2 name.
MXHA-22740 The *CSTIND will now report as *EQ for File Attributes (#FILATR) audit and
Compare File Attributes (CMPFILA) command when target constraint
management is not in use and constraints are enabled on both systems.
MXHA-22777 Performing a virtual switch involving files with case-sensitive physical file foreign
key constraints no longer fails in step program MXDSBCSTV.
MXHA-22780 The MIMIX replication manager job no longer fails with message CPF7037 when
processing an object tracking exception for logical files.
MXHA-22781 The MIMIX user journal apply process will no longer fail with message CPF24B4
when processing replayable journal entries.
MXHA-22783 Database reader (DBRDR) job will no longer get error messages MCH3601 and
MCH0602 when processing incomplete database level journal entries.
License Manager
MXHA-22870 APYLICKEY will no longer receive MCH3601 and the lock on record in LM3100P
will be released as expected.
MIMIX Portal Application
MXHA-22839 Audits initiated through the Run Audits dialog are now able to successfully run in
environments that have a different CCSID than 37.

8.1.05.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 43
Vision Solutions Portal
Vision Solutions Portal version 3.0.17.00 is included with MIMIX service pack 8.1.05.00.

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.0.17.00 includes all relevant changes to earlier VSP level 3.0 service
packs and the following:
STR-4867 Message VSE1002 now references the proper publication when referring users to
view software requirements when VSP is not able to be started.
STR-5019 IBM i file server connections are now established for IBM i portal connections
when a user signs in to VSP.

8.1.05.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 44
Highlights Version 8.1 Service Pack 8.1.04.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Understanding Correction Activity in your MIMIX


Environment video
A new informational video is available under the topic “Understanding Correction Activity in your
MIMIX Environment” in the Did You Know? window in VSP. Take the “Did You Know?” action from
the toolbar in the Enterprise Status portlet.
The video provides a quick tour of MIMIX’s enhanced ability to automatically correct issues
detected by replication, audits, and target journal inspection, as well as an overview of the Object
Correction Activity window in Vision Solutions Portal, which makes identifying and understanding
correction activity easier.
(STR-4956)

Improvements to RJ Link threshold reporting


In data groups with periods of very low activity, customers will now rarely experience false
positive RJ Link threshold conditions. The RJ Link threshold is defined in the data group
definition and can be specified as a time difference, a number of journal entries, or both.
Previously, the RJ Link threshold could appear to be exceeding its time value while waiting for the
operating system to send internally generated journal entries to the remote journal on the target
system.
Action required:
No action is necessary for systems running on IBM i 7.2. For earlier operating system releases,
an IBM PTF is required to get the improved behavior when MIMIX is started following the
installation of this service pack. The PTF can be applied either before or after installing this
service pack.
• For IBM i 6.1, apply SI43711 or its supersede
• For IBM i 7.1, apply SI43712 or its supersede
Use the CHKIBMPTF command to determine whether the PTF is already applied. See Step 1 in
“Before installing the service pack” on page 5 for instructions on using the command.

8.1.04.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 45
Fixes included in service pack 8.1.04.00
This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.13.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-14050 IFS tracking entries with missing FID values for a disabled data group are
corrected for application groups with three or more nodes.
MXHA-22327 Priority audits of IFS Attribute (#IFSATR) and Object Attribute (#OBJATR) audits
no longer fail with MCH3601.
MXHA-22578 CHGDG command and step MXCHGDG no longer report failures when disabling
an already disabled data group where one node is not reachable.
MXHA-22596 Displaying recovery progress no longer results in a QRY1058 message.
MXHA-22643 Count of recoveries shown on WRKDG now includes recovery notifications.
MXHA-22653 Objects with audit differences that were not recovered now correctly mark
exceptions as failed.
MXHA-22655 Performance of Collector Services is improved when there are many activity
entries.
MXHA-22667 Synchronizing referential constraints no longer fails with MCH0601.
MXHA-22683 Step program MXTGTJRNFE no longer fails with CPF70B1 and no longer
attempts to change journal settings for logical files during virtual switch recovery.
MXHA-22690 Step program MXCHKTJI in procedure PRECHKVRT checks the target journal
inspection status correctly.

Vision Solutions Portal


Vision Solutions Portal version 3.0.16.00 is included with MIMIX service pack 8.1.13.00.

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.0.16.00 includes all relevant changes to earlier VSP level 3.0 service
packs and the following:
STR-4796 VSP no longer goes into a Pending state after issuing endvsisvr when VSP is
installed on Windows.
STR-4952 The expvsiinf tool in VSP now appends the current date to the end of the
generated ZIP file to allow multiple files to co-exist for different VSP log collection
dates.

8.1.04.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 46
Highlights Version 8.1 Service Pack 8.1.03.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Improvements to Data Protection Reports and actions for


configuring from VSP
Several changes to the Data Protection Reports portlet and to actions available from the portlet
improve the ability to configure selection rules when using Vision Solutions Portal. Many of the
improvements are associated with configuring libraries. Unless otherwise noted, these
improvements apply when using the indicated interface for an instance running MIMIX version
8.1.03.00 or higher but not for instances running earlier software levels.

Data Protection Reports portlet automatically refreshes configured


replication information
The Data Protection Reports portlet automatically refreshes the information displayed in the
Configured Replication columns of each report and will no longer display the configuration
changed icon. The configuration information is refreshed whenever you use the Include, Exclude,
Ignore, and Stop Ignoring actions to change the protection status of a selected library, directory,
or folder. You may still need to manually run reports to access the most recent objects created on
the system and to have the report reflect the results of configuration changes made from other
interfaces such as from actions on the Selection Rules window or from the native user interface.

Related journal information in Library reports


The Library tab of the Data Protection Reports portlet includes these enhancements:
• The Library report now includes a Journal column to identify the names of journals related to
the library. When the value Multiple is displayed, more than one journal resides in the library,
more than one journal is journaling the library or its contents, or can automatically journal new
objects created in the library. You can see the journal names in flyover text or by using the
Details action. A new Sort libraries preference available in the portlet’s Edit mode allows you
to control whether libraries are sorted by their protection status (default) or alphabetically by
the fully qualified journal name (library/journal) of their associated journal.
• You can now access a list of all the journals related to a library in the Library report by using
the Details action. The Related Journals tab added to the Library Details dialog identifies all
the journals related to the library and its contents, the type of content journaled to each listed
journal (the library, files, data areas, and data queues), and the name of any application
group, resource group, or data group that replicates from each listed journal. If present in the

8.1.03.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 47
library, the list also identifies the QSQJRN journal and the journal identified in the QDFTJRN
*DTAARA because they may be used for journaling newly created objects.

Include in Replication wizard improvements


When you use the Include action from the Data Protection Reports portlet, or from a
MMNFYNEWE notification in the Notifications portlet, the resulting Include in Replication wizard
has the following improvements:
• You can now specify a reason why you are including a library, directory, or folder in the
Summary panel of the wizard.
• Preferences now determine the default value shown in the wizard for the Synchronize when
replication starts option on the Synchronization Options panel and for the Start replication (or
Restart replication) option on the Summary panel. You can change the specified value in the
wizard each time you use it, or you can change the preference value in the Edit mode of the
Data Protection Reports portlet.
• When including a library, you will see the words “not recommended” and a Help icon next
to the choice to create a new application group on the Configure Replication panel when
there are existing application groups listed that you can use. Click the Help icon to display
more information about determining how many application groups you need.
• When including a library that contains physical files or trigger programs that are related to
files or programs in multiple libraries that are replicated by different resource groups or data
groups, the wizard now issues a warning message instead of an error message. You may
want to perform additional manual evaluation before continuing with the wizard configuration.
Click the help icon to display more information. When using the wizard for an instance
running an earlier MIMIX service pack level, this scenario is too complex for the wizard and
results in an error message.

Improved access to configuration for replicated system objects


In a two-node environment that has one or more application groups, you can now access the
Replicate System Objects dialog any time you need to add selection rules to replicate system
objects, such as user profiles or job descriptions. Previously, the dialog was not available after its
initial use. Now, for subsequent uses, you can access the dialog from the global menu on the
Data Protection Reports portlet or the Replication Configuration window.
When selection rules exist for system objects, using the Selection Rules action from the
Replicate System Objects dialog will display those rules in the Selection Rules for System
Objects window.

Ignored reason can now be changed


When you use the Details action from a library, directory, or folder that is Ignored in the Data
Protection Reports portlet, you can now change the Reason for ignoring field. This change is
available regardless of what software level is running on the instance.

8.1.03.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 48
Enhancements to exported reports
If you export reports to an Excel® spreadsheet or PDF, you can now choose the type of related
information to include in the exported report. The Include related field in the Export Data
Protection Reports dialog supports these values:
• Configuration details (default). The report includes the name of the application group,
resource group, or data group to which the library, directory, or folder is configured for
replication. For libraries, the Journal column in the report identifies the journal used for
replication. For directories and folders, the Journal column in the report is always a dash (–).
• Journals. A Library report includes all journals related to the library regardless of whether the
journals are used by replication. Directory and Folder reports do not include any journal
information.
Also, header information is now frozen in a report exported to a spreadsheet.
(MXHA-19767)

Fixes included in service pack 8.1.03.00


This service pack includes all relevant changes to earlier level 8.1 service packs, all relevant
fixes in 8.0.13.00 or earlier levels of version 8.0, and the following reported problems:
MIMIX
MXHA-22325 Exception records for objects that are detected by the audits but not handled
within one day will now be marked as failed.
MXHA-22372 Members that contain extra deleted records at the end of the source file will no
longer cause the File Data (#FILDTA) audit to report an exception for the member.
MXHA-22437 Replicated objects with detected problems are now reported and handled
correctly.
MXHA-22522 Recovery of record level detected problems will no longer result in database apply
job looping.
License Manager
MXHA-22433 RSTLICPGM of the 7VSI001 LPP no longer affects files in the LAKEVIEW library
and no longer causes a subsequent License Manager installation to fail.

Vision Solutions Portal


Vision Solutions Portal version 3.0.15.00 is included with MIMIX service pack 8.1.03.00.

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.0.15.00 includes all relevant changes to earlier VSP level 3.0 service
packs and the following:
STR-4972 INSVSISVR command no longer fails when VSP is already installed.

8.1.03.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 49
Highlights Version 8.1 Service Pack 8.1.02.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

MIMIX DR supports virtual failover and priority auditing


Beginning with this service pack, MIMIX DR users can now take advantage of virtual failover
(virtual switching) capabilities and use prioritized object auditing.
Virtual switching is the process of testing your production environment applications on a backup
node without shutting down the applications on your production node or ending replication. See
“Support for virtual switching” on page 52.
In prioritized object auditing, an audit run checks only prioritized objects, which may be a subset
of the objects replicated by the data group. The audit is allowed to start only during its specified
time range. MIMIX determines the auditing priority of an object based on the results of its most
recent audit, most recent change, and the frequency specified for auditing priority categories.
Prioritized auditing is enabled in new installations of MIMIX DR running MIMIX 8.1.02.00 or
higher. MIMIX DR installations that upgrade to 8.1.02.00 or higher and want to use prioritized
auditing must enable it, which is done through audit scheduling interfaces. You can also change
scheduling details for when a prioritized audit is allowed to run.
For more information about either capability, see online help for the MIMIX portal application in
VSP or the MIMIX Operations book.
(MXHA-22258)

Viewing and comparing details of replicated objects


From Vision Solutions Portal (VSP), it is now possible to view details of replicated objects and
pinpoint where differences exist between source and target nodes. The Compare Object Details
from Nodes window displays detailed information from the operating system on the source and
target nodes for a selected replicated object or file member. This information can be useful for
problem determination when replication activity for the source object is held due to an error or
when investigating unresolved audit differences. Information is organized on multiple tabs. The
information displayed reflects the current state of the object, which may be different than its state
at the time that a replication or audit error was reported.
General tab: Lists object or member attribute values from the operating system of both nodes. An
icon may appear next to an attribute when there are differences between nodes.
• A red Action Required icon is displayed when values between the two nodes are not the
same and the difference is significant to replication. User action is required to investigate the

8.1.02.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 50
difference and determine the appropriate action to resolve the problem.
• A blue Informational icon is displayed when values between the two nodes are not the
same. A difference may or may not be expected or significant for a replicated object.
• For some date attributes, differences are expected and are never identified with a difference
icon. Examples include the date created, date of last journal start, and date last changed,
used, saved, or restored.
Locks tab: Identifies any locks on the object or file member on the source and target nodes and
provides available details retrieved from the operating system about the lock type and lock
holder. If any locks exist on either node, they are listed with their associated job (name, user, and
number) and lock type. For directory objects, there may be multiple types of locks listed. For
objects within libraries and folders, additional columns identify the status and scope of the lock,
as well as the affected thread ID and member.
You can access the Compare Object Details from Nodes window by using the Compare Details
action for an object or file member listed in any of these locations:
• An Activity tab on the Data Group Details and Activities portlet
• The File Activity Details window, Related Files window, Object Activity Details window,
Related IFS objects window
• The Replicated Objects window (or portlet)
• An Audit Results window or an Audit Result Details window
(MXHA-20048)

Changed behavior for OBJONTGT policy


The replication manager now ignores the OBJONTGT policy when automatic replication recovery
policies (DBRCY, OBJRCY) are set to *DISABLED, and no recovery is performed for object-only-
on-target errors found during replication.
MXHA-22177

Fixes included in service pack 8.1.02.00


This service pack includes all relevant changes to earlier level 8.1 service packs and fixes in
8.0.12.00 and earlier levels of version 8.0.

Vision Solutions Portal


Vision Solutions Portal version 3.0.14.00 is included with MIMIX service pack 8.1.02.00.

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.0.14.00 includes all relevant changes to earlier VSP level 3.0 service
packs and the following:
STR-4890 VSP now ships with and runs on Apache Tomcat version 6.0.44.

8.1.02.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 51
Highlights Version 8.1 Service Pack 8.1.01.00
This service pack includes the contents of superseded MIMIX service packs, and the following
changes.
These icons indicate:

A change that may require action. For example, you may need to modify automation
programs or exit programs or perform other actions before or after installing the service pack.

A change in behavior or a change to the user interface. You should be aware of the change,
but no action may be required.

New function or an enhancement in the indicated software.

Support for virtual switching


MIMIX® Availability™ now includes support for virtual switching, which is the process of testing
your production environment on a backup node without shutting down your applications on your
production node or ending replication.
MIMIX support for virtual switching sets up your test environment to allow a designated backup
node to be used for testing while the production environment and MIMIX are active. Only apply
processes for data groups that currently use the test node as their backup node are ended. Other
replication processes remain active, so production node transactions are processed, sent to the
target node, and remain queued for apply processes until testing is complete. While you are
testing that the applications can run on the designated test node, MIMIX tracks any changes
made to objects on the test node that are eligible for replication by the affected data groups in the
application group. After you indicate that testing is complete, MIMIX reverts those changes, starts
apply processes and begins processing their queued transactions, and returns the node to
normal operations. This support is available for instances running version 8.1 of MIMIX or higher
and that meet other configuration requirements.
Non-cluster application groups support virtual switching through the virtual switch procedure
(SWTVRT) and a related precheck procedure (PRECHKVRT). These default procedures are
created automatically when a new application group is created and when upgrading an existing
installation to this release of MIMIX. The PRECHKVRT procedure checks for configuration
requirements and limitations, and for conditions that would otherwise end the virtual switch
procedure. The SWTVRT procedure performs those same checks, then performs several setup
steps to prepare the MIMIX environment and objects on the test node for testing, including
ending apply processes for the data groups in the application group that use the test node as
their target node. When MIMIX and the replication environment on the test node are ready, the
procedure waits while you test your applications. When you are finished testing, you must
respond to the procedure's waiting message to indicate that MIMIX can begin recovering the
target environment to match the production environment. During this recovery phase, apply
processes are started and begin to process the queued journal entries for replicated production
node transactions that accumulated while you were testing. Changes to objects on the target
node are removed, with the exception of spooled files or objects created outside the configured
scope of objects eligible for replication.
Effect on replication processes and status: While the procedure is running, one of three
virtual switch statuses is reflected in the replication status of the application group, resource
groups, and data groups when no other conditions that require action exist. Each status is

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 52
triggered by a specific step program in the procedure. The statuses are: Virtual switch starting
(*VRTSWTSTR) to indicate when changes to your test environment begin, Virtual switch testing
in progress (*VRTSWTTST) to indicate that testing can be started and may be in progress, and
Virtual switch recovery in progress (*VRTSWTRCY) to indicate that testing completed, test
changes are reverted, and queued transactions are being applied. In Vision Solutions Portal, all
three statuses are represented by the virtual switch icon .
For the duration of the virtual switch procedure, the virtual switch controls when the apply
processes are ended in a controlled manner and when they are restarted. You can start or stop
other replication processes as needed on the production node. When other replication processes
are active, replicated transactions accumulate in queues for apply processes and will not be
applied to the target node until the apply processes are started by the recovery phase of the
virtual switch procedure.
While a virtual switch status is displayed, other less severe conditions can exist, and you will
need to drill into more detailed interfaces to see those problems. Also, when using Vision
Solutions Portal, an important difference is that in the overall status column in the Application
Groups portlet, any virtual switch status takes precedence over all other possible statuses so that
you can easily identify that a virtual switch is in progress. Other issues are reflected in the
detailed column statuses for that application group.
Status values are also reflected in the RTVAPYSTS and RTVDGSTS commands, and outfiles for
the commands WRKAG, WRKDTARGE, and WRKDG.
Important considerations: Virtual switching is not a substitute for performing a complete
planned switch test. However, it can be a valuable tool to prepare for a planned switch test.
Topics for virtual switching support included in MIMIX online help in Vision Solutions Portal
include detailed information about MIMIX configuration requirements, operational considerations,
and application testing considerations. Key points include:
• The data groups within the non-clustered application group must be configured to be
switchable, allow journaling on their target nodes, and allow cooperative processing through
the user journal. Keyed replication is not supported and cannot be configured for the data
groups or in their replication selection rules (data group entries). Target journal inspection
must be configured and active on the test node. Virtual switching is not supported in
instances configured as INTRA. These requirements are checked by the PRECHKVRT and
SWTVRT procedures.
• There are additional test and recovery considerations for application groups that replicate an
IBM WebSphere MQ queue manager.
• Evaluate the behavior of applications to be tested prior to starting the virtual switch
procedure, as some applications may not be suitable for virtual switching. MIMIX does not
support removing changes made to objects or data that are not eligible for replication, that
are nodes other than the test node or on other connected servers in your environment, or in
the cloud. Applications that use IP impersonation to change addresses or that hardcode
system names or IP addresses must be evaluated carefully to ensure that the application can
be used on the test node. Any objects, profiles, authorities, or other items needed to run the
application must be available on the test node.
• Audits are not allowed to run during a virtual switch. While in testing status, target journal
inspection will not send notifications of objects changed on the target node.
• Only target changes logged by the virtual switch will be recovered by the virtual switch.
MIMIX will not recover any spooled files created, changed, or deleted on the test node; those
must be recovered manually. Changes to objects that are not eligible for replication are not

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 53
recovered, and changes made to other applications, nodes, servers, or the cloud are not
recovered.
• A failed or canceled virtual switch procedure can only be acknowledged if the failure or
cancel request occurred before the step that begins changing the test environment. If the
procedure fails or is canceled after the virtual switch started status is displayed for replication,
you will not be able to start, stop, or switch the application group until after the virtual switch is
resumed and runs to completion.

Virtual Switch Activity window


From the Application Groups portlet in Vision Solutions Portal (VSP), you can view the objects
changed on the test node of a virtual switch from the Virtual Switch Activity window. The window
lists objects affected by the most recent virtual switch of an application group and identifies any
automatic recovery action for each object.
When a new virtual switch is started, the list is reset. Objects are listed as they are changed on
the test node. Refresh the window to view the latest information. When a virtual switch is in
progress, the list may contain information about object changes and automatic recovery actions
that have not completed.
More than one problem or change may be identified for an object. The list shows changes
detected for an object during switch testing as well as any other detected problems for the same
object that need recovery, regardless of the process that detected them. The most severe
reported error takes precedence and determines the recovery action and recovery status icon
displayed for the object.
Recovery actions for objects changed on the test node as well as recoveries for problems
detected by other processes are processed during the recovery phase of the virtual switch
procedure. When the virtual switch procedure has completed, manual intervention or correction
may be required if an automatic recovery action could not be performed or failed to correct the
problem.
An object is automatically removed from the list when its recovery status is completed or failed
and three days have passed since the date in the Reported field. If another problem or change is
detected, the reported date is updated. When the recovery phase of a virtual switch has started,
it is possible for an object to meet automatic removal criteria and be removed from the list before
the virtual switch procedure completes.
Failed recovery actions generate either replication activity errors or notifications, which are
visible in other areas of the user interface where they can be manually resolved.

Additional changes to support virtual switching


Other significant changes to the product to support virtual switching include:
• Virtual switching uses the enhancements to automatic error detection and recovery and the
source capture delay policy described in the section for “Automatic problem detection and
recovery enhancements” on page 55.
• A new procedure type of virtual switch (*SWTVRT) is supported in interfaces and commands
for creating and using procedures, including outfiles for the WRKPROC and WRKPROCSTS
commands.
• Within the virtual switch procedure, two user-customizable steps, STRUSRAPPV and
ENDUSRAPPV are available. Respectively, these steps can be customized to perform any
actions necessary to start and stop the user application as part of a virtual switch test. These

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 54
steps are initially disabled. For information about customizing and enabling steps, see topic
“Customizing step programs within shipped procedures” in online help for the MIMIX portal
application.
• New and changed interfaces support starting a virtual switch procedure. From VSP, the
Application Groups portlet added the toolbar action Start Virtual Switch and the row action
Virtual Switch, and the Procedures portlet added the row action Start Virtual Switch. These
actions open the Start Virtual Switch dialog. In the native user interface, the Switch
Application Group (SWTAG) command supports a value of *VIRTUAL for Switch type
(SWTTYP). In these interfaces, the default value for the test node is the node identified as
the first backup in the current node roles of the recovery domain (ROLE parameter). If the
application group has three or more nodes in its recovery domain, you can select to use a
different backup node as the test node. Replicate nodes cannot be selected as the test node.
Also, in VSP, the Switch Precheck dialog and actions for accessing it have been renamed to
Precheck, and the dialog now supports selecting whether to run the precheck for a planned
switch or a virtual switch.
• The Application Groups portlet now supports the Message Details action, which provides the
ability to respond to waiting messages from procedures that start, stop, or switch (planned,
unplanned, and virtual) an application group directly from this portlet. The message waiting
icon will appear in the overall status column if it is the most severe issue, and always
appears in the Procedure column.
• New subscription events within VSP will notify you of the replication status changes for virtual
switching and when the switch recovery is complete. Other subscription events are changed
to not be triggered during a virtual switch or during specific virtual switch statuses. Affected
events include those that report application groups, resource groups, and data groups which
have action required or partially stopped processes, procedures with an action required
status, and data group thresholds exceeded. For details, see the MIMIX subscription events
list in VSP online help.
• A new informational video is available under the topic “Testing Applications using MIMIX
Virtual Switch” in the Did You Know? window in VSP. Take the “Did You Know?” action from
the toolbar in the Enterprise Status portlet.The video provides a quick tour of the interfaces
for performing a virtual switch and checking its results.
(MXHA-10072)

Automatic problem detection and recovery enhancements


This release provides significant enhancements to automatic recovery capabilities that, when
enabled for replication, change how MIMIX reports replication errors to show errors only after all
automatic attempts to correct the problem have been exhausted and result in fewer objects
requiring manual correction. In the MIMIX portal application, the Object Correction Activity
window provides a consolidated location to view all objects for which automatic recovery actions
exist, regardless of their origin. Automatic recoveries can now originate from target journal
inspection and from virtual switch procedures. This release also includes numerous updates to
other areas of MIMIX to support recoveries, including policies, conditions that end switching, and
notifications sent by recovery actions.

Replication
This release changes how the problems that MIMIX detects during replication are reported and
how automatic recoveries are attempted when automatic recovery policies for database and

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 55
object replication processes are enabled. More recovery actions will occur automatically. Overall,
users should see fewer reported replication problems and those should require less intervention.
Previously, when a replication error occurred and automatic recovery policies were enabled,
replication activity for the file or object was marked as an error before a recovery action started.
Now, problems detected by replication processes are tracked internally as exceptions to
replicated objects. Database and object apply processes automatically request recovery actions
for the detected problems without changing the status of replication activity to an error status.
The replication manager, now a persistent job, periodically checks for requested recovery actions
and initiates the additional processing needed to perform the correction. Replication errors are
reported to application groups and data groups only when the file or object cannot be
automatically corrected after all available automatic recovery attempts are exhausted. Except for
objects that exist only on the target node, objects that have a recovery action are flagged for
prioritized auditing regardless of whether their recovery was successful.
In the event of a switch, you can determine what objects are potentially not synchronized. From
Vision Solutions Portal, you can view the list of objects with recovery actions; this window is
described in more detail in “Object Correction Activity window” on page 57. Additional changes
include:
• You can see the number of objects with new or in-progress recovery actions in the
Replication Recovery column added to the Data Groups portlet. The equivalent information in
the native user interface appears in the recoveries count in the Audits/Recov./Notif. field on
the Work with Data Groups display (WRKDG).
• In-progress statuses now appear in the File Activity tab of the Data Group Details and
Activities portlet when recovery actions are in progress.
• In the native user interface, several views of the Display Data Group Status display
(DSPDGSTS) now include new count fields for database and object recoveries that are new
or in-progress. The RTVDGSTS command and outfile for the WRKDG command also
support new parameters and fields for the number of files, IFS tracking entries, and object
tracking entries with new or in-progress recoveries, as well as a new status field to report the
status of a virtual switch.

Extended policy removed


The extended policy MIN_JRN_CRC_ERR is no longer supported. If present, this extended
policy is automatically removed when upgrading to MIMIX version 8.1.

Target Journal Inspection


Automatic recovery actions are now generated for target node changes detected by target
journal inspection. Target journal inspection recoveries are also a key component of the recovery
phase of a virtual switch. The same policies (database replication recovery and object recovery)
that enable recoveries also enable replication recoveries for target journal inspection from the
respective target node journals.
In Vision Solutions Portal (VSP), the results of target journal inspection are displayed in the
Objects Changed on Target window. The information displayed varies according to the release of
the instance you are managing. When managing instances running MIMIX version 8.1 and
higher, the Objects Changed on Target window includes the automatic recovery actions to correct
problems detected by target journal inspection.

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 56
Object Correction Activity window
This new window provides a consolidated location to view all objects that currently need recovery
for detected problems as well all objects that require attention because of failed replication
activity. The recovery actions for listed objects include those generated by replication processes,
audits, target journal inspection, and virtual switch procedures. The Object Correction Activity
window is accessed by using the Correction Activity action from the global menu and row menus
on the Application Groups portlet and the Data Groups portlet, and as a global action from the
Audits portlet and Replicated Objects window. The window is only available from Vision Solutions
Portal (VSP) in the MIMIX portal application, and only for instances running MIMIX version 8.1 or
later.
The Object Correction Activity window identifies objects for which recovery actions exist. More
than one problem may be listed for an object. When replication errors exist for the object and
there are other issues detected that need recovery actions, the most severe replication error
takes precedence and determines the recovery action and status icon. Depending on how the
window is accessed or filtered, the recovery actions may be New, Waiting (in-progress),
Recovered, or Not recovered. The initial view of the window does not include objects whose
recovery completed successfully, but you can change filtering criteria to view objects with a
Recovered status. Several predefined filters are available to easily locate only active recoveries,
objects that need manual action, or objects that were not equal in their last audit.
Note: This window always displays current problems, recovery, and recovery status for listed
objects. If you filter the window to the process that detected the problem (originator), the
list will show objects with problems detected by the selected originator as well as any
current problems and new or waiting recoveries regardless of their originator. If you use a
filter, be aware that current problems take precedence over completed or failed
recoveries that are within the retention period for completed or failed recoveries.
An object is automatically removed from the list when its recovery status is completed or failed
and three days have passed since the date in the Reported field. If another problem or change is
detected, the reported date is updated.
Failed recovery actions generate either replication activity errors or notifications and direct you to
other areas of the user interface for manual problem resolution.
When managing instances running MIMIX version 8.1 or higher, the Object Correction Activity
window replaces the Recoveries window. Also, the Recovery Details dialog is replaced by the
Audit Details portlet. Older versions of these interfaces are still available when managing
instances running earlier versions of MIMIX.

Related Changes
New versions of the following interfaces are also used only for instances running version 8.1 and
higher:
• The Recoveries tab of the Audits, Notifications, and Recoveries portlet now varies according
to the version of the instance being managed. The information displayed for an 8.1 or higher
instance is similar to the Object Correction Activity window for new and waiting-to-process
recoveries for the selected data group.
• The Object Details dialog includes more problem and recovery information and is redesigned
to more easily distinguish between details for the object, replication problems and recovery,
and the latest auditing details.

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 57
Recoveries included in conditions that end switching
Procedures and interfaces for switching now check for the existence of recoveries as a condition
that would otherwise end a switch and may change the recovery action status depending on
which value is specified. They also now check for the existence of constraints disabled by MIMIX
on the target node.
The Switch Data Group dialog and the SWTDG command support two new values for addressing
new or in-progress recoveries in the Conditions that end switch (ENDSWT parameter). The
dialog implements these values as a multi-part selection; when you select the value Recoveries,
you can then change the value of the Objects with recoveries field. Both new recovery values
affect recoveries for replication and target journal inspection processes. The new recovery values
are:
• Set status to error (*FAILRCY).
The process checks for any new or in-progress conditions. Before ending the process, any
new or in-progress recoveries are converted to held file activities, held tracking activities, or
failed object activities (file, tracking, and object entries in the native user interface). If a
recovery action has no associated replication activities, an error notification is sent. The
resulting held and failed activities need to be resolved manually. Planned or unplanned
switching when there are any existing recoveries, held activities, or failed activities can result
in objects that are not synchronized between the source and target nodes.
• No status change (*RCY).
The process is ended if there are any new or in-progress recoveries for replication processes
or target journal inspection. The status of any new or in-progress recoveries is not changed
before ending the process. Planned or unplanned switching when any recoveries exist can
result in objects that are not synchronized between source and target nodes.
Additional changes to the Conditions that end switch include:
• The behavior of the value Default (*DFT) is updated. For a planned switch, all conditions
except *RCY are checked, and any new or in-progress recoveries are converted to
replication error conditions. For an unplanned switch, the process is ended if there are any
backlogs for the database apply process (similar to the value Database Pending (*DBPND)).
• On the SWTDG command, if both *RCY and *FAILRCY are specified, the process checks for
the *RCY condition first. The dialog prevents both values from being selected.
• A new value, Disable Constraints (*DSBCST), checks for the existence of constraints
disabled by MIMIX on the target node files.
For application groups, new step programs added to procedures for switching (SWTPLAN,
SWTUNPLAN, and SWTVRT) check for recoveries as a condition that ends a switch. Step
MXCHKRCY is equivalent to the value No status change (*RCY), and is also added to
procedures PRECHECK and PRECHKVRT. Steps MXFAILRCYB and MXFAILRCYR are
equivalent to the value Set status to error (*FAILRCY) and check the backup nodes and replicate
nodes, respectively. Following these steps, the addition of a second occurrence of steps
MXDBERR, MXNFYERR, and MXOBJERR will check for any new replication errors resulting
from recoveries.

Notifications
A recovery that is not successful will issue an error notification when there is no associated
replication file, object, or tracking activity for the object that can be marked as failed in the Data
Group Details and Activities portlet. One notification is issued per object recovery during normal

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 58
replication processes. During the recovery phase of a virtual switch, one notification per data
group is issued.
The number of notifications issued by successful replication recoveries is significantly reduced.
Only object replication processes that successfully process an object while using the configured
third delay/retry cycle will send an informational (*INFO) notification. See the Policies section for
more detail.

Policies
A new policy provides a configurable source capture delay for recoveries that need to capture
source information to perform synchronizations. Other policy changes reflect changes to
notifications for successful recoveries and clarify help for several other policies related to
recovery behavior.
Source capture delay (SRCCAPDLY) policy. In VSP, this policy is located on the Replication
tab of policy interfaces. It specifies the delay (in minutes) between detecting the need for a
replication recovery and capturing the affected file records, attributes, authorities, or the entire
object from the source system. A replication recovery is additional processing that attempts to
correct the detected error. There are two delay settings, one for recoveries during normal
replication, and one for recoveries during the testing phase of a virtual switch. During the
recovery phase of a virtual switch, MIMIX ignores both delay settings in this policy and
immediately captures objects and file records for which replication recoveries have been
identified. Changes to either value become effective automatically as the replication manager
checks for recoveries to process.
During replication (Repl. recovery processing)
Specifies the time, in minutes, to delay before capturing an object or file records that
replication processes have identified as needing replication recovery. During the delay, any
additional replication recoveries needed for the same object or file record range will not be
tracked, thereby reducing the number of captures. The default value is No Delay. Possible
values are:
• No Delay (*NONE). No delay is used and captures occur immediately.
• number-of-minutes. You can specify the time in minutes, with valid values ranging from 1
through 120.
During virtual switch (Virtual switch testing)
Specifies the time, in minutes, to delay before capturing an object or file records identified as
needing replication recoveries during the application testing phase of a virtual switch. During
the delay, any additional replication recoveries needed for the same object or file record
range will not be tracked, thereby reducing the number of captures. The default value is 5
minutes. Possible values are:
• No Delay (*NONE). No delay is used and captures occur immediately.
• number-of-minutes. You can specify the time in minutes, with valid values ranging from 1
through 120.
• Delay Until Recovery (*VRTSWTRCY). Capture of the object or file records is delayed
until the application testing phase of a virtual switch is complete and virtual switch
recovery begins.
Other policy changes: Additional changes to policies that affect replication include:
• Online help for the Database automatic recovery (DBRCY) and Object automatic recovery
(OBJRCY) is updated to indicate that, when enabled, these policies also apply to recoveries

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 59
for target journal inspection. When replication and target journal inspection recovery actions
require synchronization, the recoveries will use the Source capture delay policy.
• The Database recovery notify on success (DBNFY) policy is no longer used and is removed
from user interfaces. During upgrades to this release of MIMIX, existing values for the
instance and data groups are preserved to avoid breaking automation.
• The Object recovery notify on success (OBJNFY) policy is now limited to object replication
processes that use the third delay/retry cycle. If processing completes successfully after
using the configured third delay/retry, the process sends an informational notification. In the
MIMIX portal application, this policy has been renamed to Notify on success and is now
grouped with other Third delay retry policies.
• The Object only on target (OBJONTGT) policy now applies to recoveries for objects identified
by target journal inspection during normal replication as well as by audits. The location of this
policy within VSP varies according to the release of the instance you are managing. When
managing instances running MIMIX 8.1 and higher, the Object only on target policy is located
under the heading Automatic Recovery on the Replication tab of the Policies Summary
window and dialogs for changing policies. When managing instances running earlier
releases, the policy only applies to objects identified by audits and remains on the Audits tab.
• On the Audits tab of the Policy Summary window and dialogs for changing policies, the
Automatic audit recovery (AUDRCY) policy has been moved so that it is now under the
heading Recovery Phase.

Audit recovery changes


The following changes affect recoveries for audits:
• On the Data Groups portlet, the previous Recoveries column is now moved under the Audits
heading and indicates the number of audits in recovery.
• On the Audits portlet, a new Held status is possible and indicates that the recoveries for an
audit are held. New actions are available to Hold and Release an audit that is in its recovery
phase. This replaces similar actions that were available from the Recoveries tab in the
Audits, Recoveries, and Notifications portlet.
• The Run Audits action added to the Application Groups portlet, Data Groups portlet, and the
Object Correction Activity window allows you to run all audits for the instance. You can run, all
audits for all data groups in an application group, for all data groups not in an application
group, or for a specific data group. The requested audits select all objects.
• In the Audits portlet and other VSP interfaces for audits, the Display Results action is now
available for audits with a status of Held or Recovering and for #FILDTA and #MBRRCDCNT
audits with a status of Audit ended.
(MXHA-5932)

Customizable procedure for performing backup operations


For environments with application groups, the new Run Backup (RUNBACKUP) procedure and
several new steps are available to assist you in ensuring that MIMIX is properly handled when
performing tape backups or nightly saves from the target node. The RUNBACKUP procedure
first verifies that there are no active procedures for the application group (step MXCKPRCACT),
then ends data group replication processes using one of several available steps, enables any
constraints on target node files that were previously-disabled by MIMIX (steps MXECSTB,

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 60
MXECSTR), and performs the user application backup using the operations you include in the
new step BACKUPAPP.
The procedure defaults to step MXENDDG for ending replication processes, which performs a
controlled end. However, several other disabled steps are included as alternative choices. When
enabled, step MXENDDGDB performs a controlled end of only the database apply processes.
When enabled, step MXENDDGNMX performs a controlled end of the data group with no timeout
maximum. Or, you can enable the following set of steps to perform a controlled end of only the
apply processes: MXSTRDG, MXCHKDGSTR, MXENDDGAPY, MXCKDGEAPY. If you choose
this option, all four steps are necessary to ensure that all apply jobs end.
Upgrading to this version of MIMIX will automatically create the procedure for application groups
that existed prior to the upgrade. Application groups created after installing this version of MIMIX
automatically have the RUNBACKUP procedure created.
Action required:
The RUNBACKUP procedure requires action and programming expertise to customize the
BACKUPAPP step for your environment and to compile the program. Also, to use one of the new
steps for ending replication requires that you enable the step from within the context of the
RUNBACKUP procedure for each application group. Both types of customization require access
to the native user interface. Options and instructions for customizing steps within shipped
procedures are available within the MIMIX portal application's online help as well as the MIMIX
Administrator Reference book. Instructions for disabling and enabling steps within a procedure
(CHGSTEP command) are available in the MIMIX Administrator Reference book.
(MXHA-10070)

Changes to support for unconfirmed entries in


synchronous remote journaling environments
MIMIX no longer supports handling unconfirmed journal entries during an unplanned switch. This
affects environments in which remote journaling is configured for synchronous delivery mode.
Remote journaling configurations that use asynchronous delivery mode are not affected.
Step program MXUNCNFE is no longer available. When upgrading MIMIX software to version
8.1 or higher, the upgrade process will remove MXUNCNFE step from existing SWTUNPLAN
procedures and the MXUNCNFE step program will be removed from the instance. In the event of
an unplanned switch of an environment that uses synchronous remote journaling, the
unconfirmed entries on the source node will be lost. The target node contains the most recent
copy of the data.
(MXHA-14302)

Support for MIMIX-managed foreign key constraints on


target node
Target constraint management is now a configurable attribute of database apply processing for
handling referential (foreign key) constraints. Its capabilities support virtual switching, but it can
also be used during in limited environments to improve database apply performance during
replication. Target constraint management replaces the previous solution for managing target
node constraints that was implemented via extended policies.

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 61
For a data group associated with an application group, you can allow MIMIX to manage when
foreign key constraints are enabled and disabled on replicated files on the target node. In some
environments, allowing MIMIX to perform target constraint management may improve
performance of the database apply (DBAPY) process by allowing workloads to be more evenly
balanced across multiple database apply sessions.
MIMIX-managed constraints may improve performance of the database apply process in
environments with high-activity files with established networks of foreign key constraints, but that
do not routinely add or remove constraints or add or remove files involved in constraints.
Replication environments that add or remove foreign key constrains or create and delete files
with foreign key constraints should not use target constraint management. For details, see
Constraint Support topics in online help for the MIMIX portal application.

Upgrade behavior
For most customers, the upgrade process preserves the behavior of previous releases by setting
existing data groups to the default value for target constraint management, in which target files
retain the same constraint setting (enable or disable) as the replicated source files. If you want to
allow MIMIX to perform target constraint management, user action is required after upgrading to
change the configuration. For more information about configuration requirements and
configuration procedures, see Constraint Support topics in online help for the MIMIX portal
application.
The upgrade process makes multiple changes to existing procedures, as follows:
• Step programs MXECSTB and MXECSTR are automatically added as enabled steps to all
existing procedures of type *SWTPLAN procedures and as disabled steps to all procedures
of type *SWTUNPLAN, *END, and to ENDTGT procedures. Steps MXECSTB and
MXECSTR enable foreign key constraints previously disabled by MIMIX on all backup nodes
and replicate nodes, respectively. In environments that previously added and enabled step
MXENBCST in procedures, the step is removed.
• Step programs MXCKDCSTB and MXCKDCSTR are automatically added and enabled to
procedures of type * SWTPLAN and *SWTUNPLAN, and PRECHECK procedures. These
steps verify that there are no disabled constraints previously disabled by MIMIX on any of the
backup nodes and replicate nodes, respectively.
• Step programs MXECSTNCB and MXECSTNCR are automatically added to the following
procedures but are not enabled: END, ENDTGT, RUNBACKUP, SWTPLAN, and
SWTUNPLAN. When enabled, these steps will enable foreign key constraints without
checking data in referenced files on all backup nodes and all replicate notes, respectively.
In environments that implemented the extended policy solution in previous releases, the affected
data groups are migrated to the target constraint management during the upgrade to MIMIX
version 8.1. The upgrade process will implement the following:
• If the extended policy DISABLE_CONSTRAINTS_FOR_DBAPY is used to disable
constraints on the target node, the current settings are mapped to the equivalent setting in
the configuration of affected data groups. If you disabled constraints, the affected data groups
will bet set to *YES for target constraint management. The extended policy will be removed
after its values are migrated.
• Step program MXDSBCST, previously used with the extended policy, is removed from
existing procedures during the upgrade to MIMIX 8.1. The functionality it provided is now
covered by the product as needed when configuration is set to allow MIMIX to perform target
constraint management. This affects the following procedures: SWTPLAN, SWTUNPLAN,

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 62
END, ENDTGT, ENDIMMED, START.
• If the extended policy ENABLE_CONSTRAINTS_WITH_NOCHK is used, existing data
groups will retain their current setting. However, be aware that the default for this extended
policy changed to ensure that default behavior of the configuration is to not check. This
change affects any data groups that set this extended policy for the first time following the
upgrade to MIMIX version 8.1.

Implementation and behavior


Target constraint management is a configuration option for the database apply process. Although
configured within data groups, this capability is only used by data groups associated with
application groups. The data group must also have two or more apply sessions and must meet
requirements for cooperatively processing *FILE objects through the user journal. Files that are
constrained together need to be replicated by the same data group. If constraints are added
between files replicated by different data groups, or between a replicated file and a file that is not
replicated, constraint operations may fail.
In VSP interfaces for configuring new or changing existing resource groups and data groups, a
new Manage constraints on target field is added under the Apply processing heading on the
Database tab. In the native interface, CRTDGDFN and CHGDGDFN commands added a new
element, Target constraint management, to the Database apply processing (DBAPYPRC)
parameter. Possible values are:
• No (*NO)
MIMIX will not enable or disable foreign key constraints on the target node files by target
constraint management operations. Target node files retain the same constraint setting
(enable or disable) as the replicated source files. When a clear pending start of the data
group is performed, MIMIX will move files that are constrained together into the same
database apply session. This is the default value and provides the same behavior as in
previous releases.
• Yes (*YES)
MIMIX manages when foreign key constraints are enabled and disabled on replicated target
node files as part of the Database apply processing. When database apply processes are
started, MIMIX will disable foreign key constraints on all target node *FILE objects that are
identified by configured file selection rules (data group file entries). The constraints remain
disabled when replication processes are stopped by default. (However, you have the option
to allow them to be enabled when necessary.) MIMIX also leaves the constraints disabled
when a virtual switch recovery ends and normal replication processing continues. When a
clear pending start of the data group is performed, MIMIX will distribute files to apply sessions
without regard to constraint relationships.
Important! A controlled end of the data group is required before changing the value specified for
target constraint management. The data group must be inactive and have no open commit cycles
when the change is made. After changing the specified value, the data group must be started
with a request to clear pending activity (CLRPND(*YES)).
Additional fields are added to the RTVDGDFN2 command and the outfile for the WRKDGDFN
command to support this change.
For additional details about configuration requirements and instructions, and detailed
descriptions of switching behavior, see target constraint management topics in online help for the
MIMIX portal application.

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 63
MIMIX-managed target constraints and switching behavior
MIMIX-disabled constraints must be enabled before switching the data group. When performing
a planned switch, default values cause the switch operation to check for the existence of MIMIX-
disabled constraints as a condition that ends the switch.
When switching in environments with application groups or when starting a virtual switch of an
application group that includes the data group, MIMIX will automatically check and attempt to
enable any constraints it disabled, so the target node files match their source node settings
during the step that ends appropriate replication processes. Before starting the actual switch or
virtual switch processing, the procedure has an additional step program that checks to ensure
that all MIMIX-disabled constraints have been enabled.
When switching in environments that only use data groups, the Switch Data Group dialog
(SWTDG command) defaults the Conditions that end switch (ENDSWT) parameter to
automatically check for the existence of constraints previously disabled by MIMIX, which may
have occurred if the data group was previously associated with an application group. For more
information about changes to the Switch Data Group dialog and command, see the “Recoveries
included in conditions that end switching” on page 58.
When a virtual switch includes a data group that uses target constraint management, the shipped
default virtual switch procedure, SWTVRT, ensures that any MIMIX-disabled constraints remain
disabled when the virtual switch recovery ends and normal replication processing continues.

Temporarily enabling constraints when stopping replication


Changes to interfaces for stopping replication allow you to optionally enable any existing
constraints that were previously disabled by MIMIX. This capability is useful when preparing an
ended data group for a switch or before performing other operations for which you would want
constraints enabled, such as before running a backup of target node files.
To enable any MIMIX-disabled constraints when stopping an application group, enable steps
MXECSTB and MXECSTR in the END or ENDTGT procedures.
On the Stop Data Group dialog (ENDDG command), the Enable constraints on target field
(Enable constraints (ENBCST) parameter) allows you to specify that the stop data group request
will also enable any foreign key constraints on replicated target node files that were previously
disabled by MIMIX.
Only MIMIX-disabled constraints on target node files for which there are existing file selection
rules (data group file entries) with a status of *ACTIVE can be processed. When performed,
constraint processing occurs after the specified replication processes stop and before the
command completes. Both interfaces have the following configuration and command request
requirements that must be met.
• When the ENDDG request specifies an immediate end (*IMMED) or specifies *SBMRQS for
Wait time (WAIT), constraints can only be enabled if database apply processes have already
been ended by a previous controlled end (*CNTRLD) request. The Stop Data Group dialog
does not allow specifying a value for the Enable constraints on target field when Immediately
or Submit Request is specified.
• When the request specifies a Controlled end (*CNTRLD) and the data group configuration
allows target constraint management, constraints can only be enabled if replication
processes end within the specified Wait time (WAIT) and there are no open commit cycles.
• The Enable constraints on target (ENBCST) value is ignored and no constraints are enabled
when the request specifies a value other than *ALL for Apply session (APYSSN) or when a

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 64
value other than *ALL, *ALLTGT, *DBALL, *DBTGT, or *DBAPY is specified for Processes
(PRC).
Possible values are:
• Default (*DFT)
Constraints previously disabled by MIMIX are enabled on the target node if all configuration
and stop request requirements are met. If requirements are not met, the constraints are not
enabled and no error message is issued.
• No (*NO)
Do not enable constraints for files on the target node that were previously disabled by MIMIX.
Any MIMIX-disabled constraints will remain disabled. This improves performance on this end
operation request and the next start operation.
• Yes (*YES)
Enable any constraints for files on the target system that were previously disabled by MIMIX.
Constraints are enabled if all configuration and command request requirements are met. Use
this value when you are ending the data group in preparation for a switch or before
performing other operations for which you would want these constraints enabled, such as
before running a backup from the target system.
MIMIX-disabled constraints that failed to be enabled may still exist on the target node after a stop
data group request completes or after the configuration is changed to no longer allow target
constraint management. Constraints that were not enabled when a data group was ended can be
enabled in one of two ways. You can run the ENDDG command again or you can use the Enable
Constraints action added to the Data Groups portlet. The ENDDG command can be used on data
groups that are active or inactive. The Stop Data Group dialog can only be used on a data group
that is not stopped.
To support enabling constraints on a data group that is already stopped from VSP, the Enable
Constraints action is added to the Data Groups portlet as a row action that is only available when
the data group has been stopped by a controlled stop request, has no open commits, and has
disabled constraints.
(MXHA-10071)

Compatibility of VSP with product portal applications


Note: This topic applies only to versions 8.1.01.00 through 8.1.10.00. See “VSP 3.1
compatibility with product portal applications” on page 3 for current compatibility
requirements.
Vision Solutions Portal (VSP) version 3.0.13.00 is included with this service pack. If you use the
installation wizard for the product, the wizard automatically installs or upgrades VSP to version
3.0.13.00 and deploys the product portal application on all systems in the installation. The first
time VSP version 3 is installed on a system, you must upgrade any other portal applications on
the same system to a level that is compatible with VSP version 3. Portal applications for MIMIX
and iOptimize can be upgraded without having to upgrade their associated product on the IBM i
platform. If you use VSP on a Windows server and have the Double-Take RecoverNow for AIX
portal application installed, you may need a second VSP server because the RecoverNow portal
application is not compatible with VSP version 3.
Portal applications that cannot be upgraded to meet the compatibility requirements with VSP 3.0
will require a VSP server that remains at version 2.0.

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 65
Note: Product portal applications can connect to and manage multiple instances of their
products. The product instances to which some of the product portal applications
connect may be at different versions. For example, a MIMIX 8.1 portal application can
be used to connect to and manage MIMIX 8.1 and MIMIX 8.0 instances. For more
information, see the Vision Solutions Portal (VSP) User’s Guide.
Action required:
• Ensure product portal applications are at a compatible version for VSP 3.0.13.00. See Table
1 on page 66. You can use a products’ installation wizard and select the “portal application”
option to upgrade a portal application.
• If you are using VSP 2.0 on a Windows platform where the MIMIX DR for AIX for AIX portal
application is installed along with the MIMIX or iOptimize portal application, you need to
install VSP 3.0 on a separate server to support portal applications for version 8.1 of MIMIX or
iOptimize.

Table 1. Compatibility of supported product portal applications and VSP.


Product Portal Application VSP server VSP server
versions prior to 3.0 versions 3.0 and higher

MIMIX 8.0

MIMIX 8.1

iOptimize 8.0

iOptimize 8.1

Double-Take MIMIX DR for


AIX 4.1 for AIX

Double-Take for AIX 5.0

MIMIX Installation Wizard now supports Windows® 8.1 and


Windows® 10
MIMIX Installation Wizard can now be run on a Windows® 8.1 or Windows® 10 server to install
MIMIX on an IBM i. The system using the MIMIX Installation Wizard must meet requirements for
their specific operating system. The complete list of wizard requirements is available from
Support Central as well as from the More Info link on the wizard's Welcome panel.
(STR-4861, MXHA-21096)

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 66
Fixes included in service pack 8.1.01.00
This service pack includes all relevant changes to 8.0.12.00, earlier levels of version 8.0, and the
following reported problems:
MIMIX
MXHA-19412 IFS objects moved into user journal replicated namespace and subsequently
moved or renamed are now replicated correctly.
MXHA-20179 Improved performance of the database reader process (DBRDR), which is used
for user journal replication in environments configured with remote journaling.
MXHA-20523 Priority-based auditing now correctly reports previously reported objects that
existed only on target when the OBJONTGT policy is disabled.
MXHA-21767 VSP no longer truncates the displayed hours Reader estimated time in the DB
Statistics tab of the Data Group Details and Activities portlet.
MIMIX Portal Application
MXHA-20207 The File Activities tab of the Data Group Details and Activities portlet in VSP now
shows file entries having a status of Compare Release, Compare Active, and
Compare Repair.

Vision Solutions Portal


Vision Solutions Portal version 3.0.13.00 is included with MIMIX service pack 8.1.01.00.

Fixes for Vision Solutions Portal


Vision Solutions Portal 3.0.13.00 includes all relevant changes to earlier VSP level 3.0 service
packs and the following:
MXHA-20875 VSP will no longer add duplicate subscription events or re-add events to existing
subscriptions on an update of the software.

8.1.01.00 (Included with 8.1.13.00) © Copyright 1999, 2017 Vision Solutions, Inc. All rights reserved. 67

You might also like