DSXchange

You can find a few operators and its details under your PXEngine directory.

/Ascential/DataStage/PXEngine/examples

Well if you are not able to connect to the server using the command prompt then clearly you dont have access, or your giving incorrect password.
You said you got connected via explorer. Disconnect it and try to reconnect via explorer with the exact same user name and password. See if that works.

Just to clarify, by funnel kumar means to collect it into one file that will be loaded into the DB.
Didnt want the OP to get confused

There is a difference in the way ftp command line works and ftp stage works. Ftp command line sends blocks of data, whereas the ftp stage tends to keep track of columns. Search the forum for more detailed explanation, this has been covered a lot over here before. You must be getting some error code ...

To get the the information from Log you can you use the DSGetLog function. As far as emailing is concerned,Sorry, Probably no one can do that. To read Premium Content you need to be a chartered member. Beleive me its worth it. So much for the price of peanuts. 13.7 cents a day for one year is define...

To my understanding this should be possible to be accoplished.

@Craig
Thats true, missed out on that piece, it definetly eats up time.

What is your source and target database? thats what Ray had asked too.
And also provide the original source and target datatypes.

Example#1 How many CPUs do you have that your DBA has switched on the parrallel execution. This problem usually arises due to indexes. I have faced this problem in Datastage Enterprise Edition, where the PX Deq: Signal ACK( acknowledgment of insert, update, or delete) was time consuming. PX Deq: Sig...

Doing an arithmatic manipulation on a charcter forces it to be changed to an integer. Just try multiplying it by 1 that should work.

Pay attention to Craig's suggestion. That will be much faster.
As far as getting the year from ICONV/OCONV, use

Ok. So it is a bug, and still is. Hmmm, well thanks for sharing that with me, as i had no idea that it was a bug. I was under the impression that since its set up as a default date, its acting up. Anywho, thanks for the info.

What format is your timestamp in? Take a look at the ICONV/OCONV functions. If your date part of timestamp is alway YYYY-MM-DD then for year you can do LEFT(in.timestamp,4) for month you can do OCONV(ICONV(LEFT(in.timestamp,10),"D-YMD[4,2,2]"),"DM")

Also keep in mind that you should send a date part and a time part seperately, or timestamp with only integers in it. Because unix doesn like space in the param file and in a timestamp you will have a space between a date and time part.

Most definately. That is another option surely, and it will work. I just think changing the sql type from timestamp to varchar for this unique situation is much better. Having all the processing done in minimal stages.