Rocket iCluster

Installation Guide
Version 8.3

October 2020
ICL-083–IG-02
Notices
Edition
Publication date: October 2020
Book number: ICL-083–IG-02
Product version: Version 8.3

Copyright
© Rocket Software, Inc. or its affiliates 1997-2020. All Rights Reserved.

Trademarks
Rocket is a registered trademark of Rocket Software, Inc. For a list of Rocket registered trademarks go
to: www.rocketsoftware.com/about/legal. All other products or services mentioned in this document
may be covered by the trademarks, service marks, or product names of their respective owners.

Examples
This information might contain examples of data and reports. The examples include the names of
individuals, companies, brands, and products. All of these names are fictitious and any similarity to
the names and addresses used by an actual business enterprise is entirely coincidental.

License agreement
This software and the associated documentation are proprietary and confidential to Rocket Software,
Inc. or its affiliates, are furnished under license, and may be used and copied only in accordance with
the terms of such license.

Note: This product may contain encryption technology. Many countries prohibit or restrict the
use, import, or export of encryption technologies, and current use, import, and export regulations
should be followed when exporting this product.

2
Corporate information
Rocket Software, Inc. develops enterprise infrastructure products in four key areas: storage, networks,
and compliance; database servers and tools; business information and analytics; and application
development, integration, and modernization.
Website: www.rocketsoftware.com
Rocket Global Headquarters
77 4th Avenue, Suite 100
Waltham, MA 02451-1468
USA
To contact Rocket Software by telephone for any reason, including obtaining pre-sales information
and technical support, use one of the following telephone numbers.

Country Toll-free telephone number

United States 1-855-577-4323
Australia 1-800-823-405
Belgium 0800-266-65
Canada 1-855-577-4323
China 400-120-9242
France 08-05-08-05-62
Germany 0800-180-0882
Italy 800-878-295
Japan 0800-170-5464
Netherlands 0-800-022-2961
New Zealand 0800-003210
South Africa 0-800-980-818
United Kingdom 0800-520-0439

Contacting Technical Support

The Rocket Community is the primary method of obtaining support. If you have current support and
maintenance agreements with Rocket Software, you can access the Rocket Community and report
a problem, download an update, or read answers to FAQs. To log in to the Rocket Community or to
request a Rocket Community account, go to www.rocketsoftware.com/support.
In addition to using the Rocket Community to obtain support, you can use one of the telephone
numbers that are listed above or send an email to [email protected].

3
Contents
Notices................................................................................................................................................................................... 2
Corporate information......................................................................................................................................................... 3
Chapter 1: Rocket iCluster installation............................................................................................................................... 5
Performing preinstallation tasks............................................................................................................................. 5
Verifying system requirements.................................................................................................................... 5
System requirements....................................................................................................................... 5
Configuring memory pools.......................................................................................................................... 6
Setting IBM i operating system values........................................................................................................6
Creating the audit journal and the journal receiver.................................................................................. 7
Obtaining license keys................................................................................................................................. 7
Downloading software and generating license keys..................................................................................7
Installing iCluster...................................................................................................................................................... 8
Installing software and adding license keys...............................................................................................8
Completing postinstallation tasks...............................................................................................................9
Verifying auditing and system values........................................................................................... 10
Registering users.............................................................................................................................10
Authorizing product use to specific users.....................................................................................11
Adding the dmcluster entry to the TCP/IP service table..............................................................12
Enabling DDM access......................................................................................................................13
Starting iCluster.......................................................................................................................................... 15
Starting the XDMCLUSTER subsystem automatically.................................................................. 15
Scheduling iCluster startup and shutdown.................................................................................. 15
Configuring iCluster.................................................................................................................................... 16
Configuring the failover mechanism............................................................................................. 16
Configuring iCluster automatically................................................................................................16
Modifying default cluster system values.......................................................................................18
Verifying the iCluster installation.............................................................................................................. 19
Chapter 2: Upgrading iCluster........................................................................................................................................... 21
Supported iCluster releases...................................................................................................................................21
Downloading software and generating license keys........................................................................................... 21
Upgrading iCluster..................................................................................................................................................21
Upgrading from Rocket iCluster 7.1 or later.............................................................................................22
Registering access path lists..........................................................................................................24
Ending replication when groups do not use commitment control..................................................................... 24
Ending replication when groups use commitment control.................................................................................24
Chapter 3: Uninstalling iCluster.........................................................................................................................................26
Uninstalling the product and license keys........................................................................................................... 26
Removing the dmcluster entry from the TCP/IP service table............................................................................ 26
Index.................................................................................................................................................................................... 28

4
Chapter 1: Rocket iCluster installation
Rocket iCluster is a logical replication solution that operates on IBM Power or PureFlex systems that
run IBM i. To install iCluster, perform the following tasks:
1. Performing preinstallation tasks
The preinstallation tasks ensure that the high availablity and disaster recovery environment that
you configure optimizes performance and meets the needs of the business.
2. Installing iCluster
Install iCluster on each node.

Performing preinstallation tasks

The preinstallation tasks ensure that the high availablity and disaster recovery environment that you
configure optimizes performance and meets the needs of the business.
Logical replication products require appropriate planning, configuration, and deployment. Determine
the applications and objects to replicate to the backup system or systems in the cluster.
Before you install iCluster, perform these tasks:

1. Verifying system requirements

Verify that the system meets the minimum hardware and software requirements to install and
operate iCluster.
2. Configuring memory pools
To improve performance, change the default settings to ensure that business applications do not
experience interactions that cause decreased throughput.
3. Setting IBM i operating system values
Set the operating system values for objects.
4. Creating the audit journal and the journal receiver
If the QAUDJRN audit journal and the journal receiver do not exist, create them in the QSYS
library.
5. Obtaining license keys
A new license key is required for new product releases and new hardware.
6. Downloading software and generating license keys
Obtain the license key for each server, and if needed, download the software.
Next topic: Installing iCluster
Parent topic: Rocket iCluster installation

Verifying system requirements

Verify that the system meets the minimum hardware and software requirements to install and operate
iCluster.
Next topic: Configuring memory pools
Parent topic: Performing preinstallation tasks

System requirements
The hardware and software requirements for iCluster are described below.

5
Chapter 1: Rocket iCluster installation

Hardware
Each node requires the following minimum available disk space:
▪ 200 MB for installation
▪ 90 MB for operation
▪ 512 MB for the staging store library. A typical disk space allocation is 10 GB.
▪ Additional disk space for large save files and journal receivers.

