DSXchange

[quote="ray.wurlod..The project template is - effectively - a regular project but without a VOC...[/quote] Oddly enough I was looking into that project earlier today and noticed that all of the indexed files have invalid indices as well; so DS force-fixes them when copying.

There are up to 3 log file entries that are used to hold internal data (including the purge settings) and that have different metadata than the other records. Since you don't want (or need) them, Ray added the filter to remove them. These records begin with "//"

If you give it a default value or handler or nulls then the row won't be rejected. Do rows 2 and 3 go down the "normal" link?

Did you specify a "default value" in the attributes for the column "Salary"?

Shrek - you can get free UNIX utilities on Windows that include such tools as sed and awk; the most common one I know of is MKS toolkit, but MS also offers a package that will do this.

Ray - thanks for pointing that out; I didn't realize that the SQL syntax was being used.

Nilesh - note that this is an executable and is meant to be run from the Windows client, not the UNIX server.

vij - why would you want to maintain any particular order when writing to this SQL server table? Sometimes the order of keys can make a performance difference when loading, but that doesn't sound like your issue. Basically no matter what the order is of the records you are inserting to SQL Server th...

Since you are on Windows and haven't mentioned using anything else, I believe that the "at" scheduler has a log file called "Schedlgu.txt" which might help give you additional information.

...I have tried writing to Peek stage with 1 node configuration file and the job ends OK. it never fails... It does seem to be related to the Teradata output. If you change back to your normal configuration file and run the job a couple of times and it still doesn't fail you can be fairly certain o...

You could try using F7 instead of the EVAL statement to get field 7. I'm not at a client now to check, but am fairly certain that F1-F9 are declared for use as positional columns.

Try "DATE('9999-12-31')"

I think it doesn't like the string '9999-12-31' - what is the column data type for that value? Perhaps you need to cast this string to a date or timestamp...

Or write a simple job with the dataset as the source, a constraint stage (perhaps a condition in a transform) and then output to a peek stage.

When you refer to DataStage internal variables and routines in your own job, you need to add the following line to your code: