DSXchange

Welcome aboard! :D My guess is that it's writing UNIX-style line terminators (LF) rather than Windows-style line terminators (CRLF). If you open with, say, Word you can convert them. There are also converter programs out there, such as unix2dos , that will perform these conversions. (Or you could cr...

You get that error because a stage aborted.
Reset the job in Director. There should then be an entry in the job log "From previous run..." which contains additional diagnostic information.

The number of rows processed on each link connected to an active stage, such as a Transformer stage, is captured automatically in the job log, in an event called "Active stage finishing..."

Opening the Help for this stage gives a useful and concise explanation.

Hi Ray I have tried using the solution you mentioned and was not able to generate the dates from one input date i need to generate it using one input date and it should get generated in the first run that means when i run my datastage job the dates should get generated for all the five years can u ...

Usually have the DBA kill the session. No-one else has the privileges necessary.

Just to make the point that there are many ways, you could also do it with simple string concatenation, perhaps formatting each component to ensure that leading zeroes exist. Fmt(InLink.DayNumber, "R%2") : "/" : Fmt(InLink.MonthNumber, "R%2") : "/&q...

Look in the DSINCLUDE folder in your project (on the server) for a file called JOBCONTROL.H within which you will find a section of constants whose names begin with DSJE. Among those find the one that equates to -14 and you're well on your way to a diagnosis. (I am in a hotel room at the moment and ...

Even TIME() does not give milliseconds on all platforms. On some platforms you can only do it in code, by specifying the compiler declaration $OPTIONS TIME.MILLISECOND. Try SYSTEM(12) - if I recall correctly - this will report in milliseconds if the system is capable of providing same. Therefore OCO...

On the reject link you can access the other link's link variables to obtain:

SQLSTATE (ODBC-specific code)

DBMSCODE (the error code generated by the DBMS server)

LASTERR (the text of the error/warning message from the driver/server)

REJECTED (true = row rejected by output link)

It's my understanding that a persistent DataSet can exist as multiple files, each of which isn't bigger than 2GB. Are you saying that this is not the case for virtual Data Sets?

In a QS project there is a directory called Data in which QS expects to find its data files. The error messages suggest that a file called FPLOCALR can not be found there. Are you sure you placed this file in the correct location? And that it's readable and/or writeable by whatever user ID you're us...

When you're working with QualityStage rule sets, there is a menu option that allows you to test. I don't have QS where I am working at the moment. Explore. That's how I find most things.

DataStage sets no limit on password length. However, your system administrator may have.

Do you really mean for each column? Or each row?

If "each row" then Craig's solution, and yours (if in stage variables), will work.
Otherwise, you need a separate stage variable for each column, and one that updates the driver stage variable by the number of columns in the row.