Software
▪ IBM i 6.1 or later, with the current cumulative PTF level applied
▪ Installing or upgrading to iCluster 8.3 requires that the following IBM PTFs have been applied:
▫ IBM i 6.1 - SI55092
▫ IBM i 7.1 - SI55093
▫ IBM i 7.2 - SI55094
▫ IBM i 7.4 - SI72671, SI70837

Communication protocol
▪ TCP/IP

Configuring memory pools

To improve performance, change the default settings to ensure that business applications do not
experience interactions that cause decreased throughput.

About this task

By default, iCluster runs out of the *BASE shared memory pool with the batch jobs that run at a priority
of 20, with a time slice of 5,000 milliseconds, and a default wait time of 30 seconds.

Procedure
▪ Run the iCluster subsystem in a different shared memory pool, not the default *BASE shared
memory pool.
▪ Run iCluster batch jobs with a priority of at least 30, a time slice of 500 milliseconds, and a default
wait time of 0 seconds.

Next topic: Setting IBM i operating system values

Previous topic: Verifying system requirements
Parent topic: Performing preinstallation tasks

Setting IBM i operating system values

Set the operating system values for objects.
1. Set the Allow User Domain Objects (QALWUSRDMN) system value to *ALL.
2. Set the Allow Object Restore (QALWOBJRST) system value to *ALL.
3. Set the Retain Server Security (QRETSVRSEC) system value to 1.

6
 Creating the audit journal and the journal receiver

Next topic: Creating the audit journal and the journal receiver
Previous topic: Configuring memory pools
Parent topic: Performing preinstallation tasks

Creating the audit journal and the journal receiver

If the QAUDJRN audit journal and the journal receiver do not exist, create them in the QSYS library.
1. From the command line, enter the following IBM i command: CRTJRNRCV.
2. In the Journal receiver field, type the name of the journal receiver.
3. In the Library field, type the name of the library for the journal receiver.
4. Enter values in the other fields on this screen.
5. From the command line, enter the following IBM i command: CRTJRN.
6. In the Journal field, type QAUDJRN.
7. In the Library field, type QSYS.
8. In the next two fields, type the journal receiver name and library that you specified on the Create
Journal Receiver (CRTJRNRCV) screen.
9. Ensure that the DLTRCV parameter is set to *NO.
10. Enter values in the other fields on this screen.
Next topic: Obtaining license keys
Previous topic: Setting IBM i operating system values
Parent topic: Performing preinstallation tasks

Obtaining license keys

A new license key is required for new product releases and new hardware.

About this task

A new license key is required in the following situations:
▪ When the installation is upgraded from iCluster 8.2 or earlier to iCluster 8.3.
▪ When the hardware serial number or Processor Group (P Group) changes.
A new license key is not required for pack ID updates, interim fixes, and technical refreshes.

Procedure
Purchase a license key for each server on which iCluster is installed.
Next topic: Downloading software and generating license keys
Previous topic: Creating the audit journal and the journal receiver
Parent topic: Performing preinstallation tasks

Downloading software and generating license keys

Obtain the license key for each server, and if needed, download the software.

7
Chapter 1: Rocket iCluster installation

Procedure
1. Log on to the Rocket Community (www.rocketsoftware.com/support).
2. Select the DOWNLOADS page.
3. On the My Downloads tab, click the ID for the iCluster release to install.
4. If you do not have physical installation media, download the zip file that contains the software,
extract the contents of the zip file, and confirm that you have the correct files.
The zip file includes the following files:
▪ CSBASE save file for installing iCluster on Power Systems running IBM i
▪ setup.exe file for installing the optional iCluster Administrator on Microsoft Windows
▪ iCMobileMon.war web application archive file for installing the optional iCluster Mobile
Monitor under Apache Tomcat Web Server
5. Select the My License Keys tab to view the license key or keys.
6. Record the 18-character license key from the download site, or obtain the license key from the
order confirmation.
7. Record the Vendor Data value (up to 10 characters) from the download site, or obtain it from the
order confirmation.
8. To put the installation software on the server where you want to install iCluster, use one of the
following methods:
▪ Use FTP to copy the save files to the QGPL library.
▪ Insert the physical media into the IBM i optical drive.
Previous topic: Obtaining license keys
Parent topic: Performing preinstallation tasks

Installing iCluster
Install iCluster on each node.
1. Installing software and adding license keys
Use the IBM i Restore License Program (RSTLICPGM) command or the GO LICPGM command
(option 11) to install iCluster on each node.
2. Completing postinstallation tasks
After you install iCluster, perform these postinstallation configuration tasks:
3. Starting iCluster
After installation and configuration, start iCluster to work in the active replication environment.
4. Configuring iCluster
After installation is complete, perform these tasks to configure iCluster:
5. Verifying the iCluster installation
After you install iCluster on two nodes and complete the automatic configuration, verify the
installation and ensure that replication is active.
Previous topic: Performing preinstallation tasks
Parent topic: Rocket iCluster installation

Installing software and adding license keys

Use the IBM i Restore License Program (RSTLICPGM) command or the GO LICPGM command (option
11) to install iCluster on each node.

8
 Completing postinstallation tasks

Prerequisites
Complete the steps in Downloading software and generating license keys, on page 7.

Procedure
1. To install iCluster, use one of the following methods:
▪ To install from a save file, use the following command:

RSTLICPGM LICPGM(4RICLUS) DEV(*SAVF) OPTION(*BASE) SAVF(QGPL/CSBASE)

▪ To install from physical media, use the following command:

RSTLICPGM LICPGM(4RICLUS) DEV(<optical device>) OPTION(*BASE)

2. Review the software agreement, and press F14 to accept it.

3. Optional: To install iCluster Administrator on a computer that runs Microsoft Windows, extract
the setup.exe file, run the executable file, and follow the prompts to install the iCluster
Administrator.
4. To add the license key to the product, enter the following command on each server:
ADDLICKEY PRDID(4RICLUS) LICTRM(V8R3) FEATURE(5050)
SERIAL(<xxxxxxx>) PRCGRP(P Group)
LICKEY(<xxxxxx yyyyyy zzzzzz>) USGLMT(*NOMAX) EXPDATE(*NONE)
VNDDTA(<Vendor Data provided by Rocket>)
where:
▪ <xxxxxxx> is the serial number of the IBM i server.
▪ <xxxxxx yyyyyy zzzzzz> is the iCluster license key.
▪ <P Group> is the IBM Power Systems Processor Group. To install iCluster installation as part of
Rocket iCluster HA Assist, specify *ANY.
▪ The VNDDTA field must be filled in with the Vendor Data that was provided to you by Rocket
Software when you were given the iCluster license key you are using on this command.
5. To confirm the installation, complete these steps:
a. Enter the following IBM i command: GO LICPGM.
b. To display installed licensed programs, use option 10.
The following entry verifies that iCluster is a licensed program: 4RICLUS *INSTALLED
Rocket iCluster.
Next topic: Completing postinstallation tasks
Parent topic: Installing iCluster

