DSXchange

All of the information Vignesh seeks can be found in the DataStage Repository - and therefore can be reported on using the Reporting Tool (Documentation Assistant) or MetaStage. In current versions, indeed, all the information is in a single table, but this is one of those tables for which complete ...

It's interesting to note how very different the final (?) specification was from the original specification!

An interesting cross check is to see whether you can load the file (or a subset of it containing the problematic row) into a spreadsheet. If the spreadsheet also can't handle it, then there's most likely a data problem rather than a DataStage problem.

Default limits can be set in Director, under Tools > Options.

Is that really a valid email address?? Upcase(Email.Address) MATCHES "0X'@'0X'.'3A" : @VM : "0X'@'0X'.'2A'" : @VM : "0X'@'0X'.'4A'" : @VM : "0X'@YAHOO.'" would handle just the yahoo case in a non-case-sensitive manner. I suspect you don't want to handl...

You need to establish which column is causing the offence. Then check your source data (perhaps within DataStage - an extra output containing both the column and its length) looking for things like trailing space characters that cause the column to be longer than the maximum length specified by its ...

You can always send to an email address that is a list. That is, the address is processed by your mail client to send to a number of actual addresses.

As Arnd said, you have looked at the log for the controller. You now need to look at the log for the controlled job, CopyOfFXRate_Extraction. There will likely be a number of warnings; the first of these is the most important one. Also check the Fatal message (the one with the red icon); but don't p...

Empty strings are only read from text files as null because the "representation of null" field on the Format tab contains "".

That's what causes the conversion, the default representation. There's nothing to stop you changing that, after which "" will be read as "".

Just to clarify one point - you DO need a compatible C++ compiler.

This isn't Orchestrate, it's QualityStage (the software formerly known as INTEGRITY from Vality). I think, if you inspect the execution scripts, you would be able to recover the field names manually, but as to the column widths I think that would be trickier. Unfortunately most of the metadata is co...

I thought my earlier post was witty. I was half right.

The write cache is good. What you get is writing to random locations in memory rather than writing to random locations on disk (within the file structure, of course). Once all rows have been written, the cache is flushed to disk in group order, which is maximally efficient I/O. You can preallocate d...

Investigate the UNIX find command. For example:

Read the man pages for find to garner more information.

The problem is almost certainly in your OpenSeq statement. You have assumed that nothing will go wrong but, this time, it has. You have not coded for anything going wrong; indeed you have explicity specified a no-operation (NULL statement). The OpenSeq statement actually has up to four clauses (ON E...