Documente Academic
Documente Profesional
Documente Cultură
MIMIX®
Version 9.0 Service Pack 9.0.02.00
MIMIX version 9.0.02.00 includes all relevant changes to earlier level 9.0 service packs, 8.1.24.00, and
earlier levels of version 8.1.
Prerequisites:
• The minimum level required for the IBM i operating system is IBM i 7.1.
• Upgrades to MIMIX version 9.0 require version 9.0 license keys and are supported from any MIMIX
version 8.1 service pack (8.1.01.00 or higher).
• MIMIX portal application version 9.0.02.00 is the minimum version required to manage MIMIX
9.0.02.00 instances and later.
• MIMIX portal application version 9.0.02.00 requires VSP version 3.2.02.00 or higher.
Action required
This document provides service pack installation instructions for all supported installation media.
Required Document Section
“Before installing the service pack” on page 6
“Installing the service pack on IBM Power Systems” on page 10
“After installing the service pack instructions” on page 13
Important changes
Before you install this service pack, you should be aware that it includes changes that may affect the
behavior of your MIMIX and VSP environments. Check the Before Installing and After Installing sections
for potential configuration changes.
To see a list of the behavior changes and enhancements included, see “Features in MIMIX version 9.0”
on page 4.
MIMIX and Vision Solutions are registered trademarks and iOptimize, MIMIX Availability, MIMIX Enterprise, MIMIX Global, and
MIMIX Professional are trademarks of Vision Solutions, Inc. Syncsort is a registered trademark of Syncsort Incorporated. 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.
MIMIX 9.0
iOptimize 9.0
VSP supports the indicated versions of AIX portal applications only on AIX or Windows platforms.
To see a list of fixes included with this service pack, see “Fixes included in service pack 9.0.02.00” on
page 18.
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
9.0.02.00. To see highlights and additional fixes for a superseded service pack, click on the link.
There are no superseded service packs.
9.0.01.00 - Highlights and fixes
Data area polling Checks the installation for Data Area Poller LVE3813
entries.
File alias naming Checks installation for file alias naming LVE3814
entries.
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.
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.
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:
7. 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. Review Technical Alerts, which can be found at Support Central in the Notifications section of the
Support page.
9. 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 9.0.02.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.)
9.0.01.00
Check for IBM PTFs required for multithreaded database apply processing . . . . . .25
Ensure product portal applications are compatible with VSP when installing . . . . . . .2
Ensure that Java requirements for installing and runtime are met . . . . . . . . . . . . . .66
Ensure that systems are running IBM i 7.1 or higher . . . . . . . . . . . . . . . . . . . . . . . .66
Upgrades to 9.0 may need to address obsolete configuration . . . . . . . . . . . . . . . . .67
IMPORTANT: When preparing to upgrade to version 9.0, 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.
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
nodes. The node identified as the primary node will have its system definition assigned the role of a
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
9.0.02.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.)
9.0.01.00
Configure *JOBQ objects to replicate jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Configure attributes to ignore in data distribution environments . . . . . . . . . . . . . . . .56
Review the OBJONTGT policy value and KEEPSPLF parameter setting for all
data group object entries that replicate output queues . . . . . . . . . . . . . . . . .54
Upgrades to 9.0 may need to address obsolete configuration or update
automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Upgrades to 9.0 may need to convert resource groups to use multithreading or
update automation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Upgrades to 9.0 may need to update automation that creates or changes data
groups or configured selection rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
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. Download the VSP 3.2 & Portal Application Installation Wizard for this service pack.
2. Run the wizard.
Installed Location: Version 3.2 of VSP 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.2, 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.
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.
VSP
VSP version 3.2.02.00 is included with MIMIX service pack 9.0.02.00.
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.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 19
These enhancements are not available when viewing an instance running a previous version of MIMIX.
When an earlier instance is selected, the Summary page shows the Application Groups, Data Groups,
and Nodes, Notifications, and DPR Summary portlet portlets.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 20
Last Refresh (A) - Identifies the date and time when the displayed information was last refreshed from
the available data.
The displayed information is automatically refreshed every 60 seconds; however some of the available
data may be older than that.
Notifications (B) - When there are new notifications, fields identify the count of new action required,
attention, or informational notifications that exist. The Notifications action, which provides access to the
Notifications window, appears next to count fields when there new notification and is always available
from the global menu. The Notifications window is only accessible from this portlet and provides the
same information previously available from the Notifications portlet.
Application Group/Data Group (C) - In an instance that uses application groups, application groups
are listed by their severity (default). You can select a toggle to view the list of data groups associated
with each application group. When expanded, data in these columns are blank: Backlogs, Correction
Activity, and Audits.
Icons can appear to the right of an application group name or data group to indicate:
• A virtual switch is in progress.
• An unplanned switch occurred.
• Configuration changes are pending.
• Replicated jobs exist on the current source node and must be submitted or removed before the next
switch.
• When displayed on smaller devices or windows, additional icons can appear to identify issues with
audits or procedures when those columns are not displayed due to size.
Data Groups Not in Application Groups (D) - When an instance also has standalone data groups,
they are listed below the application groups.
Note: If the instance has only data groups, the portlet does not have columns for Procedures and
Planned Switch. Also, the Model switch framework field will appear above the toolbar.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 21
Model switch framework (E) - If model switch framework is enabled and used to switch standalone
data groups, its status is displayed.
Processes (F) - The status icon represents the most severe status related to processes.
• For application groups without clustering, this is the most severe status for the node-level processes
(MIMIX collector services, system manager, journal manager, and target journal inspection) for all
nodes in the application group, all data group processes, and replication direction. For an application
group with clustering, this also includes the most severe status of the application resource group,
IBM i CRG objects associated with data resource groups, and nodes associated with data resource
groups. When an application group is expanded, the status of each data group shows its most
severe status for replication processes on the data group's source and target nodes. Data group
replication processes are: remote journal link or database send, object send, container send, and
object retrieve, database apply, object status send, and object apply.
• For a standalone data group, this is the most severe status of replication processes on the source
and target node. Replication processes are: remote journal link or database send, object send,
container send, and object retrieve, database apply, object status send, and object apply.
Backlogs (G) - The Source and Target columns identify the number of journal entries that are
backlogged for database and object replication processes on that node, shown respectively as n | n. For
an application group, each number is a summation of the associated data groups. For a data group,
each number is specific to that data group. When one of the processes has reached its threshold, the
threshold icon is also displayed. A dash ( - ) in both columns of a data group means the data group is
disabled and a dash in one column means the data group is either object only or database only.
Note: Data for backlogs is collected at regular intervals and can be a couple of minutes old when
displayed. To retrieve current backlogs for a specific data group, go to the Data Group Details
and Activities portlet on the Data Groups page and view the DB Statistics and Object Statistics
tabs. The Replication Environment portlet will also be updated with the newer data group
backlogs.
Correction Activity (H) - This column identifies the number of objects that need manual recovery and
the number of objects that are being automatically recovered, shown as n | n. An icon appears next to
the manual recovery count and the count is highlighted when the most severe status is action required
(red) or attention (yellow). The automatic recovery count includes all objects being automatically
corrected, including out-of-synchronization conditions found by audits and replication.
Audits (I) - The icon shown reflects the most severe combined status of the last audit runs and audit
compliance for all audits for all of the data groups in an application group, or for all audits in a data
group.
Procedures (J) - This shows the most severe status of all procedures for an application group.
Planned Switch (K) - These columns help you identify problems that could prevent a planned switch,
identify when the last planned switch was performed, and provide historical data about previous
switches to help you estimate how long a planned switch may take. Three columns are displayed by
default:
• Precheck - Shows a status icon and the date and time of the last run of the planned switch precheck
procedure.
• Last Start - Shows the date of the last run of the planned switch.
• Average - Shows the average duration of planned switch procedure runs that had a status of
Completed (*COMPLETED), Completed with errors (*COMPERR), or Acknowledged completed with
errors (*ACKERR).
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 22
A dash ( - ) is displayed in these columns if the precheck procedure or a planned switch has never been
run. Additional columns can be selected from Edit mode for the portlet to display the duration of the
shortest, longest, and last run of a planned switch for the application group.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 23
include the ability to run reports, display a report, change the report schedule or policies, display a list of
replicated objects, and access the Replication Configuration window.
(MXHA-11232)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 24
data groups in one or more resource groups between single-threaded and multithreaded database apply
processing.
Action Required
Before installing or upgrading to MIMIX 9.0, use the CHKIBMPTF command to check for required IBM
PTFs. The list includes IBM PTFs that are critical to support multithreaded database apply processing.
The PTFs critical to multithreading must be applied on all nodes. On some operating system levels, an
IPL may be required to apply the PTFs. See Step 1 of the instructions in “Before installing the service
pack” on page 6 for more information about the CHKIBMPTF command.
Also, after upgrading an installation to MIMIX 9.0, action is required if either one of these scenarios
apply:
• In order to use multithreading in an existing resource group, the resource group must be converted.
See “Conversion to and from multithreaded database apply processing” on page 27 for details.
• Even if you do not plan to convert resource groups to multithreading, you may need to update
automation to prevent failures, especially in environments that do not use application groups. You
may also need to update scripts that create data groups or that add or change selection rules (data
group entries), as well as update any user-created instructions. See the automation impacts in the
Action Required section of “Configuration changes to support best practices and multithreading” on
page 30 to support best practices and multithreading.
(MXHA-22349)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 25
System Journal (*SYSJRN) for Cooperative processing type (COOPJRN parameter). Data groups
that specify this value and their associated selection rules (data group entries) must first be
converted to using cooperative processing via the user journal before becoming eligible for
conversion to multithreading.
• Data groups that use multithreading cannot be configured for keyed replication and cannot have any
selection rules (data group entries) configured for keyed replication. Multithreading is not supported
for data groups that implement techniques that require keyed replication, such as bi-directional user
journal replication, file combining, and file splitting.
• In environments that implement cascading and involve referential constraints, if any data group in
the cascade chain is part of a resource group that uses multithreading, all subsequent downstream
data groups must also be in multithreaded resource groups.
• In environments that use MIMIX with IBM’s High Availability Journal Performance IBM i option 42
(journal standby state & journal caching), it is not possible to use standby state on the target system
when multithreading is configured. There are no restrictions with journal caching.
• Multithreading requires that database apply processing (DBAPYPRC parameter) specify the Commit
mode as Immediate (*IMMED). If you access data on the target system, this change may affect your
processing. See “New default for Commit mode (DBAPYPRC)” on page 34 for more information.
• Multithreaded data groups use commitment control to apply record level changes on the target. In
some cases, such as when errors occur, transactions are rolled back, and some or all of the changes
are re-applied by the database apply B job without using commitment control.
• Some record level operations may not be applied when two or more journal entries for the same
record occur close to each other on the journal. Only the final entry will be applied.
• In data groups whose journal definitions specify to use Minimize entry specific data (MINENTDTA)
values other than *NONE, the opportunity for multithreading database apply processing to combine
multiple journal entries for the same record to a single write, update, or delete operation is reduced.
• MIMIX for MQ resource groups cannot be configured for or converted to use multithreaded database
apply processing. The reconstruction data group requires the value 1 for the number of database
apply sessions (NBRDBAPY), which is not compatible with multithreading.
• Data groups that use multithreading cannot specify a recovery window, which is part of the MIMIX
CDP feature.
• Data groups that use multithreading cannot have database apply user exit programs.
Configuration requirements are listed in the conversion section.
Status reporting
The status of the multithreaded job is included in the DB Target column on the Data Groups portlet and
on the Work with Data Groups (WRKDG) display.
Detailed status for the multithreaded job can be found in the following locations:
• From VSP, the DB Statistics tab of the Data Group Details and Activities portlet displays the status of
the Multithreaded apply job in the Supporting processes section. Possible statuses for the
multithreaded job are Action Required, Stopped, Stopped due to a virtual switch in progress, and
Active.
• From the native user interface, the multithreaded job (DBAPYT) status appears in the following
views of Display Data Group Status (DSPDGSTS). Possible status values for the job are: -I (inactive,
red), -V (ended due to virtual switch in progress, yellow), -A (active, blue), and -U (unknown, white).
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 26
– Merged view: The process DBAPYT appears in the statuses listed horizontally in the Target
Statistics section.
– DB views 1 and 2: The process DBAPYT appears to the left of the Held for other reasons field in
the top half of the display.
– DB view 3: The process DBAPYT appears in the Target system row, above the Database Apply
section.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 27
groups. While this command is running, do not switch the application groups associated with the
resource groups, and do not change the data group definitions or their selection rules (entries).
After a conversion, the data groups must be started specifying to clear pending entries
(CLRPND(*YES)). If the Start Application Group (STRAG) command is used to start replication, it will
automatically perform the clear pending start of the data groups.
Running the audits after conversion is recommended if you specify to discard open commits.
Check multithreading Validates that the data groups in the selected resource groups meet the
requirements: requirements for conversion to multithreaded database apply processing and
• Check Multithreading reports problems that would prevent conversion. Replication processes can be
Eligibility dialog active when this option is used. The following requirements are checked:
• Menu option: 31=Check • The data groups cannot have a database apply user exit program.
for conversion • Each data group must specify Use User Journal for Cooperative processing
• CVTRG type (COOPJRN(*USRJRN)), values other than None (*NONE) for the
OPTION(*CHECK) Node 1 and Node 2 journal definition fields (JRNDFN1, JRNDFN2) a
numeric value for the database Apply sessions (NBRDBAPY), and *NONE for
the Process and Duration elements of Recovery window (RCYWIN). (VSP
interfaces do not support fields for configuring a recovery window.)
• Each data group and all of its library and file selection rules (data group object
and file entries) must specify or resolve to Positional (*POSITION) for the
Replication type field of the File and tracking options (FEOPT).
• Stopped (inactive) data groups are checked for the presence of open commits
and whether they were ended controlled.
• File activities (file entries) must have statuses of *ACTIVE or *HLDIGN.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 28
Table 1. Operation and available interfaces with descriptions
Convert to multithreading: Converts eligible data groups within the specified resource groups from existing
• Convert Resource configuration values to values required for multithreaded database apply
Groups to Multithreaded processing. Resource groups whose data groups are already configured for
dialog multithreading are not processed. Prior to converting, this option verifies the same
• Menu option: requirements as performed by *CHECK, with one difference. The check for open
32=Convert to commit activity is performed on all associated data groups and no open commit
multithreading activity can exist unless you explicitly select the checkbox for Discard open
commit cycles (in VSP) or specify *DISCARD for Open commit handling
• CVTRG
(OPNCMT) in native user interfaces.
OPTION(*CVTTOMT)
After requirements are successfully checked, the conversion process changes the
following in the configuration:
• Journal definitions associated with the data groups are set to *YES for Target
journal inspection (TGTJRNINSP).
• Data group definitions within the resource groups are changed as follows:
- The database Apply sessions (NBRDBAPY) is set to either Low, Medium,
or High (*THDLOW, *THDMED, or *THDHIGH). The value is determined
by evaluating the current configuration and the installed product.
- Journal on target (JRNTGT) is set to Yes (*YES).
- File and tracking options (FEOPT) have these fields set as follows: Lock
member during apply is set to Do Not Lock (*NONE), Apply sessions is set
to Threads are in use (*ALL), Disable and process triggers during apply is
set to Yes. The FEOPT parameter uses separate elements for these
trigger options with values of *YES.
- Database Apply processing options (DBAPYPRC) have these fields set as
follows: Commit mode is set to Immediate (*IMMED), Manage constraints
on target (not displayed in VSP) is set to *YES.
• All configured data group library and file selection rules (object and file entries)
for the converted data groups are changed to set these File and tracking
options (FEOPT):
- Replication type is set to Default (Positional), (*DGDFT)
- Lock member during apply is set to Default (Do Not Lock), (*DGDFT)
- Apply session is set to Any in library selection rules (*DGDFT within object
entries) and to ‘B’ in file selection rules (file entries).
- Disable and process triggers during apply is set to Yes (*DGDFT). The
FEOPT parameter uses separate elements for these trigger options.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 29
Table 1. Operation and available interfaces with descriptions
Convert from Converts data groups configured for multithreading that are within the specified
multithreading: resource groups to configuration values compatible with single-threaded database
• Convert Resource apply processing. Resource groups whose data groups are already configured for
Groups to Single- single-threaded database apply processing are not processed.
threaded dialog When converting from multithreading to single-threading, you can optionally
• Menu option: specify to use configuration data saved by an earlier conversion of the resource
33=Convert to single- group to multithreading. Replication processes must be ended by a controlled
threaded end, and no open commit activity can exist unless you explicitly select the Discard
• CVTRG open commits checkbox in the dialog or specify *DISCARD for Open commit
OPTION(*CVTFRMMT) handling (OPNCMT) on the command. If saved configuration does not exist or is
not used, the affected data group definitions will be changed to these values,
which are compatible with single-threaded database apply processing:
• Database Apply sessions (NBRDBAPY) is set to 6.
• Target constraint management (element of DBAPYPRC) is set to *NO. (This is
not shown in VSP.)
• Lock member during apply (element of FEOPT) is set to Exclusive, Allow Read
(*EXCLRD).
Change expiration on Changes the expiration date for a saved configuration associated with a specified
saved configuration: resource group. The resource group must have had configuration saved by a
• Change Configuration previous conversion to multithreading. If saved configuration does not exist for the
Expiration dialog resource group, a diagnostic message is issued. Replication processes can be
• Menu active when this option is used.
option:34=Change
saved config retention
• CVTRG
OPTION(*CHGEXP)
(MXHA-23668)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 30
Automation impacts
• The CRTDGDFN command will fail in environments that do not have application groups with error
message LVE3507. To continue to create data groups not associated with a resource group
(standalone), the automation must be modified to specify non-default values for the command.
• If you have application groups and invoke the CRTDGDFN command using default values, the
resulting data group uses multithreading. You may need to modify automation to add the
RSCGRPAG parameter and provide values for it and the resource group (DTARSCGRP). If
automation attempts to create the data group within an existing resource group, the command will
fail if its values are not compatible with the database apply processing values used by the other data
groups in that resource group.
• Automation that invokes the CRTDGDFN command and expects the resulting data group to have
specific values for these parameters needs to be checked and possibly updated because of changes
to the parameter defaults, behavior changes, or restrictions when multithreaded database apply
processing is configured: DTARSCGRP, COOPJRN, NBRDBAPY, the FEOPT element Lock
member during apply, and the DBAPYPRC elements Commit mode and Target constraint
management.
• Automation that invokes the CHGDGDFN command may need to be modified. In multithreaded data
groups, parameters that are now required values for multithreading can no longer be changed with
this command.
• Automation that invokes any of the following commands for data group object entries and file entries
may need to be checked. Non-default values specified for file entry options (FEOPT parameter) may
not be able to be specified in environments configured for multithreaded database apply processing:
ADDDGOBJE, CHGDGOBJE, CPYDGOBJE, LODDGOBJE, ADDDGFE, CHGDGFE, CPYDGFE,
LODDGFE.
(MXHA-23349)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 31
Application Groups tab of the Replication Configuration window. Values that are not valid for a
standalone data group cannot be selected from this dialog.
From the native user interface, the Create Data Group Definition (CRTDGDFN) command requires that
an application group exist before the command can be used with default values. Under certain
conditions, the command may also create the resource group to which the data group belongs. To
support this behavior, CRTDGDFN has the following changes:
• Data resource group entry (DTARSCGRP).
– The default value changed from *DFT to *DGDFN. The value *DGDFN uses the resource group
whose name matches the first part (name) of the three-part name of the data group definition.
– When a specified name or the value *DGDFN resolves to the name of a resource group that does
not exist and the value specified for RSCGRPAG is an existing application group name or the
value *DFT, which resolves to the name of the only configured application group, the resource
group will be created in that application group.
• Appl. group for resource group (RSCGRPAG).
This new parameter identifies the application group that controls the resource group in which the
data group participates. You can specify a name or use the default value, *DFT, which determines
the application group associated with the resource group identified by the DTARSCGRP parameter
as follows:
– When that resource group exists, *DFT resolves to the name of the application group to which the
resource group is configured, as follows:
– When that resource group does not exist and there is only one application group, *DFT resolves
to the application group name and creates the resource group using the first part of the data
group name.
– When that resource group does not exist and there are multiple application groups in the
configuration, the command will fail.
– When *NONE is specified for the resource group, the value *DFT is ignored and the resulting data
group is not associated with a resource group or application group. Only single-threaded data
groups can be created without a resource group.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 32
• Use multithreading for database apply (on General tab).
This field determines whether the resource group and its associated data groups will use
multithreaded or single-threaded database apply processing. The value Yes is the default and
results in multithreading. The value No results in single-threaded processing.
• Multithreading level (on General tab).
Available when Yes is selected in the field above, this field displays the default thread level allowed
for the installed product. Additional thread levels may be available based on the product license.
Possible values are Low, Medium, and High. See the descriptions of *THDLOW, *THDMED, and
*THDHIGH, below, for more detail. In existing resource groups, this field allows you to change the
threading level if allowed by the product license.
• Apply sessions field (on Database tab).
When multithreading is selected, this field displays “Threads are in use” and cannot be changed.
When multithreading is not selected, this field allows you to specify the number of single-threaded
apply sessions that run in parallel.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 33
The previous default value (*DFT) is no longer available in user interfaces but if used in automation, it
resolves to *SYSJRN if the data group type is *OBJONLY. Otherwise, it resolves to *USRJRN.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 34
• The only scenario where the target constraint management value can be changed is for a data group
that existed before the upgrade to MIMIX version 9.0 and specified the value *YES. After upgrading,
the value can be changed to *NO, but attempts to change it back to *YES require a conversion to
multithreading.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 35
Copy data group (CPYDGDFN) changes
When using the Copy Data Group definition (CPYDGDFN) command to copy a data group, the
command verifies that the database apply processing configuration (either single-threaded or
multithreaded) is the same between the copied from data group (FROMDGDFN) and the resulting data
group (TODGDFN). The command will not allow you to copy a data group whose settings are not
compatible with those necessary for the resource group (TORSCGRP) in which the copied to data group
will exist.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 36
Object Correction Activity window improvements
The Object Correction Activity window is the recommended location to see the current status of
automatic recovery and to perform any manual recovery that is required. Here, an object’s recovery
status reflects a complete view of its detected replication and auditing problems.
Includes automatic recoveries from audits: The Object Correction Activity window now includes
recovery activities associated with differences found by audits as well as those associated with
replication and other processes. Recovery actions for audits that have been submitted to the replication
manager are included on this window. This is in addition to any failed or handled recoveries that were
performed by the audit job itself.
Manual recovery actions added: For recovery actions that failed, the Object Correction Activity
window added actions that you can use to manually recover the affected object. This provides consistent
recovery regardless of which process initially identified the problem. Also, you can use toolbar actions
for manual recovery of multiple objects that require the same recovery action.
Failed recoveries reported to data group details: Regardless of whether an automatic recovery was
initiated by replication or auditing, if the recovery fails, it is also reported on the corresponding replication
activity tab in the Data Group Details and Activities portlet.
For additional information, see “Audit recovery improvements” on page 44.
Recovery status added for file, IFS tracking, and object tracking activities
(entries)
You can now view the most severe status of any recoveries for an object identified in replication
activities (entries) for files, journaled IFS objects, and journaled data areas and data queues in either
user interface.
From VSP, the Correction Activity Recoveries column is added to the following tabs on the Data Group
Details and Activities portlet and related windows accessible from the tabs:
• File Activity tab, Related Files window
• IFS Tracking Activity tab, Related IFS Objects window
• Object Tracking Activity tab
From the native user interface, the Recovery Status (RCYSTS) parameter added to the following
commands allows you to subset the resulting display by a specific recovery status or by all recovery
statuses other than *NONE. The Recovery Status column is added in a new view on the resulting
display. Use F10 (Rcy sts view) to access the view:
• WRKDGFE command, Work with DG File Entries display
• WRKDGIFSTE command, Work with DG IFS Trk. Entries display
• WRKDGOBJTE command, Work with DG Obj. Trk. Entries display
These possible values and how they correlate between interfaces:
- Not recovered. Manual *FAILED - The most severe status of any recoveries indicates that the
recovery is required. recovery has failed.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 37
Table 2. Recovery statuses for VSP and native user interface
- Waiting for recovery. For *CAPTURING -The most severe status of any recoveries indicates that the
details, use the Object Details recovery is capturing information on the source system.
action. *WAITING - The most severe status of any recoveries indicates that the
recovery is waiting to be processed. Either the database apply process is
ended or has a backlog while a virtual switch is in progress.
- New Recovery. For details, *NEW - The most severe status of any recoveries indicates that the recovery
use the Object Details action. is new and processing has not yet started.
- (dash) - NA *NONE - No recoveries exist for the object or all known recoveries for the
object have been successfully handled.
You can view more information about a recovery using the Object Details action from the Object
Correction Activity window in VSP.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 38
Multi-object selection available for manual corrections
One or more of the following toolbar actions have been added to several interfaces within VSP to allow
you to select multiple objects for manual recovery: Start Journaling, Release, Synchronize. Affected
interfaces include:
• Object Correction Activity window
• Objects Changed on Target window
• Virtual Switch Activity window
• File Activity, IFS Tracking, and Object Tracking tabs of the Data Group Details and Activities portlet
• Related Files window
(MXHA-26088)
Auditing Enhancements
This version of MIMIX includes numerous changes associated with auditing best practices, recovery
performance, and reporting of issues. These enhancements and additional changes are described
below:
• Changes to auditing best practices
• Adding the ability to perform recoveries for the File Member Record Counts (#MBRRCDCNT) audit
• Separating policy controls for enabling and disabling auditing from options that select comparison
options to perform
• Improving audit performance by changes to scheduling and recovery processing
• Audits with differences are no longer considered action required
• Integrating audit recoveries into the Object Correction Activity window and other interfaces, and
reporting unresolved audit recoveries as replication errors
• Auditing now supports spooled files. See “Audit and compare support for spooled files” on page 54
for details.
• Auditing restrictions for permissions and masks (RCAC) and temporal tables have been removed.
See.“Auditing supported for RCAC permission and masks” on page 48 and “Auditing supported for
temporal tables” on page 48.
Terminology changes
The terms used to refer to the method by which an audit selects objects for auditing is clarified:
• All-objects audits is now used to refer to audit runs that select all objects within the name space
defined by the data group’s selection rules (configuration entries). Previously, all-objects audits were
called “scheduled audits” even though they can also be manually invoked, and prioritized audits also
have scheduling criteria.
• Prioritized objects audits refers to audit runs that select replicated objects to audit based on their
priority classification and the eligibility frequency of the priority category. Prioritized objects audits are
allowed to start automatically within a range of time.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 39
These changes affect numerous portal application and native user interfaces, and are most apparent in
those used for scheduling audits: the Audits tab on the Schedule Summary window, Audit Schedule
portlet, and Audit Schedule Details dialog. Keywords and values on the Set MIMIX Schedules
(SETMMXSCD) command are not affected but prompt text and help are updated.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 40
Scheduling changes: Within the priority-based audit start range, MIMIX now submits a mixture of
audits on each priority check instead of submitting the same audit for all data groups at the same time.
MIMIX will not start another request for the same audit and data group while the previous request is still
running. On each cycle to start audits within the start time range, the next priority-based audit start
request for that audit type is performed for the next eligible data group. This change applies to new and
upgraded installations.
Existing customers will see the following changes in new data groups created after installing MIMIX
version 9.0:
• Prioritized-object auditing is enabled for #MBRRCDCNT audits. The value None (*NONE) is set for
the Unchanged objects frequency and the Audited with no differences frequency.
• Prioritized-object auditing is disabled for #FILDTA audits. The value None (*NONE) is set for the
Unchanged objects frequency and the Audited with no differences frequency so that these
categories are set as expected if you choose to enable prioritized-object auditing.
Object selection changes for priority-based objects: The #FILDTA and #MBRRCDCNT audits no
longer need to evaluate configured selection rules (data group entries) when determining which objects
are eligible for selection. This improves the performance of these audits.
Audit level (AUDLVL) policy replaced by Audit runs and Audit Options
New policies in MIMIX 9.0 separate the controls for enabling and disabling the ability to perform audits
from controls that determine the comparison option (previously called audit level) to use for the subset of
audits that support multiple comparison options. These changes make both capabilities more intuitive
and allow you to easily disable auditing while retaining audit comparison options. In previous versions,
both capabilities were performed using the Audit level (AUDLVL) policy, which is no longer available. The
Instance Policies dialog, Data Group Policies dialog, Audits tab of the Policy Summary window and the
Set MIMIX Policies (SETMMXPCY) command are affected. You will also see related changes in other
locations that previously included audit level information.
The new policies can be set for the installation and overridden by a data group level value.
Audit runs (AUDRUN) - This policy determines whether audits are allowed to run when requested and
applies to all auditing requests regardless of whether they are invoked by the automatic scheduler or
manually by user action. Valid values are:
• Enable (*ENABLED) - Auditing requests are allowed to run when requested or scheduled. This is the
shipped default.
• Disable (*DISABLED) - Auditing requests are prevented from running. Use this value when you need
to disable auditing completely, such as when performing a backup from a target system, during
system or network maintenance, or on a test data group.
Audit Options policies: Three audits support multiple comparison options: File Data (#FILDTA),
Directories (#IFSATR), and Folders (#DLOATR). Each of the three audits now have separate audit
options policies for setting the comparison option to use. These policies support the ability to specify
different values to use for all-objects audit requests and for prioritized and differences audit requests. All-
objects audit requests select all objects within the data group’s configured name space for the class of
objects checked by the audit. Prioritized and differences audit requests select objects based on their
object-auditing priority or previous auditing differences. By design, each run of a prioritized or differences
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 41
audit may select a unique subset of the objects replicated by the data group that are within the class of
objects checked by that audit.
• File data percentage to audit (FILDTAOPT) - Specifies the percentage of file records to compare in
file members of each physical file (PF) that is selected for auditing by a run of the File Data
(#FILDTA) audit. A value less than 100 percent reduces the quantity of records checked for the files
selected.
Valid values for both elements are:
– 100 - One hundred percent of the records for each file member are compared for the selected
files. This is the most extensive check available and is the shipped default value.
– 20 - Twenty percent of the records for each file member are compared for the selected files. (It will
take 5 audit runs to check all data that existed at the time the first audit started.)
– 5 - Five percent of the records for each file member are compared for the selected files. (It will
take 20 audit runs to check all data that existed at the time the first audit started.)
• Directory audits (IFSAUDOPT) - Specifies whether to compare attributes and data, or only
attributes, of the objects selected for auditing by a run of the Directory (#IFSATR) audit.
Valid values for both elements are:
– Attributes and Data (*ALL) - Attributes and data within the selected IFS objects are compared.
This is the most extensive check available and is the shipped default value.
– Attributes (*ATTRONLY) - Only attributes of the selected IFS objects are compared.
• Folder audits (DLOAUDOPT) - Specifies whether to compare attributes and data, or only attributes,
of the DLO objects selected for auditing by a run of the Folder (#DLOATR) audit.
– Attributes and Data (*ALL) - Attributes and data within the selected DLO objects are compared.
This is the most extensive check available and is the shipped default value.
– Attributes (*ATTRONLY) - Only attributes of the selected DLO objects are compared.
Note: Best practice is to enable auditing and to allow audits that support options to perform the most
extensive checking available in all of the audit option policies. If you use a lower value for an
auditing option policy, consider its effect on how often you need to guarantee data integrity
between source and target systems. Regardless of the option you use for daily operations,
Syncsort strongly recommends running audits using the most extensive checking option before
performing a planned switch to the backup system and before switching back to the production
system to ensure that 100 percent of the data is valid on the target system.
A value that performs less than the most extensive check is a compromise that may reduce the audit’s
effect on system resources, performance, or amount of time needed to run while increasing exposure to
data integrity issues. When choosing values, consider how much data there is to compare, how
frequently the data changes, how long the audit runs, how often you run the audit, and how often you
need to be certain that data is synchronized between source and target systems.
Policy mapping for upgrades: When upgrading to MIMIX 9.0, the AUDLVL policy settings are mapped
to new policies as follows:
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 42
Table 3. Policy mappings for upgrades
Audit level Audit runs File data per- Directory audits Folder audits
(AUDLVL) (AUDRUN) centage to audit (IFSAUDOPT) (DLOAUDOPT)
(FILDTAOPT)
On the Audits tab of the Policy Summary window, the Audit Runs column replaces the Audit level
column, and columns are added for the auditing options. Also, the Audits tab now has two Data Group
columns, located on the left and right sides, so that the data group name can be seen when scrolling
right to access actions.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 43
options policy, the current settings of that policy are used.
• Yes, run and check attributes and all data (*ALL).
The specified audit will run regardless of whether auditing is enabled or disabled (AUDRUN policy)
and with values that override any applicable auditing options policies. If a specified audit has an
applicable auditing option policy, the audit will run using the highest possible auditing option value
regardless of the policy setting.
Note: Only the File Data (#FILDTA), Directory (#IFSATR), and Folder (#DLOATR) audits have
auditing options policies (FILDTAOPT, IFSAUDOPT, and DLOAUDOPT, respectively).
• Yes, run object existence-only check (not recommended).
If the specified audit is Libraries (#OBJATR), Folders (#DLOATR), File Attributes (#FILATR), File
Member Attributes (#FILATRMBR), or Directories (#IFSATR), the audit will be run regardless of
whether auditing is enabled or disabled, and the audit will only perform an existence check on the
selected objects. No other audits will be run. An existence check is useful to confirm that objects
within the configured name space for an audit exist on both systems.
Note: This value is available only from the dialogs in VSP. An existence check does not compare
object data or attributes and does not ensure data integrity between systems. An existence
check should not be used to determine switch readiness and does not determine auditing
compliance. This choice is not supported for the File Selection Rules (#DGFE), File Data
(#FILDTA), and File Member Record Counts (#MBRRCDCNT) audits.
On the Work with Audits display (WRKAUD), the new option, 39=Run rule with override, will start the
selected audit immediately regardless of whether auditing is enabled (AUDRUN policy) and overrides
any applicable auditing options (FILDTAOPT, IFSAUDOPT, or DLOAUDOPT policies) to perform the
highest possible level of checking. This is equivalent to specifying the following command: RUNRULE
OVRAUDPCY(*ALL).
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 44
manual recovery actions to synchronize the object the same as if its error had been originally detected
by replication processes.
Also, if the remaining audit recoveries handled by the audit job fail, they are tracked internally and will
also appear in the Object Correction Activity window and the other interfaces identified above.
In the Work with Audited Objects display and Work with Audited Object History displays (WRKAUDOBJ
and WRKAUDOBJH commands), the audited status category *RCVD is updated to include objects with
a summary status of *RCYSBM as well as *RECOVERED.
Note: If the data group is inactive or exceeds its database apply threshold when the audit runs and the
value of the Action for running audits policy (RUNAUDIT) in effect is Compare Recover
(*CMPRPR), any recovery actions for differences detected by the audit are queued for the
replication manager and will be processed after the data group starts or the backlog that
exceeded the threshold is resolved. If the Automatic audit recovery policy (AUDRCY) is disabled,
any objects with differences are reported as failed recoveries on the appropriate interfaces.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 45
Other auditing-related changes
The following additional changes associated with auditing are included.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 46
• In the Conditions that end switch field in the Switch Data Group dialog, the value Audit Differences
has been renamed to Audit Not Run.
• Conditions that end switch (ENDSWT) parameter on the Switch Data Group (SWTDTG) command,
the value *AUDDIFF is replaced by *AUDNOTRUN. If the value *AUDDIFF is used in automation, it
is processed as *AUDNOTRUN.
The check performed by this step program or value will end the procedure or switch data group request
if any audits exist with statuses that require action or attention. This includes audit statuses indicating
that the audit did not run due to policy, failed, or was ended.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 47
– File entry recovery count (failed) (FERCYFAIL)
– IFS tracking entry recovery count (failed) (ITERCYFAIL)
– Object tracking entry recovery count (failed) (OTERCYFAIL)
These are also added as parameters to the Retrieve Data Group Status 2 (RTVDGSTS2)
command, which is new. MIMIX 9.0 updates to the Retrieve Data Group Status (RTVDGSTS)
command have caused it to each its maximum number of parameters.
• The MXDGACTE outfile (WRKDGACTE command) added these two new possible values for the U-
MX subtype (UMXSUBTYPE) field: RD (Audit recovery disabled), RQ (Audit recovery failed).
(MXHA-23106, MXHA-23109, MXHA-23111)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 48
Changes to switch processing will now check for the existence of replicated jobs on the current source
system as a condition that ends switch processing. In application group environments, the switch
procedures also wait for you to either submit or remove any remaining previously replicated jobs on the
new source system following the switch and sets an indicator if any replicated jobs still exist for the
affected data groups.
Note: MIMIX does not replicate jobs submitted before the configuration changes are made available to
replication processes. Replication must be stopped and started to make configuration changes
available. When the data group is started with replication of jobs configured, MIMIX checks the
QAUDLVL system value for the presence of either *JOBDTA or *JOBBAS and, if necessary, will
change QAUDLVL to add *JOBBAS to ensure that journal entries for job level auditing can be
placed in the system journal. This may result in more journal entries in the system (QAUDJRN)
journal. MIMIX does not update the QAUDLVL system value to remove the *JOBDTA or
*JOBBAS value if you later change configuration to no longer replicate jobs.
Replication of job queues requires a switchable data group. Therefore, this capability is not supported for
MIMIX DR.
Action Required:
To use this capability, eligible environments must modify the configured selection rules (data group
object entries) to allow replication of jobs associated with replicated *JOBQ objects. Replication
processes must be stopped and started to make the changes available to replication.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 49
MXWAITRJB - Wait for replicated jobs to be submitted/removed. This step waits for all replicated
jobs on the new source node to be manually submitted or removed.
This step is added to and enabled in the SWTPLAN and SWTUNPLAN procedures with a before
action of *WAIT and an error action of *MSGW. This step runs after the switch operation occurs.
MXSETRJBI - Set replicated jobs indicator. This step sets an indicator if there are remaining
replicated jobs on the new source node for the data group. The data group cannot be switched again
until all remaining replicated jobs are submitted or removed.
This step is added to and enabled in the SWTPLAN and SWTUNPLAN procedures with an error
action of *QUIT. This step runs after the switch operation occurs and cannot be disabled or removed.
Optionally, you can also use any of the following new steps which are added as disabled steps in the
SWTPLAN and SWTUNPLAN procedures. User action is required to enable these steps. When
enabled, the following steps have a before action of *WAIT and an error action of *MSGW.
MXSBMRJB - Submits all replicated jobs. This step submits all replicated jobs on the new source
node, allowing the jobs to run.
MXSBMRJBN - Submits all new (not started) replicated jobs. This step submits all replicated jobs
that had not yet been started on their original source node to run on the new source node.
MXRMVRJB - Removes all replicated jobs. This step removes all replicated jobs from the new
source node to prevent the jobs from being submitted to run.
On the Switch Data Group dialog and SWTDG command, the new value, Replicated Jobs (*REPJOB), is
added to the Conditions that end switch field (ENDSWT parameter). This value will cause the switch
process to end if any replicated jobs exist on the source system. In a planned switch, this is also
included with the value Default (*DFT).
In VSP, this condition is indicated by the Attention icon next to the name of the affected application
group, resource group, or data group in the following interfaces: Replication Environment portlet,
Application Group Resource Groups portlet, Data Groups portlet, Data Group Details and Activities
portlet, Application Group Details window, Data Group Details window, RPO/RTO Analysis window, Start
Application Group dialog, Start Resource Group dialog, and Start Data Group dialog.
In the native user interface, the name of the data group is highlighted in yellow on the Work with Data
Groups (WRKDG) display.
The Replicated job indicator field (REPJOBIND) is added to the RTVDGSTS2 command and to the
MXDGSTS outfile for WRKDG command, with possible values of *YES and *NO.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 50
• Work with Data Groups display
When the local system is the current target system, the display lists the jobs that have been replicated to
this system. During normal replication activity, the listed jobs are automatically removed when MIMIX
processes the journal entry for the job completion from the source system. Following a switch, the listed
jobs need to be either submitted or removed before the data group can be is switched another time.
When the local system is the current source system, the display lists the jobs that were replicated to the
system prior to the last switch, when this system was the target. These jobs did not complete on the
originating system before the time of the last switch. Evaluate whether these jobs should be removed or
submitted to run on the local system before switching the data group.
You can use options to display or print details for the specified job, submit the job to run on the local
system, or remove the job from the list. Some actions may not be appropriate for the current role (source
or target) of the local system.
• Use option 4=Remove to remove a replicated job from the list. When you remove a job, a
confirmation display appears. Once a job is removed, it cannot be submitted. The RMVREPJOB
command can also be used to remove a job.
• Use option 5=Display to display the command string that was submitted on the original system.
• Use option 7=Submit to submit the command string of the replicated job on the local system. You
have the option to add or replace parameters (other than the Command to run (CMD) parameter)
before the command string is submitted. Any differences of Submit Job (SBMJOB) command
defaults or name-mapping of objects between systems will not be reflected in the shown command
string. If any differences are important when submitting the command string, edit the command string
accordingly. After the job is submitted on the local system, it is removed from the list of replicated
jobs. The SBMREPJOB command can also be used to submit a job.
The Work with Replicated Jobs (WRKREPJOB) command also supports the ability to output results from
the local system to the MXREPJOB outfile.
MIMIX also supports retrieving information about replicated jobs on the local system with the Retrieve
Replicated Jobs (RTVREPJOB) command.
The Open MIMIX List (OPNMMXLST) command added the value *REPJOB to the Type of request
(TYPE) parameter to support opening a list of all replicated jobs from the local system. This is for use
with RTVREPJOB command.
(MXHA-23617)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 51
Configuration
The MIMIX portal application in VSP includes changes to selection rule dialogs to support enhanced
spooled file configuration. Selection rules now provide the ability to identify specific spooled files for
replication. The selection rules allow you to specify *SPLF for the Type field and new subfields for the
Replicate spooled files field allow you to fine-tune spooled file selection by the Spooled file name, Job
name, and Job user subfields. Each uses a default value of All, or can specify a name or generic name.
Changes to the Include Libraries and Objects, Copy Selection Rule, Selection Rule Details, and Exclude
Libraries and Objects dialogs provide significantly more flexibility to include or exclude spooled files and
include the following:
• When adding or changing a rule that includes objects in replication and Yes is specified for Replicate
spooled files, the Type field can use the default All or specify *OUTQ or *SPLF, and the Spooled file
name, Job name, and Job user fields can use the default All or be qualified with a name or generic
name or number.
• When adding a rule to exclude objects from replication and the Type field is *SPLF, the Spooled file
name, Job name, and Job User fields can use the default value All or be qualified with a name or
generic name or number.
• When copying a rule, the spooled file fields will be displayed, enabled, or disabled depending on the
Type value selected. Refer to the corresponding help topic in VSP for more information.
The Move Selection Rule dialog supports *SPLF for the Type field and displays the values for the
Replicate spooled files field and subfields when the Type is All, *OUTQ, or *SPLF.
In the Data Protection Reports, the protection status of a library is impacted by explicitly included or
excluded spooled files.
In the native user interface, data group object entries now provide the ability to identify specific spooled
files for replication. The object entry commands now include the value *SPLF for the Object type
(OBJTYPE) parameter and a new parameter, Spooled file criteria (SPLF) that has three elements
(Spooled file name, Job name, and Job user). Each uses a default value of *ALL or can specify a name
or generic name.
Changes to the Add Data Group Object Entry (ADDDGOBJE) and Change Data Group Object Entry
(CHGDGOBJE) commands that provide significantly more flexibility to include or exclude spooled files
include the following:
• When adding or changing an entry to include objects in replication (PRCTYPE(*INCLUDE)) and
*YES is specified for the Replicate spooled files (REPSPLF), the Object type (OBJTYPE) parameter
can use the default *ALL or specify *OUTQ or *SPLF, and the Spooled file criteria (SPLF) parameter
can use the default value *ALL or be qualified with a name or generic name or number.
• When adding or changing an entry to exclude objects from replication (PRCTYPE(*EXCLUDE)) and
*YES is specified for Replicate spooled files (REPSPLF), the only valid Object type (OBJTYPE) is
*SPLF, and the Spooled file criteria (SPLF) can use the default value *ALL or be qualified with a
name or generic name or number.
Other configuration commands that support *SPLF for the OBJTYPE parameter and can specify values
for the Spooled file criteria parameter include:
• Display DG Object Entry (DSPDGOBJE)
• Load Data Group Object Entry (LODDGOBJE)
• Remove DG Object Entry (RMVDGOBJE)
• Retrieve Data Group Object Entry (RTVDGOBJE)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 52
The Work with DG Object Entries display added a new view for spooled file information and includes a
column for spooled file criteria (Splf Crit). The possible values include:
• Specific - Additional criteria exists. Use option 5=Display or 6=Print to view the additional selection
criteria for spooled files.
• *ALL - All spooled files for output queues matching this data group object entry are replicated.
• - (dash) - No spooled files are replicated based on this data group object entry.
The Retrieve Data Group Object Entry (RTVDGOBJE) command also has three new CL variable
parameters for the three-part spooled file criteria: spooled file name, spooled file job name, and spooled
file job user (RTNSPLFNAME, RTNSPLFJOB, and RTNSPLFUSR) to qualify the entry retrieved by the
request.
The Copy Data Group Object Entry (CPYDGOBJE) command supports *SPLF for the OBJTYPE
parameter and includes two parameters, From spooled file criteria (FROMSPLF) and To spooled file
criteria (TOSPLF). These parameters support *ALL, generic names, and fully specified names. The
default value for each element in FROMSPLF is *ALL. The default value for each element in TOSPLF is
*FROMSPLF, which means that the values specified for the corresponding spooled file name element of
the FROMSPLF parameter are used.
Fields added to the WRKDGOBJE outfile, MXDGOBJE, include Spooled file name (SPLFNAME),
Spooled file job name (SPLFJOB), and Spooled file job user (SPLFUSR).
Replication
Object replication will now replicate the specified spooled file or its attributes that are identified by
configured selection rules (object entries).
The MIMIX portal application in VSP includes changes to dialogs, windows, and tabs to support
enhanced spooled file replication.
You can now see your replicated spooled files in the Replicated Objects window and portlet, which now
support spooled file objects (Type field displays *SPLF). The Source Object field displays spooled file
information in the format outputq(spooledfilename/spooledfilenumber). The Target Object field displays
the spooled information in library/outputq(spooledfilename/spooledfilenumber) format. Hover the cursor
over the spooled file to display the spooled file name, number, and three part job name (splname/splnum
- jobnum/jobuser/jobname).
• Object Details dialog - When the Type is *SPLF, the source and target spooled file information is
displayed, including Source spooled file and Target spooled file fields with their respective Number,
Output queue, and Job fields.
• Compare Object Details from Nodes window - Spooled file comparisons display *SPLF in the Type
field and Spooled file name, Number, and Job (jobnum/jobuser/jobname format) information.
– Compare Object Details from Nodes, General tab - Spooled files with differences between nodes
that are significant to replication display the icon. For replicated attributes that are different
between nodes, the icon is displayed. For attributes that are different between nodes but that
are not replicated, the icon is displayed. Flyover text provides information and suggested
recovery action.
You can see current spooled file activity on the Object Activity tab in the Data Group Details and
Activities portlet on the Data Groups page. The Object Activity Details window displays spooled file
information in the Spooled file and Type fields.
In the native user interface, you can see the current and completed activity for Spooled files on the Work
with DG Activity Entries (WRKDGACTE) and the Work with Data Group Activity (WRKDGACT) displays.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 53
Both support *SPLF for the OBJTYPE parameter. On WRKDGACT, you can specify values for the
Spooled file criteria (SPLF) parameter and on WRKDGACTE, you can specify the Spooled file name
(SPLF) and Spooled file job (SPLFJOB) parameters. The spooled file information view of the Work with
DG Activity Entries display (accessed using F11) added a new Job Name column to the existing SPLF
Information columns (Name, Number), which displays the name of the job that produced the spooled file
number. The full spooled file name, number, and three-part job name is shown on the 5=Display panel
and 6=Print details output.
Interface changes:
The MIMIX portal application in VSP includes changes that support spooled file replication
enhancements in the following:
• Libraries Audit Results (#OBJATR) window - Displays the spooled file information in the Object fields
for both Source and Target.
– Details row action - Displays spooled file information in the resulting Libraries Audit Results
Details window.
– Libraries Audit Results Details window - Supports the Compare Details and Synchronize row
actions for spooled files.
• Compare Details row action - Displays spooled file information in the resulting Compare Object
Details from Nodes window.
• Audited Objects window - Displays audited spooled files in the list of objects in the upper pane of the
window.
• Object Audit History window - When the Type field is *SPLF, the Object on node fields display the
spooled file information. The Job field is displayed directly below them.
In the native user interface, the Work with Audited Objects (WRKAUDOBJ) and Work with Audited Obj.
History (WRKAUDOBJH) commands include spooled file support for any of the Object, Object Type,
Spooled file criteria, Spooled file name and Spooled file job parameters (and/or elements). On the
resulting Work with Audited Objects and Work with Audited Obj. History displays, spooled files are
displayed in the format NAME/NUMBER JOBNBR/JOBUSER/JOBNAME.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 54
Fields added to MXAUDOBJ, the outfile for both WRKAUDOBJ and WRKAUDOBJH, include Spooled
file name (SPLFNAME), Spooled file number (SPLFNBR), Spooled file job name (SPLFJOB), Spooled
file job user (SPLFJOBUSR), and Spooled file job number (SPLFJOBNBR).
The Compare object attributes (CMPOBJA) command includes the following changes:
• The Object type element of the Object (OBJ) parameter now includes the *SPLF value.
• The Object parameter added two new qualified elements (Spooled file name, Spooled file job) and
specify *ALL as the default. The Spooled file name can be qualified by its number, and the Spooled
file job can be qualified by the job user and job number. Generic names and *NONE may also be
specified.
• The Attributes to compare (CMPATR) and Attributes to omit (OMITATR) parameters now support the
Spooled file attributes indicator (*SPLATRIND).
Fields added to CMPOBJA outfile, MXCMPOBJA, include Spooled file name (SPLFNAME), Spooled file
number (SPLFNBR), Spooled file job name (SPLFJOB), Spooled file job user (SPLFJOBUSR), and
Spooled file job number (SPLFJOBNBR).
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 55
In the native user interface, spooled files with errors are included in the Object errors column on the
Work with Data Groups (WRKDG) display. You can see the current and completed activity and issues
that require resolution for Spooled files on the Work with DG Activity Entries (WRKDGACTE) display.
You can then take corrective action using commands that also include spooled file support for any of the
Object, Object Type, Spooled file criteria, Spooled file name, and Spooled file job parameters (and/or
elements). They include the following:
• Synchronize object (SYNCOBJ)
• Synchronize DG Activity Entry (SYNCDGACTE)
• Remove DG Activity Entries (RMVDGACTE)
• Retry DG Activity Entries (RTYDGACTE)
• Cancel DG Activity Entry (CNLDGACTE)
Other changes
The DSPDGSPLF command and resulting Display DG Spooled Files display have been removed.
(MXHA-22052)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 56
In VSP, when a selection rule is configured to ignore attributes of replicated objects, the Ignored
Differences column identifies the ignored attributes on the appropriate tab of the Selection Rules window
or on the File Selection Rules window
In VSP, dialogs for adding (Include) or changing (Details) selection rules have a new Differences to
ignore during auditing field that you can use to identify which attributes of replicated objects will be
ignored by auditing. In the native user interface, the equivalent is the Attributes to ignore (IGNATR)
parameter on the Add and Change commands for data group entries. Audits will ignore differences
detected for the specified attributes and any differences will be maintained by the default behavior of
MIMIX synchronization requests. Possible values include:
• None (*NONE) - No attributes are ignored.
• Attributes Only (*ATRONLY) - All non-data attributes are ignored.
• Data Only (*DATAONLY) - All data attributes are ignored. This includes *DATACRC and *VALUE
attributes. Data within physical files cannot be ignored.
• Attributes and Data (*ATRDATA) - All attributes (data and non-data attributes) are ignored.
• Select Differences - You can also select one or more attributes from a list of available attributes for
the type of selection rule (data group entry).
Retrieve commands and outfiles associated with data group entries have added parameters or fields to
identify the number of ignored attributes (NBRIGNATR) and the Ignored attributes (IGNATR). This
affects the following commands and outfiles: RTVDGOBJE, MXDGOBJE outfile (WRKDGOBJE),
RTVDGDLOE, MXDGDLOE outfile (WRKDGDLOE), MXDGIFSE outfile (WRKDGIFSE), RTVDGFE,
and MXDGFE outfile (WRKDGFE).
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 57
MXAUDHST outfile (for WRKAUD and WRKAUDHST commands), *IGNATR is added as a possible
value for the Audit Status (AUDSTS) field.
Object audit status category of *IGN: When an object listed on the Work with Audited Objects
(WRKAUDOBJ) display has this value, the status category is Ignored attribute, and the object has one or
more attributes with an audit status of *IN or *IC.
Audit compare status (difference indicator) values of *IN and *IC: The compare phase of audits and
the output from commands that compare attributes can report the following new difference values for
attributes when the configuration allows replicated attributes to be ignored by auditing:
*IC - The values are not equal based on the MIMIX configuration settings, but attribute differences
are configured to be ignored.
*IN - Indicates differences were detected, but were ignored according to MIMIX ignored attribute
configuration settings.
The values *IC and *IN can appear as a compare status in the Audited Objects window and the Object
Audit History window, the Work with Audited Obj. History display (WRKAUDOBJH command), and as a
difference indicator value in Audit Results and Audit Result Details windows for audits that compare
attributes. These values also can appear as values in the Compare Status (CMPSTS) field in the
MXAUDOBJ outfile (WRKAUDOBJ command, and in the Difference Indicator (DIFIND) field in outfiles
for the CMPOBJA, CMPDLOA, CMPIFSA, and CMPFILA commands.
(MXHA-12049)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 58
and the Object only on target action policy to indicate that the policy was disabled by MIMIX due to
an unplanned switch of an application group. These new values also identify the previous value.
Interfaces for starting data groups also have the ability to enable the recovery polices that were
disabled by the SWTUNPLAN procedure. For details, see “Policy changes due to an unplanned
switch of an application group” on page 62.
Be aware that starting replication and enabling policies before journal analysis has been performed risks
data loss for any unprocessed entries that you still need to recover manually.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 59
specified object. The user journal entries for the identified object that have not been processed by
MIMIX are listed on the resulting Work with Jrn. Entries for Jrn. Analysis display.
Note: From the Work with Jrn. Entries for Jrn. Analysis display, you can use options to display or
print details about the selected user journal entry for the object that has not been processed
by MIMIX.
• 46=Acknowledge - Allows you to acknowledge that you have analyzed journal entries for the
specified object.
• 47=Mark as new - Allows you to mark a previously acknowledged object as new to indicate that
additional analysis of journal entries needs to be performed for the specified object.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 60
• Start all data groups in an application group with a request to clear the journal analysis indicator.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 61
Notes:
• Be aware that if an unplanned switch was performed on a data group that is not part of an application
group, the journal analysis indicator is never set. Accessing journal analysis information via F9 on
the Journal Analysis Summary display is not tracked and information about any unprocessed entries
is lost when the data group is started following an unplanned switch.
• The checkbox does not appear in the Start Data Group dialog and the CLRJRNANZ parameter on
the STRDG command has no effect on a data group that is not part of an application group.
• When using the Start Application Group dialog or STRAG command for application groups with three
or more nodes, data groups that do not include the node that was the primary node before the switch
can be started without specifying to clear journal analysis information. The application group will
have a replication status of Attention (*ATTN).
Table 4. New values for polices disabled by MIMIX via the SWTUNPLAN procedure
Important Note: When these policies display these values, the unplanned switch procedure disabled the
policies to prevent interference with your ability to perform journal analysis and address unprocessed
transactions in the user journal on the system that was the source before the unplanned switch was performed.
When you have completed those activities, you must change these policies at the data group level to return to
normal operations.
Object only on target action • Disabled by MIMIX (previously Delete Object) - *MXDBSDEL
(OBJONTGT) The action to be taken on objects that exist only on the target is disabled
because an unplanned switch was performed. The unplanned switch
process disabled this policy, which was previously set to Delete Object
(*DELETE).
• Disabled by MIMIX (previously Use Instance Value) - *MXDSBINS
The action to be taken on objects that exist only on the target is disabled
because an unplanned switch was performed. The unplanned switch
process disabled this policy, which was previously set to Use Instance
Value (*INST).
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 62
Start DG request returns policies disabled by unplanned switch to previous values
In order to return to normal operations after you have completed journal analysis and any manual
recovery activities for a data group that was part of an unplanned switch of an application group, you
must change the data-group-level policies disabled by the unplanned switch procedure back to their
previous values. Changes to the Start Data Group dialog and STRDG command allow you to perform
this task as part of starting replication processes for a data group.
The Enable recovery policies checkbox (ENBRCYPCY parameter) specifies whether to enable policies
associated with recovery behavior for the specified data group that were disabled by an unplanned
switch. The affected policies are those listed in Table 4. (The checkbox appears in the dialog when the
selection includes one or more data groups that were part of an unplanned switch and have one or more
policies that were disabled by MIMIX.) Possible values are:
• When unchecked (*NO), the policies disabled by the unplanned switch will remain disabled for the
data group. This is the shipped default. This value is appropriate when there is a business need to
start replication even though all of the unprocessed entries from the system that was the source prior
to the unplanned switch have not been recovered. Before starting with disabled recoveries, ensure
that you have printed a list of the objects and unprocessed journal entry information that you will
need to finish manually recovering the entries. Allowing replication processes to start with disabled
recoveries prevents automatic recovery actions from potentially causing data loss for the
unprocessed entries that you still need to recover manually.
• When checked (*YES), the recovery policies for the data group will be enabled to their previous
values. This is appropriate when you are ready to return to normal operations.
(MXHA-22918)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 63
The command can be added to a delete journal receiver exit program (QIBM_QJO_DLT_JRNRCV) or
inserted into any customer program that deletes receivers or checks if receivers are ready for deletion.
(MXHA-27056)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 64
include the object send, object retrieve, container send, status receive, object receive, container receive,
status send, database reader, database send/receive, and object apply jobs.
The ability to configure the job restart time (RSTARTTIME parameter) has been removed from system
definition and data group definition commands (such as CRTSYSDFN, CHGSYSDFN, CRTDGDFN, and
CHGDGDFN) and from dialogs for creating and changing resource groups and data groups. The
removal of the automatic restart also means that configuration changes no longer become effective due
to the automatic restart. The end restart required to make changes effective now must always be
initiated by you.
After upgrading an existing installation that specified a time for RSTARTTIME system definitions or data
group definitions, the specified time will be ignored and cannot be changed. The new behavior is
equivalent to the previous restart time value of *NONE. Previously, RSTARTTIME defaulted to 000000
(midnight).
IMPORTANT! Be aware that if you previously relied on the “nightly restart” to make configuration
changes effective, you must now ensure that you end and restart replication processes to make
configuration changes effective. If you previously used a restart time of *NONE and have automation
that performs the job cleanup functions that were not performed as a result, you should evaluate
automation to determine whether it may interfere with how automatic MIMIX job cleanup is now
performed.
(MXHA-22351)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 65
In the native user interface, changes are included in the:
• Work with Data Groups display (WRKDG command) - Target Obj column status for the data group
now provides a summation status of the object apply and status send processes.
• Data Group Status display (DSPDGSTS command) - Detailed object views (object View 1 and View
2) accessed from this display now have a new Status Send field that shows the status of the status
send process on the target system for the data group. From this display, use F7 (Object view) to
access View 1 and View 2 (use F11 to toggle between the object views).
• Start and End Data Group (STRDG/ENDDG commands) - Status send (STSSND) is checked
separately for starting or ending a data group and is included when any of the following values are
specified for the Start processes (STRDG) or Processes (ENDDG) fields: All, All target, All Object,
and Object target.
• Previously, STSSND was started or ended as part of the OBJSND processing. For STRDG, if
OBJSND was up and STSSND was down, then STSSND would not be restarted. For ENDDG, if
OBJSND was down and STSSND was up, then STSSND would not be ended.
• MXDGSTS outfile (WRKDG command) - New field STSSNDSTS is added to automate the collection
of status for the object STSSND process.
(MXHA-23598)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 66
Java Runtime requirements
• System i: Java 8 JRE (64 bit) is the preferred version. However, Java 7.1 JRE or Java 7 JRE are
supported and can be used instead.
• Windows or AIX: Java 8 JRE (included with the install wizards).
(STR-5347)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 67
• The Apply history log spaces element of the Database apply processing (DBAPYPRC) parameter of
the data group definitions is changed to the value 0 by the upgrade process. The value 0 will always
be used regardless of what is specified on the CRTDGDFN or CHGDGDFN commands, or on Data
Group or Resource Group dialogs.
• The Synchronize Data Group (SYNCDG) command is removed.
• The UPS monitor is no longer supported and UPSMON is no longer a restricted name for other
configuration objects. The following commands have been removed: UPDUPSAVL, TSTPWRCHG,
CHGUPSAVL, CHGUPSCFG, CHGUPSMSG, DSPUPSSTS.
• The MIMIX for SAP feature no longer supports 3-tier transparent switching. The CHKR3PRF, and
INZR3SWT commands and the R3SWTCMN *SVRVPGM have been removed.
• The Electronic Customer Support function within License Manager is no longer supported. The
CHGLKVSPT, DLTLKVSPT, ENDLKVSPT, and STRLKVSPT commands have been removed.
• The support tools provided by the CHKMMX and CLRMMXDTA commands are removed.
When checking automation, also check for the following:
• Check automation that specifies the PROTOCOL parameter for the values *SNA or *OPTI in these
commands: CRTTFRDFN, CHGTFRDFN, RMVTFRDFN, WRKTFRDFN CPYACTF, RUNCMD, and
RUNCMDS.
• The following commands for data group data area entries have been removed: ADDDGDAE,
CHGDGDAE, CPYDGDAE, CPYDGDAE, DSPDGDAE, DSPDGDAEX, LODDGDAE, RMVDGDAE,
RTVDGDAE, RTVDGDAE, VFYDGDAE, WRKDGDAE. Also, the DTAARAITV parameter is no
longer available on commands for data group definitions or the DPYDGCFG, OPNMMXLST, and
RTVDGSTS commands.
• The following commands for file alias naming have been removed: ADDDGFEALS, CHGDGFEALS,
DSPDGFEALS, DSPDGFEALX, RMVDGFEALS, WRKDGFEALS.
• The following switch definition commands no longer support TYPE values of *SM517A or *SM9001:
CRTSWTDFN, CHGSWTDFN.
(MXHA-10781)
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 68
MXHA-26476 The object status and recovery text in the Object Correction Activity window are now
correct when an object with a failed recovery is in the process of having a different
exception recovered.
MXHA-26627 Status for disabled data groups is no longer included in rollup status for application
groups displayed in the Replication Environment portlet on the VSP Summary page.
MXHA-26647 VSP has updated flyover text for the notification icon in the Nodes portlet to instruct users
to go to the Notifications portlet for more details.
MXHA-26916 When a metered usage MIMIX instance is removed from VSP, it is now also removed
from the Metered Usage portal application.
MXHA-26965 The adjusted time stamps for the received and applied WRKDGTSP timestamp fields will
no longer show large (999:99) fields when system to system timestamp difference is too
large.
MXHA-27197 Journal Manager status no longer shows *RCYASP or *INACTASP when the available
spaces on the system ASP exceeds 2,147,483 MB (about 2TB).
VSP
VSP version 3.2.01.00 is included with MIMIX service pack 9.0.01.00.
9.0.01.00 (included in 9.0.02.00) © 2017, 2018 Vision Solutions, Inc. All rights reserved. 69