Completing postinstallation tasks

After you install iCluster, perform these postinstallation configuration tasks:
1. Verifying auditing and system values
Change the QADUCTL and QAUDLVL IBM i system values to capture object changes in the system
audit journal.
2. Registering users
A registered iCluster user must have an IBM i user profile that is defined with *IOSYSCFG authority.
Add one or more iCluster users on each node.
3. Authorizing product use to specific users

9
Chapter 1: Rocket iCluster installation

The objects in the ICLUSTER product library, which is created during installation, are owned
by the DMCLUSTER user profile. Ensure that the DMCLUSTER user profile parameter 'Limit
capabilities' (LMTCPB) is set to *NO.
4. Adding the dmcluster entry to the TCP/IP service table
To enable communication between nodes, add the dmcluster entry to the TCP/IP service table.
5. Enabling DDM access
For secure DDM connections that require password validation, a QDDMSERVER server
authentication entry is required on the primary and backup nodes for the DMCLUSTER user
profile and user profiles for registered iCluster users that use the Status Monitor.
Next topic: Starting iCluster
Previous topic: Installing software and adding license keys
Parent topic: Installing iCluster

Verifying auditing and system values

Change the QADUCTL and QAUDLVL IBM i system values to capture object changes in the system audit
journal.

About this task

The VFYHAJRN—Verify Audit Journal command verifies, and if necessary, automatically changes the
system values.

Procedure
1. To review the system values, run the following commands:
DSPSYSVAL QAUDCTL
DSPSYSVAL QAUDLVL
DSPSYSVAL QAUDLVL2
2. Make a note of the system values.
3. To change the current library to the iCluster product library, enter the following command:
CHGCURLIB ICLUSTER
4. To set the appropriate level of security auditing, run the following command:
VFYHAJRN AUDQTEMP(*NO) AUDSPLF(*NO)

Note: This command sets the two IBM i system values, QAUDLVL and QAUDCTL, which are
required for replication. Other system values that were set for QAUDLVL and QAUDCTL are not
affected by this command.

5. To review the updated system values, run the following IBM i commands again:
DSPSYSVAL QAUDCTL
DSPSYSVAL QAUDLVL
DSPSYSVAL QAUDLVL2
6. Verify that the values are appropriate for your installation.
Next topic: Registering users
Parent topic: Completing postinstallation tasks

Registering users
A registered iCluster user must have an IBM i user profile that is defined with *IOSYSCFG authority. Add
one or more iCluster users on each node.

10
 Authorizing product use to specific users

About this task

Registered users can work with iCluster without having to log on to the system as the QSECOFR service
tools user profile or a user with QSECOFR authority.
To define which cluster operations can be performed, register an IBM i user profile or group profile,
and identify the authority level (administrator, operator, or user) for each profile.
If the number of iCluster users is large or if the users change frequently, add the iCluster users as
members of an IBM i group profile. Then, instead of registering each user, register the group profile.
Users inherit the iCluster authority of the group profile.
To ensure operational security, restrict the ability to run commands that are based on user access
levels. Grant administrative (*ADMIN) privileges to at least one iCluster user.
The specified user or group profile is registered only on the node where you run the DMADDUSR—Add
User command.

Procedure
1. To register a user, enter the following command: DMADDUSR.
2. In the User field, enter an IBM i user profile or group profile that is defined on the node. 
3. In the Authority field, enter one of the following security levels for the profile:

Option Description

*USER Grants User privileges. This is the default

value.

*OPERATOR Grants Operator privileges.

*ADMIN Grants Administrative privileges.

4. Optional: In the Description field, enter a short description that identifies the full name of the
user or group profile.
5. Optional: In the iCA password field, enter the password to use to access to iCluster
Administrator, or enter * (asterisk) to prevent access to iCluster Administrator.
A user who does not have a password cannot log on to iCluster Administrator, but can use iCluster
commands in the native IBM i environment.
6. Repeat these steps on each node in the cluster for each user profile and group profile.
Next topic: Authorizing product use to specific users
Previous topic: Verifying auditing and system values
Parent topic: Completing postinstallation tasks

Authorizing product use to specific users

The objects in the ICLUSTER product library, which is created during installation, are owned
by the DMCLUSTER user profile. Ensure that the DMCLUSTER user profile parameter 'Limit
capabilities' (LMTCPB) is set to *NO.

About this task

By default, *PUBLIC authority provides *CHANGE authority to the ICLUSTER library. If you remove
*PUBLIC, you must add additional authorized users and grant them *CHANGE with authority. Another
approach is to change the value from *CHANGE to *EXCLUDE for *PUBLIC.

11
Chapter 1: Rocket iCluster installation

Procedure
1. To edit the authority of the ICLUSTER library, use the following IBM i command: EDTOBJAUT.
2. In the Object field, type ICLUSTER.
3. In the Library field, type QSYS.
4. In the Object Type field, type *LIB.
Next topic: Adding the dmcluster entry to the TCP/IP service table
Previous topic: Registering users
Parent topic: Completing postinstallation tasks

Adding the dmcluster entry to the TCP/IP service table

To enable communication between nodes, add the dmcluster entry to the TCP/IP service table.

About this task

iCluster Port Requirements
The following TCP/IP ports are required for iCluster and related functions:

Function name Service name Port number Explanation

iCluster Service dmcluster 4545 4545 is the default port
specified when the
dmcluster service was
defined to the TCP/IP
service table.
iCluster 10001-10100 The range of ports
Communications on source and
target as defined
by DMADDNODE
(via MINPORT and
MAXPORT parameters).
For details, refer to
“DMADDNODE—Add
Node” chapter of the
Rocket iCluster User
Guide.
iCluster Replications drda 446-447 iCluster uses DDM
and Status Monitor connections to get
the metadata from
the target node. For
DDM a service port on
the target is required
(default 446).
Remote Journaling rmtjournal rmtjournal- 3777 3888 The remote journal TCP
(IPV4, IPV6) ipv6 connections use the
TCP local port of 3777
or 3888.

