Académique Documents
Professionnel Documents
Culture Documents
Version 6.1
End-user documentation
Table of Contents
Table of Contents
About Transformation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Installing Transformation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Specifying Transformation Server Product Library Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Specifying D_MIRROR User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Previous Installation of Transformation Server and Existing D_MIRROR User Profile . . . . . . . . . . . . . .15
Port Requirements for Transformation Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Installing Transformation Server for AS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Step 1—Sign on with authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Step 2—Restore the installation program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Step 3—Run the Installation Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Step 4—Specify CD ROM Device Name or Save File Information . . . . . . . . . . . . . . . . . . . . . . . . 17
Step 5—Select D_Mirror User Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Step 6—Accept the Software License Agreement and Start the Installation . . . . . . . . . . . . . . . . . 19
Step 7—Specify the Authorization Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Step 8—Specify Product and Tutorial Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Step 9—Specify a Full Product Installation or Only Work Library Installation . . . . . . . . . . . . . . . . 20
Step 10 (Optional)—Specify Product and Tutorial Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
After You Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Configuring Transformation Server to use TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Verifying the Configuration of Your Domain Name Server (DNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Verifying Journal and Journal Receiver Authorities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
To verify the journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
To verify journal receivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Starting the Subsystem and the Listener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Securing Transformation Server Product Library (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Scheduling Transformation Server Start Up and Shut Down (Optional) . . . . . . . . . . . . . . . . . . . . . . . . .26
To schedule Transformation Server to start up or shut down automatically . . . . . . . . . . . . . . . . . 26
Upgrading Transformation Server for AS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Before You Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Upgrading Transformation Server for AS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Updating Transformation Server for AS/400 to the Latest Service Pack. . . . . . . . . . . . . . . . . . . . . . . . .29
To update Transformation Server for AS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Creating Multiple Installations of Transformation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Creating Multiple Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
To create multiple installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Verifying Additional Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
To verify the authority of the D_MIRROR User Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Software Requirements
Operating System: OS/400 V4R4 or greater
For correct product operation, you may require Program Temporary Fixes (PTFs). Contact IBM for PTF information for your
operating system.
Related Topics
• D_MIRROR User Profile considerations for remote journals on page 41
Related Topics
• Installing Management Console, see Transformation Server Management Console Administration Guide
• Installing Access Manager, see Transformation Server Access Manager Configuration Guide
• Connecting to a datastore, see Transformation Server Management Console Administration Guide
• Defining a subscription, see Transformation Server Management Console Administration Guide
• Detecting Available Replication Agents on your Network with Auto-Discovery, see Transformation Server Access Manager
Configuration Guide
Device Name The device (CD ROM device name) OR save file (*SAVF) that you are using to run the
installation program.
If you are restoring the installation program from a save file, then enter the following information:
Library Name The name of the library where the save file is located. You must transfer the save file to this
library.
Library Name The library name where the save file for the tutorial tables is located. You must transfer the
save file to this library. You can also enter *LIBL to specify the set of libraries in your list. The
installation program searches libraries in order of the first occurrence of the specified library.
This screen indicates that the installation program has detected the existence of the D_MIRROR user profile. This user profile
may exist through a previous installation of Transformation Server. Transformation Server requires that the D_MIRROR user
profile be configured properly for Version 6.1. Use this screen to determine if you want to configure the D_MIRROR user profile.
Press one of the following keys:
F2 Leaves the D_MIRROR user profile unchanged. If the user profile was created during an
installation of a previous Transformation Server version, and its configuration has not been
changed, then the user profile should still be valid for Version 6.1.
F3 Cancels the installation. You may want to cancel the installation to verify that you have
configured the user profile.
You can verify whether or not the user profile is configured properly by issuing the following
command:
DSPUSRPRF USRPRF(D_MIRROR)
Verify that the following parameters are set to the indicated values:
• Special authority: *JOBCTL
• Password: *NONE
• Password expiration: *NO
• Message queue: QUSRSYS/D_MIRROR
Step 6—Accept the Software License Agreement and Start the Installation
The Software Licensing Agreement screen appears.
Press F2 to accept the terms expressed in the DataMirror software license agreement and start the installation.
Press Enter to continue.
Authorization Code The Transformation Server authorization code, as provided by DataMirror Technical Support
or obtained from the DataMirror web site.
DTS/400 Product Library The name of the library where you want to install Transformation Server. The default product
library is DMIRROR. If you specified the name of an existing library, proceed to Step 10
(Optional)—Specify Product and Tutorial Libraries on page 21.
DTS/400 Tutorial Library The name of the library where you want to install the tutorial tables (optional).
DTS/400 IASP Device The name of your Independant Auxiliary Storage Pool (IASP) device where you want to
install Transformation Server. Enter the name of the IASP device if you want to install
Transformation Server on an IASP. If you do not have an ASP device, then accept the default
value as *SYSBAS.
You must install Transformation Server and the tutorial tables into different libraries. The default tutorial library is DTUTOR.
Press Enter to install Transformation Server on your server.
Note: The installation program creates the specified library and installs Transformation Server on your system. After
the installation has been completed, a final message is generated to indicate whether or not the installation
was successful. If the installation was unsuccessful, error messages are placed in the job log. Use the
DSPJOBLOG command to identify the errors and take the necessary corrective actions before running the
installation program again.
F (Full product installation) Installs Transformation Server for AS/400 product into the specified IASP device and
required support objects (*SBSD, *CLSD, and *JOBQ) into a work library on the system ASP
of the machine currently connected to the IASP device.
W (Work library only) Only installs the required support objects (*SBSD, *CLSD, and *JOBQ) into the work library
on the system ASP of the machine that is connected to the IASP device. Specify this option if
you already have a full product installation of Transformation Server for AS/400 on the
connected IASP device. You can also specify this option when you have implemented a
switchable IASP environment and require another copy of the work library on a secondary
machine.
The installation program automatically creates the work library. The name of the work library
is the first eight characters of your product library appended with 01. For example,
TS60SP101. If the library exists, then the installation program ends.
Replace Specified The name of the library where you want to install Transformation Server. The default product
Library library is DMIRROR. Enter Y if you want to install Transformation Server in the specified
product library, or N if you want to install into a different library. If you entered N, specify the
name of a different library.
Selecting Y deletes all existing contents of this library.
Service ‘dmirror’
(in single quotes)
Protocol ‘tcp’
(in single quotes)
Related Topics
• To verify the journal on page 25
• To verify journal receivers on page 25
Related Topics
• To schedule Transformation Server to start up or shut down automatically on page 26
Device Name The device (CD ROM device name) OR *SAVF that you are using to run the installation
program.
If you are restoring the installation program from a save file, then enter the following information:
Library Name The name of the library where the save file is located. You must transfer the save file to this
library.
Library Name The library name where the save file for the tutorial tables is located. You must transfer the
save file to this library. You can also enter *LIBL to specify the set of libraries in your list. The
installation program searches libraries in order of the first occurrence of the specified library
If the D_MIRROR user profile does not exist in the QSYS library on the server where Transformation Server is being installed,
proceed to Step 4—Accept the Software License Agreement on page 29.
Related Topics
• To update Transformation Server for AS/400 on page 29
Related Topics
• Step 1—End All Transformation Server Version 6.0 Replication on page 27
• Step 2—End All Online Transformation Server Version 6.0 Activities on page 27
• Step 3—Save Transformation Server Version 6.0 Metadata on page 27
Related Topics
To create multiple installations on page 31
Related Topics
• Installing Transformation Server for AS/400 on page 17
Related Topics
• To verify the authority of the D_MIRROR User Profile on page 32
• To verify the attributes of the renamed subsystems on page 32
• To verify the library list of each additional installation on page 33
QSECOFR *ALL X X X X
*PUBLIC *EXCLUDE
Related Topics
To run the additional installations on page 33
Related Topics
• Step 1—Sign on with authorities on page 17
• Step 1—End All Transformation Server Version 6.0 Replication on page 27
• Step 2—End All Online Transformation Server Version 6.0 Activities on page 27
The following sections refer to the system where your local journals reside as the Data Origin Server and refer to the system
where your remote journals reside as the Source Server.
In this section, you will learn:
• About Installing Transformation Server for AS/400 on the Data Origin Server on page 40
• About Installing Transformation Server for AS/400 on the Source Server on page 40
• About Installing Transformation Server on the Target Server on page 41
• Verifying the creation of the SQL package on the TS/400 Data Origin Server on page 41
• D_MIRROR User Profile considerations for remote journals on page 41
• Configuring Remote Journaling on page 42
• Configuring TS/400 Source Server to retrieve source files from the TS/400 Data Origin Server on page 43
Related Topics
• To install Transformation Server for AS/400 on a Data Origin Server, see the steps in Installing Transformation Server for
AS/400 on page 17
• After installing Transformation Server for AS/400 on each system, make sure you start the subsystem and the listener, see
Starting the Subsystem and the Listener on page 25
Related Topics
• To install Transformation Server for AS/400 on a Source Server, see the steps in Installing Transformation Server for AS/400
on page 17
• After installing Transformation Server for AS/400 on each system, make sure you start the subsystem and the listener, see
Starting the Subsystem and the Listener on page 25
Related Topics
• If you have installed Transformation Server for AS/400 on the Target Server, make sure you start the subsystem and the
listener, see Starting the Subsystem and the Listener on page 25
Verifying the creation of the SQL package on the TS/400 Data Origin Server
After installing Transformation Server for AS/400 on the Data Origin Server, Source Server, and installing a Transformation Server
product on the Target Server, you need to ensure that a SQL package named ‘DMS125SQL’ in the QGPL folder on the TS/400
Data Origin Server is created. When you start a refresh on the TS/400 Source Server, Transformation Server attempts to create
this object if it does not exist and uses the SQL package to retrieve data from the source files on the TS/400 Data Origin Server.
Related Topics
• Installing and Configuring Transformation Server to Replicate Data from a Remote Journal on page 39
Related Topics
• Specifying D_MIRROR User Profile on page 15
• Installing and Configuring Transformation Server to Replicate Data from a Remote Journal on page 39
5 On the TS/400 Data Origin Server, activate the remote journal by running the CHGRMTJRN command with the
JRNSTATE(*ACTIVE) parameter. For example, the following command activates the remote journal:
> CHGRMTJRN RDB(NEWYORK) SRCJRN(TORLIB/MYJRN) TGTJRN(NYLIB/MYJRN)
JRNSTATE(*ACTIVE)
Related Topics
• About Installing Transformation Server for AS/400 on the Data Origin Server on page 40
• About Installing Transformation Server for AS/400 on the Source Server on page 40
Configuring TS/400 Source Server to retrieve source files from the TS/400
Data Origin Server
After adding a remote journal and installing Transformation Server for AS/400 on the Source Server, you must do the following on
the Source Server:
• Add a relational database directory entry—This relational database directory entry must reference the Data Origin Server.
• Enable Transformation Server to retrieve source files from the Data Origin Server—Using system parameters, you can
configure Transformation Server to use the IP address/hostname and port number of the Data Origin Server and to use the
relational database directory entry that references this server.
Before configuring Transformation Server to retrieve source files from the Data Origin Server, make sure you have:
• Installed Transformation Server for AS/400 on both the Data Origin Server and the Source Server. The following procedures
refer to these systems as the TS/400 Data Origin Server and the TS/400 Source Server.
• Ensure that the iSeries user profile for both the Data Origin Server and the Source server have the same name. You will use
this user profile to connect to the replication agent you created on the Source server.
Related Topics
• To add a replication agent in Access Manager, see Transformation Server Access Manager Configuration Guide.
• To connect to a replication agent in Access Manager, see Specifying Database Access Parameters in the Transformation
Server Access Manager Configuration Guide.
To add a relational database directory that references the Data Origin Server
1 On the TS/400 Source Server, add a relational database directory entry that references the database where the source files
reside on the TS/400 Data Origin Server by running the ADDRDBDIRE command. For example, if the name of the database
on the TS/400 Data Origin Server is TORONTO, then the following command creates this relational database directory entry:
> ADDRDBDIRE RDB(TORONTO) RMTLOCNAME(192.168.0.15)
2 On the TS/400 Data Origin Server, add a relational database entry that references the local database where the source files
reside by running the ADDRDBDIRE command. For example,
> ADDRDBDIRE RDB(TORONTO) RMTLOCNAME(*LOCAL)
Related Topics
• About Installing Transformation Server for AS/400 on the Data Origin Server on page 40
• About Installing Transformation Server for AS/400 on the Source Server on page 40
To enable the TS/400 Source Server to retrieve source files from the TS/400 Data Origin Server
1 Ensure you have already created a publisher-type replication agent for TS/400 Source Server. You can create replication
agents in Access Manager. This replication agent will use the IP address/hostname and port number of the TS/400 Source
Server.
2 Start Transformation Server Management Console and connect to the publisher-type replication agent (displayed as a
datastore) you created in Access Manager.
3 Add the following system parameters for the publisher-type replication agent (source datastore) you connected to:
• Data Origin TCP/IP Name—Specify the IP address or hostname of the TS/400 Data Origin Server. This enables
Transformation Server (installed on the TS/400 Source Server) to use the IP address of the TS/400 Data Origin Server.
For example, the IP address of the TS/400 Data Origin Server is ‘192.168.0.15’. This is the value you would enter for
Data Origin TCP/Name system parameter.
• Data Origin Port—Specify the TCP listener port number of the TS/400 Data Origin Server. This enables Transformation
Server (installed on the TS/400 Source Server) to use the port number of the TS/400 Data Origin Server.
For example, the port number of the TS/400 Data Origin Server is ‘10101’. This is the value you would enter for Data
Origin Port system parameter.
• Relational Database Directory Entry—Specify the relational database directory entry that you added for
Transformation Server (installed on the TS/400 Source Server). This entry should reference the TS/400 Data Origin
Server.
For example, the relational database directory that references the database where the source files reside is ‘TORONTO’.
This is the value you would enter for Relational Database Directory Entry system parameter.
The following diagram illustrates the system parameters you need to set on the Source System so that Transformation Server for
AS/400 can retrieve source data on the Data Origin Server and the systems Management Console is connected to.
Related Topics
• To install and start Access Manager, see Transformation Server Access Manager Installation Guide.
• To create a replication agent, see Adding a New Replication Agent in Transformation Server Access Manager Configuration
Guide.
• To install and start Transformation Server Management Console, see Installing Management Console in the Transformation
Server Management Console Administration Guide.
• To connect to a datastore, see Connecting to a datastore in Transformation Server Management Console Administration
Guide.
• To add system parameters, see Adding System Parameters in Transformation Server Management Console Administration
Guide.
• For more information about the Data Origin TCP/IP Name system parameter, see Data Origin TCP/IP Name on page 134.
• For more information about the Data Origin Port system parameter, see Data Origin Port on page 134.
• For more information about the Relational Database Directory Entry system parameter, see Relational Database Directory
Entry on page 134.
Related Topics
• For more information about the Change Journal Receiver command, see CHGJRNDM—Change Journal Receivers on
page 90.
• For a description of the Data Origin Server and Source Server , see About Installing Transformation Server for AS/400 on the
Data Origin Server and About Installing Transformation Server for AS/400 on the Source Server on page 40.
Related Topics
• For more information about the Retrieve Transformation Server Journal Entry command, see RTVDMJENT—Retrieve
Transformation Server Journal Entry on page 94.
• For a description of the Data Origin Server and Source Server, see About Installing Transformation Server for AS/400 on the
Data Origin Server and About Installing Transformation Server for AS/400 on the Source Server on page 40.
Related Topics
• For more information about the Retrieve Transformation Server Journal Entry command, see VFYTSJRN—Verify Journal on
page 94.
• For a description of the Data Origin Server and Source Server, see About Installing Transformation Server for AS/400 on the
Data Origin Server and About Installing Transformation Server for AS/400 on the Source Server on page 40.
Conventions
• Underline ( ___ ) indicates mandatory parameters..
• Square brackets ( [ ] ) indicate an optional parameter sequence. If a parameter sequence is omitted, one or more default
values may be used.
• Braces ( { } ) group multiple parameters together.
• A vertical bar ( | ) indicates that only one of the parameters in the list can be selected. When one or more vertical bars appear
in a list of parameters that is enclosed by square brackets ( [ ] ), the choices are limited to the parameters in the list, but you
have the option to not specify any of the parameter sequences.
• Ellipsis ( ... ) mean that a parameter or option can be repeated more than once.
Replication Commands
In this section, you will learn about commands that control replication:
• ENDDTAMIR—End Continuous Mirroring on page 53
• ENDDTAMIR—End Net Change Mirroring on page 54
• ENDDTARSH—End Data Refresh on page 55
• STRDTARSH—Start Data Refresh on page 55
• STRDTAMIR—Start Continuous Mirroring on page 56
• STRDTAMIR—Start Net Change Mirroring on page 58
Parameter Description
ENDTYP Indicates how you want to end replication. You can end replication immediately or when
Transformation Server completes replication (controlled).
Enter one of the following:
• *CNTRLD (controlled): Replication is ended when Transformation Server completes
replication. This is the recommended setting.
• *IMMED (immediate): Mirroring is ended immediately. Use this setting only if you
cannot end data mirroring in a controlled manner.
Default Setting
*CNTRLD
Result
Messages are placed in the Event Log.
Examples
• ENDDTAMIR TARGET(SUB1)
Transformation Server ends continuous mirroring on source tables selected to subscription SUB1 in a controlled manner.
• ENDDTAMIR TARGET(SUB1) ENDTYP(*IMMED)
Transformation Server ends continuous mirroring on source tables selected to subscription SUB1 immediately.
• ENDDTAMIR TARGET(*ALL) ENDTYP(*IMMED)
Transformation Server ends continuous mirroring of source tables to all subscriptions immediately.
Parameter Description
ENDTYP Indicates how you want to end replication. You can end replication immediately or when
Transformation Server completes replication (controlled).
Enter one of the following:
• *CNTRLD (controlled): Replication is ended when Transformation Server completes
replication. This is the recommended setting.
• *IMMED (immediate): Mirroring is ended immediately. Use this setting only if you
cannot end data mirroring in a controlled manner.
Default Setting
*CNTRLD
• ENDDTAMIR TARGET(SUB1)
Transformation Server ends net-change mirroring on subscription SUB1 in a controlled manner.
• ENDDTAMIR TARGET(SUB1) ENDTYP(*IMMED)
Transformation Server ends net-change mirroring on subscription SUB1 immediately.
• ENDDTAMIR TARGET(*ALL) ENDTYP(*IMMED)
Transformation Server ends net-change mirroring on subscriptions immediately.
Parameters Description
ENDTYP Indicates how you want to end replication. You can end replication immediately or when
Transformation Server completes replication (controlled).
Enter one of the following:
• *CNTRLD (controlled): Specifies a controlled end to a refresh. This is the recommended
setting.
• *IMMED (immediate): Transformation Server ends a refresh immediately.
Default Setting
*CNTRLD
Result
None
Examples
• ENDDTARSH TARGET(SUB1)
Transformation Server ends the refresh on subscription SUB1 end in a controlled manner.
• ENDDTARSH TARGET(SUB1) ENDTYP(*IMMED)
Transformation Server ends the refresh on subscription SUB1 immediately.
• ENDDTARSH TARGET(*ALL) ENDTYP(*IMMED)
Transformation Server ends the refresh on all subscriptions immediately.
Depending on the value set for the Allow Refresh While Active system parameter, Transformation Server can allocate and
exclude source tables until it completes a refresh operation. This ensures complete synchronization between the source and
target tables. As a result, you should schedule a refresh so as not to interfere with normal operations. For more information about
the Allow Refresh While Active system parameter, see the Allow Refresh While Active on page 131.
Command Syntax
STRDTARSH TARGET( ) [TABLES( )]
Parameters Description
Result
Messages are placed in the Event Log.
Examples
• STRDTARSH TARGET(SUB1)
Transformation Server refreshes all target tables that have a status of Refresh on subscription SUB1.
• STRDTARSH TARGET(SUB1) TABLES(*ALL)
Transformation Server refreshes all target tables on subscription SUB1.
• STRDTARSH TARGET(*ALL) TABLES(*FLAG)
Transformation Server refreshes all target tables flagged for a refresh on all subscriptions.
Applies To
Source
Parameters Description
IDLE Specifies the action that Transformation Server will take when it determines that all available
data has been replicated to the target.
Enter one of the following values:
• *WAIT
Transformation Server replication process remains active after all changes are replicated
to the target.
• *END
Transformation Server replication process ends after all changes are replicated to the
target.
Default Setting—*WAIT
Result
Messages are placed in the Event Log.
Examples
• STRDTAMIR TARGET(SUB1)
Starts continuous mirroring on subscription SUB1. Transformation Server starts continuous mirroring on tables that have a
replication method set to mirroring, and a table status set to Refresh or Active. Transformation Server continues to monitor the
journal for activity after all available data has been mirrored.
• STRDTAMIR TARGET(SUB1) IDLE(*WAIT) FORMAT(*NO)
Starts continuous mirroring on subscription SUB1. Tranformation Server starts continuous mirroring of tables that have a
replication method set to mirroring, and a table status set to Refresh or Active. Transformation Server continues to monitor the
journal for activity after all available data has been mirrored.
Parameters Description
Parameters Description
IDLE Specifies the action that Transformation Server will take when it determines that all available
data has been replicated to the target.
Enter one of the following values:
• *WAIT
Transformation Server replication process will remain active after all changes have been
replicated.
• *END
Transformation Server replication process will end after all changes have been
replicated.
Default Setting—*WAIT
Note: If you want to start net-change mirroring, you must specify *END.
Examples
• STRDTAMIR TARGET(SUB1) IDLE(*END)
Transformation Server starts net change mirroring on subscription SUB1. All Transformation Server processes end after all
available data has been mirrored.
• STRDTAMIR TARGET(SUB1) IDLE(*END) FORMAT(*NO)
Transformation Server starts net change mirroring on subscription SUB1. All Transformation Server processes end after all
available data has been mirrored.
• STRDTAMIR TARGET(*ALL) IDLE(*END) FORMAT(*NO)
Transformation Server starts net change mirroring on all subscriptions. All Transformation Server processes end after all
available data has been mirrored.
ADDTBL—Add Tables
Use this command to add source tables to the catalog for possible replication. You can add individual tables, generic groups of
tables, or all tables within a library with a single execution of this command. After adding the tables you want to replicate, you need
to select the table for replication using the SLTTGTTBL command. For more information, see the SLTTGTTBL—Select Source
Tables for Replication on page 69. You can remove added tables by using the RMVTBL command. For more information, see the
RMVTBL—Remove Tables on page 64.
Command Syntax
ADDTBL TABLE()
Applies To
Source
Parameters Description
TABLE The name of the source table to add to the Source Tables area in Management Console.
Enter the name of a table, a generic name (for example, abc* specifies all tables starting with
abc), or the following value:
*ALL – Specifies all source tables in the library.
The name of the library where the table resides must precede the source table specification.
For example, PRODLIB/CUSTOMER.
Result
Relevant messages are produced to the job log.
Examples
ADDTBL TABLE(PRODLIB/CUSTOMER)
Adds the source table named CUSTOMER that resides in library PRODLIB to the catalog.
ADDTBL TABLE(DTUTOR/*ALL)
Adds all source tables that reside in library DTUTOR to the catalog.
Parameters Description
Default Setting
Not Applicable
Result
The next time you start replication, Transformation Server applies data using the new replication method. When you issue this
command, you should see the appropriate messages in the Event Log.
Examples
• CHGREPMTD TARGET(SUB1) TABLE(DTUTOR/CUSTOMER) REPMTD(*REFRESH) UPDMTD(*KEYED)
The source table CUSTOMER (in library DTUTOR) has its replication method changed to *REFRESH in the subscription
(SUB1).Transformation Server will update the target table using unique keyed access paths. Since the replication method is
*REFRESH, this parameter is not applicable in this command invocation.
• CHGREPMTD TARGET(SUB1) TABLE(DTUTOR/*ALL) REPMTD(*MIRROR) UPDMTD(*KEYED)
All source tables (in library DTUTOR) have their replication methods changed to *MIRROR in the subscription (SUB1).
Transformation Server will update the target table using unique keyed access paths.
• CHGREPMTD TARGET(SUB1) TABLE(DTUTOR/SALES) REPMTD(*MIRROR) UPDMTD(*RRN)
The source table SALES (in library DTUTOR) has its replication method changed to *MIRROR in the subscription (SUB1).
Transformation Server will update the target table using its relative record number.
Parameters Description
TARGET The name of the subscription, as defined in Management Console, to which the source table
is selected. For information about subscriptions, see the Transformation Server Management
Console Administration Guide.
TABLE The name of the source table that is de-selected from the subscription.
Enter the name of a table, a generic name (for example, abc* specifies all tables
starting with abc), or the following value:
*ALL – Specifies all tables in the library that are selected to the subscription.
The name of the library where the table resides must precede the source table
specification.
Result
Relevant messages are produced to the job log.
Examples
DSLTGTTBL TARGET(SUB1) TABLE(DTUTOR/*ALL)
All source tables in library DTUTOR selected to subscription SUB1 are deTransformation selected.
DSLTGTTBL TARGET(SUB1) TABLE(DTUTOR/CUSTOMER)
Parameters Description
TABLE The name of the source table that you have updated and want to make available for
replication by either:
• Adding it Transformation Server metadata (using the command line).
• Adding it to the source tables area in the Transformation Server Management Console
(using the Management Console GUI).
LIB The name of the library in which the updated source table resides.
Result
Transformation Server adds the source table to the metadata table. If you are using
Transformation Server Management Console, you should see the table in the Source Tables area. Also, when you issue this
command, you should see relevant messages in the Event Log.
Examples
READDTBL TABLE(MYSRCTABLE) LIB(MYLIB)
Changes the definition of MYSRCTABLE which resides in MYLIB.
RMVTBL—Remove Tables
Use this command to remove source tables that were added to a catalog for possible replication. For more information about
adding tables, see the ADDTBL command. You can remove individual tables, generic groups of tables or all tables in a library with
a single execution of this command. Only source tables that have been added are considered when you issue this command.
Before using this command to remove the source tables, you should de-assign target tables and de-select source tables. For
more information about deassigning tables, see the DASTGTTBL—Unmap Source and Target Tables on page 77. For more
information about deselecting tables, see the DSLTGTTBL—Deselect Source Tables on page 63.
Command Syntax
RMVTBL TABLE( ) [ENDJRN( )]
Applies To
Source
Parameters Description
TABLE The name of the source table that is removed from the catalog.
Enter the name of a table, a generic name (for example, abc* specifies all tables
starting with abc), or the following value:
*ALL – Specifies all added tables in the library.
The name of the library where the table resides must precede the source table
specification.
ENDJRN Indicates whether or not journaling to the default Transformation Server journal should
stop or continue for the specified table.
Specify one of the following values:
Y – Specifies that journaling stop for the specified table.
N – Specifies that journaling continue for the specified table.
Default Setting: Y
This parameter does not have any effect if a user-defined journal, as opposed to the
default journal, is being used.
Result
Relevant messages are sent to the job log.
Examples
RMVTBL TABLE(DTUTOR/SALES)
Source table SALES in library DTUTOR is removed from the catalog.
Journaling is stopped for the SALES table.
RMVTBL TABLE(DTUTOR/*ALL) ENDJRN(Y)
All added source tables in library DTUTOR are removed from the catalog.
Journaling is stopped for the removed source tables in library DTUTOR.
RMVTBL TABLE(DTUTOR/CUSTOMER) ENDJRN(N)
Source tableublication table CUSTOMER in library DTUTOR is removed from the catalog.
Journaling continues for the CUSTOMER table.
Source
Parameters Description
IDLE Specifies the action that Transformation Server will take when it determines that all definitions
have been sent to the subscription.
Enter one of the following values:
• *WAIT
Transformation Server will remain active after all source tables have been described.
• *END
Transformation Server will end after all source tables have been described.
Default Setting—*WAIT
Result
None.
Examples
• STRDTAMIR TARGET(SUB1) IDLE(*END) FORMAT(*ONLY)
Sends definitions of all source tables selected to subscription SUB1. After the transfer has been completed, all Transformation
Server jobs end.
• STRDTAMIR TARGET(*ALL) IDLE(*END) FORMAT(*ONLY)
Sends definitions of all source tables selected to all subscriptions. After the transfer has been completed, all Transformation
Server jobs end.
Command Syntax
SETMIRSTS TARGET() TABLE() [STATUS()]
Applies To
Source
Parameters Description
Result
Transformation Server changes the status of a source table you set for mirroring to either idle, refresh, or active. You should
also receive the apprioprate messages in the Event Log.
Examples
• SETMIRSTS TARGET(SUB1) TABLE(DTUTOR/SALES)
Sets the status of the selected source table SALES (in library DTUTOR) to Refresh (*RFSH). The status change applies to the
SALES source table selected to the subscription SUB1 for mirroring.
• SETMIRSTS TARGET(SUB1) TABLE(PRODLIB/CUSTOMER) STATUS(*ACTV)
Sets the status of the selected source table CUSTOMER (in library PRODLIB) to Active (*ACTV). The status change applies
to the CUSTOMER source table selected to the subscription SUB1 for mirroring.
• SETMIRSTS TARGET(*ALL) TABLE(PRODLIB/CUSTOMER) STATUS(*IDLE)
Sets the status of the selected source table CUSTOMER (in library PRODLIB) to Idle (*IDLE). The status change applies to all
CUSTOMER source tables selected to any subscription for mirroring.
• SETMIRSTS TARGET(*ALL) TABLE(*ALL/*ALL) STATUS(*RFSH)
Sets the status of all selected source tables (in all libraries) to Refresh (*RFSH). The status change applies to all source tables
selected to any subscription for mirroring.
Parameters Description
Result
None
Examples
• SETRSHSTS TARGET(SUB1) TABLE(DTUTOR/SALES)
Sets the status of the selected source table SALES (in library DTUTOR) to Refresh (*RFSH). The status change applies to the
SALES source table selected to subscription SUB1 for refresh.
• SETRSHSTS TARGET(SUB1) TABLE(PRODLIB/CUSTOMER) STATUS(*IDLE)
Sets the status of the selected source table CUSTOMER (in library PRODLIB) to Idle (*IDLE). The status change applies to
the CUSTOMER source table selected to subscription SUB1 for refresh.
• SETRSHSTS TARGET(*ALL) TABLE(PRODLIB/CUSTOMER) STATUS(*RFSH)
Sets the status of the selected source table CUSTOMER (in library PRODLIB) to Refresh (*RFSH). The status change applies
to all CUSTOMER source tables selected to any subscription for refresh.
• SETRSHSTS TARGET(*ALL) TABLE(*ALL/*ALL) STATUS(*RFSH)
Sets the status of all selected source tables (in all libraries) to Refresh (*RFSH). The status change applies to all source tables
selected to any subscription for refresh.
Source
Parameters Description
UPDMTD The update method Transformation Server uses to apply mirrored data to the target. This
parameter applies only if you selected mirroring for the source table.
Enter one of the following values:
• *KEYED
Indicates that Transformation Server is applying data is using unique access paths.
• *RRN
Indicates that Transformation Server is applying data using relative record numbers.
Parameters Description
ROWSELEXP The row selection expression that determines which rows in the source table are replicated.
You must enter a row selection expression based on columns in the source table.
Result
Messages are sent to the Event Log.
Examples
• SLTTGTTBL TARGET(SUB1) TABLE(DTUTOR/*ALL) REPMTD(*MIRROR) UPDMTD(*KEYED) INITSTS(*ACTIVE)
Selects all source tables (in library DTUTOR) to subscription SUB1. The replication method for the tables is mirroring. The
update method is by unique access paths. The initial status for the tables is Active (*ACTIVE). This means that an initial
refresh is not performed before mirroring begins. A row selection expression is not defined for each source table in library
DTUTOR.
• SLTTGTTBL TARGET(SUB1) TABLE(DTUTOR/AP*) REPMTD(*MIRROR) UPDMTD(*RRN) INITSTS(*REFRESH)
ROWSELTYP(*OMIT) ROWSELEXP("STATE =NY")
Selects all source tables starting with the letters AP (in library DTUTOR) to subscription SUB1. The replication method for the
tables is mirroring. The update method is by relative record number. The initial status for the tables is Refresh (*REFRESH).
This ensures that the table is refreshed before mirroring begins. A row selection expression is defined for each source table.
Only rows in the source tables where STATE is not set to NY are replicated.
• SLTTGTTBL TARGET(SUB1) TABLE(DTUTOR/CUSTOMER) REPMTD(*REFRESH) INITSTS(*REFRESH)
ROWSELTYP(*SELECT) ROWSELEXP("SALES > 10000")
Selects the source table CUSTOMER (in library DTUTOR) to subscription SUB1. The replication method for the table is
refresh. The initial status for the table is Refresh (*REFRESH). This ensures that the table is refreshed. A row selection
expression is defined for the CUSTOMER table. Only rows in the CUSTOMER table where SALES is greater that 10,000 are
replicated.
Parameters Description
TARGET The name of the subscription, as defined in Management Console, for which the earliest
backup point should be determined and set. For information about subscriptions, see the
Transformation Server Management Console Administration Guide.
Result
Relevant messages are produced to the job log.
Example
• SETTSSYNC TARGET(SUB1)
Sets the synchronization point for all tables selected for mirroring to subscription SUB1.
Source
Parameters Description
JOURNAL The name of the journal associated with the journal receiver that has its position changed by
this command. The library where the journal resides must be identified. Prefix the journal with
the name of the library where the journal is located.
TARGET The name of the subscription, as defined in Management Console, which is affected by this
command. For information about subscriptions, see the Transformation Server Management
Console Administration Guide.
JRNRCVNME The name of the first or starting journal receiver to be searched for the specified sequence
number or date and time. The library where the journal receiver resides must be identified.
Prefix the journal receiver with the name of the library where the journal receiver is located.
STRDTE The date of the journal entry that Transformation Server processes first when mirroring is
started. The date must be specified in the format 'MMDDYYYY'. For example, '09302004'.
STRTIM The time of the journal entry that Transformation Server processes first when mirroring is
started. The date must be specified in the format 'HHMMSS'. For example, '184304'.
STRSEQNBR The sequence number that Transformation Server processes first when mirroring is started.
Result
Relevant messages are produced to the job log.
Examples
• SETJRNPOS JOURNAL(D_MIRROR/DMCJRN) TARGET(SUB1) JRNRCVNME(D_MIRROR/DMCRCV004)
STRDTE('07052004') STRTIM('141200')
The search for the specified entry starts with journal receiver D_MIRROR/DMCRCV004 associated with journal
D_MIRROR/DMCJRN. Positions Transformation Server to start mirroring at the entry in a journal receiver that was
timestamped on July 5, 2004 at 2:12 PM.
• SETJRNPOS JOURNAL(D_MIRROR/DMCJRN) TARGET(SUB2) JRNRCVNME(D_MIRROR/DMCRCV006)
STRSEQNBR(127855)
The search for the specified entry starts with journal receiver D_MIRROR/DMCRCV006 associated with journal
D_MIRROR/DMCJRN. Positions Transformation Server to start mirroring at the entry that has a sequence number of 127855.
Parameters Description
FROMSYS The name of the subscription containing the source table. This name is the source identifier,
as defined in Management Console. For information about source identifiersource identifiers,
see the Transformation Server Management Console Administration Guide.
SRCTBL The name of the source table to assign. The table name is case-sensitive. The type of
database where the source table resides determines the case that has to be used.
SRCLIB The name of the library or database where the source table resides. This setting is case-
sensitive. The location where the source table resides determines the case that has to be
used.
TGTLIB The name of the library where the target table resides. In this library, a target table that has
the same name as a source table is assigned. If the selected mode of replication for a source
table is keyed file processing, then a unique keyed access path is required in the target table
library. If the command cannot find a unique access path (keyed physical or logical), then the
assignment is not completed and an error is logged.
TGTMBRNME The name of a member in the subscription physical file. Enter the name of a member or one
of the following values: *ONLY – Specifies the only member in the subscription physical file.
You can specify this value only when the subscription physical file is limited to one member.
The MAXMBR attribute for the subscription physical file must be equal to one.Specify this
value if you want a source table to be assigned to a target table.
Parameters Description
ASNTYP Indicates the type of assignment. The assignment type defines how replicated data is applied
to the target table.
Enter one of the following values:
• *STD—Specifies the standard replication assignment type.
• *AUD—Specifies the audit assignment type (LiveAudit).
• *SUM—Specifies the summarization assignment type.
• *CN1—Specifies the row consolidation - one-to-one assignment type.
• *CN2—Specifies the row consolidation - one-to-many assignment type.
• *ADA—Specifies the adaptive apply assignment type.
Default Setting: *STD
For more information about assignment types, see the Transformation Server Management
Console Administration Guide.
MULTISRC Indicates whether or not the target table is populated by more than one source table. For
more information about mapping source and target tables, see the Transformation Server
Management Console Administration Guide.
This parameter applies only when *SUM (Summarization) is selected for the ASNTYP
parameter.
Enter one of the following values:
• *NO—Indicates that the target table does not contain summarized data from multiple
source tables.
• *YES—Indicates that the target table does contain summarized data from multiple
source tables.
Default Setting: *NO
Result
Relevant messages are produced to the job log.
Examples
ASNTGTTBL FROMSYS(PUB1) SRCTBL(MBR1) SRCLIB(PRODLIB) TGTLIB(SUBLIB) TGTMBRNME(*MEMBER)
ASNTYP(*ADA)
Assigns the publication member named MBR1 that resides in library PRODLIB to the subscription member of the same name
in library SUBLIB. The members are assigned under adaptive apply.
ASNTGTTBL FROMSYS(PUB1) SRCTBL(EMPLOYEE) SRCLIB(EMPSRC)
TGTLIB(EMPTGT) TGTMBRNME(*ONLY) ASNTYP(*AUD)
Assigns the source table named EMPLOYEE that resides in library EMPSRC to the target table of the same name in library
EMPTGT. The tables are assigned under auditing (LiveAudit).
ASNTGTTBL FROMSYS(PUB1) SRCTBL(CUSTOMER) SRCLIB(PRODLIB) TGTLIB(SUBLIB) TGTMBRNME(*ONLY)
ASNTYP(*SUM) MULTISRC(*YES)
Assigns the source table named CUSTOMER that resides in library PRODLIB to the
target table of the same name in library SUBLIB. The tables are assigned under summarization, and data from more than one
source table is summarized in the target table.
Parameters Description
FROMSYS The name of the subscription containing the source table. This name is the source identifier,
as defined in Management Console. For information about source identifiers, see the
Transformation Server Management Console Administration Guide.
SRCTBL The name of the source table that is de-assigned. The table name is case-sensitive. The type
of database where the source table resides determines the case that has to be used.
SRCLIB The name of the library or database where the source table resides. This setting is case-
sensitive. The location where the source table resides determines the case that has to be
used.
Result
Relevant messages are produced to the job log.
Example
DASTGTTBL FROMSYS(PUB1) SRCTBL(CUSTOMER) SRCLIB(DTUTOR)
The assigned source table CUSTOMER in library DTUTOR that is under the subscription PUB1 is de-assigned from its target
table.
Parameters Description
FROMSYS The name of the subscription to have all or part of its configuration copied. This name is the
source identifier, as defined in Management Console. For information on how to add a
subscription, see the Transformation Server Management Console Administration Guide.
SRCTBL The name of the described source table to have its configuration copied. Enter the name of a
table, a generic name (for example, abc* specifies all tables starting with abc), or the
following value:
*ALL—Specifies all source tables in the library (see the SRCLIB parameter below) that are
contained in the subscription. The table name is case-sensitive. The type of database where
the source table resides determines the case that has to be used.
SRCLIB The name of the library or database where the source table resides. This setting is case-
sensitive. The location where the source table resides determines the case that has to be
used.
TOSYS The name of the subscription that receives the copied configuration. This name is the source
identifier, as defined in Management Console. For information on how to add a subscription
in Management Console, see theTransformation Server Management Console
Administration Guide
ROWID The row identifier expression that is defined for the assigned target table. For information on
how to add an expression to filter a row during replication, see Transformation Server
Management Console Administration Guide.
Result
Relevant messages are produced to the job log.
Examples
CPYTGTASN FROMSYS(PUB1) SRCTBL(*ALL) SRCLIB(DTUTOR) TOSYS(PUB2)
All described source tables in library DTUTOR have their configuration copied from subscription PUB1 to subscription PUB2.
A row identifier expression is not defined for each assigned target table.
Parameters Description
TARGET The name of the subscription, as defined in Management Console, that has its configuration
copied. For information on how to add a subscription, see the Transformation Server
Management Console Administration Guide.
TOTARGET The name of the subscription, as defined in Management Console, which receives the copied
configuration. For information on how to add a subscription, see the Transformation Server
Management Console Administration Guide.
INTSTSRSH The initial replication status for source tables that are refreshed.
Specify one of the following values:
• *IDLE—Specifies a status of Idle to ensure that the table is not refreshed.
• *REFRESH—Specifies a status of Refresh to ensure that the table is refreshed.
INTSTSMIR The initial replication status for source tables that are mirrored.
Specify one of the following values:
• *IDLE—Specifies a status of Idle to ensure that the table is not mirrored.
• *REFRESH—Specifies a status of Refresh to ensure that the table is refreshed before
mirroring begins.
• *ACTIVE—Specifies a status of Active to ensure that the table is not refreshed before
mirroring begins.
Parameters Description
ROWSELTYP The type of row selection applied to the source table. Specify one of the following values:
• *SELECT—Replicate rows that satisfy the row selection expression.
• *OMIT—Do not replicate rows that satisfy the row selection expression. All other rows
that do not satisfy the row selection expression are replicated
ROWSELEXP The row selection expression that determines which rows in the source table are replicated.
You must enter a row selection expression based on columns in the source table.
Result
Relevant messages are produced to the job log.
Examples
CPYTGTTBL TARGET(SUB1) TOTARGET(SUB2) TABLE(DTUTOR/SALES) INTSTSRSH(*IDLE) INTSTSMIR(*ACTIVE)
The replication configuration for source table SALES in library DTUTOR is copied from subscription SUB1 to subscription SUB2.
The initial replication status for the table when it is refreshed is *IDLE. The initial replication status for the table when it is mirrored
is *ACTIVE. A row selection expression is not defined for the SALES table.
CPYTGTTBL TARGET(SUB1) TOTARGET(SUB2) TABLE(DTUTOR/CUSTOMER) INTSTSRSH(*IDLE)
INTSTSMIR(*REFRESH) ROWSELTYP(*OMIT) ROWSELEXP("CUSTID > 5000")
The replication configuration for source table CUSTOMER in library DTUTOR is copied from subscription SUB1 to subscription
SUB2. The initial replication status for the table when it is refreshed is *IDLE. The initial replication status for the table when it is
mirrored is *REFRESH. A row selection expression is defined for CUSTOMER table. Only rows in the table that have a CUSTID
column value less than or equal to 5000 are replicated.
CPYTGTTBL TARGET(SUB1) TOTARGET(SUB2) TABLE(DTUTOR/*ALL) INTSTSRSH(*REFRESH) INTSTSMIR(*ACTIVE)
ROWSELTYP(*SELECT) ROWSELEXP("SALES > 10000")
The replication configuration for all selected source tables in DTUTOR are copied from subscription SUB1 to subscription SUB2.
The initial replication status for the table when it is refreshed is *REFRESH. The initial replication status for the table when it is
mirrored is *ACTIVE. A row selection expression is defined for each table in the DTUTOR library. Only rows in each table that
have a SALES column value greater that 10,000 are replicated.
Parameters Description
TABLE The name of the added source table in the test library to have its publisher metadata copied.
Specify the name of the table, a generic table name (for example, CUST*), or the following
value:
*ALL—Specifies all added tables in the library. The name of the library where the table
resides must precede the table specification.
TOLIB The production library containing the added source table that corresponds to the test table
specified in the TABLE parameter (see above).
Result
Relevant messages are produced to the job log.
Examples
DUPTBL TABLE(TSTPUB/*ALL) TOLIB(PRDPUB)
Publisher metadata for all added source tables in library TSTPUB is copied to library PRDPUB.
DUPTBL TABLE(TSTPUB/CUSTOMER) TOLIB(PRDPUB)
Publisher metadata for added source table CUSTOMER in library TSTPUB is copied to library PRDPUB.
on) in the test area. Metadata is modified to reference table assignments and data transformations in production that are based on
settings already defined for corresponding tables in the test environment. Transformation Server verifies that the corresponding
source tables in production exist and have the same names and attributes as the tables in the test environment. If Transformation
Server detects a discrepancy, the attempt to modify the metadata through this command fails. In this case, messages are
generated to inform you of the differences that were detected.
Command Syntax
DUPTGTASN FROMSYS( ) TOSYS( ) SRCTBL( ) SRCLIB( ) TOSRCLIB( ) TOTGTLIB( )
Applies To
Target
Parameters Description
FROMSYS The name of the subscription in the test environment to have its subscriber metadata copied.
This name is the source identifier, as defined in Management Console. For information about
source identifiers, see the Transformation Server Management Console Administration
Guide.
TOSYS The name of the subscription in the production environment that receives the copied
subscriber metadata. This name is the source identifier, as defined in Management Console.
For information about source identifiers, see the Transformation Server Management
Console Administration Guide.
SRCTBL The name of the source table in the test library to have its subscriber metadata copied. The
table name is case-sensitive. The type of database where the source table resides
determines the case that has to be used.
SRCLIB The name of the test library or database where the source table resides. This setting is case-
sensitive. The location where the source table resides determines the case that has to be
used.
TOSRCLIB The name of the production library containing the source table that corresponds to the source
table in the test environment (see SRCTBL parameter above).
TOTGTLIB The name of the production library containing the target table that corresponds to the
assigned target table in the test environment.
Result
Relevant messages are produced to the job log.
Examples
DUPTGTASN FROMSYS(PUBTSTID) TOSYS(PUBPRDID) SRCTBL(CUSTOMER) SRCLIB(TSTPUB) TOSRCLIB(PRDPUB)
TOTGTLIB(PRDSUB)
Subscriber metadata for source table CUSTOMER in the TSTPUB test library that is contained in the test subscription PUBTSTID
is copied to the production subscription PUBPRDID. The corresponding source table in the production environment is located in
the library PRDPUB. The target table in the production environment that corresponds to the assigned target table in the test
environment is located in the library PRDSUB.
refers to source table selection attributes (for example, column selection, row selection, critical columns, replication method, and
so on) in the test environment. Metadata is modified to define the same selection attributes for the corresponding selected source
tables in production. Transformation Server verifies that the corresponding selected tables in production exist and have the same
names and attributes as the tables in the test library. If Transformation Server detects a discrepancy, the attempt to modify the
metadata through this command fails. In this case, messages are generated to inform you of the differences that were detected.
Command Syntax
DUPTGTTBL TARGET( ) TOTARGET( ) TABLE( ) TOLIB( )
Applies To
Target
Parameters Description
TARGET The name of the subscription in the test environment, as defined in Management Console, to
have its publisher metadata copied. For information about subscriptions, see the
Transformation Server Management Console Administration Guide.
TOTARGET The name of the subscription in the production environment, as defined in Management
Console, that receives copied publisher metadata. For information about subscriptions, see
the Transformation Server Management Console Administration Guide.
TABLE The name of the selected source table in the test library.
Specify the name of the table, a generic table name (CUST*), or the following value:
*ALL—Specifies all tables in the library that are selected to the subscription (see the
TARGET parameter above). The name of the library where the table resides must precede
the source table specification.
TOLIB The name of the production library containing the selected source table that corresponds to
the selected source table in the test library (see the TABLE parameter above).
Result
Relevant messages are produced to the job log.
Examples
TOLIB(PRDPUB)
Publisher metadata for all source tables in the TSTPUB test library that are selected to the test subscription SUBTST is copied to
the production subscription SUBPRD.
The name of the production library containing the selected source tables that correspond to the tables in the test library is
PRDPUB.
DUPTGTTBL TARGET(SUBTST) TOTARGET(SUBPRD) TABLE(TSTPUB/V*) TOLIB(PRDPUB)
Publisher metadata for all source tables starting with the letter V in the TSTPUB test library that are selected to the test
subscription SUBTST is copied to the production subscription SUBPRD. The name of the production library containing the
selected source tables that correspond to the tables in the test library is PRDPUB.
Parameters Description
ENBSQL Indicates whether or not the specification of SQL statements in Management Console is
enabled or disabled.
Enter one of the following values:
• *NO—Specifies that SQL statements cannot be entered in Transformation Server
Management Console.
• *YES—Specifies that SQL statements can be entered in Transformation Server
Management Console.
Default Setting—*NO
Note: This command can only be run from the QSECOFR user profile.
Note: The use of SQL statements may constitute a security concern in your working environment. Therefore, you
should exercise caution when issuing this command to enable the specification of SQL statements in
Management Console.
Parameters Description
JOURNAL The name of the journal for which journal receivers are generated.
Enter the name of a valid journal or the following value:
*ALL – Specifies all journals in the library that are used by Transformation Server.
Default Setting: *ALL
The library where the journal resides must be identified. Prefix the journal with the
name of the library where the journal is located.
CHGRCV Indicates whether or not the journal receiver should be changed for the specified
journal.
Enter one of the following values:
*NO - Indicates that journal receivers are not changed for the specified journal(s).
You need to change the journal receivers manually.
*YES - Indicates that journal receivers are changed for the specified journals.
Default Setting: *YES
Parameters Description
DLTRCV Indicates whether or not processed or obsolete journal receivers should be deleted for
the specified journal.
Enter one of the following values:
*NO – Specifies that you do not want to delete processed or obsolete journal receivers
associated with the journal. These receivers remain until you delete or archive them.
*YES – Specifies that you want to delete processed and obsolete receivers associated with
the journals.
*DFT – Specifies that you want to delete processed and obsolete receivers associated with
the Transformation Server default journal. This setting applies only when JOURNAL (see
above) is set to the current Transformation Server default journal, which is specified in the
CHGDMSVAL command.
Default Setting: *DFT
CLSTRLIB If you have the DataMirror iCluster product installed, then Transformation Server could
possibly change or delete journal receivers that iCluster requires.
By specifying the iCluster library name, Transformation Server makes sure it does not
change or delete any iCluster journal receivers that reside in this library.
Enter the library name where iCluster is installed or the following value:
*NONE – Specifies that iCluster is not installed.
Default Setting: *NONE
Result
Relevant messages are produced to the job log.
Examples
CHGJRNDM JOURNAL(LIB1/*ALL)
Journal receivers associated with all journals in library LIB1 that are used by Transformation Server are changed. Processed
and obsolete journal receivers for the Transformation Server default journal are not deleted. The default setting for the
DLTRCV parameter is only applicable when the current default Transformation Server journal is specified for JOURNAL.
iCluster has not been installed.
CHGJRNDM JOURNAL(LIB1/DMCJRN) CHGRCV(*YES) DLTRCV(*DFT) CLSTRLIB(CLUSLIB1)
Journal receivers associated with the Transformation Server default journal DMCJRN in library LIB1 are changed. Processed
and obsolete journal receivers for DMCJRN are deleted. Transformation Server does not delete any processed or obsolete
journal receivers in iCluster library CLUSLIB1.
CHGJRNDM JOURNAL(LIB1/DMCJRN) CHGRCV(*NO) DLTRCV(*NO) CLSTRLIB(*NONE)
Journal receivers associated with the Transformation Server default journal DMCJRN in library LIB1 are not changed.
Processed and obsolete journal receivers for DMCJRN are not deleted. iCluster has not been installed.
Related Topics
• CHGJRNDM—Change Remote Journal Receivers on page 47
Parameters Description
PRODLIB The name of the product library where Transformation Server is installed.
Enter a library name or the following value:
*CURLIB—Specifies the current library.
Default Setting: *CURLIB
PUBID This name is the source identifier, as defined in Management Console, for which
bookmarks are displayed.
Enter a source identifier or the following value:
*ALL—Specifies all defined source identifiers.
For information about source identifiers, see the Transformation Server Management
Console Administration Guide.
Parameters Description
OUTFILE The name of the database file where the results of this command are sent. This parameter
applies only if you specified *OUTFILE for the OUTPUT parameter (see above).
You can specify either a new or an existing file.
The name of the library where the database file resides must precede the database file
specification.
Specify a library name or the following value:
*CURLIB—Specifies the current library.
MBROPT Indicates whether the database file specified for the OUTFILE parameter (see above) is
cleared before new records are added to the database file. This parameter applies only if you
specified *OUTFILE for the OUTPUT parameter (see above).
Enter one of the following values:
*REPLACE—Specifies that the database file is cleared before new records are added to
the database file.
*ADD—Specifies that the new records are appended to the existing database file.
Default Setting: *REPLACE
Result
Relevant messages are directed to the job log or to a database file. Messages in the job log contain first and second level text.
First-level text indicates the publisher ID name. To view specific bookmark information, you need to display second level
message text. Second level text contains the following items of information:
Publisher ID—The publisher ID for which bookmark information is being retrieved.
Entry—The name of the journal or log, and where it is located.
Last Committed Position—The position of the last journal or log entry to be applied to the target table that is confirmed.
Confirmed indicates either that the commitment control group where the journal or log entry belongs has been committed, or
that the journal or log entry was processed outside commitment control.
Earliest Open Position—The position marking the beginning of the oldest commitment control transaction that is still
uncommitted or being rolled back.
Last Applied Position—The position of the last journal or log entry applied to the target table. The Last Committed Position,
Earliest Open Position, and Last Applied Position settings are the same when the commitment control level is set to *NONE
(see the CHGDMTVAL command).
Apply Time—The timestamp of the last journal or log entry applied to the target table (see Last Applied Position above).
Log Time—The timestamp in the publication journal or log of the last journal or log entry applied to the target table (see Last
Applied Position above). If the command fails to retrieve a set of bookmarks, an error message is logged.
Examples
• DMVWBKMK PUBID(PUB1)
Bookmark information that is retrieved applies to the Transformation Server installation in the current library. Bookmark
information associated with source identifier PUB1 is directed to the job log or a spooled file.
• DMVWBKMK PRODLIB(D_MIRROR) PUBID(PUB1) OUTPUT(*DSP)
Bookmark information that is retrieved applies to the Transformation Server installation in the product library D_MIRROR.
Bookmark information associated with source identifier PUB1 is directed to the job log or a spooled file.
• DMVWBKMK PRODLIB(D_MIRROR) PUBID(*ALL) OUTPUT(*OUTFILE) OUTFILE(LIB1/FILE1) MBROPT(*ADD)
Bookmark information that is retrieved applies to the Transformation Server installation in the product library D_MIRROR.
Bookmark information associated with all source identifiers is added to the database file FILE1 located in library LIB1.
Parameters Description
Results
JRENTCONF
The last confirmed (replicated) journal entry sequence number.
JRNRCVNME
The journal receiver name of the last confirmed entry.
JRNRCVLIB
The library where the journal receiver is located.
Examples
RTVDMJENT JOURNAL(D_MIRROR/DMCJRN)
Retrieves journal information for journal DMCJRN in library D_MIRROR.
VFYTSJRN—Verify Journal
Use this command to verify that the required Transformation Server journal exists for all tables selected for replication to the
named subscription. If the journal cannot be found, this command ensures that the proper journal is created. This command also
verifies all tables selected to the subscription. All tables that have a replication method of refresh are excluded during this
verification process.
Parameters Description
TARGET The name of the subscription, as defined in Management Console, for which journaling is
verified. For information about subscriptions, see the Transformation Server Management
Console Administration Guide.
Result
Relevant messages are produced to the job log.
Example
VFYTSJRN TARGET(SUB1)
Verifies journaling for all source table selected to subscription SUB1.
Communication Commands
In this section, you will learn about commands that:
• STRDMTCP—Start Transformation Server TCP/IP Communications on page 97
• STRDMUDP—Start UDP Listener on page 99
• ENDDMTCP—End Transformation Server TCP/IP Communications on page 100
• ENDDMUDP—End UDP Listener on page 103
Parameter Description
SERVICE The TCP/IP service table entry name that is used by Transformation Server for TCP/IP
communications. This service table entry must not be used by another job. The TCPLISTEN
listener job listens on the port that is associated with this entry in the TCP/IP service table.
You must allocate an entry and unique port number in the TCP/IP service table before
invoking this command. The service name is case-sensitive and must be enclosed in single
quotes.
Default Setting—‘dmirror’
JOBD The name of the job description that you want to associate with both the TCPLISTEN and
UDPLISTEN listener jobs. Default Setting: DMCJOBD You also need to specify the library
where the job description resides. The library where the job description resides must precede
the job description specification.
Specify the name of a library or one of the following values:
• *LIBL—Specifies the set of libraries in your library list. The libraries are searched in
order for the first occurrence of the specified job description.
• *CURLIB—Specifies the current library.
Default Setting— *LIBL
Parameter Description
HOST The host name or full IP address of the server where Transformation Server is running.
Default Setting: ‘ ‘ (a single blank character which indicates the local server)
ACPORT The port number on an Access Server that is used to receive broadcasts from the
UDPLISTEN listener job.
This parameter is applicable only when the AUTODISCOV parameter (see above) is set to
*YES. If you change the Access Server port numbers, you need to change this parameter
setting as well.
Default Setting
10101
Result
Messages are placed in the Event Log.
Examples
• STRDMTCP
The TCP/IP service table entry for Transformation Server is dmirror. The job description for both the TCPLISTEN and
UDPLISTEN listener jobs is the first occurrence of the Transformation Server job description (DMCJOBD) in the library list.
This command starts the TCPLISTEN listener job on the local server.
• STRDMTCP SERVICE(‘tsmir’) JOBD(SUBLIB/JOBD1) HOST(‘ ‘) AUTODISCOV(*YES) ACPORT(12121)
The TCP/IP service table entry for Transformation Server is tsmir. The job description for both the TCPLISTEN and
UDPLISTEN listener jobs is JOBD1 in library SUBLIB. This command starts both the TCPLISTEN and UDPLISTEN listener
jobs on the local server. The port number on the Access Servers that is used to receive UDPLISTEN broadcasts is 12121.
• STRDMTCP JOBD(*CURLIB/JOBD1) HOST(SYS1) AUTODISCOV(*NO)
The TCP/IP service table entry for Transformation Server is dmirror. The job description for both the TCPLISTEN and
UDPLISTEN listener jobs is JOBD1, which is located in the current library. This command starts the TCPLISTEN listener job
on server SYS1.
Parameter Description
UDPSERVICE The name of the service that was defined in the TCP/IP service table for the UDPLISTEN
listener job. This parameter is case-sensitive and must be enclosed in single quotes.
Default Setting
‘dmirror’
TCPSERVICE The name of the service that was defined in the TCP/IP service table for the TCPLISTEN
listener job. For more information about TCPLISTEN, see the STRDMTCP command. This
parameter is case-sensitive and must be enclosed in single quotes.
ACPORT The port number on an Access Server that is used to receive broadcasts from the
UDPLISTEN listener job. This parameter is applicable only when the AUTODISCOV
parameter in a STRDMTCP command invocation is set to *YES. For more information about
the AUTODISCOV parameter, see the STRDMTCP command.
Default Setting
10101
JOBD The name of the job description that you want to associate with the UDPLISTEN listener job
and all jobs started by the UDPLISTEN listener job. The job description that you specify is
used only if you are using this command to start the UDPLISTEN listener job. If you use the
STRDMTCP command to start the UDPLISTEN listener job, then the value that you specified
for the JOBD parameter in the STRDMTCP command is used instead.
Default Setting: DMCJOBD
Job Description Library The name of the library where the job description is located must
precede the job description specification.
Specify the name of a library or one of the following values:
• *LIBL—Specifies the set of libraries in your library list. The libraries are searched in
order for the first occurrence of the specified job description.
• *CURLIB—Specifies the current library.
Default Setting
*LIBL
Result
Target
Parameter Description
Parameter Description
AUTODISCOV Indicates if Transformation Server ends or continues with the UDPLISTEN listener job which
terminates autodiscovery. Auto-discovery is a way for Access Server to recognize, upon
startup, all available replication agents on the local network so that you do not need to create
each agent manually in Access Manager. For more information about Access Server, Access
Manager, replication agents, and auto-discovery, see the Transformation Server Access
Manager Configuration Guide.
Enter one of the following values:
• *YES—Specifies that Transformation Server ends the UDPLISTEN listener job and
disables auto-discovery.
• *NO—Specifies that Transformation Server continues the UDPLISTEN listener job and
auto-discovery.
Default Setting
*NO
JOBD The name of the job description that you want Transformation Server to associate with both
the TCPLISTEN and UDPLISTEN listener jobs, and all jobs started by TCPLISTEN. By
default, Transformation Server uses the job description DMCJOBD. You must specify the
name of the library before the name of the job description.
Specify the library name or one of the following values:
• *CURLIB—Specifies the current library.
• *LIBL—Specifies the set of libraries in your library list. Transformation Server searches
libraries in order of first occurrence of the specified job description.
Default Setting
*LIBL
Result
Messages are placed in the Event Log.
Examples
ENDDMTCP
Transformation Server stops the TCPLISTEN listener job in a controlled manner and uses the default settings for the TCP/IP
service table entry, autodiscovery, and job description.
ENDDMTCP ENDTYP(*CNTRLD) SERVICE(‘tsmir’) AUTODISCOV(*YES) JOBD(LIB1/JOB1)
Transformation Server stops TCPLISTEN listener job in a controlled manner. This job was using tsmir as the TCP/IP service
table entry. Transformation Server also disables auto-discovery by stopping the UDPLISTEN listener job. Both listener jobs
are using the job description JOB1 in the library LIB1.
ENDDMTCP ENDTYP(*IMMED) SERVICE(‘tsmir’) AUTODISCOV(*NO) JOBD(*CURLIB/JOB1)
Transformation Server stops TCPLISTEN listener job immediately. This job was using tsmir as the TCP/IP service table entry.
Transformation Server continues to use auto-discovery by continuing with the UDPLISTEN listener job. Both listener jobs are
using the job description JOB1 in the current library.
Parameter Description
SERVICE The name of the TCP/IP service table entry name that Transformation Server uses for the
UDPLISTEN listener job. Transformation Server stops the UDPLISTEN listener job on the
port reserved by this TCP/IP service table entry. The service name is case-sensitive and
must be enclosed in single quotes.
Default Setting
‘dmirror’
Result
Messages are placed in the Event Log.
Examples
• ENDDMUDP
Transformation Server stops the UDPLISTEN listener in a controlled manner and uses the default name for the the TCP/IP
service table entry (dmirror).
• ENDDMUDP ENDTYP(*IMMED) SERVICE(‘tsmir’)
Transformation Server stops the UDPLISTEN listener job immediately and uses tsmir as the TCP/IP service table entry.
Parameter Description
PRODLIB The name of the product library where Transformation Server is installed. Enter a library
name or one of the following values:
*CURLIB—Specifies the current library.
Default Setting: *CURLIB
This command does not affect Transformation Server jobs associated with other product
installations on the same server that are located in different product libraries.
PUBID This name is the source identifier, as defined in Management Console, which has its
Transformation Server jobs ended by this command.
Enter a source identifier or the following value:
*ALL—Specifies all defined source identifiers.
For information about source identifiers, see the Transformation Server Management
Console Administration Guide.
Result
Relevant messages are produced to the job log.
Examples
DMENDPROC PUBID(PUB1)
Ends Transformation Server jobs in the current library that support replication from the publisher identified by PUB1.
DMENDPROC PRODLIB(D_MIRROR) PUBID(*ALL)
Ends all Transformation Server jobs in the product library D_MIRROR.
DMENDPROC PRODLIB(*CURLIB) PUBID(*ALL)
Ends all Transformation Server jobs in the current product library.
Other Commands
In this section, you will learn about commands that:
• ADDS36TBL—Add S/36 Flat File Table on page 107
• DMCMVFY—Run Communications Verifier on page 108
• RTVDMVSTS—Retrieve Transformation Server Installation Information on page 111
• CHGDMSVAL—Set Source System Parameters on page 111
• CHGDMTVAL—Set Target System Parameters on page 120
Parameters Description
TABLE NAME The full name of the S/36 flat file table to be added.
LIBRARY The library name where the S/36 flat file resides.
Result
Relevant messages are produced to the job log.
After issuing the command, the Define Columns for Non-Externally Defined Table screen is displayed. You need to supply
information as specified in Description. Press Enter after specifying this information. Confirmation messages are displayed,
and the table is added to the Management Console catalog.
Example
ADDS36TBL TBLNAME(S36TBL1) LIBRARY(LIB36_1)
Adds table S36TBL1, located in library LIB36_1, to the Management Console catalog.
Parameters Description
RMTNME The host name or full IP address of the remote server in the communications test.
RMTPRT The port number on the remote server that is used to perform the communications test.This
port number was allocated when you installed Transformation Server.
Default Setting: 2223
NBRPKT The number of packets that are sent to the remote server. This parameter is valid only when
the TSTTYP parameter (see above) is set to *PACKETS.
Default Setting: 5 packets
Minimum Setting: 1 packet
Maximum Setting: 99999 packets
Parameters Description
TIMLMT Specifies the duration, in seconds, of the test. This parameter is valid only when the TSTTYP
parameter (see above) is set to *TIMED. The value specified for the NBRPKT parameter is
ignored. When the VERBOSE parameter (see below) is set to either *MEDIUM or *HIGH, a
message is displayed for every packet that is sent. This can add to the amount of time the
test requires to complete, and therefore, may cause the time of the test to exceed the time
specified.
Default Setting: 60 seconds
Minimum Setting: 0 seconds (the test runs continuously)
Maximum Setting: 999999 seconds
LCLNME The host name or full IP address of the local server in the communications test. The local
server is the server where this command has been issued. Enter the host name or full IP
address of the local server, or the following value:
• *DFT—Specifies the host name or full IP address of the server where this command is
issued. This is the default setting for this parameter.
Default Setting: *DFT
Another physical server cannot be designated as the local server by identifying its host name
or full IP address. Therefore, this parameter must be set to the host name or full IP address of
the server where this command is issued, or *DFT.
LCLPRT The port number on the local server that is used to perform the communications test. This
port number was allocated when you installed Transformation Server.
Default Setting: 0 (allows the local server to use any available port number)
Parameters Description
PKTLEN The length, in bytes, of each test packet that is sent to the remote server.
Default Setting: 512 bytes
Minimum Setting: 100 bytes
Maximum Setting: 63500 bytes
SNDDLY The time interval, in milliseconds, to wait before sending more test packets to the remote
server.
Default Setting: 0 milliseconds (indicates that there is no delay between consecutive packets)
Minimum Setting: 0 milliseconds (indicates that there is no delay between consecutive
packets)
Maximum Setting: 999 milliseconds
RCVDLY The time interval, in milliseconds, to wait for a confirmation to be received from the remote
server. This value should consider communication bandwidth and utilization.
Default Setting: 0 milliseconds (indicates that there is no delay between consecutive
confirmations)
Minimum Setting: 0 milliseconds (indicates that there is no delay between consecutive
confirmations)
Maximum Setting: 999 milliseconds
Result This command generates the following return codes for both types of tests:
• 1—Indicates that each step of the test has been completed successfully.
• Non-zero—Indicates that an error occurred during the test.
Examples
DMCMVFY RMTNME(SYS1)
Verifies communications with remote server SYS1 by sending a number of packets.
Default values are used for all parameters that are not specified.
DMCMVFY RMTNME(SYS1) RMTPRT(2252) TSTTYP(*PACKETS) NBRPKT(6)
Verifies communications with remote server SYS1 by sending 6 packets.
Packets are sent to port number 2252 on the remote server.
Default values are used for all parameters that are not specified.
DMCMVFY RMTNME(SYS2) RMTPRT(4444) TSTTYP(*TIMED) TIMLMT(300) VERBOSE(*MEDIUM) LCLNME(*DFT)
LCLPRT(5151) PKTLEN(2000) SNDDLY(900) RCVDLY(900)
Verifies communications with remote server SYS2 by conducting a timed test for 5 minutes (300 seconds).
Packets are sent to port number 4444 on the remote server.
An asterisk for each step that is successfully completed is displayed. Packets are sent from the local server on port number
5151. The length of each packet is 2,000 bytes, and there is a 900 second delay between consecutive packet deliveries and
confirmations.
Note: This command has replaced the DMVFYTCP command. For information about the DMVFYTCP command,
contact your DataMirror representative.
Source
Parameters Description
JOURNAL The name of the Transformation Server default journal. By default, tables that are mirrored by
Transformation Server use this journal. Enter the name of the default journal or the following
value:
*SAME—Keeps the present setting for this parameter.
Default Setting: *SAME
Journal Library
The name of the library where the journal resides must precede the name of the journal.
Enter the name of the library or one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *LIBL—Specifies the set of libraries in your library list. The libraries are searched in
order for the first occurrence of the specified default journal.
• *CURLIB—Specifies the current library.
Default Setting: *LIBL
NOTIFYQ The name of the message queue where notifications are sent when the number of errors
detected by Transformation Server exceeds the notify message threshold (see the
NOTIFYCNT parameter below).
Enter the name of the notify message queue or the following value:
*SAME—Keeps the present setting for this parameter.
Default Setting: *SAME
The name of the library where the notify message queue resides must precede the name of
the notify message queue.
Message Queue Library
Enter a library name or one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *LIBL—Specifies the set of libraries in your library list. The libraries are searched in
order for the first occurrence of the specified message queue.
• *CURLIB—Specifies the current library.
Default Setting: *LIBL
Parameters Description
NOTIFYCNT The number of errors that Transformation Server generates before a notification is sent to the
notify message queue (see the NOTIFYQ parameter above).
Enter the number of errors or the following value:
*SAME—Keeps the present setting for this parameter.
If a value smaller than the minimum setting (see below) is specified, the minimum setting is
used. If a value larger than the maximum setting (see below) is specified, the maximum
setting is used.
Default Setting: *SAME
Minimum Setting: 1 error
Maximum Setting: 99999 errors
RESTORE Indicates how Transformation Server should refresh tables that have been restored.
Enter one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *IMMED—Specifies that tables should be refreshed immediately when Transformation
Server detects the restore.
• *DELAY—Specifies that tables are refreshed the next time a refresh is started.
This includes a refresh before mirroring is started.
Default Setting: *SAME
AUTCDE The authorization code that is issued by DataMirror Corporation. Adjustments to the
authorization code are required when moving from a temporary license to a permanent
license, when machine classes have changed, or when upgrading Transformation Server to a
new version.
Enter the authorization code or the following value:
*SAME—Keeps the present setting for this parameter.
Default Setting: *SAME
Parameters Description
REFWHLACT Specifies whether or not to enable Refresh While Active. Refresh While Active is a feature
that allows Transformation Server to refresh a target table while the source table is active and
subject to changes during the time of the refresh. After the refresh has been completed,
source table changes that occurred during the refresh are also sent to the target table.
Enter one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *YES—Indicates that refresh while active is enabled.
• *NO—Indicates that refresh while active is disabled.
Default Setting: *SAME
USDEFJRN Indicates whether or not user-defined journal entries should be processed for replication. This
parameter allows you to disable processing required for user-defined journal entries that
could impact overall performance.
Enter one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *YES—Indicates that the user-defined journal entries specified in the Transformation
Server metadata table are processed for replication.
• *NO—Indicates that no user-defined journal entries are processed for replication.
Default Setting: *SAME
For more information about processing user-defined journal entries for replication, see User-
defined Journal Entry Replication
Parameters Description
HEARTTIME Specifies the number of minutes of communication inactivity to wait before active
Transformation Server jobs for a subscription are stopped.
Heartbeat is a feature that manages Transformation Server processes when a problem with
communications or a process has been detected through the absence of communications
over a specified period of time. For each active subscription, internal heartbeat messages are
sent regularly from a publisher to a subscriber to determine communications and job status. If
a reply to a message is not received by the publisher within the specified timeout interval,
then Transformation Server determines that a problem has occurred, and an attempt is made
to stop all Transformation Server publisher and subscriber jobs for the subscription. In
addition, messages (message identifiers DMU3165 and DMU0647) are placed in the event
log when heartbeat timeouts occur. For information about using the Management Console
Event Log Viewer to examine the contents of an event log, see the Transformation Server
Management Console Administration Guide.
If a value smaller than the minimum setting (see below) is specified, the minimum setting is
used. If a value larger than the maximum setting (see below) is specified, the maximum
setting is used.
Default Setting: 15 minutes
Minimum Setting: 3 minutes
Maximum Setting: 999 minutes
REPTPOSTIM Specifies how often, in seconds, the publisher informs the subscriber about its position in the
current journal during inactive periods. During inactive periods, when there are no journal
entries pertaining to the current subscription, the publisher informs the subscriber of its
current position so that the subscriber can advance its bookmarks accordingly. By specifying
a low setting for this parameter, the subscriber can reflect more accurately how far replication
has progressed. This parameter can also prevent the reprocessing of entries that do not
apply to the table currently being replicated. The value of this parameter affects the
information that is displayed in progress and bookmark messages in the Event Log Viewer,
and in the Monitoring view in Management Console. A high setting for this parameter may
result in information that is not up-to-date being presented. If a value smaller than the
minimum setting (see below) is specified, the minimum setting is used. If a value larger than
the maximum setting (see below) is specified, the maximum setting is used.
Default Setting: 5 seconds
Minimum Setting: 1 second
Maximum Setting: 300 seconds
BKMARKSYNC The period of time, in seconds, between consecutive synchronizations performed between
the publisher and the subscriber. Synchronization is achieved when the subscriber reports to
the publisher the position of the last committed change. If you are replicating large volumes of
information, you may want to set this value to a lower number to allow obsolete journals
receivers to be removed more frequently. If a value smaller than the minimum setting (see
below) is specified, the minimum setting is used. If a value larger than the maximum setting
(see below) is specified, the maximum setting is used.
Default Setting: 60 seconds
Minimum Setting: 1 second
Maximum Setting: 300 seconds
Parameters Description
MONSAMPFRQ The period of time, in seconds, between consecutive updates to a data store that is used to
maintain replication latency metrics. The data store is referenced by Management Console to
present replication latency information.
If a value smaller than the minimum setting (see below) is specified, the minimum setting is
used. If a value larger than the maximum setting (see below) is specified, the maximum
setting is used.
Default Setting: 5 seconds
Minimum Setting: 0 seconds
If this parameter is set to 0, replication latency metrics are not updated in the data store.
Maximum Setting: 3600 seconds (1 hour)
STARTUP The maximum amount of time, in seconds, to wait before terminating the Transformation
Server initialization phase. During Transformation Server initialization prior to data
replication, process termination on the publication or subscription server can result in a
suspension of the initialization phase. This parameter allows you to set the maximum waiting
period in this case. If a value smaller than the minimum setting (see below) is specified, the
minimum setting is used. If a value larger than the maximum setting (see below) is specified,
the maximum setting is used.
Default Setting: 120 seconds
Minimum Setting: 4 seconds
Maximum Setting: 3600 seconds (1 hour)
PROGRESS The amount of time to wait, in seconds, before generating the next progress message.
Progress messages are placed in the event log. If a value smaller than the minimum setting
(see below) is specified, the minimum setting is used. If a value larger than the maximum
setting (see below) is specified, the maximum setting is used.
Default Setting: 0 seconds (no progress messages are issued)
Minimum Setting: 0 seconds (no progress messages are issued)
Maximum Setting: 7200 seconds (2 hours)
LCKTIMEOUT The amount of time, in seconds, Transformation Server waits for a table or row to become
unlocked before generating an error message in the event log. If a value smaller than the
minimum setting (see below) is specified, the minimum setting is used. If a value larger than
the maximum setting (see below) is specified, the maximum setting is used.
Default Setting: 30 seconds
Minimum Setting: 2 seconds
Maximum Setting: 60 seconds
Parameters Description
UNICODE The default method of treating data in defined Unicode columns. In Management Console,
you can establish how data in each Unicode column in a source table is treated. For more
information about settings at the column level, see the Transformation Server Management
Console Administration Guide.
For each Transformation Server installation on a server, this parameter defines the system
default method of treating data in Unicode columns. If a Unicode column in Management
Console is set to the system default, the current system default method, as defined by this
parameter, is used.
The following DB2 UDB for iSeries data types are considered to be Unicode columns, and
are therefore affected by the value assigned to this parameter:
• GRAPHIC or VARGRAPHIC with code page 1208 (UTF-8)
• CHARACTER or VARCHAR with code page 1208 (UTF-8)
Enter one of the following values:
*SAME—Keeps the present setting for this parameter.
CHAR—Transformation Server treats all data in Unicode columns as single-byte characters.
Use this setting when Unicode columns contain single-byte character data.
NOCHANGE—Transformation Server treats all data in Unicode columns as a continuous bit
stream. Use this setting when Unicode columns contain nonsingle- byte character data.
NOCHANGE ensures Transformation Server handles non-single-byte character data in the
same way as previous Transformation Server releases. NOCHANGE does not ensure that
replicated non-single-byte character data in Unicode columns are represented properly on
the subscription server. For replicated non-single-byte character data, you may have to apply
user exit programs or other customizations to properly represent the data in Unicode
columns. For more information about user exit programs, see the Transformation Server for
AS/400 User Exits Guide.
Default Setting: *SAME
For more information about the handling of data in Unicode columns with the Unicode
Handling system parameter, see the Transformation Server Management Console
Administration Guide.
Parameters Description
AUDFILTRAN Indicates whether or not to audit both before and after images after a row update results in
only one of these images satisfying a defined row selection expression. Environments that
may want to enable this system parameter are:
• Using LiveAudit to audit source table changes.
• Recording both the before and after images in the subscription audit table when a row
update operation is applied to the assigned source table.
• Using row selection to filter rows placed in the subscription audit table. You can use this
parameter to override row selection when it is necessary to audit both before and after
images in the subscription audit table, but only one of these images satisfies the defined
row selection expression.
You can use two journal codes (FP and FB) to identify before and after images in the
subscription audit table that do not satisfy a row selection expression in this situation. For
more information about these codes and how they can be accessed from the &ENTTYP
journal control field, see the Transformation Server Management Console Administration
Guide.
Enter one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *YES—Audits both the before and after images when a row update results in only one of
these images satisfying a defined row selection expression.
• *NO—Audits only the after image that satisfies or does not satisfy a defined row
selection expression. This setting maintains existing Transformation Server behavior
prior to support for this parameter.
Default Setting: *SAME
The initial setting for this parameter differs based on whether you are upgrading from a
previous Transformation Server release that does not support this parameter or installing this
Transformation Server release. An initial setting of *YES applies when installing
Transformation Server on an iSeries server. The initial setting for Transformation Server
upgrades, as described above, is *NO. This ensures that existing product functionality is
maintained after completing this type of upgrade.
Result
Relevant messages are produced to the job log.
Example
CHGDMSVAL JOURNAL(JRNLIB/JRN1) NOTIFYQ(NOTQLIB/NOTQ1) NOTIFYCNT(10) RESTORE(*IMMED)
AUTCDE(12345678) UPDCOLUMN(*NO) CASCADE(*NO) REFWHLACT(*YES) USDEFJRN(*YES) HEARTTIME(60)
REPTPOSTIM(120) BKMARKSYNC(15) MONSAMPFRQ(15) STARTUP(180) PROGRESS(5) LCKTIMEOUT(40)
UNICODE_IS(CHAR) AUDFILTRAN(*YES)
Tables are journaled to journal JRN1 located in library JRNLIB.
Notification messages are sent to message queue NOTQ1 that is located in library NOTQLIB.
Transformation Server can detect up to 10 errors before a notification is sent to the message queue.
Tables are refreshed immediately when Transformation Server detects a restore.
The authorization code is 12345678.
Critical column filtering and cascading replication are not enabled, but refresh while
active is enabled.
User-defined journal entries are processed for replication.
The publisher waits for a maximum of 60 minutes for a reply from the subscriber before an attempt is made to end all
Transformation Server publisher and subscriber jobs for a subscription.
The publisher informs the subscriber every 120 seconds about its position in the current journal during inactive periods.
Synchronizations between the publisher and subscriber to convey information about the last committed change are performed
every 15 seconds.
Updates to the data store that is used to maintain replication latency metrics are made every 15 seconds.
The Transformation Server initialization phase terminates if it cannot be completed in 180 seconds.
Progress messages are generated every 5 seconds.
Transformation Server waits 40 seconds for a table or row to become unlocked before generating an error message in the event
log.
Data in GRAPHIC, VARGRAPHIC, CHARACTER, and VARCHAR columns are treated as single-byte characters.
When auditing changes applied to a source table, both the before and after images are placed in the subscription audit table when
a row update results in only one of these images satisfying a defined row selection expression.
Command Syntax
CHGDMTVAL [NOTIFYQ( )] [NOTIFYCNT( )] [AUTCDE( )] [REFRESH( )] [MIRROR( )] [COLUMNVAL( )] [NUMCOLMSG( )]
[CMTCTRL( )] [MSGNOTNULL( )] [DFTDATE( )] [MONSAMPFRQ( )] [STARTUP( )] [PROGRESS( )] [LCKTIMEOUT( )]
[RCDFMTCHK( )] [DBPERCENT( )]
Applies To
Target
Parameters Description
NOTIFYQ The name of the message queue where notifications are sent when the number of errors
detected by Transformation Server exceeds the notify message threshold (see Chapter 4 -
Transformation Server Commands © DataMirror Corporation 31 the NOTIFYCNT parameter
below).
Enter the name of the message queue or the following value:
*SAME—Keeps the present setting for this parameter.
Default Setting: *SAME
Message Queue Library
The name of the library where the message queue resides must precede the name of the
message queue.
Enter a library name or one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *LIBL—Specifies the set of libraries in your library list. The libraries are searched in
order for the first occurrence of the specified message queue.
• *CURLIB—Specifies the current library.
Default Setting: *LIBL
NOTIFYCNT The number of errors that Transformation Server generates before a notification is sent to the
notify message queue (see the NOTIFYQ parameter above).
Enter the number of errors or the following value:
*SAME—Keeps the present setting for this parameter. If a value smaller than the minimum
setting (see below) is specified, the minimum setting is used. If a value larger than the
maximum setting (see below) is specified, the maximum setting is used.
Default Setting: *SAME
Minimum Setting: 1 error
Maximum Setting: 99999 errors
Parameters Description
AUTCDE The authorization code that is issued by DataMirror Corporation. Adjustments to the
authorization code are required when moving from a temporary license to a permanent
license, when machine classes have changed, or when upgrading Transformation Server to a
new version.
Enter the authorization code or the following value:
*SAME—Keeps the present setting for this parameter.
Default Setting: *SAME
REFRESH Specifies whether Transformation Server ends a data refresh when an error is encountered.
Enter one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *YES—Specifies that Transformation Server end a refresh immediately after it detects
an error.
• *NO—Specifies that Transformation Server report the error and continue the refresh
after it detects the error.
Default Setting: *SAME
It is recommended that you set this parameter to *YES.
MIRROR Specifies whether Transformation Server ends mirroring when an error is encountered.
Enter one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *YES—Specifies that Transformation Server end mirroring immediately after it detects
an error.
• *NO—Specifies that Transformation Server report the error and continue mirroring after
it detects the error.
Default Setting: *SAME
It is recommended that you set this parameter to *NO.
COLUMNVAL Indicates whether Transformation Server should check decimal and numeric columns for
valid formats before applying the numeric data to the target table.
Enter one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *YES—Indicates that you want the data in each packed and zoned field to be validated
before it is applied to the target table. If invalid packed/zoned data is found, a message is
generated and the field is set to 0 automatically.
• *NO—Indicates that you do not want the data in each packed and zoned field to be
validated before it is applied to the target table. If you are sure that numeric data does not
have to be validated, set this parameter to *NO to maintain existing performance levels.
Default Setting: *SAME
Parameters Description
NUMCOLMSG Indicates how Transformation Server generates messages when it detects invalid numeric
data. Transformation Server can convert invalid numeric data to zero on the subscription
server (see the COLUMNVAL parameter below).
Enter one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *YES—Specifies that a message be generated for each invalid numeric field detected.
• *NO—Specifies that no messages be generated for each invalid numeric field detected.
If you are sure that numeric data does not have to be validated, set this parameter to *NO
to maintain existing performance levels.
• *NB—Specifies that no messages be sent when blank or uninitialized numeric fields are
detected. Messages for other types of invalid numeric data are still generated.
Default Setting: *SAME
MSGNOTNULL Indicates whether you want to generate the same message each time an attempt is made to
replicate NULL to a target table column that is not NULL-capable.
Enter one of the following parameters:
• *SAME—Keeps the present setting for this parameter.
• *YES—Generate a message each time NULL is replicated to a target table column that
is not NULL-capable.
• *NO—Do not generate a message each time NULL is replicated to a target table column
that is not NULL-capable. For all instances, you are not notified by a message.
Default Setting: *SAME
Parameters Description
DFTDATE The date that is returned when an invalid date is passed to the %TODATE column
manipulation function.
Enter one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *NEW—Returns the date 1901-01-01.
• *OLD—Returns the date 0001-01-01.
Default Setting: *SAME
For information about the %TODATE function, see the Transformation Server Management
Console Administration Guide.
MONSAMPFRQ The period of time, in seconds, between consecutive updates to a data store that is used to
maintain replication latency metrics. The data store is referenced by Management Console to
present replication latency information. This setting also represents how often the data store
is sampled to determine whether or not latency has risen above or fallen below specified
threshold settings. Latency messages are generated when latency rises above or falls below
the thresholds, and alerts can be configured in Management Console in response to a
generated message.
For more information about latency threshold settings and configuring notifications in
Management Console, see the Transformation Server Management Console Administration
Guide.
If a value smaller than the minimum setting (see below) is specified, the minimum setting is
used. If a value larger than the maximum setting (see below) is specified, the maximum
setting is used.
Default Setting: 5 seconds
Minimum Setting: 0 seconds
If this parameter is set to 0, replication latency metrics are not updated in the data store.
Maximum Setting: 3600 seconds (1 hour)
STARTUP The maximum amount of time, in seconds, to wait before terminating the Transformation
Server initialization phase. During Transformation Server initialization prior to data
replication, process termination on the publication or subscription server can result in a
suspension of the initialization phase. This parameter allows you to set the maximum waiting
period in this case. If a value smaller than the minimum setting (see below) is specified, the
minimum setting is used. If a value larger than the maximum setting (see below) is specified,
the maximum setting is used.
Default Setting: 120 seconds
Minimum Setting: 4 seconds
Maximum Setting: 3600 seconds (1 hour)
Parameters Description
PROGRESS The amount of time, in seconds, to wait before generating the next progress message.
Progress messages are placed in the event log. If a value smaller than the minimum setting
(see below) is specified, the minimum setting is used. If a value larger than the maximum
setting (see below) is specified, the maximum setting is used.
Default Setting: 0 seconds (no progress messages are issued)
Minimum Setting: 0 seconds (no progress messages are issued)
Maximum Setting: 7200 seconds (2 hours)
LCKTIMEOUT The amount of time, in seconds, Transformation Server waits for a table or row to become
unlocked before generating an error message in the event log. If a value smaller than the
minimum setting (see below) is specified, the minimum setting is used. If a value larger than
the maximum setting (see below) is specified, the maximum setting is used.
Default Setting: 30 seconds
Minimum Setting: 2 seconds
Maximum Setting: 60 seconds
Parameters Description
RCDFMTCHK Indicates whether or not Transformation Server checks the record formats of the physical and
logical files when the physical file is selected to receive mirrored data using a unique key.
Enter one of the following values:
• *SAME—Keeps the present setting for this parameter.
• *YES—Transformation Server checks the record formats of the physical and logical
files. Only a physical file that has the same record format as the logical file can be
selected as a destination of mirrored data using a unique key.
• *NO—Transformation Server does not check the record formats of the physical and
logical files. You can select a physical file to be the destination of mirrored data using a
unique key that does not have the same record format as the logical file.
Default Setting: *SAME
DBPERCENT The size of the range around each latency threshold setting.
Based on latency threshold settings defined in Management Console, a latency message is
generated when latency has risen above or fallen below a threshold. Latency is calculated at
regular intervals, where the interval is the current setting for the MONSAMPFRQ parameter
(see above). Alerts can be configured in Management Console in response to a generated
message. For more information about setting a latency threshold and configuring a
notification in Management Console, see theTransformation Server Management Console
Administration Guide.
This parameter, which is expressed as a percentage, allows you to pad a threshold equally
on both sides to create a range around the threshold. By adjusting this Transformation Server
parameter, the size of the range around the threshold can be increased or decreased, and
the threshold itself can be made thicker or thinner. A latency message is generated only
when latency has risen above the upper limit of the range or fallen below the lower limit of the
range. By changing the value assigned to this parameter, you can control the number of
latency messages placed in the event log. For an example illustrating how this parameter can
affect the number of latency messages that are generated, see the Deadband Percentage
system parameter. For more information on the Transformation Server for AS/400 system
parameters that you can configure through Management Console, see Transformation
Server Management Console Administration Guide.
Since there are two latency threshold settings in Management Console (a warning threshold
and a problem threshold), two separate ranges are defined when this parameter is set to a
non-zero value. Each range is attached to its threshold, and so the two ranges can overlap
with no change in behavior. If a value smaller than the minimum setting (see below) is
specified, the minimum setting is used. If a value larger than the maximum setting (see
below) is specified, the maximum setting is used.
Default Setting: 3%
Minimum Setting: 3%
Maximum Setting: 10%
Authorization Code
Use this system parameter to adjust the authorization code issued by DataMirror.
You may need to modify your authorization code when:
• Moving from a temporary license to a permanent license
• Machine classes have changed
• Upgrading to a new version of Transformation Server
Applies To—Source and Target
Startup Timeout
Use this system parameter to specify the maximum amount of time (in seconds) to wait before Transformation Server terminates
the initialization phase. During the initialization phase and prior to data replication, process termination on the source or target can
result in a suspension of the initialization phase. This parameter allows you to set the maximum waiting period in this case.
Applies To—Source and Target
Default Setting—120 seconds
Minimum Setting—4 seconds
Maximum Setting—3600 seconds
Note: If you set a value outside the acceptable range, then Transformation Server uses the defaults.
TCP_KEEPALIVE_SECS
Use this system parameter to determine the time (in seconds) Transformation Server waits before sending a keep alive
notification over the network. During idle periods, Transformation Server sends a keep alive notification to keep the connection
open.
Applies To—Source and Target
Default Setting—300 seconds (5 min)
Minimum Setting—0
Guidelines
• It is important you set this system parameter when you have a firewall connection that has been configured to timeout. This
prevents the firewall from closing the connection.
• To set this system parameter, do the following:
1 Create a data area named DMCOMMS by issuing the following command:
CRTDTAARA DTAARA(<TS product library>/DMCOMMS) TYPE(*CHAR) LEN(2000)
2 Set the timeout value by issuing the following command:
CHGDTAARA DTAARA(<TS product library>/DMCOMMS (521 10)) VALUE(‘<value>’)
where value is a 10-digit number that represents the setting for this system parameter. For example, to set to 1 minute,
issue:
CHGDTAARA DTAARA(DMIRROR/DMCOMMS (521 10)) VALUE(‘0000000060’)
• To prevent the firewall from closing during active data replication, set this parameter to a value lower than the configured
firewall timeout.
Related Topics
• Default Journal Name on page 132
Default Setting—DMCJRN
Synchronization Interval
Use this system parameter to set how often, in seconds, Transformation Server performs log synchronization between the source
and the target. Synchronization is achieved when the source reports to the target the position of the last committed change.
Applies To—Source
Default Setting—60 seconds
Minimum Setting—1 second
Maximum Setting—300 seconds
Guidelines
If you are replicating large volumes of information, you may want to set this system parameter to a lower number to remove
obsolete logs more frequently.
Note: If you set a value outside the acceptable range, then Transformation Server uses the defaults.
Commitment Control
Use this system parameter to enable or disable Transformation Server from using commitment control. Enabling commitment
control maintains transaction consistency during replication and ensures that all transactions are applied to the target system. If
there is a communications or server failure, and you have enabled this sytem parameter, then Transformation Server rolls back
the partially applied transaction to the last commit. For more information about commitment control, see Considerations for
Commitment Control (*LEVEL1) in Transformation Server for AS/400 Commands Reference.
Applies To—Target
Related Topics
• Allow Refresh While Active on page 131
Unicode Handling
Use this system parameter to set how Transformation Server treats data in a defined Unicode column. This system parameter
defines the system default method of treating data in Unicode columns for each installation of Transformation Server on a server.
Applies To—Source
The following DB2 UDB for iSeries data types are considered to be Unicode columns and are affected by the value assigned to
this system parameter:
• GRAPHIC or VARGRAPHIC with code page 1208 (UTF-8)
• CHARACTER or VARCHAR with code page 1208 (UTF-8)
The Unicode Handling system parameter can be set to either CHAR or NOCHANGE:
• CHAR—Transformation Server treats all data in Unicode columns as single-byte characters. Use this setting when
Unicode columns contain single-byte character data.
• NOCHANGE—Transformation Server treats all data in Unicode columns as a continuous bit stream. Use this setting
when Unicode columns contain non-single-byte character data. NOCHANGE ensures that Transformation Server
handles non-single-byte character data in the same way as previous Transformation Server releases.
Default Setting—NOCHANGE
Note: NOCHANGE does not ensure that replicated non-single-byte character data in Unicode columns are
represented properly on the target. For replicated non-single-byte character data, you may have to apply user
exit programs or other customizations to properly represent data in Unicode columns. For more information
about user exit programs, see Transformation Server for AS/400 User Exits Guide.
Related Topics
• For more information on how to set handling for unicode character encodings, see Transformation Server Management
Console Administration Guide.
Deadband Percentage
Use this system parameter to set the size of the range (in percentage) around each latency threshold. Based on the latency
thresholds you have set in Management Console, Transformation Server generates a message when latency rises above or falls
below the range of the threshold. Transformation Server calculates latency at regular intervals. This parameter, which is
expressed as a percentage, lets you pad an equal threshold on both sides to create a range around the threshold. By adjusting
this parameter, you can increase or decrease the size of the range around the threshold.
Applies To—Target
Default Setting—3%
Minimum Setting—3%
Maximum Setting—10%
Example
For example, if you set a latency threshold of 5 minutes in Management Console and set the Deadband Percentage to 10%, then
Transformation Server applies a 10% range around the 5-minute threshold. Transformation Server performs the following
calculations to determine the lower and upper limits (in minutes) of the range around the threshold:
Padding = 10% of 5 minutes = 0.5 minutes (rounded up to 1 minute)
Padding is rounded up or down to the nearest whole minute.
Upper limit of range = 5 minutes + 1 minute (padding) = 6 minutes
Lower limit of range = 5 minutes - 1 minute (padding) = 4 minutes
As a result, a latency message is generated only when latency rises above 6 minutes or falls below 4 minutes.
Given sample latency over a ten minute period in where latency is calculated every minute, three latency messages are
generated.
Figure 1 Latency Message Generation—10% Setting
If this system parameter is set to 3 (the default setting) for the same example, no padding is applied to the latency threshold.
Therefore, a latency message is generated each time latency crosses over the latency threshold of 5 minutes. Based on the same
sample latency in , where latency is calculated every minute, five latency messages are generated when this system parameter is
set to 3 ().
Figure 2 Latency Message Generation—3% Setting
If the number of latency messages generated over the ten minute period for the 10% (3 latency messages) and 3% (5 latency
messages) settings are averages, an additional 288 latency messages would be generated each day if this system parameter is
not changed from its default setting to 10%.
Since there are two latency thresholds that you can set (a warning threshold and a problem threshold), two separate ranges are
defined when padding is at least one minute. In this case, each range is attached to its threshold, and the two ranges can overlap
with no change in behavior.
Note: If you set a value outside the acceptable range, then Transformation Server uses the defaults.
Related Topics
• For more information on how to set latency thresholds, see Setting Latency Thresholds and Notifications in Transformation
Server Management Console Administration Guide.
Related Topics
• Numeric Column Validation on page 139
Data Types
Data type system parameters let you control how Transformation Server handles certain data types.
Related Topics
• For more information about the %TODATE column function, see Date Conversion—%TODATE in the Transformation Server
Management Console Administration Guide.
Related Topics
• For more information about journal codes, see the section on Journal Control Fields in the Transformation Server
Management Console Administration Guide.
Related Topics
• Notify Message Threshold on page 141
Related Topics
• Notify Message Queue on page 141
Related Topics
• Notify Message Queue on page 141
Parameter Description
Return Code (RTNCD) The return code that indicates whether or not the user exit program was successful. In the
user exit program, return an error message ID if errors occurred in the user exit program or
blank characters if no errors occurred in the user exit program.
User Exit Program Name The name of the user exit program that was called. This is the name of the program that you
(PGMNM) specify in Management Console. For more information on how to configure user exits in
Management Console, see Transformation Server Management Console Administration
Guide.
User Exit Point (ENTRYB) The table/row-level user exit point where the user exit program was called.
Returns either:
• 1—Before Clear
• 2—After Clear
• 3—Before Insert
• 4—After Insert
• 5—Before Update
• 6—After Update
• 7—Before Delete
• 8—After Delete
• 9—Before Refresh
• 10—After Refresh
Publisher Before Image The row before image in the source table.
(BDATA)
Publisher After Image The row after image in the source table.
(ADATA)
Publisher Before Image NULL The number of NULL-capable fields in the before image (see BDATA above). Each NULL-
Indicator Count (BNULCB) capable field will have a NULL indicator (see BNULL below)
Publisher After Image NULL The number of NULL-capable fields in the after image (see ADATA above). Each NULL-
Indicator Count (ANULCB) capable field will have a NULL indicator (see ANULL below).
Publisher Before Image NULL NULL indicators for all NULL-capable fields in the before image (see BDATA above).
Indicators (BNULL)
Returns either:
• 0—NULL-capable field is not set to NULL.
• 1—NULL-capable field is set to NULL.
Parameter Description
Publisher After Image NULL NULL indicators for all NULL-capable fields in the after image (see ADATA
Indicators (ANULL)
above).
Returns either:
• 0—NULL-capable field is not set to NULL.
• 1—NULL-capable field is set to NULL.
Publisher Before Image Journal control information associated with the before image (see BDATA above). For
Journal Data (BJRNL) information about the accessible journal control information, see Journal Control Fields below
Publisher After Image Journal Journal control information associated with the after image (see ADATA above).For
Data (AJRNL) information about the accessible journal control information, see Journal Control Fields
below.
Subscriber Final Image Length The length of the fully formatted (final) image (see ATDATA below) that will be applied to the
(DTLNGT) target table.
The fully formatted (final) image and the length of this image will contain inconsistent
information in the following situation:
Note: When the subscriber job is operating under SQL update mode (in the
target system parameters), an update operation is performed, and there
are target columns with default values. In this case, the length of the final
image and the image itself will not include the columns with the default
values. Therefore, the length of the final image for a row update
operation will be shorter than the length of the final image for a row insert
operation.
Subscriber Final Image The fully formatted (final) image that will be applied to the target table.
(ATDATA)
Note: When the subscriber job is operating under SQL update mode (in the
target system parameters), an update operation is performed, and there
are target columns with default values. In this case, the length of the final
image and the image itself will not include the columns with the default
values. Therefore, the length of the final image for a row update
operation will be shorter than the length of the final image for a row insert
operation.
The fully formatted image contains the results of data transformations applied to the
replicated after image in the target environment. For target tables that have been mapped
under summarization, row consolidation (one-to-one and one-to-many), and adaptive apply,
this image, in before user exit program invocations, will contain only default values (blanks,
zeroes, and so on) instead of the final image.
Subscriber Final Image NULL The number of NULL-capable fields in the fully formatted (final) image. Each NULL-capable
Indicator Count (NULCNT) field will have a NULL indicator (see NULIND below).
Parameter Description
Subscriber Final Image NULL NULL indicators for all NULL-capable fields in the fully formatted (final) image.
Indicators (NULIND) Returns either:
• 0—NULL-capable field is not set to NULL.
• 1—NULL-capable field is set to NULL.
source identifier (SYSTEM) The source identifier identifying the subscription containing the source table. Source
identifiers and subscriptions are defined in Management Console. For more information
about source identifiers and subscriptions, see the TTransformation Server Management
Console Administration Guide.
Journal Entry Length The length of the journal entry that includes the entry length field and all
(JOEENTL) subsequent positions of the journal entry.
Journal Sequence Number The sequence number assigned to the journal entry by the system.
(JOSEQN)
Journal Library The name of the library where the journal is located.
(JOJRNLIB)
Journal Receiver Library The name of the library where the journal receiver is located.
(JORCVLIB)
Journal Entry Timestamp The system date and time when the entry was journaled.
(JOTSTP)
Publisher Job Name The name of the job that generated the journal entry.
(JOJOB)
Publisher Job User The user profile of the user that started the job (see JOJOB above).
(JOUSER)
Publisher Job Number The job number of the job generated the journal entry (see JOJOB above).
(JONBR)
Publisher Program Name The name of the program that generated the journal entry.
(JOPGM)
Ssource Table Name The name of the source for which the journal entry was generated.
(JOOBJ)
Source Table Library The name of the library containing the source table (see JOOBJ above).
(JOLIB)
Publication RRN The relative record number (RRN) of the row that caused the journal entry or a count that is
(JOCTRR) pertinent to the specific type of journal entry.
Journal Flag (JOFLAG) Based on the type of entry, indicates whether or not there is extended information.
The following values determine whether or not extended information is presented:
• 1—Extended information is available.
• 0—No extended information is available.
The extended information is placed immediately after the Entry Specific Data and will have
the following structure:
• Length (4 bytes)—Total length of the extended entry.
• Format (7 bytes)— Format of extended information. Currently, it is ‘DM_0100’.
• Extended Object Name (128 bytes)—Full name of source table.
• Extended Schema Name (137 bytes)—Full name of source schema.
Commit Cycle ID The number that identifies the commit cycle. This number only applies to an entry associated
(JOCCID) with a commitment transaction.
Publisher Job User The name of the user profile under which the job (see JOJOB above) was running when the
(JOUSPF) entry was created.
Publication Server Name The name of the system on which the journal entry was generated.
(JOSYNM)
The total length of all journal control fields is 191. This is equal to the defined size of both the BJRNL and AJRNL parameters. For
more information about the journal control fields, see the appropriate IBM publication.
Return Code (LK-RETURN- The return code that indicates whether or not the user exit program was successful. In the
CODE) user exit program, return an error message ID if errors occurred in the user exit program or
blank characters if no errors occurred in the user exit program.
User Exit Program Name The name of the user exit program that was called. This is the name of the program that you
(LKPROGRAM) specify in Management Console. For more information on how to configure user exits in
Management Console, see Transformation Server Management Console Administration
Guide.
User Exit Point (LK-ENTRY) The table/row-level user exit point where the user exit program was called.
Returns either:
• 1—Before Clear
• 2— After Clear
• 3—Before Insert
• 4—After Insert
• 5—Before Update
• 6—After Update
• 7—Before Delete
• 8—After Delete
• 9—Before Refresh
• 10—After Refresh
Publisher Before Image (LK- The row before image in the source table.
BEFORE-RECORD)
Publisher After Image (LK- The row after image in the source table.
AFTER- RECORD)
Publisher Before Image NULL The number of NULL-capable fields in the before image (see LK-BEFORE-RECORD above).
Indicator Count (LK BEFORE- Each NULL-capable field will have a NULL indicator (see LK-BEFORENULLINDS below).
NULLIND-CNT)
Publisher After Image NULL The number of NULL-capable fields in the after image data (see LK-AFTER RECORD
Indicator Count (LK-AFTER- above). Each NULL-capable field will have a NULL indicator (see LK-AFTERNULLINDS
NULLIND-CNT) below).
Publisher Before Image NULL NULL indicators for all NULL-capable fields in the before image (see LKBEFORE-RECORD
Indicators (LK-BEFORE- above).
NULLINDS) Returns either:
• 0—NULL-capable field is not set to NULL.
• 1—NULL-capable field is set to NULL.
Parameter Description
Publisher After Image NULL NULL indicators for all NULL-capable fields in the after image (see LKAFTER-RECORD
Indicators (LK-AFTER- above).
NULLINDS)
Returns either
• 0—NULL-capable field is not set to NULL.
• 1—NULL-capable field is set to NULL.
Publisher Before Image Journal control information associated with the before image. (see LK-BEFORE-RECORD
Journal Data above).
(LK-BEFORE-JOURNAL
Publisher After Image Journal Journal control information associated with the after image data (see LKAFTER
Data (LK-AFTER-JOURNAL) RECORD above).
Subscriber Final Image Length The length of the fully formatted (final) image (see LK-DM-BUFFER below) that will be
applied to the target table.
(LK-DATA-LENGTH)
Note: The parameters containing the fully formatted (final) image and the
length of this image will contain inconsistent information in the following
situation: when the subscriber job is operating under SQL update mode
(in the subscription system parameters), an update operation is
performed, and there are subscription columns with default values. In this
case, the length of the final image and the image itself will not include the
columns with the default values. Therefore, the length of the final image
for a row update operation will be shorter than the length of the final
image for a row insert operation.
Subscriber Final Image (LK- The fully formatted (final) image that will be applied to the target table.The fully formatted
DM-BUFFER) image contains the results of data transformations that may have been applied to the
replicated after image in the target environment. For target tables that have been assigned
under summarization, row consolidation (one-to-one and one-to-many), and adaptive
apply,this image, in before user exit program invocations, will contain only default values
(blanks, zeroes, and so on) instead of the final image.
Note: The parameters containing the fully formatted (final) image and the
length of this image will contain inconsistent information in the following
situation: when the subscriber job is operating under SQL update mode
(in the subscription system parameters), an update operation is
performed, and there are subscription columns with default values. In this
case, the length of the final image and the image itself will not include the
columns with the default values. Therefore, the length of the final image
for a row update operation will be shorter than the length of the final
image for a row insert operation.
Subscriber Final Image NULL The number of NULL-capable fields in the fully formatted (final) image (see LK-DM-BUFFER
Indicator Count (LK DM- above). Each NULL-capable field will have a NULL indicator (see LK-DM-NULLINDS below).
NULLIND-CNT)
Parameter Description
Subscriber Final Image NULL NULL indicators for all NULL-capable fields in the fully formatted (final) image
Indicators (LK-DM-NULLINDS) (see LK-DM-BUFFER above).
Returns either:
• 0—NULL-capable field is not set to NULL.
• 1—NULL-capable field is set to NULL.
source identifier (LK- The source identifier identifying the subscription containing the source table.Source
SYSTEMID) identifiers and subscriptions are defined in Management Console. For more information on
how to add a subscription in Management Console, see Transformation Server Management
Console Administration Guide.
Return Code The return code that indicates whether or not the user exit program was successful. In the
(pReturnCode) user exit program, return an error message ID if errors occurred in the user exit program or
blank character if no errors occurred in the user exit program.
User Exit Program Name The name of the user exit program that was called. This is the name of the program that you
specify in Management Console. For more information on how to configure a user exit
(pProgramName)
program in Management Console, see Transformation Server Management Console
Administration Guide.
User Exit Point The table/row-level user exit point where the user exit program was called.
(entryPointCode) Returns either:
• 1—Before Clear
• 2—After Clear
• 3— Before Insert
• 4—After Insert
• 5— Before Update
• 6—After Update
• 7—Before Delete
• 8—After Delete
• 9—Before Refresh
• 10—After Refresh
Publisher Before Image The row before image in the source table.
(pBeforeRecordData)
Publisher After Image The row after image in the source table.
(pAfterRecordData)
Publisher Before Image The number of NULL-capable fields in the before image (see pBeforeRecordData above).
NULL Indicator Count Each NULL-capable field will have a NULL indicator (see pBeforeRecordNullInd below).
(nullIndBeforeCount)
Publisher After Image The number of NULL-capable fields in the after image (see pAfterRecordData above). Each
NULL Indicator Count NULL-capable field will have a NULL indicator (see pAfterRecordNullInd below).
(nullIndAfterCount)
Publisher Before Image NULL indicators for all NULL-capable fields in the before image (see pBeforeRecordData
NULL Indicators above).
(pBeforeRecordNullInd) Returns either:
• 0—NULL-capable field is not set to NULL.
• 1—NULL-capable field is set to NULL.
Parameter Description
Publisher After Image NULL indicators for all NULL-capable fields in the after image (see pAfterRecordData above).
NULL Indicators
Returns either:
(pAfterRecordNullInd)
• 0—NULL-capable field is not set to NULL.
• 1—NULL-capable field is set to NULL.
Publisher Before Image Journal control information associated with the before image. For information about the
Journal Data accessible journal control information, see Journal Control Fields below.
(pBeforeJournalHeader)
Publisher After Image Journal control information associated with the after image. For information about the
Journal Data accessible journal control information, see Journal Control Fields below.
(pAfterJournalHeader)
Subscriber Final Image The length of the fully formatted (final) image (see pTSInternalBuffer below) that will be
Length applied to the target table.1
(internalDataLength)
Subscriber Final Image The fully formatted (final) image that will be applied to the target table. FOOTNOTE
(pTSInternalBuffer) Note: The fully formatted image contains the results of data transformations
that may have been applied to the replicated after image in the target
environment. For target tables that have been mapped under
summarization, row consolidation (one-to-one and one-to-many), and
adaptive apply, this image, in before user exit program invocations, will
contain only default values (blanks, zeroes, and so on) instead of the final
image.
Subscriber Final Image The number of NULL-capable fields in the fully formatted (final) image (see pTSInternalBuffer
NULL above). Each NULL-capable field will have a NULL indicator (see pTSInternalNullInd below).
Indicator Count
(internalNullIndCount)
Subscriber Final Image NULL indicators for all NULL-capable fields in the fully formatted (final) image (see
NULL Indicators pTSInternalBuffer above).
(pTSInternalNullInd) Returns either:
• 0—NULL-capable field is not set to NULL.
• 1—NULL-capable field is set to NULL.
source identifier The source identifier identifying the subscription containing the source table. Source
(pSourceSystemId) identifiers and subscriptions are defined in Management Console. For more information on
how to add a subscription in Management Console, see Transformation Server Management
Console Administration Guide.
Related Topics
• For more information on how to setup a notification so that it is handled by a user exit program, see To set a notification using
a user exit Program (TS for AS/400 ) in Transformation server Management Console Administration Guide.
Parameter Description
Return Code (RTNCD) The return code that indicates whether or not the user exit program was
successful.
In the user exit program, return blank characters if no errors occurred in the user exit program
or non-blank characters if an error occurred.
User Exit Program Name The name of the user exit program that was called.
(PGMNM)
This is the name of the program that you specify in Management Console.
For more information on how to configure a user exit in Management Console, see
Transformation Server Management Console Administration Guide.
Source (Publisher) or The environment in which the user exit program was called.
Target Returns either:
(Subscriber) Indicator
• 1: Publisher
(ENGTYP)
• 2: Subscriber
Publisher ID or The source identifier (if program was called from a target) or the name of the subscription (if
Subscription program was called from a source) from which the user exit program was called.
(SRTGTN) Source identifiers and subscriptions are defined in Management Console.
For more information on how to add a subscription in Management Console, see the
Transformation Server Management Console Administration Guide.
Parameter Description
Zone (ZONE) The functional zone for which the user exit program was invoked.
If Source (Publisher) or Target (Subscriber) Indicator (see above) is set to 1,
one of the following zone settings apply:
• 1: SCRAPE/REFRESH
• 2: COMMUNICATIONS
• 3: ENVIRONMENT
• 4: JOURNAL/LOG MAINTENANCE
If Source (Publisher) or Target (Subscriber) Indicator (see above) is set to 2,
one of the following zone settings apply:
• 1: APPLY
• 2: COMMUNICATIONS
• 3: ENVIRONMENT
Category (CTGRY) The message category for which the user exit program was invoked.
Returns either:
• 1: Fatal
• 2: Error
• 3: Informational
• 4: Status
• 5: Operational
Message Id (MSGID) The identifier of the message that caused the user exit program to be invoked.
Message Text (MSGTXT) The text that has been substituted into the message (see MSGID above).
Message Length (MSGLN) The length of the text (in bytes) that has been substituted into the message see MSGID
above).
Send Date (SNDDTE) The date when the message (see MSGID above) was sent.
The date is expressed in *ISO format.
Send Time (SNDTME) The time when the message (see MSGID above) was sent.
The time is expressed in *ISO format.
Parameter Description
Target Table Name The name of the target table that has been identified to receive transferred data.
(TGTTBL)
Parameter Description
Target Table Library The name of the library where the target table (see TGTTBL above) is located.
(TGTLIB)
Target Table Member The name of the member in the target table that has been identified to receive transferred
data.
(TGTMBR)
Parameter Descriptions
Control Structure A structure containing various items of information about the publisher and subscriber, as
(*pControl) well as various indicators.For more information about the structure, see Control Structure.
Publisher Row Before A structure containing the image of the row in the source table before changes were applied
Image to the row. For information about the structure, see Row Image Structure. The control
structure contains an indicator that you can use to determine whether or not this image was
(*pBeforeImage)
passed to the conflict resolutions user exit program. For more information about this
structure, see Control Structure.
Publisher Row After Image A structure containing the image of the row in the source table after changes were applied to
the row. For more information about the structure, see Row Image Structure. The control
(*pAfterImage)
structure contains an indicator that you can use to determine whether or not this image was
passed to the conflict resolutions user exit program. For more information about this
structure, see Control Structure.
Subscriber Row Before A structure containing the image of the row in the target table when the user exit program was
Image called. For more information about the structure, see Row Image Structure. The control
structure contains an indicator that you can use to determine whether or not this image was
(*pTargetImage)
passed to the conflict resolutions user exit program. For more information about this
structure, see Control Structure.
Result Image A structure containing the image of the row that will be applied to the target table. If the
(*pDesiredImage) conflict is resolved by the user exit program, this is the image defined in the user exit
program, returned to the calling environment, and subsequently applied to the target table.
This parameter applies only to conflicts caused by rows being inserted or updated in the
source table (see Operation Type). For row deletes, do not assign an image to this
parameter. For more information about the structure, see Row Image Structure.
The control structure contains an indicator that you can use to determine whether or not this
image can be returned by the user exit program. For more information about this structure,
see Control Structure.
Notifications CL DMCALRMCLP
Warning: It is strongly recommended that you test all sample programs before they are invoked in your production
environment.
Troubleshooting
Troubleshooting and diagnostic information is provided in the DataMirror Knowledge Base that you can access from the
DataMirror web site at www.datamirror.com. Articles in the knowledge base are categorized by product, but you can also search
for information using keywords and other attributes. The knowledge base also contains articles translated into different languages.
You must complete a registration process before accessing the knowledge base.
Trademark Notice
CONSTELLAR, DATA FROM WHERE IT IS TO WHERE IT NEEDS TO BE, DATAMIRROR, DATAMIRROR DB/XML
TRANSFORM, DATAMIRROR DB/XML VISION, DATAMIRROR SYNAPSE MOBILITY, DATAMIRROR TRANSFORMATION
SERVER, DBMIRROR, ENTERPRISE ADMINISTRATOR, ERP GATEWAY, HA SUITE, HIGH AVAILABILITY SUITE,
ICLUSTER, ICLUSTER FOR EMC SYMMETRIX, IDELIVER, IREFLECT, ITRANSMIT, JOBSCHEDULER, MANAGEMENT
CONSOLE, OBJECTMIRROR, QUICKMARTS, SWITCHOVER SYSTEM, THE EXPERIENCE OF NOW, TRANSFORMATION
SERVER, TRANSFORMATION SERVER/ES, TRANSFORMATION SERVER/EVENT SERVER, TRANSFORMATION SERVER
MANAGEMENT CONSOLE, and XTREMECACHE are registered, unregistered or pending trademarks of DataMirror Corporation
and may not be used without the express written permission of DataMirror Corporation. POINTBASE, POINTBASE EMBEDDED,
POINTBASE MICRO, POINTBASE UNISYNC, and TRANSFORMATION SERVER FOR MOBILE are trademarks of DataMirror
Mobile Solutions Inc. ("PointBase") and DataMirror Corporation's use of these trademarks is by way of license with PointBase.
This list of trademarks may not be complete; other trademarks or registered trademarks may be owned by DataMirror Corporation
from time to time and may be used in this manual.
All other trademarks or service marks are the properties of their respective owners.
Disclaimers
DataMirror Corporation reserves the right to revise this manual and make periodic changes to its content without obligation on
DataMirror Corporation's part to notify any person of such revisions or changes. DataMirror Corporation does not assume
responsibility for the use of this manual. DataMirror Corporation makes no representation or warranty as to the accuracy of the
contents of this manual. All statements made and information provided in this manual is provided on an errors and omission
excepted (E. & O.E.) basis only.
IBM DATAMIRROR TRANSFORMATION SERVER® for AS/400 Version 6.1
DataMirror Corporation, an International Business Machines Corporation Company
March 7, 2008