Documente Academic
Documente Profesional
Documente Cultură
Action required
This document can be used for either or both of the following:
• Install or upgrade the product, its portal application, and Vision Solutions Portal (VSP) on its native
operating system.
• Install the product's portal application and VSP on a system running a supported Windows operating
system.
The following topics provide instructions associated with installing this service pack. Any changes which
may require you to take additional action are listed below with links to additional descriptions.
“Before installing the service pack” on page 3 - required for all installation methods.
“Installing the service pack on IBM Power Systems” on page 5 - it is recommended you use the
MIMIX Installation Wizard.
“After installing the service pack instructions” on page 6 - required for all installation methods.
“Installing VSP 2.0 & Portal Application on Windows” on page 8 - instructions for using the Vision
Solutions Portal (VSP) 2.0 & Portal Application Installation Wizard for Windows®.
Important changes
You should be aware of the information in the following topics before you install this service pack:
Enhancements
New IBM Flex System Event portlet in VSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
To see a list of fixes included with this service pack, see “Fixes included in service pack 7.1.03.00” on
page 9.
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
7.1.03.00. To see highlights and additional fixes for a superseded service pack, click on the link.
7.1.02.00 - Highlights and fixes
MIMIX® is a registered trademarks of Vision Solutions, Inc. MIMIX Availability, iOptimize, MIMIX Enterprise, MIMIX Professional,
and MIMIX Global are trademarks of Vision Solutions, Inc. AS/400, DB2, eServer, i5/OS, IBM, iSeries, OS/400, Power, System
i, IBM i, and WebSphere are trademarks of International Business Machines Corporation. All other trademarks are the property
of their respective owners.
7.1.03.00 © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 1
Read This First
MIMIX® is a registered trademarks of Vision Solutions, Inc. MIMIX Availability, iOptimize, MIMIX Enterprise, MIMIX Professional,
and MIMIX Global are trademarks of Vision Solutions, Inc. AS/400, DB2, eServer, i5/OS, IBM, iSeries, OS/400, Power, System
i, IBM i, and WebSphere are trademarks of International Business Machines Corporation. All other trademarks are the property
of their respective owners.
7.1.03.00 © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 2
Installation Instructions
Before installing the service pack
The following describes changes that may require modifications to your MIMIX environment before you
install the service pack.
Action required:
• Do not replicate libraries LAKEVIEW, MIMIXQGPL, VSI001LIB, any MIMIX installation libraries
including MXIWIZ*, any MIMIX data libraries, libraries in which iOptimize is installed, and the
following IFS directories: ‘/visionsolutions/http/vsisvr’ and ‘/LakeviewTech’.
• Do not replicate the MIMIXOWN or LAKEVIEW user profiles.
• If iOptimize™ or MIMIX Director is installed in the same system or partition as MIMIX, do not
replicate the following:
• Do not place user created objects or programs in the LAKEVIEW, MIMIXQGPL or VSI001LIB
libraries or in the IFS location /visionsolutions/http/vsisvr. This includes any programs created as part
of your MIMIX Model Switch Framework. If you place such objects or programs in these libraries,
they will be deleted during the installation process. Objects that are in these libraries must be placed
in a different library before installing this service pack. Job descriptions, such as the job description
used by the MIMIX Port job, can continue to be placed into the MIMIXQGPL library.
• QTEMP cannot be in the system portion of the library list.
• It is strongly recommended that you apply any IBM PTFs (or their supersedes) associated with IBM i
releases as they pertain to your environment. Refer to the Recommended OS Fixes link on the
Customer Care page in Support Central for a list of required and recommended IBM PTFs.
• If you run other products that use the same journals on the same systems as MIMIX, such as
Replicate1™ or iOptimize™, there may be considerations for journal receiver management. For
details, see "Interaction with other products that manage receivers" in the MIMIX Administrator
Reference book.
• Review Technical Alerts which can be found at Support Central in the Notifications section of the
Customer Care page. From Support Central, choose My Product >Customer Care > Notifications.
7.1.03.00 © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 3
Before installing the service pack
Special instructions are listed below by service pack. Perform any actions necessary for
your environment before installing. It is necessary to perform any special instructions
provided for 7.1.03.00, as well as any listed special instructions for service packs that are
not yet installed. (You can skip special instructions for service packs already installed on
your system.)
The following procedure ends MIMIX products for an installation. If you have multiple
installations of MIMIX, the first installation updated will update License Manager. Because
of this, you should end MIMIX operations on all installations before installing.
1. Use the following command on a management system to end all system managers,
journal managers, collector services, application groups, data groups, active audits
and recoveries, the master monitor, and all MIMIX monitors:
installation-library/ENDMMX ENDOPT(*CNTRLD)
Note: Based 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.
2. Repeat Step 1 for each additional MIMIX installation.
3. If you are not using MIMIX to schedule audits, ensure that your scheduling
mechanism does not start audits during the installation process.
4. If you currently use MIMIX Availability Manager, use the following command on any
system which hosts an instance of MIMIX Availability Manager:
LAKEVIEW/ENDMMXAM INST(name)
where name is the name of the instance. The Vision Solutions supplied default
instance name is MIMIXAM.
5. Use the following command on all systems to end the MIMIX subsystem:
ENDSBS SBS(MIMIXSBS)OPTION(*IMMED)
7.1.03.00 © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 4
Installation Instructions
Installing the service pack on IBM Power Systems
MIMIX Installation Wizard recommended: Vision Solutions strongly recommends that you use the
MIMIX Installation Wizard to install version 7.1 products. The MIMIX Installation Wizard provides a
simple method for downloading, distributing, and installing products on a single IBM Power™ System or
on multiple Power Systems simultaneously.
In addition, the MIMIX Installation Wizard also does the following:
• Easily and automatically obtains and applies license keys via Vision AutoValidate™.
• Automatically installs the Vision Solutions Portal (VSP) server and MIMIX portal application on the
selected IBM Power™ Systems, or upgrades them if needed. If you skip the VSP shutdown step,
updates to the server are not installed and MIMIX portal application updates are not deployed to the
server. The server provides support for browser-based user interfaces to Vision Solutions products
which provide portal applications.
The MIMIX Installation Wizard does not support installing into a library located on an independent ASP.
For more information about requirements for using MIMIX Installation Wizard, see Support Central.
Support Central provides an executable (.exe) file for each product download, which contains the MIMIX
Installation Wizard as well as the actual product update.
If you cannot use the MIMIX Installation Wizard, the following books provide information for using other
means to install:
• The Using License Manager book describes requirements and best practices that must be in place
before installing products in your environment. This book also includes the secondary install
procedures and supporting information for installing via the 5250 emulator.
• The Getting Started with Vision Solutions Portal book describes requirements and installation options
for Vision Solutions Portal. This book also describes how to manually make the MIMIX portal
application known to the server and describes best practices for configuration.
7.1.03.00 © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 5
Installation Instructions
After installing the service pack instructions
The following topics describe changes in this service pack that may require modifications to your MIMIX
environment after you install.
Special instructions are listed below by service pack. Perform any actions necessary for your
environment after installing. It is necessary to perform any special instructions provided for 7.1.03.00, as
well as any listed special instructions for service packs that are not yet installed. (You can skip special
instructions for service packs already installed on your system.)
2.0.03.00
Add IBM Flex System Event Log portlet to a custom page in VSP . . . . . . . . . . . . . .10
7.1.01.00
Perform a controlled end and change data group to use immediate commit mode. .12
Change definition for preexisting data groups to use shared object send process . .13
Update automation that uses MXSYSDFN outfile if needed . . . . . . . . . . . . . . . . . . .17
Change policies to allow priority auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Change journal definitions for systems on which target inspection will run . . . . . . . .26
Run DPYDGCFG for data groups before starting replication processes . . . . . . . . . .26
Evaluate programs for use of journal entry time stamp . . . . . . . . . . . . . . . . . . . . . . .33
Change FEOPT parameter for lock member during apply. . . . . . . . . . . . . . . . . . . . .35
Optionally install VSP on a Windows system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
7.1.03.00
Synchronize replicated *VLDL objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
\
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. 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(system) PORT(nnnnn)
where system is the host name or address and nnnnn is the port number or alias defined in the
transfer definition for the system on which you are running this command
3. 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 MXAUDITSCD job, and the MXCOMMD job:
installation-library/STRMMX
4. Repeat Step 2 and Step 3 for each additional MIMIX installation.
5. As needed, make any known configuration changes on any installation that was upgraded.
6. Perform this step if you will be using Vision Solutions Portal from a system running IBM i:
a. Do one of the following:
• If you installed using the MIMIX Installation wizard and accepted defaults, skip to Step b.
• If you installed using 5250 emulator processes and Vision Solutions Portal is not at a level
which supports the latest portal application, download the MIMIX Installation wizard from
Support Central and use that wizard to upgrade the Vision Solutions Portal server.
7.1.03.00 © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 6
Installation Instructions
• If you installed using 5250 emulator processes and Vision Solutions Portal is presently at a level
compatible with the latest portal applications, make the portal application known to the server,
enter the command: VSI001LIB/ADDVSIAPP APP(MIMIX).
• If you want Vision Solutions Portal but it is not currently installed, you can use the MIMIX
Installation wizard and choose the option to install the portal application.
b. If you started Vision Solutions Portal from the MIMIX System i Installation Wizard, skip this step.
Otherwise, start the server using the following command:
VSI001LIB/STRVSISVR
The default port is 8410. Each instance of the server uses three consecutive ports. If you cannot
use this port, go to the Getting Started with Vision Solutions Portal book for instructions on
changing the port number and other information.
c. Enter the following URL in your web browser and Log In:
http://server:port
where:
• server is the IP address or host name where Vision Solutions Portal is installed
• port is the port number (the default is 8410)
7. As needed, update your Runbook. For more information about the Runbook, contact your certified
MIMIX consultant.
Note: The Runbook Capture Tool is not supported in V7.
8. If you use MIMIX Availability Manager™ to monitor earlier versions of MIMIX, specify the name of the
server instance to start in the following command:
LAKEVIEW/STRMMXAM INST(name)
The default instance name is MIMIXAM.
Note: MIMIX Availability Manager™ does not support monitoring of MIMIX V7 or later. It can only
be used to monitor installations running earlier versions of MIMIX.
9. If you use the Vision Solutions plug-in for the IBM® Systems Director Navigator for i5/OS® you must
end and restart the HTTP Administration Server. This plug-in is associated with MIMIX Availability
Manager. Check with your i5/OS administrator before doing the following:
a. End the server using the following command:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
b. Confirm that all jobs in the QHTTPSVR subsystem have ended by using the command:
WRKACTJOB SBS(QHTTPSVR)
c. Start the server using the following command:
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
d. Ensure that the ADMIN2 job in the QHTTPSVR subsystem is started before attempting to access
the Vision Solutions plug-in. Use the command:
WRKACTJOB SBS(QHTTPSVR)
10. Check your MIMIX status using the information provided in the Using MIMIX book.
11. If you plan to use Vision Solutions Portal from a system running the Windows operating system, use
the instructions in “Installing VSP 2.0 & Portal Application on Windows” on page 8.
7.1.03.00 © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 7
Installing on Windows
Installing VSP 2.0 & Portal Application on Windows
These instructions are for the Vision Solutions Portal (VSP) 2.0 & Portal Application Installation
Wizard for Windows®. This wizard automatically installs the VSP server (version 2) and the portal
application for the selected Vision Solutions® product onto a system running a supported release of the
Windows® operating system. Support Central provides an executable (.exe) file which contains this
wizard.
Note: This wizard does not install the associated Vision Solutions 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.
7.1.03.00 © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 8
Highlights Version 7.1 Service Pack 7.1.03.00
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.
7.1.03.00 © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 9
SP7.1.03.00 Highlights
MXHA-10703 In environments that replicate journaled IFS objects, newly created *STMF objects
now have their target journaling status set to *YES and the *STMF data is
replicated.
MXHA-10774 MIMIX upgrade from V7.0 to V7.1 no longer fails with MCH3601 messages when
converting IFS exception entries.
MXHA-10804 SYNCIFS and #IFSATR no longer fail with LVE0101 due to incorrect IFS path
length in installations with more than 2 nodes.
MXHA-10820 Target Journal Inspection no longer reports F-OP (File Opened) and F-CL (File
Closed) journal entries as unauthorized entries on Target.
MXHA-10823 MXREPMGR job improved to use less CPU when processing object and DLO
exceptions.
MXHA-10832 Target Journal Inspection no longer reports valid entries as "unauthorized on
target" after switching a DG of TYPE(*DB).
MXHA-10864 Shared audit reader now does additional checks before determining if a data
group should be added to its processing.
MXHA-10866 Improved performance of MXIFCMGR which no longer writes unneeded history
records for disabled data groups.
MXHA-10872 Database apply no longer fails with MCH3601 when the record in OMIFSXEP is
not found.
7.1.03.00 © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 10
Highlights Version 7.1 Service Pack 7.1.02.00
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.
7.1.02.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 11
Highlights Version 7.1 Service Pack 7.1.01.00
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.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 12
Previous service packs (included)
• In Vision Solutions Portal, this can be seen in the DB Statistics tab in the Data Group
Details and Activities portlet. When immediate commit mode is used and there is an open
commit cycle, the last sequence number processed should be near the last sequence
number applied. Also, the count of open commit entries will be lower in immediate commit
mode than in delayed mode.
Changes to starting data groups - The Start Data Group (STRDG) command and the
corresponding dialog in Vision Solutions Portal are changed to prevent starting a data group
following a change to the specified commit mode when a data group has open commit cycles.
Message LVEC0B3 is issued to indicate that open commit cycles must be resolved before a start
request can make the configuration change effective.
Additional changes - The following additional changes were made to provide programmatic
support for commit mode:
• Added the DBCMTMODE parameter to the Retrieve DG Definition 2 (RTVDGDFN2)
command.
• Added the DBCMTMODE field to the MXDGDFN outfile for the WRKDGDFN command.
Action required:
No action is necessary if you want to continue using delayed commit mode, which preserves
previous behavior of MIMIX. If you want to use immediate commit mode, do the following after
upgrading to or installing version 7.1:
1. Perform a controlled end of the data group that you want to change.
2. When the controlled end completes, verify that there are no open commit cycles using
DSPDGSTS DGDFN(name system1 system2) VIEW(*DBVIEW1).
3. Change the data group definition to specify *IMMED for the Commit mode element of the
Database apply processing (DBAPYPRC).
4. Start the data group.
(MXHA-62)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 13
Previous service packs (included)
• *SHARED This default value results in the data group using the shared default object
send job on the source system. All data groups with the same source system that specify
*SHARED use the same job for the object send process. The prefix MX$ is used in the job
name, unless those characters are already used for a data group short name. In that case,
the third character of the prefix is changed to create a unique prefix.
• *DGDFN The object send job is unique to the data group and uses the data group short
name for the job name prefix. The value *DGDFN preserves the behavior of previous
releases.
• name When you specify a three-character prefix, this data group and any other data
groups on the same source system that specify the same prefix will share the object send
job with this prefix.
Note: A shared object send job can process journal entries for objects within SYSBAS or within
only one independent ASP. In environments with independent ASPs, each system within
the set of data groups sharing the same object send job must be identified consistently
within those data groups in the appropriate ASP group parameter (ASPGRP1 or
ASPGRP2). This is required regardless of whether a system is currently the source or
target for the data groups.
Status - Detailed status for a data group now indicates when the send process is shared.
• In a 5250 emulator, this is identified below the object send process field on the merged
view and right of the field on object views 1 and 2 of the Data Group Status display (option
8 from Work with Data Groups display or DSPDGSTS command). The value *SHARED
indicates the default shared job for the system is used. A three-character prefix indicates
the job is shared with a subset of data groups using the same prefix.
• In the Vision Solutions Portal, this is identified in the Send and receive row within the
Processes section of the Object Statistics tab of the Data Group Details and Activities
portlet. The name "Instance" is appended to the process name when the default shared
job for the system is used. When the data group uses a job shared with a subset of data
groups, its three-character prefix is appended to the process name. These values are also
included in flyover help for the process in this portlet as well as for the Source column in
the Data Groups portlet.
A prefix is not displayed in either interface when the data group has a dedicated object send job.
Start and end behavior - When starting data groups that share an object send process, the first
data group to start will start the shared job at that data group’s starting point in the system
journal. As additional data groups start, each recognizes that the shared object send job is active.
The object send job determines whether the starting point for that data group is earlier or later
than the sequence number being read. If the data group’s starting point is later, replication will
begin when the shared job reaches the data group's starting point. If the data group’s starting
point is earlier, the shared job completes its current block of entries, then returns to the earliest
point for any of the data groups being started. The shared job reads the earlier entries and routes
the transactions to the data group being started. When the shared job reaches the last entry it
read at the time of the STRDG request, it resumes routing transactions to all active data groups
using the shared job.
If the starting data group has a significant object send backlog, the other data groups sharing the
job will not receive transactions to replicate while the backlog for the starting data group is being
addressed. Therefore, when a backlog exists, it is recommended that you change the data group
configuration to use a dedicated job, start the data group, and allow it to catch up to the current
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 14
Previous service packs (included)
location of the shared job. Then end the data group, change its configuration to use the desired
shared job, and restart the data group.
When ending data groups that use a shared object send job, the job is ended by the last data
group to end.
Job restart behavior - When a object send job is shared by multiple data groups, the data group
with the earliest configured job restart time (RSTARTTIME) in the data group definition is used to
restart the shared job.
Additional changes - The configuration and status changes are also reflected in the following:
• Added OBJSNDPFX parameter to the Retrieve DG Definition 2 (RTVDGDFN2) and
Retrieve Data Group Status (RTVDGSTS) commands
• Added OBJSNDPFX field to the outfiles for WRKDGDFN command (MXDGDFN) and
WRKDG command (MXDGSTS) command
Action required:
If you want to use a shared object send process for data groups that existed before the upgrade
to version 7.1, do the following:
1. Ensure that data group does not have a significant backlog for its object send process.
2. End the data group.
3. Change the data group definition (CHGDGDFN) to specify either *SHARED or a prefix in the
Object send prefix element of the Object processing (OBJPRC) parameter.
4. Start the data group.
Determining the optimal number of data groups that can share an object send process in your
environment may require adding small numbers of data groups into a shared object send
process and monitoring the impact on performance and throughput. Factors include the number
of data groups acted on together, the type of data replicated by the sharing data groups, and the
existence or lack of persistent threshold conditions for the object send process. (MXHA-72,
MXHA-8737)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 15
Previous service packs (included)
For each type of replication, three key pieces of information are displayed:
• Arrivals - the calculated number of transactions that have been arriving in journals on
source nodes within the selected time. This is the potential amount of work to perform.
The actual amount performed may have been filtered to smaller amounts.
• Backlog - the sum of replication backlogs within the selected time. This indicates whether
MIMIX processes kept pace with arrivals. For database replication, the chart and data tabs
include the RJ backlog. The RJ backlog represents the transactions on the source that
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 16
Previous service packs (included)
have not been transferred to the target. This is your exposure to data loss in the event of
an outage on the source.
• Process status - the worst of the tracked replication statuses within the selected time. This
indicates whether replication processes were stopped or replication problems may have
been the cause of a backlog.
Initially, the portlet displays data for all data groups in the instance over the past two hours,
calculated in five minute intervals. You can filter the data to specific node pairs or data groups, as
well as change the length of time for the displayed data, which also changes the length of the
intervals. Data displayed in the portlet is retrieved when the Analysis page is accessed or
refreshed. Changing filtering criteria refreshes your view of the data but does not retrieve new
data. (MXHA-1395, MXHA-8416)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 17
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 18
Previous service packs (included)
Priority-based auditing
Version 7.1 introduces the concept of prioritized object auditing. Prioritized auditing can reduce
the impact of auditing on resources and performance that some customers experienced with
previous auditing capability (now called scheduled auditing). Prioritized object auditing benefits
customers who cannot complete IFS audits, cannot audit every day, or do not audit at all
because of time or resource issues.
The biggest difference between prioritized object auditing and scheduled auditing is how objects
are selected to be audited. The other significant difference is when each type of audit is allowed
to run.
• In prioritized object auditing, an audit run selects objects according to their internally
assigned priority category and an auditing frequency assigned to the category. The result
may be a subset of the objects replicated by the data group. Each time a prioritized audit
runs, its subset of objects selected to check may be unique. MIMIX automatically runs a
prioritized audit periodically within its specified time range every day. It may run
approximately once per hour or more often during its time range.
• In scheduled object auditing, an audit run selects all objects that are configured for the data
group and within the class of objects checked by the audit. MIMIX automatically runs the
audit according to its specified scheduling criteria. Each time a scheduled audit runs, all
eligible objects are selected.
A manually invoked audit is always a scheduled audit. The #DGFE audit is not eligible for
prioritized auditing because it checks configuration data, not objects. When both scheduled and
priority audits are allowed for the same rule and data group, MIMIX may not start a prioritized
audit if the scheduled audit will start in the near future.
MIMIX determines the auditing priority of each replicated object based on its most recent change,
most recent audit, and the frequency specified for auditing priority categories. At any time, every
replicated object falls within one of several predetermined categories. Objects that had
differences in their most recent audit have the highest priority. Objects in this category are always
selected, even if the differences were automatically resolved. Also, within all object selection
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 19
Previous service packs (included)
categories for prioritized object auditing, the #FILDTA audit always selects all members of a file
for which auditing is less than 100 percent complete. Policies determine how often replicated
objects within other priority categories are eligible to be selected for auditing.
Initially, the objects selected by a prioritized audit may be nearly the same as those selected by a
scheduled audit. However, over time the number of objects selected by a prioritized audit
stabilizes to a subset of those selected by a scheduled audit.
Results of prioritized audit runs are reflected within auditing user interfaces. When MIMIX is used
from the Vision Solutions Portal (VSP) you can use additional functions, such as filtering the
Replicated Objects portlet to the objects that had an audit status of not equal in their last audit.
Policies determine whether an audit for a data group runs by priority, by schedule, or both.
Policies also determine when prioritized audits are allowed to run every day and when scheduled
audits run. New data groups default to using both prioritized and scheduled auditing. Data groups
that existed before upgrading to MIMIX version 7.1 continue to use their existing values for
scheduled audits.
Action required: Customers who upgraded to version 7.1 and want to use prioritized object
auditing must change policies. Each unique audit for a data group must be set separately. This is
most easily done using the Policy Summary window in Vision Solutions Portal. It can also be
accomplished using the Audit Schedule portlet or the Set MIMIX Policies (SETMMXPCY)
command to specify values for the Priority audit (PTYAUD) parameter.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 20
Previous service packs (included)
Shipped default values for the Priority audit policy for new data groups.
Field Default value Additional values Description
Allowed to start (VSP) 3 a.m to 8 a.m. Any time (*ANY), *NONE Specifies a time range, in 24-hour
Start after, Start until format during which prioritized
(5250) audits are allowed to start. De-
selecting the Prioritized object
auditing checkbox in VSP or the
value *NONE prevents prioritized
auditing.
New objects Daily Hourly A new object is one that has not
been audited since it was
created.
Changed objects Daily Weekly, Monthly A changed object is one that has
been modified since the last time
it was audited.
Unchanged objects Weekly Daily, Monthly, None An unchanged object is one that
has not been modified since the
last time it was audited.
Audited with no Monthly Daily, Weekly, None An object with no differences is
differences one that has not been modified
since the last time it was audited
and has been successfully
audited with no changes on at
least three consecutive audit
runs. Objects remain in this
category until a change occurs.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 21
Previous service packs (included)
Also, the Audit Schedules tab on the Policy Summary window now includes these columns for
prioritized auditing: Start After, Start Until, New Objects, Changed Objects, Unchanged Objects,
Audited with no Differences. Preferences allow control over which of these fields are displayed.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 22
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 23
Previous service packs (included)
Related changes
The Audit Details portlet now shows additional fields when the selected audit's status is Not run
or Waiting to run. The Objects to audit field indicates whether all objects will be selected by the
audit (a scheduled audit) or prioritized objects will be selected by the audit (a prioritized audit).
The Run on node field identifies where the audit will run. Also, the Last attempt field is no longer
displayed when the audit status is Not run.
Commands that compare attributes now have a new report type available. The Compare File
Attributes (CMPFILA), Compare Object Attributes (CMPOBJA), Compare IFS Attributes
(CMPIFSA), and Compare DLO Attributes (CMPDLOA) commands now support the value
*OPTIMIZED for the Report type (RPTTYPE) parameter. The value *OPTIMIZED creates a
combined report that indicates at an object level when the objects are equal. For objects that are
not equal, the individual attributes that are not equal are included in the report. Audits now use
this report type to return results.
Outfile changes:
The Objects selected (OBJSEL) field has been added to the MXAUDHST outfile for the Work
with Audit History (WRKAUDHST) command to identify how objects were selected for the audit
run.
The System 1 object type (SYS1OBJTYP) and System 2 object type (SYS2OBJTYP) fields have
been added to the following outfiles to facilitate tracking audits for each object:
• MXCMPIFSA outfile for the Compare IFS Attributes (CMPIFSA) command
• MXCMPDLOA outfile for the Compare DLO Attributes (CMPDLOA) command
(MXHA-5930, MXHA-8134, MXHA-9431)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 24
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 25
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 26
Previous service packs (included)
Note:
– Target journal inspection does not occur for the journals identified in the following journal
definitions: JRNMMX, MXCFGJRN, and those that identify the remote journal used in RJ
configurations (whose names typically end with @R).
– In environments that perform bi-directional replication, target journal inspection does not
report a target object as changed by user when that object is also replicated by a different
data group using that system as its source.
– The first time that a target journal inspection process is started, it begins at the first entry
of the currently attached journal receiver regardless of where replication from the journal is
started. This can result in false target journal inspection notifications being reported.
For new installations, shipped default values for journal definitions and data group definitions
allow MIMIX to automatically perform target journal inspection.
Action Required: Journal definitions that existed before upgrading to MIMIX version 7.1 do not
automatically allow target journal inspection. Customers who have upgraded and want to use
target journal inspection need to change journal definitions for systems on which target
inspection will run. In switchable environments, change all journal definitions associated with the
data group that can become a target journal to allow inspection to start on the opposite system
following a switch. Also, data group definitions that perform user journal replication may need to
be changed to allow journaling on the target system. For examples and detailed instructions, see
topic "Performing target journal inspection" in the MIMIX Administrator Reference book.
Viewing results
Each target journal inspection process sends a notification once per day per user that changed
objects on the target system. The notifications appear in the Notifications portlet in Vision
Solutions Portal (VSP) and on the Work with Notifications display (WRKNFY command). The
source of these notifications is identified as TGTJRNINSP. You can view the details of the
notification from either user interface.
Only the first object changed by the user is identified in the notification. However, each object
changed by the user is logged in an internal database along with the notification ID. The
notification ID is used by enhanced capabilities available only when using MIMIX in VSP.
When using MIMIX through Vision Solutions Portal, the filter on the Replicated Objects portlet
allows you to see a list of objects changed on the target system. You can further filter by a
particular user, program, job, or notification ID. Also, when viewing details of a notification sent by
target journal inspection, the notification ID is displayed in the Notification Details dialog. You can
use this ID in the filter for the Replicated Objects portlet to see a list of objects changed by this
user on the target node. These capabilities are only available through Vision Solutions Portal.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 27
Previous service packs (included)
priority object audit. The next run (either scheduled or priority-based) of an audit which
checks the object type will correct the problem if the automatic audit recovery policy is
enabled.
• Object created on target system is within replication scope. The replication manager uses the
current settings of the Object only on target (OBJONTGT) policy to determine whether to
recover the object to the source system. If the policy permits, the object is synchronized to
the source system. The policy can also be set to delete the object from the target system.
• Replicated object was deleted on target system. The replication manager determines if the
object still exists on the source system. If the source object exists and is still within the
replication scope, it is synchronized to the target system by the next run of an audit which
checks the object type.
MIMIX tracks error conditions for three days. Once an error condition is corrected, the object will
no longer be identified as being "changed on target by user" in the Replicated Objects portlet.
Also, if it is not already started, the replication manager is started by the system manager to
perform daily cleanup activities.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 28
Previous service packs (included)
summarized status of the target journal inspection processes associated with a data group. In
the portlet's summary view, this is in the Target status values. In the details view, this is in the
Tgt Jrn column. From a 5250 emulator, the Work with Data Groups display (WRKDG)
includes a summary of the target journal inspection processes associated with a data group
in the Target Mgr column.
• Individual process statuses in data group details - When displaying detailed status of a
data group, status is also available for the individual inspection processes associated with
target journals for that data group. In VSP, this information is in the Data Group Details and
Activities portlet. The portlet's DB Statistics tab includes as many as two separate rows in the
Supporting Processes section, for the target user journal and system journal inspection
processes. The Object Statistics tab has one possible row in the Supporting Processes
section for the target system journal inspection process. From a 5250 emulator, the merged
view of the Data Group Status display (DSPDGSTS command) includes target journal
inspection status in the Sys Jrn Insp and User Jrn Insp fields within the Target Statistics
section. In both user interfaces, inspection status is not displayed if target journal inspection
is not configured or the data group has not been started.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 29
Previous service packs (included)
In the Notifications portlet, checkboxes added to the headings for the New and Acknowledged
lists allow you to take action on multiple notifications at once.
In the Recovery Domain portlet, the resulting dialogs from these actions have changed:
• The Start action now calls the Start Managers and Services Dialog instead of Start MIMIX
Managers dialog. When called from this portlet, the dialog starting the master monitor is not
possible and other managers and services can be started only on selected node.
• The Stop action now calls the Stop Cluster Services dialog. This action from this portlet does
not stop target journal inspection.
In the Nodes portlet, the Start action now calls the Start Managers and Services dialog.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 30
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 31
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 32
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 33
Previous service packs (included)
name, and the status of each member is identified with an icon. A Filter button and controls for
page navigation have also been added.
The new Filter Activity Details dialog allows you to filter the File Activity Details window by file
member in error and to set the maximum number of activities to display for the file.
Page navigation controls have been added to the Object Activity Details Window. The default
number for the maximum activities displayed is now 100. (MXHA-6631)
The portlet has tabs for libraries, directories (IFS), and folders (DLO) as well as a content area
where replicated objects are listed. A tree control on each tab provides navigation through the
available data. The content area displays the replicated objects that are within the library,
directory, or folder selected from the tree of the current tab. When auditing history has been
retained, actions are available for displaying an object’s audit history and the audited objects
within a selected library, directory, or folder.
Robust filtering capability is available to limit the displayed objects to those changed on the
source system within a selected length of time, by object type, by data group, or by application
group. You can also filter the portlet by the status of the most recent audit of the objects or by
attributes of information retained about changes to objects that occurred on the target node
outside of MIMIX operations.
For replicated IFS objects, directories (*DIR) are displayed regardless of their configured method
of replication. However, only cooperatively processed stream files (*STMF) and symbolic links
(*SYMLNK) can be displayed in the portlet. *STMF and *SYMLNK objects replicated entirely
through the system journal cannot be displayed. A message indicates when a selected directory
contains but cannot display these objects.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 34
Previous service packs (included)
For replicated files with members, each member can be audited by three different audits. The
portlet displays only the most recent of these audits. Use the Details action for the object to view
information about the most recent results from all three audit types.
In environments with more than two nodes or that perform bi-directional replication, replicated
objects may appear in the list multiple times, once for each data group that replicates the object.
The three-part name of the data group and the direction of replication distinguish the objects. The
three-part name is available in flyover text for the data group column and in the object details.
You can also filter by the three-part name. Objects in disabled data groups are not displayed by
default.
Normal replication and audit processes update the data available for display in the portlet. During
initial configuration, configuration changes, and regular validation activities, a message at the top
of the portlet indicates that some objects may not appear until MIMIX finishes collecting
information about objects. (MXHA-7125)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 35
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 36
Previous service packs (included)
Ending Recoveries
Queued Procedures
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 37
Previous service packs (included)
Acknowledged Procedures
Acknowledged Audits
The following changes are for the Data Group Details and Activity portlet.
Held Reorganize File Activity tab
Held Promoter File Activity Details window
Held Rename Related Files window
Release
Held Rename IFS Tracking tab
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 38
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 39
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 40
Previous service packs (included)
The following parameters have been removed from the command: Data group name space
(NAMESPC) and Data resource group entry (DTARSCGRP). (MXHA-9577)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 41
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 42
Previous service packs (included)
When a user in a product instance selects an action that emails, the user provides the recipient's
address.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 43
Previous service packs (included)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 44
Previous service packs (included)
Switching stopped. The flow of replication data is in the process of changing direction.
However, a switching procedure stopped or other critical errors occurred during the switch that
require user action.
Undo in progress. A task is being performed that affects the entire instance and cannot be
interrupted while in progress.
Instances for more than one Vision Solutions product can be displayed in this portlet. Each
product determines which status values it will use in this portlet. Some of these status values
may not be used by every product. (STR-2393)
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 45
Previous service packs (included)
MXHA-9122 Status icons have been changed to provide consistency between portlets and to
enhance product status information.
MXHA-9140 The Audit Details portlet now shows the correct date and time when a data group
is re-enabled.
MXHA-9292 The Nodes portlet will show the configured nodes for a MIMIX instance even if
collector services is not active.
MXHA-9316 Audited Objects and Data Group Audited Objects windows now correctly show
object compare status values as CO (LOB), EQ (DATE), or EQ (OMIT).
Vision Solutions Portal 2.0.00.06
MXHA-9811 Accurate information is now displayed in VSP when reconnecting to a MIMIX
instance.
7.1.01.00 (Included with 7.1.03.00) © Copyright 1999, 2012 Vision Solutions, Inc. All rights reserved. 46