If any of the above ports are restricted using a firewall or any other mechanism, iCluster or related
functions might fail to operate. For assistance with configuring ports or working with a firewall beyond
the above information, contact the firewall provider or obtain a consulting agreement.
Command syntax

12
 Enabling DDM access

You can use the following command or the steps in the task to add the dmcluster entry:

ADDSRVTBLE SERVICE(‘dmcluster’) PORT(4545) PROTOCOL(‘tcp’) TEXT(‘<user description>’)

Procedure
1. Sign on as the QSECOFR user profile or as a user with *SECOFR special authority.
2. Enter the following IBM i command: CFGTCP.
3. Type 21 to configure related tables.
4. Type 1 to work with service table entries.
5. In the Opt column, type 1.
6. In the Service field, type dmcluster.
Type dmcluster in lower case.
7. In the Port field, type 4545 (the default port). If port 4545 is already in use, enter an unused port
number from 1 through 65535.
8. In the Protocol field, type tcp.
9. In the Text 'description' field, type a description that describes how the port is used by the
iCluster TCP/IP node.
Next topic: Enabling DDM access
Previous topic: Authorizing product use to specific users
Parent topic: Completing postinstallation tasks

Enabling DDM access

For secure DDM connections that require password validation, a QDDMSERVER server authentication
entry is required on the primary and backup nodes for the DMCLUSTER user profile and user profiles
for registered iCluster users that use the Status Monitor.

About this task

DDM access to iCluster metadata is required for many replication activities, including the following
operations:
▪ Remote journal replication
▪ DMMONHA—replication monitoring
▪ Status Monitors
▪ File content sync check
▪ File activation of files that are in an out-of-sync (ACTOOS) state
▪ WebSphere MQ replication

Note: For non-secured DDM connections, password validation and server authentication entries
are not required for the DMCLUSTER user profile and other user profiles.

Procedure
1. Log on as a user with *IOSYSCFG special authority.
2. Issue the following IBM i command: CHGDDMTCPA.
3. To determine whether secure DDM server authentication is in use, review the value that is
displayed for the PWDRQD parameter.

13
Chapter 1: Rocket iCluster installation

Value of PWDRQD parameter DDM server authentication

*USRID or *VLDONLY Authentication is not in use. Do not complete

the following steps.

A value other than *USRID or *VLDONLY Secure DDM server authentication is in

use. The DMCLUSTER user profile and user
profiles for registered iCluster users that
use the Status Monitor must have a valid
QDDMSERVER server authentication entry on
each node. Complete the following steps.

4. To create the QDDMSERVER authentication entry for the DMCLUSTER user profile, enter the
following IBM i command:
ADDSVRAUTE USRPRF(DMCLUSTER) SERVER(QDDMSERVER) USRID(<name>)
PASSWORD(<password>)
where:
<name> is the user ID that exists on all nodes of the cluster
<password> is a valid password for the userid
Enter the SERVER name QDDMSERVER in uppercase
If the password changes, use the Change Server Authentication Entry (CHGSVRAUTE) command
to update the QDDMSERVER authentication entry.
5. To create the QDDMSERVER authentication entry for user profiles for registered iCluster users that
use the Status Monitors, enter the following IBM i command:
ADDSVRAUTE USRPRF(<userprf>) SERVER(QDDMSERVER) USRID(*USRPRF) PASSWORD(<password>)
where:
<userprf> is the user profile for registered iCluster users who use the Status Monitors
<password> is a valid password for the user profile
Enter the SERVER name QDDMSERVER in uppercase
If the password changes, use the IBM i Change Server Authentication Entry (CHGSVRAUTE)
command to update the QDDMSERVER authentication entry.
6. Optional: Remote journaling and IBM WebSphere MQ replication require authentication
entries. If you use remote journaling or WebSphere MQ replication, run these commands for the
automatically created remote database directory entries (RDBDIRE) on each node and for the
remote database directory entries (RDBDIRE) that are used for remote journaling.
a. On the primary node of the group, enter the following IBM i command:
ADDSVRAUTE USRPRF(DMCLUSTER) SERVER(<rdbentry_bn>) USRID(<name>)
PASSWORD(<password>)
where:
<rdbentry_bn> is the name of the remote database directory entry for the backup node
<name> is the user ID that exists on all nodes of the cluster
<password> is a valid password for the user ID
b. On the backup node of the group, enter the following IBM i command:
ADDSVRAUTE USRPRF(DMCLUSTER) SERVER(<rdbentry_pn>) USRID(<name>)
PASSWORD(<password>)
where:
<rdbentry_pn> is the name of the remote database directory entry for the primary node
<name> is the user ID that exists on all nodes of the cluster
<password> is a valid password for the user ID
Previous topic: Adding the dmcluster entry to the TCP/IP service table
Parent topic: Completing postinstallation tasks

14
 Starting iCluster

Starting iCluster
After installation and configuration, start iCluster to work in the active replication environment.

Procedure
1. Log on to a node as a user with iCluster *ADMIN authority.
2. To change the current library to the iCluster product library, enter the following command:
CHGCURLIB ICLUSTER.
3. To start iCluster, enter the following command: GO DMCLUSTER.
4. To monitor the replication environment from the Full Cluster Status Monitor, enter the following
command: WRKCSMON.
5. To view a list of supported commands, navigate to the iCluster main menu and press F22 (Shift +
F10).
Next topic: Configuring iCluster
Previous topic: Completing postinstallation tasks
Parent topic: Installing iCluster

Starting the XDMCLUSTER subsystem automatically

You can configure the XDMCLUSTER subsystem to start automatically when the node is restarted.

Procedure
To configure the XDMCLUSTER subsystem to run when the server is restarted, add the following
command to the source code for the program that is specified in the IBM i QSTRUPPGM system value:
QSYS/STRSBS ICLUSTER/XDMCLUSTER

Scheduling iCluster startup and shutdown

Add a scheduled job to automate setting the current library to the iCluster library and starting up
iCluster; add another one to automate iCluster shut down.

