DSXchange

You need also to handle dates such as March 30.

Check out the date routines in this file

The original question had DataStage server installed on Windows, therefore iSeries for Windows was the correct client. It would not be appropriate to install this client on a UNIX server. But there is certain to be some other client component (such as DB2 Connect) that you could use. The ODBC driver...

Data Sets are not part of the server engine, and therefore a VOC entry is not the appropriate approach. Further, there is no command whatsoever to delete a row from a Data Set. Data in Data Sets is stored in blocks of 32 KiB - if you could delete rows that structure would need to carry extra inormat...

This would be the configuration file (not the Data Set descriptor file), and I'd think the advice would be to change it so as not to reference the node that is down. The Data Set (or at least the available part of it) could still be read. The -x option for the orchadmin command (with a new configura...

Alpha(), AlNum() and Num() all exist.

HariK wrote:... but it does not behave same as the SQL funtion...

Are you sure?

In a word, no.

There are some companies that offer my materials in the USA, but I am totally booked in my local region until at least November 2011 and probably much longer. The Information Server suite is "going gangbusters" here.

Assuming you mean moving the blah.fs file, yes this is correct. Locations of the data files are stored as absolute pathnames within the descriptor file.

You need the colons (delimiters) in the time format string.

Only because your data are Big-Endian.

You need to look at the score, to find out which operators were combined. Only operators generate "performance statistics". In the design area only the first link associated with a combined operator displays those statistics.

Use the Monitor in Director to get a better idea.

You are not wrong.

Pass JobActivityName.$UserStatus as the value of the command's parameter.

This could be an issue with the Connector Access Service - you probably need to involve your official support provider. These things are notoriously difficult to diagnose, not least because you have to know which logs to look at.

The rule of thumb (from a conversation at IOD 2009) is three to four times the volume of data to be profiled.