After the IBM i Install

License File

If you are FTPing the licensing file, you must specify that it is binary. The initial installation may be done without the license file. It is, however, required before you can commit a model. Rename this file to “omnilicense” and save it in every kernel directory where components are installed. See the following example:

C:\PreciselyConnect\ConnectCDCV58\kernel\omnilicense

where omnilicense is the licensing file name.

The license file must be populated across all kernel directories in order for the data movement components to work correctly.

2011-04-01 09:09:16,528 [main] ERROR:-Exception obtaining Connect CDC license information=java.io.FileNotFoundException: omnilicense (No such file or directory)
    			Connect CDC Listener has been terminated.

Start Listener

• By default, an IBM i installation creates and attempts to start the Listener in a subsystem called MXSHARE from the Command library specified on the OS400 Installation Parameters window.

A local or a remote reconfiguration starts the Listener by starting the MXSHARE subsystem. To determine if Listener is active, create a model with a host defined with the appropriate host name and port and test the connection.

Stop Listener

To stop Listener on an IBM i machine, from a shell in an IBM i green screen, do the following:

• Issue a “cd” command to change to the kernel subdirectory under the install directory.

• Issue the command:

omnilistener stop

A message similar to the following displays:

ConnectCDCV58/<machine name>/kernel $ omnilistener stop
    			2011-04-01 09:17:43,724 [main] INFO:Connect CDC <Version information> Date: 2011/03/30 05:03:46
    			 
    			2011-04-01 09:17:43,790 [main] INFO:<license information>
    			2011-04-01 09:17:43,793 [main] INFO:Using OmniSocketFactoryImpl13
    			2011-04-01 09:17:43,833 [main] INFO:Socket created from null to <machine name> at port 20007
    			2011-04-01 09:17:43,836 [main] INFO:Entering verifySocket
    			2011-04-01 09:17:43,837 [main] INFO:Socket created from null to <machine name> at port 20007
    			2011-04-01 09:17:44,144 [main] INFO:Recd:+HELLO 20007 1.171
    			 
    			Type help for a list of available commands.
    			Command>
    			Connection with Connect CDC Listener has been terminated.

Resize DB2/400 Target Files

If you intend to use Console for monitoring and control tasks, distribution can increase the size of DB2/400 target files. This can be a problem for non-SQL files defined with a specified size limit (files created using CRTPF (create physical file) are given by default a size of 13,000 rows). You may need to resize or reorganize your target files.

When Data Integration deletes target records, the deleted record slot is not reused, so the target file may grow to its maximum and cause Data Integration to receive an error or hang in a message wait state. Copy's default apply mode is the most likely to encounter this problem, since it immediately deletes all specified target records before inserting their copies.

Before using Data Integration, do one of the following:

• Adjust the size of any at-risk target files using the CHGPF SIZE(*NOMAX) command.

• Create new target tables with SQL and not CRTPF.

Otherwise, you must monitor the target file sizes and use RGZPFM as necessary to reorganize files to reclaim space.

Reconfigure

Before doing a reconfiguration, shut down Listener.

In addition to doing a full install, you can reconfigure an existing installation. The steps for running the GUI Installer or the Batch Installer are the same as for an initial, full install. All parameter values may be changed except the recipient Host and the installation directory.

• The GUI Installer attempts to detect an existing installation  on the installing host by creating a file in a well-known writeable system directory. The directory is the “temporary I/O” directory provided by the Java system property java.io.tmpdir. The 'file' is either a link to the <host_name>.properties file in the host installation directory, or a copy.

The Installer checks for the last installation done on the host being installed. It does not check for installations on the same host done prior to the last.

It displays the parameter values specified on the prior install in all windows except the initial window where the recipient host is defined.

• The Batch Installer reconfigures a host installation if the reconfigure keyword parameter in the host.list file is Y.

Create User Spaces

Create user spaces, file type USRSPC, for the change selector configuration files. If your system restricts user spaces, the metabase libraries must be added to the system variable QALWUSRDMN. Check the setting with “dspsysval qalwusrdmn”. Its value will be either *ALL or a list of libraries. If the value is a library list, the system administrator will need to add the installation and metabase libraries to this list following the installation.