IBMi method 2 - connect_cdc_mimix_share - 6.x

Since the Connect CDC Listener can also be started from the “green screen” using the OMNIL command language program that is created in the Connect CDC command library, enter the following command to start the Connect CDC Listener in batch:

ADDLIBLE <omni_library>SBMJOB CMD(CALL PGM(`INSTALL_LIBRARY`/OMNIL)) JOB(OMNIL)

where COMMAND_LIBRARY is the name of the library created when Connect CDC is installed. Doing it this way then puts it in batch, that is, runs it in the background, and frees up the green screen for other work.

The Connect CDC Listener log is located in the directory where Connect CDC is installed in the kernel subdirectory. Since you can have more than one Connect CDC Listener at a time using different port numbers, the logs are identified by the combination of the machine name and the port number, for example:

C:\PreciselyConnect\ConnectCDC60\kernel\mountain_8989.log

where mountain is the machine name, and 8989 is the port number.

The connection test may also fail for these reasons:

• Error message says something like invalid connection handle.

When Connect CDC Listener is recycled (shutdown and restarted) at a host, any Connect CDC Director connections to servers on that host must be disconnected manually after Connect CDC Listener is restarted. If you don't do this, you may receive an error about an invalid connection handle.

• Error message says something similar to the following:

error executing select count(*) from rp_db

Indicates metabase connection is failing. Might have incorrect user, or might need metabase to be installed or re-installed.

• Error message references a socket problem.

This is likely a problem connecting to Connect CDC Listener. If you receive the error on initial use of a connection, check the following:

• Are the machine name and/or listener port number correct?

• Is Connect CDC Listener running at the machine/port?

• Is SSL compatible between client and Connect CDC Listener?

• Error message references a problem with privileges.

You have logged on as a user who does not have permission to perform these activities. Although the message is database specific, it would look similar to the following:

 

Log on as a user with sufficient privileges.