Workflow Basics Guide

10.5.6
- 10.5.7
- 10.5
- 10.4.0

Back Next

Targets Node

The Targets node lists the mapping targets and displays the settings. To view and configure the settings of a specific target, select the target from the list. You can configure the following settings:

Writers.
Displays the writer that the Integration Service uses with each target instance. For relational targets, you can choose a relational writer or a file writer. Choose a file writer to use an external loader. After you override a relational target to use a file writer, define the file properties for the target. Click Set File Properties and choose the target to define.

Connections.
Displays the target connections. You can choose connection types and connection values. You can also edit connection object values.

Properties.
Displays different properties for different target types. For relational targets, you can override properties that you configured in the Mapping Designer. You can also configure the following session properties for relational targets:

Relational Target Property	Description
Target Load Type	You can choose Normal or Bulk. If you select Normal, the Integration Service loads targets normally. You can choose Bulk when you load to DB2, Sybase, Oracle, or Microsoft SQL Server. If you specify Bulk for other database types, the Integration Service reverts to a normal load. Loading in bulk mode can improve session performance, but limits the ability to recover because no database logging occurs. Choose Normal mode if the mapping contains an Update Strategy transformation. If you choose Normal and the Microsoft SQL Server target name includes spaces, configure the following connection environment SQL in the connection object: SET QUOTED_IDENTIFIER ON
Insert	The Integration Service inserts all rows flagged for insert.
Update (as Update)	The Integration Service updates all rows flagged for update.
Update (as Insert)	The Integration Service inserts all rows flagged for update.
Update (else Insert)	The Integration Service updates rows flagged for update if they exist in the target, and inserts remaining rows marked for insert.
Delete	The Integration Service deletes all rows flagged for delete.
Truncate Table	The Integration Service truncates the target before loading.
Reject File Directory	Reject-file directory name. By default, the Integration Service writes all reject files to the service process variable directory, $PMBadFileDir. If you specify both the directory and file name in the Reject Filename field, clear this field. The Integration Service concatenates this field with the Reject Filename field when it runs the session. You can also use the $BadFile Name session parameter to specify the file directory.
Reject Filename	File name or file name and path for the reject file. By default, the Integration Service names the reject file after the target instance name: target_name .bad. Optionally, use the $BadFile Name session parameter for the file name. The Integration Service concatenates this field with the Reject File Directory field when it runs the session. For example, if you have “C:\reject_file\” in the Reject File Directory field, and enter “filename.bad” in the Reject Filename field, the Integration Service writes rejected rows to C:\reject_file\filename.bad.

For file targets, you can override properties that you configured in the Target Designer. You can also configure the following session properties for file targets:

File Target Property	Description
Merge Partitioned Files	When selected, the Integration Service merges the partitioned target files into one file when the session completes, and then deletes the individual output files. If the Integration Service fails to create the merged file, it does not delete the individual output files. You cannot merge files if the session uses FTP, an external loader, or a message queue.
Merge File Directory	Enter the directory name in this field. By default, the Integration Service writes the merged file in the service process variable directory, $PMTargetFileDir. If you enter a full directory and file name in the Merge File Name field, clear this field.
Merge File Name	Name of the merge file. Default is target_name .out. This property is required if you select Merge Partitioned Files.
Create Directory if Not Exists	Creates the target directory if it does not exist.
Output File Directory	Enter the directory name in this field. By default, the Integration Service writes output files in the service process variable directory, $PMTargetFileDir. If you specify both the directory and file name in the Output Filename field, clear this field. The Integration Service concatenates this field with the Output Filename field when it runs the session. You can also use the $OutputFile Name session parameter to specify the file directory.
Output Filename	Enter the file name, or file name and path. By default, the Workflow Manager names the target file based on the target definition used in the mapping: target_name .out. If the target definition contains a slash character, the Workflow Manager replaces the slash character with an underscore. When you use an external loader to load to an Oracle database, you must specify a file extension. If you do not specify a file extension, the Oracle loader cannot find the flat file and the Integration Service fails the session. Enter the file name, or file name and path. Optionally use the $OutputFile Name session parameter for the file name. The Integration Service concatenates this field with the Output File Directory field when it runs the session. If you specify an absolute path file name when using FTP, the Integration Service ignores the Default Remote Directory specified in the FTP connection. When you specify an absolute path file name, do not use single or double quotes.
Reject File Directory	Enter the directory name in this field. By default, the Integration Service writes all reject files to the service process variable directory, $PMBadFileDir. If you specify both the directory and file name in the Reject Filename field, clear this field. The Integration Service concatenates this field with the Reject Filename field when it runs the session. You can also use the $BadFile Name session parameter to specify the file directory.
Reject Filename	Enter the file name, or file name and path. By default, the Integration Service names the reject file after the target instance name: target_name .bad. Optionally use the $BadFile Name session parameter for the file name. The Integration Service concatenates this field with the Reject File Directory field when it runs the session. For example, if you have “C:\reject_file\” in the Reject File Directory field, and enter “filename.bad” in the Reject Filename field, the Integration Service writes rejected rows to C:\reject_file\filename.bad.

