DSXchange

In Addition:

The job runs successfully but the log is filled with the above warning. This warning message is happening for a few records only.

What I dont understand is why its happening for only a few records and not all the records...?

what is the delimiter you are using. please also sketch the job flow Hello Krazykoolrohit: Delimiter is a "|" (Pipe) Job 1 DB2 ---> Transform ---> SeqFile1 JOB 2 SeqFile0 | \|/ SeqFile1 ---> Lookup -----> SeqFile2 This error is occurring when I run Job 2.

Hello: Source - DB2 AIX Target - Sequential File When I run my job I get the following Error message: Jobname: Delimiter for field "COL_NAME" not found; input: {A S S E M B L Y , 20 T O 20 T E S T 20 T H E 20 F U E L 20 H O S E 20 ( T O 20 P U M P 20 C O N N E C T I O N 20 O F 20 E F I 20 ...

chulett wrote:You need to read the DB2/UDB API Stage Guide pdf that is in your Docs directory. There is a section there that explains how to handle column names with $ or # in them.

ps. This same issue (and solution) exists for the Oracle stages.

Thank you all:

I was able to resolve the issue.

I have noticed that when I " remove " the column derivations is when this error happens. When I leave the column derivations the job runs successfully. However I need to remove the column derivations (From the DB2 API Pluggin columns) since I want to pass job parameters consisting of table...

Keep you Column name as COL_ID NEXT_COL and in the derivation mention COL_ID# NEXT_COL# in your table definitions and see how it works..And one more thing are the columns named as COL_ID#,NEXT_COL# on the DB2 database side. Hello thumsup9 I have already done that. Yes the columns named as COL_ID#,N...

Hello All: My Environment: Source : DB2 AIX 5.2 Target : Seq File On Db2 some Column Names are Named as follows: COL_ID# NEXT_COL# (ending with a '#') When I do a straight map to a Seq File in the Transform I see red on column names that end with '#'. So I remove the '#' from the column name on both...

Hello:

I was able to take care of it. The Second date column in the file I had not changed the SQL Type to VARCHAR. Once I change the DATE field to VARCHAR I am able to view the data without that error.

Thanks once again.

Hello: Following is my environment Source File: Excel Target File : Sequential File I save the excel file as a text file as well as a CSV file. This file has the first line as column name. When I import the sequential file definition I set the first line as column name. If I am importing a text file...

Thanks Everybody:

Changed the SQL Type to LongNVChar and was able to use the FMT function given by DSguru2B successfully.

Appreciate everybodys input. You guys are the best. :D

Thanks everybody:

Was able to use the Field function with Len function to get the required output.

narasimha wrote:Check with len function and add it as a constraint to the required output file

Thanks narasimha for your quick reply.

Can u elaborate...?

Hello: Need to separate data by column Id's (COL_ID) into two files. File 1 should have column id's with length 10 characters File 2 should have column id's with "everything else." COL_ID CHAR 18 AX02L7-CAL-110 AX02D7-DOM ZZZ2D7-DMM-285 Am able to put column id's with length 10 Char to fil...

Hi DS_MJ The problem is with the data coming from your source.The code which DSGURU gave you is perfect. The thing is that you are not defining the scale when you are pulling the data from the source. Just my suggestion: Source TABLE COL_NAME SQLTYPE LENGTH SCALE NULLABLE PAR_AMOUNT Dec 17 whatever...

How about FMT(out_fa003_lsmw.PAR_AMOUNT,"16'0'R2") ? ... Hello ray.wurlod: When I try FMT(out_fa003_lsmw.PAR_AMOUNT,"16'0'R2") I get 0000000012345.00 Source TABLE COL_NAME SQL TYPE LENGTH SCALE NULLABLE out_fa003_lsmw.PAR_AMOUNT Dec 17 No TARGET TABLE COL_NAME SQL TYPE LENGTH SC...