DSXchange

You almost certainly have runtime column propagation enabled. This is causing columns to "appear from nowhere". Disable RCP to fix that problem.

We still have no idea what you are trying to accomplish, so it's very difficult to give well-directed advice. Open is for hashed files or directories with a pointer in the VOC file. OpenPath is for hashed files or directories generally. OpenSeq is for operating system files opened for sequential acc...

DataStage does not recognize user DSNs. You must use a System DSN or a File DSN.

The internal form of a Sunday date is evenly divisible by 7. Therefore, Mod(Date(),7) returns a number that can be subtracted from the current date to yield the date of the prior Sunday (or today, if it IS Sunday). "basename" : Oconv(Date() - Mod(Date(),7), &quo...

Yes, particularly since you're using a job sequence. The derivation of the filename job parameter can include generation of the date component. For example "basename" : Oconv(Date(), "DMDY[2,2,2]" : @VM : "MCN") : ".txt"

Welcome aboard. :D Yes, an Execute Command activity can execute any valid operating system command, so you can choose which to use. For example, if rcp (remote copy) is available between the two systems, that might be a choice. Otherwise, probably a shell script to effect a transfer using FTP would ...

And the comma-delimited list in the final column?

Welcome aboard. :D The broken pipe can be between the DataStage processes and the job monitor. To test this theory, add APT_NO_JOBMON environment variable as a job parameter and run the job with it set to True. Search the forum for an exact match on your error text; you will find that others have ha...

... but 'e's not the Messiah...

It would be ugly SQL at best.
Easier to select all the rows into a DataStage job and effect a vertical pivot.
Search the forum for vertical pivot techniques; in this case the approach using stage variables is probably easiest.

Check your spelling.
Check that you have the correct schema name if you're not the table owner.
Check that you are connected to the Oracle instance that you believe the table to reside in.

nkln@you wrote:Hi Kumar,

There is user defined sql. But to_date() function is already used in it.

it is as follows:

TO_DATE(:6, 'YYYY-MM-DD HH24:MI:SS')

If it's a SELECT, surely you want the TO_CHAR function, not the TO_DATE function?

For Craig's edification - or at least to assuage his curiosity - can you please check whether DS.CHECKER recorded its activity in a file in the &COMO& subdirectory in your project and, if so, please post its contents?

Since I don't know what is in your datafile definition I can not answer that. But you do need a datafile definition that includes the field that is going to receive the result of the ASEQ command.

DS.TOOLS is merely a menu.

Which option from that menu appeared to correct the problem?