Command Reference

10.5.4
- 10.5.5
- 10.5.3
- 10.0

Back Next

Example 3: Configuring a PowerExchange Logger Process to Receive pwxcmd Commands

This example configures a PowerExchange Logger for Linux, UNIX, and Windows process to receive pwxcmd commands.

You issue pwxcmd commands from a Linux, UNIX, or Windows system that is remote from the system where the PowerExchange Logger for Linux, UNIX, and Windows process runs.

You must include pwxcmd command configuration statements in the DBMOVER configuration files on both systems.

Additionally, you must include a CONDENSENAME statement in the pwxccl.cfg configuration file on the system where the PowerExchange Logger for Linux, UNIX, and Windows process runs. The CONDENSENAME statement defines a service name for the PowerExchange Logger for Linux, UNIX, and Windows process.

To configure a PowerExchange Logger process to receive pwxcmd commands:

In the pwxccl.cfg configuration file on the Linux, UNIX, or Windows system where the PowerExchange Logger for Linux, UNIX, and Windows process runs, include a CONDENSENAME statement. The CONDENSENAME statement defines a service name for the PowerExchange Logger for Linux, UNIX, and Windows process that receives pwxcmd commands. For example:

CONDENSENAME=COND_NODE

In the DBMOVER configuration file on the system where the PowerExchange Logger for Linux, UNIX, and Windows process runs, include an SVCNODE statement. The SVCNODE statement specifies a TCP/IP port on which the command-handling service for the PowerExchange Logger for Linux, UNIX, and Windows process listens for pwxcmd commands. For example:

SVCNODE=(COND_NODE,6003)

In the SVCNODE statement:

The first parameter value, COND_NODE, is the service name. This service name must match the service name in the corresponding CONDENSENAME statement. The CONDENSENAME statement is in the pwxccl.cfg configuration file on the system where the PowerExchange Logger for Linux, UNIX, and Windows process runs.

The second parameter value, 6003, is the TCP/IP port number on which the service listens for pwxcmd commands. This port number must match the port number in the corresponding CMDNODE statement. The CMDNODE statement is in the DBMOVER configuration file on the Linux, UNIX, or Windows system from which you issue pwxcmd commands.

In the dbmover.cfg configuration file on the Linux, UNIX, or Windows system from which you issue pwxcmd commands, include a CMDNODE statement. The CMDNODE statement specifies connection information for a PowerExchange Logger for Linux, UNIX, and Windows process to which you want to send pwxcmd commands. For example:

CMDNODE=(COND_NODE,CONDENSE,remote_host,6003)

In the CMDNODE statement:

The first parameter value, cndnode, is a service name. This service name can be any name you want. Specify this service name when you issue pwxcmd commands to the PowerExchange Logger for Linux, UNIX, and Windows process.

The second parameter value, CONDENSE, is the service type for a PowerExchange Logger for Linux, UNIX, and Windows process.

The third parameter value, remote_host, is the name of the host where the PowerExchange Logger for Linux, UNIX, and Windows process runs.

The fourth parameter value, 6003, is the TCP/IP port number. This port number must match the port number in the corresponding SVCNODE statement. The SVCNODE statement is in the DBMOVER configuration file on the system where the PowerExchange Logger for Linux, UNIX, and Windows process runs.

In the pwxcmd command that you send to the PowerExchange Logger for Linux, UNIX, and Windows process, specify the -service
option as follows:

pwxcmd condense -service cndnode

The service name on the pwxcmd command must match the service name in the corresponding CMDNODE statement. The CMDNODE statement is in the DBMOVER configuration file on the Linux, UNIX, or Windows system from which you issue pwxcmd commands.

Rename Saved Search

Table of Contents

Command Reference

Command Reference

Example 3: Configuring a PowerExchange Logger Process to Receive pwxcmd Commands

Example 3: Configuring a PowerExchange Logger Process to Receive pwxcmd Commands