DSXchange

Ray anwsered your question regarding how to find out if the source file is a named pipe. "ls -al" will also show a "p" in the attributes for pipes.

Timstamp Type -> Format String.

Also, have you enabled the "Extended Microseconds" switch or the "extended" attribute in the column definition for the timestamp?

What exactly is your issue?

Since it couldn't connect to the database did you check the userid, password and instance to ensure that they are correct? Have you connected to DB2 in you installation already?

The bad news is that at V8 it also strips out the internal double quotes. Can you choose a different quote character for your files?

In your output sequential file timestamp column definition, do an "edit row" and add "%yyyy-%mm-%dd %hh:%nn:%ss.6" as your display conversion, that should do it.

I'm not sure the merge stage has anything to do with it. When you read your CSV data does it show up correctly in your job?

Nice - I never used that approach before, that is faster than my usual approach of opening up a shell with TCL.
Thanks!

No idea what could be causing your problem - unless your source file is a named pipe.

The Environment variables are at the end of the DSParams file, int he section "[EnvVarValues]" and you can copy those.

My fault on the naming convention, the TRANS2 means the second transform stage defined in your job. If you deleted the first one and only have one transform left then you need to look at that transform stage and see if you are doing a mathematical operation on a column or derived value that might co...

One of the powerful aspects of DSXchange is that anyone can search the collected posts to see if their error has already been encountered by others and what the solution might have been. By going off-line (be it by phone, e-mail or private messaging) this seamless history is broken and others cannot...

Do you have other jobs that work correctly? If you have replaced the source with a row generator and the target with a peek so that you no longer have sequential files in the job do you still have that error message?

I have just created a text file with 100 lines and contents like "2007-01-01", "2008-02-02" then wrote a job to read, sort and write it to another text file. Regardless of whether I define it as DATE(10) or VarChar(10) it works correctly.

That is even odder. If you replace the DB2 output with a peek stage does the job still hang?