Procedure
1. To automate iCluster startup, create a job to change the current library to the iCluster product
library by performing the following command:
CHGCURLIB ICLUSTER
2. In the same job, issue the following command to start up iCluster:
DMSTRCST
3. Compile the program.
4. To automate iCluster shutdown, create a job to change the current library to the iCluster product
library by performing the following command:
CHGCURLIB ICLUSTER
5. In the same job, issue the following command to shut down iCluster:
DMENDCST
6. Compile this program as well.
7. To add an entry to the IBM i job scheduler, enter the IBM i Add Job Schedule Entry (ADDJOBSCDE)
command.

15
Chapter 1: Rocket iCluster installation

Configuring iCluster
After installation is complete, perform these tasks to configure iCluster:
• Configuring the failover mechanism
Select the failover mechanism for your replication environment. The default failover mechanism is
SwitchOver System.
• Configuring iCluster automatically
To create nodes, groups, object specifiers for each library, default journals, and set the product
system values automatically, use the DMAUTOCFG—Auto-configure iCluster command.
• Modifying default cluster system values
To change the default cluster system values, use the input screen for the DMSETSVAL—Set Cluster
System Values command.
Next topic: Verifying the iCluster installation
Previous topic: Starting iCluster
Parent topic: Installing iCluster

Configuring the failover mechanism

Select the failover mechanism for your replication environment. The default failover mechanism is
SwitchOver System.

About this task

Two types of failover mechanisms detect node failures:
▪ SwitchOver System is a proprietary heartbeat mechanism that verifies communication between
multiple systems and provides functionality for running user exits and sending messages on
communications failures. No action is required to use the default SwitchOver System failover
mechanism.
▪ If you are replicating data using IASPs (Independent Auxiliary Storage Pools) or are using HA
Assist, change the failover mechanism to Cluster Resource Services (IBM Cluster Services for i).
Cluster Resource Services (IBM Cluster Services for i) is appropriate when communication between
systems is less stable or when switched disk or resilient applications are used.

Procedure
1. To change the default failover mechanism to Cluster Resource Services, navigate to the main
menu and type 6 at the command line to open the input screen for the DMSETSVAL—Set Cluster
System Values command.
2. Set the value of the Use IBM Cluster Services for i field to *YES.
3. Enter the IBM i Change Network Attribute (CHGNETA) command, and set the value of the Allow
add to cluster (ALWADDCLU) network attribute to *ANY or *RQSAUT.
4. When *RQSAUT is set as the ALWADDCLU network attribute, then install the Digital Certificate
Manager and a Cryptographic Access Provider on the node.
Parent topic: Configuring iCluster

Configuring iCluster automatically

To create nodes, groups, object specifiers for each library, default journals, and set the product system
values automatically, use the DMAUTOCFG—Auto-configure iCluster command.

16
 Configuring iCluster automatically

About this task

Automatic configuration creates the following replication environment:
▪ Primary and secondary nodes
▪ Default journals HADJRN and HABSFJRN and journal receivers HAD0000001 and BSF0000001
in the AAAJRNLIB library
▪ System values that use these journals in the AAAJRNLIB library as the default journals
▪ Two replication groups to use the default journals
▪ A SYSTEM replication group
▪ The following object specifiers are created and selected to the SYSTEM replication group:
▫ All user profiles
▫ All authorization lists (excluding lists with names that begin with the letter ‘Q’)
▫ All output queues (excluding queues with name that begin with the letter ‘Q’)
▫ The QGPL library (excluding objects with names that begin with the letter ‘Q’)

Procedure
1. Log on to the two systems that will be the nodes in the cluster.
2. On each system enter the following commands to start iCluster:
CHGCURLIB ICLUSTER
GO DMCLUSTER
The XDMCLUSTER subsystem and the DMCHATL TCP/IP listener job are started.
3. If you do not use the default SwitchOver System failover mechanism, run the following command
on each system to define Cluster Resource Services as the failover mechanism:
DMSETSVAL CLUSTER(*YES)
4. Ensure that the XDMCLUSTER subsystem is active on each node where iCluster is installed.
5. Ensure that the DMCHATL job is active in the XDMCLUSTER subsystem on each node.
6. On the system that is the primary node, log on as a user with iCluster *ADMIN authority.
7. To start the automatic configuration, enter the following commands:

CHGCURLIB ICLUSTER
DMAUTOCFG

8. In the Primary node field, type the name of the primary node.
9. In the Primary node IP address field, type the IP address of the primary node.
10. In the Backup node field, type the name of the backup node.
11. In the Backup node IP address field, type the IP address of the backup node.
12. In the Port field, type the TCP/IP port number for the dmcluster service entry on the node.
Valid port values are 1 - 65535. The default value is 4545.
13. In the Primary group field, type the name of the primary group.
14. In the Secondary group field, type the name of the secondary group.
15. To run the command and display a list of libraries, press Enter.
16. To complete the configuration, select the libraries to replicate to the primary or secondary
replication groups.
17. Verify the installation. For more information, see Verifying the iCluster installation, on page 19.
Parent topic: Configuring iCluster

17
Chapter 1: Rocket iCluster installation

Modifying default cluster system values

To change the default cluster system values, use the input screen for the DMSETSVAL—Set Cluster
System Values command.

About this task

You can change the default cluster system values that are set during automatic configuration.

Procedure
1. Navigate to the main menu.
2. To open the input screen for the DMSETSVAL—Set Cluster System Values command, type 6 at the
command line.
3. Press Enter.
4. To navigate, press the Page Up or Page Down keys.
5. Change values in the following categories:
▪ Operational (OPER)—Cluster system values that affect operations within the cluster.
▪ Automatic Reactivation (ACT)—Cluster system values that affect the automatic reactivation of
suspended objects.
▪ Object (OBJ)—Cluster system values that pertain to objects replicated within the cluster.
▪ Spooled File (SPLF)—Cluster system values that affect the replication of spooled files within
the cluster.
▪ Physical File (PF)—Cluster system values that affect the mirroring of physical files within the
cluster.
▪ Byte Stream File (BSF)—Cluster system values that affect the replication of Byte Stream File
(BSF) objects within the cluster.
▪ Event Log (EVNTLOG)—Cluster system values that affect the information that is displayed
through the event log.
▪ Latency (LATENCY)—Cluster system values that affect the latency threshold settings within the
cluster.
▪ Cluster Values (CLUSTER)—Controls whether iCluster uses Cluster Resource Services as its
failover mechanism.
▪ Enable communications auto-recovery (COMMRCVRY) - Specifies whether or not to use the
iCluster communications auto-recovery feature in the case of a brief communication failure
between nodes.
▪ Performance (PERFORM)—Controls the performance of iCluster in certain scenarios.
▪ *FULL sync check options (FULLSCOPTS) - Cluster system values that affect some aspects of
*FULL sync checks by iCluster.
▪ Continuous sync check (SYNCCHECK)—Cluster system values that affect the performance of
synchronization checks by iCluster.
▪ GUI options (GUIOPTS)—Cluster system values that affect the iCluster Administrator display
and update.
▪ Custom journal entries (CUSTJRNE)—Cluster system values that specify the journal entries to
process.
▪ Replication monitoring (DMMONHA)—Cluster system values that specify options to start a
job to automatically monitor group replication status, event log messages, and suspended
objects.