You can configure the following session properties for PowerExchange nonrelational targets:

Attribute Name	Description
ADABAS Password	For the ADABAS target type, the Adabas file password. If the ADABAS FDT for the target file is password protected, enter the ADABAS FDT password. PowerCenter encrypts the password and displays the encrypted password in the XML file that it generates for the workflow.
BLKSIZE	For the SEQ target type on z/OS, the z/OS data set block size. Default is 0, which means use the best possible block size. If you select VB for the RECFM value, the actual block size might be up to four bytes greater than the value you specify for BLKSIZE .
DATACLAS	For the SEQ target type on z/OS, the z/OS SMS data class name.
Delete SQL Override	For the ADABAS and VSAM target types, overrides the default Delete SQL that is sent to PowerExchange.
Disp	For the SEQ target type on z/OS, the z/OS data set disposition. Valid values: OLD SHR NEW MOD Default is MOD if the data set exists, and NEW if it does not.
File Name Override	For the SEQ and VSAM target types, overrides the data set or file name in the PowerExchange data map. Enter the complete data set or file name. For i5/OS, use the following format: `library_name`/`file_name`.
IMS AM Override	For the IMS target type, overrides the IMS access method in the imported data map for the target with the other allowable access method. The session then uses the override access method at run time. If you imported a target data map that specifies the DL/1 BATCH access method, enter O to override it with the IMS ODBA access method. For ODBA access, you must also specify the IMS PSBNAME Override and IMS PCBNAME Override attributes. If you imported a target data map that specifies the IMS ODBA access method, enter D to override it with the DL/1 BATCH access method, which provides DL/I or BMP access. You must also specify the IMS PCBNUMBER Override attribute. Before you run the session with an access method override, ensure that you complete the PowerExchange configuration tasks for the new access method. For example, if the override is DL/1 BATCH, you must configure LISTENER and NETPORT statements in the DBMOVER member and configure the netport JCL. If the override is IMS ODBA, you must perform other configuration tasks. For more information, see "IMS Data Maps" in the PowerExchange Navigator User Guide .
IMS PCBNAME Override	For the IMS target type, if you imported an IMS ODBA data map for the target and did not override the access method, this value overrides the PCB name from the data map. If you specified ODBA access as an override in the IMS AM Override attribute, you must enter this value. A PCB name is required for ODBA access. A PCB name is not used for DL/I or BMP access.
IMS PCBNUMBER Override	For the IMS target type, if you imported a DL/1 BATCH data map for the target and did not override the access method, this value overrides the PCB number from the data map. If you specified DL/I or BMP access as an override in the IMS AM Override attribute, you must enter this value. A PCB number is required for DL/I or BMP access. A PCB number is not used for IMS ODBA access.
IMS PSBNAME Override	If you imported an IMS ODBA data map for the target and did not override the access method, this value overrides the PSB name from the data map. If you specified ODBA access as an override in the IMS AM Override attribute, you must enter this value. A PSB name is required for ODBA access. If you use DL/I batch or BMP access and specify this override, you must also specify the PSB=%PSBNAME substitution variable in the netport JCL. The override value then replaces the substitution variable in the JCL. If you specify the PSB=%1 substitution variable instead of PSB=%PSBNAME in the netport JCL, the session uses the PSB name in the NETPORT statement, if specified. In this case, you need a separate NETPORT statement for each PSB. To avoid exceeding the limit of ten NETPORT statements, use this override with %PSBNAME substitution variable instead.
IMS SSID Override	For the IMS target type, if you imported an IMS ODBA data map for the target and did not override the access method, use this value to override the IMS subsystem ID (SSID). If you specified ODBA access as an override in the IMS AM Override attribute, you must enter this value. An SSID is required for ODBA access. If you use the IMS DL/1 BATCH access method and a BMP netport job, you can use this override with the %IMSID substitution variable in the netport JCL. This override replaces the substitution variable to specify the IMS SSID to use for the session. By using the substitution variable and override together, you can use the same netport JCL to access multiple IMS environments, such as development, testing, and production environments. An IMS SSID is not required for DL/I batch access to IMS data or for access to an IMS unload file.
Initialize Target	For the VSAM target type, select this option to have PowerExchange allow both inserts and updates into empty VSAM data sets. If this option is not selected, PowerExchange only allows inserts into empty VSAM data sets.
Insert Only	For the ADABAS and VSAM target types, processes updates and deletes as inserts. You must select this option when the target has no keys.
Insert SQL Override	For all nonrelational target types, overrides the default Insert SQL sent to PowerExchange.
LRECL	For the SEQ target type on z/OS, the data set logical record length. This value is ignored if Disp is not MOD or NEW. Default is 256. If you select VB for the RECFM value, specify the maximum number of data bytes in a logical record for LRECL. PowerExchange adds 4 to this value for the record descriptor word (RDW).
Map Name Override	For all nonrelational target types, overrides the target PowerExchange data map name. PWXPC sends the file name that is specified for the source in the mapping unless this name is overridden in the File Name Override attribute.
MGMTCLAS	For the SEQ target type on z/OS, the SMS management class name. This value is ignored if Disp is not MOD or NEW.
MODELDCB	for the SEQ target type on z/OS, the Model DCB for non-SMS-managed GDG data sets. This value is ignored if Disp is not MOD or NEW.
Post SQL	For all nonrelational target types, one or more SQL statements that are executed after the session runs with the target database connection.
Pre SQL	For all nonrelational target types, one or more SQL statements that are executed before the session runs with the target database connection. In certain cases, you must specify the Pre SQL run once per Connection attribute along with the Pre SQL attribute.
Pre SQL run once per Connection	For all nonrelational target types, runs the SQL that you specify in the Pre SQL attribute only once for a connection. Select this attribute in either of the following cases: In the Pre SQL attribute for a session that uses writer partitioning, you specify a SQL statement such as CREATEFILE that can run only once for the session. If you do not select Pre SQL run once per Connection , the session tries to run the statement once for each partition. In the Pre SQL attribute for a session that performs a multiple-record write, you specify a CREATEFILE statement that creates a new generation of a GDG or creates an empty file. If you do not select Pre SQL run once per Connection , the session creates a generation or tries to create a new empty file for each record that the session writes.
Primary Space	For the SEQ target type on z/OS, the primary space allocation, in the units specified in the Space attribute. This value is ignored if Disp is not MOD or NEW. Default is 1.
RECFM	For the SEQ target type on z/OS, the z/OS record format. Valid values are F, V, FU, FB, VU, VB, FBA, and VBA. This value is ignored if DISP is not MOD or NEW.
Schema Name Override	For all nonrelational target types, overrides the schema name in the target PowerExchange data map. PWXPC sends the file name for the source in the mapping unless this name is overridden in File Name Override attribute.
Secondary Space	For the SEQ target type on z/OS, the secondary space allocation, in the units specified in the Space attribute. This value is ignored if Disp is not MOD or NEW. Default is 1.
Space	For the SEQ target type on z/OS, the type of units for expressing primary or secondary space for z/OS data sets. Valid values are: CYLINDER TRACK This value is ignored if Disp is not MOD or NEW. Default is TRACK.
STORCLAS	For the SEQ target type on z/OS, the SMS storage class name. This value is ignored if Disp is not MOD or NEW.
Truncate target option	For the VSAM target type, truncates, or deletes, table contents before loading new data. VSAM data sets must be defined with the REUSE option for this truncate option to function correctly.
UNIT	For the SEQ target type on z/OS, the z/OS unit type. This value is ignored if Disp is not MOD or NEW. Default is SYSDA.
Update SQL Override	For the ADABAS and VSAM target type, overrides the default Update SQL that is sent to PowerExchange.
Upsert	For the ADABAS and VSAM target type, processes failed inserts as updates and updates as inserts.
VOLSER	For the SEQ target type on z/OS, the volume serial number. This value is ignored if Disp is not MOD or NEW.

Rename Saved Search

Table of Contents

Workflow Basics Guide

Workflow Basics Guide

Targets Node

Targets Node