DSXchange

Make sure that your datetime column is never in the second format.

C:dtexec.exe is not even a valid Windows pathname. Try again.

In general, unless you explicitly specify "sparse" lookup, you will be performing your lookup against a Data Set - a virtual Data Set. There's one associated with every link. "Sparse" lookups - directly to DB2 or Oracle tables - will be substantially slower than to a virtual Data Set (which is in lo...

How are the other Connection properties set?

Even then, don't you need to use expr in the shell script?

There's as complete a list of Modify stage functions as I've been able to construct here

I can't think of a legal way to do it. But I'd be happy to learn if there is one.

Not on a different server, Brad, on a different platform (for example mainframe or AS/400 where DataStage is on UNIX).

It does appear to be a subrecord. On that basis the Promote Subrecord stage would seem to be indicated to extract the subrecord's elements.

Assuming you've been diligent and systematic with your metadata management in DataStage, all you have to do is to select the table definition in question (before importing the new version is best) and to perform a Usage Analysis. This answers the very question you are asking, even unto which particu...

Please mark thread as resolved.

I wonder if it's because of the unbounded string specification of the data type. Try

The Repository in version 8 is "free format" as far as branch and category names are concerned - you don't have to have any particular names. That said, and as Arnd is alluding to, the product usually installs a Jobs branch for you.

Remember that Format and Column properties are properties of the Link, not of the stage. In a job with only two Sequential File stages there is only one link, so any change will be manifested on both ends of the link. You will need an intermediate stage, probably a Modify stage. You might also like ...