Installation and Upgrade Guide

10.5.8
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Step 7. Create the PowerExchange Environment

In this step, you use the CRTPWXENV command to create a PowerExchange environment.

A PowerExchange environment includes the following libraries:

dtllib. PowerExchange software library.

datalib. Library that contains data files such as the CCT file for capture registrations, PowerExchange configuration parameters, and the LISTENER and DTLOS_MSQG message queues.

condlib. Library that is used only for CDC with PowerExchange Condense. This library contains PowerExchange Condense condense files; lock files; the CFGCOND(CAPTPARM) configuration member; and the CHECKPOINT, CMDHANDLER, COLLECTOR, CONDENSE, CONTROLLER and DUMP message queues. PowerExchange deletes files in this library during normal operation. Do not place your own files in this library without first contacting Informatica Global Customer Support.

cpxlib. Library that contains extraction maps. This library is required only for CDC processing.

Ensure that the CRTPWXENV command runs under a user profile that has the required authority. For more information, see User ID Requirements. If you plan to use remote journals for CDC, ensure that the user profile has the required authority on both the local and remote systems.

Issue the following command:

ADDLIBLE LIB(dtllib) POSITION(*FIRST)

Issue the CRTPWXENV command to create the PowerExchange environment. The parameters that you specify on the CRTPWXENV command depend on whether you use CDC processing or only the bulk data movement function and whether you restored dtllib to an IASP.

If you capture change data from journal receivers on the same system as the Db2 database, use the following command syntax:

CRTPWXENV DESC('user_description') 
DATALIB(datalib) CONDLIB(condlib) 
ASPDEV(*NONE) CRTSYSOBJ(*YES) CPXLIB(cpxlib) 
JRNEXTSEQ(nnnn) RMTOSLEVEL(*LOCAL)

If you capture change data from remote journal receivers, use the following command syntax:

CRTPWXENV DESC('user_description') 
DATALIB(datalib) CONDLIB(condlib) 
ASPDEV(*NONE) CRTSYSOBJ(*YES) CPXLIB(cpxlib) 
JRNEXTSEQ(nnnn) RMTASPDEV(*NONE) 
RMTRDBDIRE(database_name) 
RMTSYSNAME(host_name) RMTOSLEVEL(os_level)

If you complete bulk data movement operations only, use the following command syntax:

CRTPWXENV DESC('user_description') 
DATALIB(datalib) CONDLIB(*NONE) 
ASPDEV(*NONE) CRTSYSOBJ(*YES)

If you restored dtllib into an IASP, specify the name of the ASP device in the ASPDEV parameter of the CRTPWXENV command. For example:

CRTPWXENV DESC('user_description') 
DATALIB(datalib) CONDLIB(condlib) 
ASPDEV(asp_device) CRTSYSOBJ(*YES)
CPXLIB(cpxlib) JRNEXTSEQ(nnnn) 
RMTOSLEVEL(*LOCAL) EXTPGMLIB(exitlib)

The following table describes the parameters of the CRTPWXENV command:

Parameter	Valid Values	Description
ASPDEV	1 to 10 characters	Name of the ASP device where `dtllib` resides. All PowerExchange libraries must reside on the same ASP device. Default is *NONE.
CONDLIB	1 to 10 characters	PowerExchange Condense library that contains objects such as a configuration source file, data files for checkpoints and condense files, message queues, and the PowerExchange Delete Journal Receiver exit program and its journal.
CPXLIB	1 to 10 characters	PowerExchange capture library that contains the extraction map files. Default is *NONE.
CRTSYSOBJ	See next table.	-
DATALIB	1 to 10 characters	PowerExchange data library that contains objects such as a configuration source file, data files for capture registrations and condense files, the message log file, message queues, and PowerExchange job description.
DESC	1 to 25 characters	A brief text description that PowerExchange uses when creating the `datalib`, `condlib`, and `cpxlib` libraries.
EXTPGMLIB	1 to 10 characters	Specifies a PowerExchange Delete Journal exit program library. Default is *NONE. Use the default unless you also specified the ASPDEV parameter.
JRNEXTSEQ	1000 through 9999	A unique four-digit number that is used to register the PowerExchange Delete Journal Receiver exit program for the exit point QIBM_QJO_DLT_JRNRCV. Specify a value that is not used on your system. To determine the numbers that are currently registered against the exit point, use the WRKREGINF command and then choose option 8. Default is 1000.
RMTASPDEV	Maximum length of 10 characters	In a remote journaling environment, the name of an ASP device on which the CRTPWXENV command creates only dtllib and datalib libraries that contain a SQL package and SQL views for accessing source table metadata. This ASP device is remote from where you run the CRTPWXENV command and create the primary PowerExchange environment. Include this parameter only if you plan to use remote journal receivers for CDC and want to use an ASP on the local system to store the files that the remote PowerExchange Listener requires to access the table metadata. Default is *.
RMTOSLEVEL	*LOCAL V7R1M0 V7R2M0 V7R3M0	Specifies the IBM i version that runs on a remote machine. Include this parameter only if the metadata being retrieved is for tables that are stored in libraries on a remote machine. If the metadata is on the machine where this command is executed, the software determines the operating system release level. This parameter controls the views that the software builds over the system metadata tables.
RMTRDBDIRE	Maximum length of 18 characters	In a remote journaling environment, the name of Db2 database on the local system that contains the Db2 source tables for CDC. This value must have been defined to IBM i with the “Work with Relational Database Directory Entries” function (WRKRDBDIRE). Include this parameter only if you plan to use remote journal receivers for CDC. Default is *LOCAL.
RMTSYSNAME	Maximum length of 68 characters	In a remote journaling environment, the name of the IBM i host that contains the Db2 source tables for CDC and the local journals and journal receivers. Also called the local system. This value must have been defined to IBM i with the “Work with TCP/IP Host Table Entries” function. Include this parameter only if you plan to use remote journal receivers for CDC. Default is *NONE.

The following table describes the objects that the CRTSYSOBJ parameter creates so that PowerExchange can run in its own subsystem:

Object Type	Description	Object Name	Library
*CLS	Class that defines the run-time attributes of PowerExchange jobs.	DTLLIST	`datalib`
*OUTQ	Output queue that stores all spooled file outputs from PowerExchange jobs.	`datalib`	QGPL
*SBSD	Subsystem description that is used to run all the PowerExchange jobs for this environment.	`datalib`	QGPL
*JOBQ	Job queue that is associated with the subsystem description.	`datalib`	QGPL
*JOBD	Job description that describes a job that uses all the system objects and libraries created for this environment.	DTLLIST	`datalib`

If you want to move the objects that are created by default in the QGPL library to other libraries, use the appropriate commands.

You might not be able to move objects to an alternative library in an IASP. IBM i does not permit certain object types, such as output queues and job queues, to reside in libraries within an IASP.

The following example shows the commands that you can use to move objects to an alternative library newlib:

ENDSBS SBS(datalib) 
MOVOBJ OBJ(save_file_library/datalib) OBJTYPE(*OUTQ) TOLIB(newlib) 
MOVOBJ OBJ(save_file_library/datalib) OBJTYPE(*JOBQ) TOLIB(newlib) 
MOVOBJ OBJ(save_file_library/datalib) OBJTYPE(*SBSD) TOLIB(newlib) 
CHGJOBD JOBD(datalib/DTLLIST) JOBQ(newlib/datalib) OUTQ(newlib/datalib) 
RMVJOBQE SBSD(newlib/datalib) JOBQ(save_file_library/datalib)
ADDJOBQE SBSD(newlib/datalib) JOBQ(newlib/datalib) MAXACT(*NOMAX) 
SEQNBR(1) MAXPTY1(*NOMAX) MAXPTY2(*NOMAX) 
MAXPTY3(*NOMAX) MAXPTY4(*NOMAX) MAXPTY5(*NOMAX) MAXPTY6(*NOMAX) 
MAXPTY7(*NOMAX) MAXPTY8(*NOMAX) MAXPTY9(*NOMAX) STRSBS SBSD(newlib/datalib)

If you specify CRTSYSOBJ(*NO) on the CRTPWXENV command, make sure the subsystem and job queue where you intend to run the PowerExchange Listener can support multiple concurrent jobs. If you are using CDC, the subsystem and job queue should support a minimum of six concurrent jobs.

Rename Saved Search

Table of Contents

Installation and Upgrade Guide

Installation and Upgrade Guide

Step 7. Create the PowerExchange Environment

Step 7. Create the PowerExchange Environment