Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

VSAM Connector

VSAM Connector

VSAM targets in a mapping

VSAM targets in a mapping

To write data to a VSAM data set, configure a VSAM object as the Target transformation in a mapping.
Specify the name and description of the VSAM target. Configure the target and advanced properties for the target object.
The following table describes the target properties under
Details
:
Property
Description
Connection
Select an existing VSAM target connection, or create a target connection that has a type of
Adabas
.
Alternatively, you can use a connection parameter in the mapping and then enter a specific connection in each mapping task that is associated with the mapping.
If you want to use a connection parameter with a specific target object, you must first select a specific connection so that you can access the target to select the target object in the
Object
field. After you select the target object, define the connection parameter.
If you want to use parameters for both the connection and target object, you do not need to first select a specific connection. You can just define the parameters in either order.
To define a connection parameter, click
New Parameter
and enter the following information:
  • Enter a parameter name that begins with a letter and is up to 200 characters in length, including @, #, _, and alphanumeric characters.
  • In the
    Type
    property, verify that
    connection
    is selected.
  • Leave the
    Connection Type
    property blank.
Target Type
To specify a target table, select
Single Object
.
To write multiple record types to a VSAM target, select
Multi Group
.
If you selected
Multi Group
and
Use Sequence Fields (Select All Tables)
for the source, make sure
Use Sequence Fields (Select All Tables)
is also selected for the target. This setting is required for multiple-record write.
  • For multiple-record writes, you must join source and target tables and manually map the source fields to the target fields through the
    Target Field Group
    field.
  • For multiple-record writes, if you select the same data map as a target, you must override the file name to avoid overwriting the source file.
Object
Click
Select
. In the
Target Object
dialog box, select
Existing
and then select an existing target table.
Operation
Select the target operation. You can perform the following operations on an VSAM target:
  • Insert
  • Update
  • Upsert
  • Delete
  • Data Driven
The following table describes the advanced target properties that appear under
Advanced
:
Advanced Property
Description
Forward Rejected Rows
Select this option to have the Target transformation pass rejected records to a reject file that is generated in the following directory:
\agent_install_directory\apps\Data_Integration_Server\data\error
Clear this option to ignore the rejected records.
This field is not displayed if a parameter is specified for the target connection.
Pre SQL
SQL statements that run on the target before the extracted data is written to a target.
Maximum length is 5000 characters.
Post SQL
SQL statements that run on the target after the extracted data is written to a target.
Maximum length is 5000 characters.
Update SQL Override
Overrides the default Update SQL that is sent to PowerExchange.
Map Schema Override
A schema name that overrides the schema name in the PowerExchange data map.
Map Name Override
A map name that overrides the target PowerExchange data map name.
Table Name Override
Overrides the table name of the imported table.
If you import one table, enter the Table Name Override by using the following format:
TABLENAME
If you import multiple tables, use the following GroupName syntax:
GroupName1=TABLENAME1;GroupName2=TABLENAME2
You override table names in Multi Group sources or targets, including Multi-Record Write, by using the same syntax you use to specify Filter Overrides and SQL Query Overrides. Use the following syntax:
GroupName
=
TableNameOverride
where the
GroupName
is the same name as the imported table name.
Use a semi-colon to delimit each entry. For example:
TABLEA=TABLE1;TABLEB=TABLE2
If
Update SQL override
,
Insert SQL override
, or
Delete SQL override
and
Table Name Override
are specified,
Update SQL override
,
Insert SQL override
, or
Delete SQL override
takes precedence.
Insert SQL override
Overrides the default Insert SQL sent to PowerExchange.
Delete SQL override
Overrides the default Delete SQL that is sent to PowerExchange.
Pre SQL run once per Connection
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.
Truncate Target
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.
Initialize Target
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.
File Name Override
Overrides the data set in the PowerExchange data map. Enter the complete data set name.
PWX Partition Strategy
Specify one of the following partitioning strategies:
  • Single Connection
    . PowerExchange creates a single connection to the data source. Any overrides specified for the first partition are used for all partitions. With this option, if you specify any overrides for other partitions that differ from the overrides for the first partition, the session fails with an error message.
  • Overrides Driven
    . If the specified overrides are the same for all partitions, PowerExchange creates a single connection to the data source. If the overrides are not identical for all partitions, PowerExchange creates multiple connections.
.

0 COMMENTS

We’d like to hear from you!