18
 Verifying the iCluster installation

▪ iCluster replication job (JOBCCSID)—Cluster system values that specify the coded character
set identifier (CCSID) to use for replication jobs.
▪ Start *RFSH groups (STRRFSHGRP)—Specifies whether *RFSH groups should be started when
multiple groups are specified on the DMSTRGRP command.
▪ Allow roleswitch *RFSH groups (RSWRFSHGRP)—Specifies whether or not roleswitch is
allowed for groups of type *RFSH
▪ Generate SNMP traps (GENTRAPS)—Specifies whether or not SNMP traps are to be generated
for the iCluster messages that are defined as alertable messages
▪ Maximum number of parallel processes (MAXNUMJOBS)—Specifies the maximum number of
jobs for parallel processing of iCluster resource-consuming requests when applicable (such as
the DMMRKPOS command).
Parent topic: Configuring iCluster

Verifying the iCluster installation

After you install iCluster on two nodes and complete the automatic configuration, verify the
installation and ensure that replication is active.

Procedure
1. Log on to the primary node as a user with iCluster *ADMIN or *OPERATOR authority.
2. To start iCluster, enter the following commands:
CHGCURLIB ICLUSTER
GO DMCLUSTER
3. On the command line, press 2 to display the Work with Groups screen.
4. On the Work with iCluster Groups screen, type 1 next to the replication group that was created by
the DMAUTOCFG command and press Enter.
5. On the iCluster Start group (DMSTRGRP) screen, type *YES for Start replication apply jobs and
press F10 to display more parameters.
6. Type *YES for Refresh selected objects and press Enter.
The following actions are performed:
▪ The replication group is started.
▪ The remote journal is created on the backup node.
▪ The staging store library is created on the backup node.
▪ The target library is created.
▪ All of the objects in the library on the primary node that require journaling and that were not
journaled when the DMAUTOCFG command was run are journaled to the default journal.
▪ The selected objects on the primary node are saved and sent to the backup node.
▪ Monitoring and mirroring of the selected objects from the production node to the backup
node is started.
7. To verify the replication and display the library, enter the following IBM i command on the backup
node:
DSPLIB LIB(<library name>)
8. Confirm that the number of objects on the backup node is the same as the number of objects on
the primary node.

19
Chapter 1: Rocket iCluster installation

Next step
For information about using iCluster and monitoring replication, see the Rocket iCluster User’s Guide
on the Rocket Documentation Library at docs.rocketsoftware.com.

Previous topic: Configuring iCluster

Parent topic: Installing iCluster

20
Chapter 2: Upgrading iCluster
The procedure to upgrade iCluster depends on the current environment and iCluster version.

Supported iCluster releases

Upgrading to iCluster 8.3 is supported from the following iCluster releases (with or without service
packs and interim fixes):
▪ 8.2
▪ 8.1
▪ 7.1 TR2
▪ 7.1 TR1
▪ 7.1

Downloading software and generating license keys

Obtain the license key for each server, and if needed, download the software.

Procedure
1. Log on to the Rocket Community (www.rocketsoftware.com/support).
2. Select the DOWNLOADS page.
3. On the My Downloads tab, click the ID for the iCluster release to install.
4. If you do not have physical installation media, download the zip file that contains the software,
extract the contents of the zip file, and confirm that you have the correct files.
The zip file includes the following files:
▪ CSBASE save file for installing iCluster on Power Systems running IBM i
▪ setup.exe file for installing the optional iCluster Administrator on Microsoft Windows
▪ iCMobileMon.war web application archive file for installing the optional iCluster Mobile
Monitor under Apache Tomcat Web Server
5. Select the My License Keys tab to view the license key or keys.
6. Record the 18-character license key from the download site, or obtain the license key from the
order confirmation.
7. Record the Vendor Data value (up to 10 characters) from the download site, or obtain it from the
order confirmation.
8. To put the installation software on the server where you want to install iCluster, use one of the
following methods:
▪ Use FTP to copy the save files to the QGPL library.
▪ Insert the physical media into the IBM i optical drive.

Upgrading iCluster
To upgrade iCluster, use one of the following tasks:
Note the following software requirements before you upgrade:

21
Chapter 2: Upgrading iCluster

▪ IBM i 6.1 or later, with the current cumulative PTF level applied, is required.
▪ Installing or upgrading to iCluster 8.3 requires that the following IBM PTFs have been applied:
▫ IBM i 6.1 - SI55092
▫ IBM i 7.1 - SI55093
▫ IBM i 7.2 - SI55094
▫ IBM i 7.4 - SI72671, SI70837

• Upgrading from Rocket iCluster 7.1 or later

Upgrade from Rocket iCluster 7.1 or later.

Upgrading from Rocket iCluster 7.1 or later

Upgrade from Rocket iCluster 7.1 or later.

Prerequisites
Download the software and generate the license keys, as described in the previous section.

About this task

Complete these steps on each node.
The following only applies to replication of files with LOB fields by local journal groups.
▪ After iCluster replication is ended, before doing the upgrade, make sure that all transactions
involving files with LOB fields replicated by local journal groups are applied on the backup node.
To ensure this occurs, run the DMSTRAPY command on an active node:

DMSTRAPY GROUP(<LOB local journal group name>

▪ Alternatively, if it is not practical to apply all staged transactions, you may run the DMSETPOS
command for each local journal group replicating files with LOB fields before restarting replication
after the upgrade is complete:

DMSETPOS GROUP(<LOB local journal group name>)

JRN(<LOB journal library>/<LOB journalname>) JRNPOS(*LASTAPY)

Procedure
1. To end all group operations, enter the following command:
DMENDGRP GROUP(<group name>) OPTION(*CNTRLD)
2. To end each node, enter the following command:
DMENDNODE NODE(<node name>)
3. Exit the iCluster menus on all clients and terminals that are accessing the current installation.
4. To end the XDMCLUSTER subsystem, enter the following IBM i command:
ENDSBS SBS(XDMCLUSTER) OPTION(*IMMED)
5. Verify that locks do not exist on the ICLUSTER library and on objects in the ICLUSTER library.
6. Clear the QPRINT output queue in the ICLUSTER library and in the DMCLUSTER job queue in the
ICLUSTER library.
7. To ensure that the locks are released, sign off of the current node, and sign on again.

22
 Upgrading from Rocket iCluster 7.1 or later

8. Verify that the current library is not the ICLUSTER library. If required, change the current library.
9. To upgrade iCluster, use one of the following methods:
▪ To upgrade from a save file, enter the following command:

RSTLICPGM LICPGM(4RICLUS) DEV(*SAVF) OPTION(*BASE) SAVF(QGPL/CSBASE)

▪ To upgrade from physical media, enter the following command:

RSTLICPGM LICPGM(4RICLUS) DEV(<optical device>) OPTION(*BASE)

10. To add the license key to the product, enter the following command on each server:
ADDLICKEY PRDID(4RICLUS) LICTRM(V8R3) FEATURE(5050)
SERIAL(<xxxxxxx>) PRCGRP(P Group)
LICKEY(<xxxxxx yyyyyy zzzzzz>) USGLMT(*NOMAX) EXPDATE(*NONE)
VNDDTA(<Vendor Data provided by Rocket>)
where:
▪ <xxxxxxx> is the serial number of the IBM i server.
▪ <xxxxxx yyyyyy zzzzzz> is the iCluster license key.
▪ <P Group> is the IBM Power Systems Processor Group. To install iCluster installation as part of
Rocket iCluster HA Assist, specify *ANY.
▪ The VNDDTA field must be filled in with the Vendor Data that was provided to you by Rocket
Software when you were given the iCluster license key you are using on this command.
11. Verify the DDM server authentication environment. If DDM server authentication is used in your
environment, enable DDM access for the DMCLUSTER user profile. For more information, see
Enabling DDM access , on page 13.
12. If the QDFTOWN user profile owns objects in the ICLUSTER library, change the ownership
to the DMCLUSTER user profile. Ensure that the DMCLUSTER user profile parameter 'Limit
capabilities' (LMTCPB) is set to *NO.
13. To change the current library to ICLUSTER, enter the following IBM i command:
CHGCURLIB ICLUSTER
14. To restart the XDMCLUSTER subsystem from the current iCluster product library, enter the
following IBM i command:
STRSBS SBSD(XDMCLUSTER)
15. Repeat the steps on all nodes.
16. Ensure that you review the products and tools that use the iCluster metadata files. Use the latest
version of iCluster to recompile routines, CL programs, and other tools.
17. After the upgrade procedure is complete on all nodes, start the node that owns the iCluster
metadata first, and then start all other nodes. Enter the following command on the command line
for each node:
DMSTRNODE NODE(<node name>)
18. To resume replication for each group at the marked position, enter the following command:
DMSTRGRP GROUP(<group name>)
19. Optional: Register the access path lists that were created with the DMCRTAPLST—Create Access
Path List command in iCluster 7.1. See Registering access path lists, on page 24.
Parent topic: Upgrading iCluster

23
Chapter 2: Upgrading iCluster

Registering access path lists

After the upgrade is complete, register the access path lists that were created with iCluster 7.1. Access
path lists that are created in iCluster 7.1 TR1 or later are automatically registered.

About this task

Access path lists that were created with the DMCRTAPLST—Create Access Path List command in
iCluster 7.1 were not automatically registered with iCluster.

Procedure
1. Verify that the file and control data area of the access path list exist and meet the following
requirements:
▪ The file and control data area have the same name and library as the access path list.
▪ The file has only two fields that are named INDEXNAME and INDEXLIB. Each field is of type
CHAR and length 10.
▪ The file has a primary key on (INDEXNAME,INDEXLIB).
▪ The control data area is of *CHAR type and length 1.
2. Issue the following command:
DMREGAPLST APLST(<LIB>/<APL_LIST>) DESC('<DESC>')
where:
<lib> is the library name
<apl_list> is the access path list name
<desc> is an optional description of the purpose of the access path list, or describes the contents
of the access path list

Ending replication when groups do not use

commitment control
To end replication when groups do not use commitment control, use this procedure on every group in
the cluster.
1. To end all group operations, enter the following command:
DMENDGRP GROUP(<group name>) OPTION(*CNTRLD)
2. To drain the staging store library in the cluster, enter the following command:
DMSTRAPY GROUP(*ALL) FRCDRN(*YES)
3. To set the journal positions for restarting the groups, enter the following command:
DMSETPOS GROUP(<group name>) JRN(*ALL) JRNRCV(*CURCHAIN)
JRNPOSLRG(*LASTAPY)

Ending replication when groups use commitment

control
To end replication when groups use commitment control, use this procedure on every group in the
cluster.

24
 Ending replication when groups use commitment control

About this task

Ensure that open commitment control cycles in replication scope do not exist. The format of
uncommitted journal entries in the commitment control staging store is not compatible after the
upgrade.

1. To end all group operations, enter the following command:

DMENDGRP GROUP(<group name>) OPTION(*CNTRLD)
2. To drain the staging store library in the cluster, enter the following command:
DMSTRAPY FRCDRN(*YES)
The apply processes end automatically after the staging store is drained.
3. To set the journal positions for restarting the groups, enter the following command:
DMSETPOS GROUP(*ALL) JRN(*ALL) JRNRCV(*CURCHAIN)
JRNPOSLRG(*LASTAPY)
All journals, including the journals that are not involved in commitment control, are properly
processed for restarting replication.
4. Verify if commitment control cycles were open when you ended replication on the backup node.
In the staging store library, which is usually named DMSTORE, look for PF-DTA files that have file
names that begin with HACMT and end in five digits. The text description shows what group and
journal the file is for. There might be multiple files for the same group and journal, but not all of
the files contain records. For each file that contains records, find the starting journal position:
a. Use the last 20 bytes of the ID field (the journal sequence number) and the first 20 bytes of
the DATA field (journal receiver and receiver library) to determine the earliest journal entry.
b. Optional: If you have SQL, run the following SQL statement: SELECT SUBSTRING(ID,
11, 20) AS JRNPOS, SUBSTRING(DATA,1,20) AS RECEIVER FROM
<staging_store_library>/<file_name> ORDER BY SUBSTRING(ID, 11,
20).
The first record in the output has the earliest uncommitted journal sequence number
(JRNPOS field) and the journal receiver and receiver library for the position (RECEIVER field).
c. On the primary node, verify that the journal, journal receiver, and journal sequence number
are the same journals that were referenced in the PF-DTA files on the backup node.
d. Run the DMSETPOS—Set Journal Start Position command using the specific journal
sequence numbers with their receivers for these journals and the groups that use these
journals.
e. Run the DMSETSVAL—Set Cluster System Values command and set the Max. record level
errors physical file value to *NOMAX. You can reset this value after the journal entries are
applied to the open commitment control cycles on the backup nodes.
5. Clear the staging store library on the backup nodes with the IBM i Clear Library
(CLRLIB) command.

25
Chapter 3: Uninstalling iCluster
To uninstall iCluster, complete the following steps on each node:
1. Uninstalling the product and license keys
Delete the iCluster product and license keys to uninstall iCluster.
2. Removing the dmcluster entry from the TCP/IP service table
To make the TCP/IP port available to other products after iCluster is uninstalled, remove the
dmcluster service entry from the TCP/IP service table.

Uninstalling the product and license keys

Delete the iCluster product and license keys to uninstall iCluster.
Complete the following steps on each node:

1. To end group operations, enter the following command for each group:
DMENDGRP GROUP(<group name>) OPTION(*CNTRLD)
2. To end the nodes, enter the following command:
DMENDNODE NODE(<node name>)
3. To end the XDMCLUSTER subsystem, enter the following IBM i command:
ENDSBS SBS(XDMCLUSTER) OPTION(*IMMED)
4. Verify that locks do not exist on the ICLUSTER library and on objects in the ICLUSTER library.
5. To uninstall the iCluster product and license keys, enter the following IBM i command:
DLTLICPGM LICPGM(4RICLUS) OPTION(*ALL)
6. To confirm the uninstallation, complete these steps:
a. Enter the following IBM i command: go licpgm.
b. To display installed licensed programs, use option 10.
c. Verify that the Rocket iCluster product is not listed as a licensed program.
Next topic: Removing the dmcluster entry from the TCP/IP service table
Parent topic: Uninstalling iCluster

Removing the dmcluster entry from the TCP/IP service

table
To make the TCP/IP port available to other products after iCluster is uninstalled, remove the
dmcluster service entry from the TCP/IP service table.
1. Sign on as the QSECOFR user profile or as a user with *SECOFR special authority.
2. Enter the following IBM i command: CFGTCP.
3. Type 21 to configure related tables, and press Enter.
4. Type 1 to work with service table entries, and press Enter.
5. Press PgDn to find the dmcluster service item.
6. In the Opt field for the dmcluster service, type 4.

26
 Removing the dmcluster entry from the TCP/IP service table

Alternatively, you can use the following equivalent command:

RMVSRVTBLE SERVICE(dmcluster) PORT(<port number>) PROTOCOL(*TCP)

Previous topic: Uninstalling the product and license keys

Parent topic: Uninstalling iCluster

27
Index
A system requirements.............................................................. 5

access path lists

registering..............................................................................24
I
audit journal IBM Restore License Program (RSTLICPGM) command
creating....................................................................................7 installing iCluster.................................................................... 8
authentication iCluster
DMCLUSTER user profile.......................................................13 starting...................................................................................15
registered iCluster user........................................................ 13 installation
secure DDM............................................................................13 creating typical..................................................................... 16
server entries.........................................................................13 iCluster.....................................................................................8
overview...................................................................................8
C planning...................................................................................5
verifying................................................................................. 19
cluster system values
changing................................................................................ 18
communication protocol
J
requirements........................................................................... 5 journal receivers
configuration creating....................................................................................7
automatic.............................................................................. 16
customer support
contacting................................................................................3 L
legal notices................................................................................ 2
D license keys
adding...................................................................................... 8
DDM generating......................................................................... 7, 21
authenticating....................................................................... 13 obtaining..................................................................................7
Delete Licensed Program (DLTLICPGM) command RSTLICPGM (Restore License Program) command............... 8
uninstalling iCluster..............................................................26
disk space
requirements........................................................................... 5 M
DLTLICPGM (Delete Licensed Program) command
memory pools
uninstalling iCluster..............................................................26
configuring...............................................................................6
DMCLUSTER
command...............................................................................15
O
E operating system
setting values.......................................................................... 6
Edit Object Authority (EDTOBJAUT) command
operating system values
authorizing users.................................................................. 11
configuring QSTRUPPGM......................................................15
EDTOBJAUT (Edit Object Authority) command
authorizing users.................................................................. 11
P
F postinstallation tasks
overview...................................................................................9
failover
product ID
configuring.............................................................................16
iCluster.....................................................................................8

G
R
group profiles
replication
registering..............................................................................10
ending.............................................................................. 24, 24
Restore License Program (RSTLICPGM) command
H installing iCluster.................................................................... 8
Rocket Software
hardware contacting................................................................................3

28
 Index

RSTLICPGM (Restore License Program) command

installing iCluster.................................................................... 8

S
secure DDM
authenticating....................................................................... 13
shutdown
scheduling............................................................................. 15
software
downloading..................................................................... 7, 21
installing.................................................................................. 8
requirements........................................................................... 5
software license keys
obtaining..................................................................................7
software support
contacting................................................................................3
startup
scheduling............................................................................. 15
STRSBS command
starting subsystems.............................................................. 15
subsystems
starting...................................................................................15
support
contacting................................................................................3
system requirements
communication protocol........................................................5
disk space................................................................................ 5
hardware..................................................................................5
software................................................................................... 5
system values
changing default................................................................... 18
changing failover mechanism.............................................. 16

T
TCP/IP service table
adding dmcluster entry........................................................ 12
removing dmcluster entry.................................................... 26
technical support
contacting................................................................................3
trademarks.................................................................................. 2
troubleshooting
contacting technical support................................................. 3

U
uninstalling
iCluster...................................................................................26
upgrade
from 7.1 or later.................................................................... 22
overview.................................................................................21
user profiles
registering..............................................................................10
users
adding.................................................................................... 10
authorizing product use....................................................... 11
DDM authentication.............................................................. 13
registering..............................................................................10

29