DSXchange

It looks like you have a text-translation error with the ENAME field... There are several methods of getting this error. Quickest is to look at the detail records in the DIRECTOR log file for the job run - I am sure that the insert/update statement is generating a database error through ODBC. You ca...

It means that this record is not fixed length, that the end-of-line mark was encountered in the wrong location. You should check your file with a text editor and should be able to quickly see the incorrect line. Since the DataStage mechanism on fixed-length files splits the processes by using a form...

Maffan76, you will notice that this thread will remain rather quiet. If you do a search of the forum using the keyword "urgent" this will be explained to you. But your best source of information on this seminal subject is the .pdf file on your own pc - look at Start -> Programs -> Ascential DataStag...

Hello qmbs, first off, welcome to the forums. The next time you post, please make sure to do it in the appropriate forum - this is the "testimonial" forum and this question doesn't belong here. I am sure that one of those with access rights will move it soon. DataStage has no problem going from ODBC...

snassimr, with a sequential source file you really should pre-sort it at the DOS/UNIX before the job to increase the effective speed. 2500 rows per seconds is not necesarily fast, but if you change your job so that it doesn't write anything (put a constraint into a transform that doesn't transfer ro...

Kumar, if I understand this correctly, you sometimes have 2 characters in a column, and sometimes the contents is a 2-byte packed decimal? This is highly unlikely coming from COBOL; most likely the column is always packed decimal and occasionally the numbers will show as valid text characters. In se...

If you take your base date and convert it to internal format ICONV("1900-01-01","D4-YMD") you can subtract that from the date in question ICONV(In.Date,"D4YMD") to get number of days since base. This is, I think, the date you are looking for. Please refrain from using the word "urgent" in your posts...

It would be helpful if you could tell us what the error is.

Yes, ds uses the normal cron scheduler on unix.

The DataStage director uses AT on Windows platform, so any jobs you schedule in DS will be visible using the AT command, just as Ray and Sainath have already stated.

I think the answer to that is more a matter of taste & opinion. For those in this forum who have been using the underlying UniVerse system since before 1980 I think the answer is "no". But I certainly hope that Px will at least close the gap to make Px more of an ETL tool than it's current EtL s...

kudaka, in a win32 or command.com shell from Windows, not from DataStage, just type AT without a hyphen. If it isn't installed then you would be getting a different type of error message.

I seem to remember having had a similar issue, where the server name changed from myhost.companyone.com to myhost.companytwo.com and we had to re-install. I cannot recall the symptoms, but your problem does sound a bit familiar.

Ouch - I have been using NOTFOUND in my recent server jobs, looking up either Hashed files or ODBC stages to hashed files. I haven't seen errors yet -- are there any known rules to the failures in NOTFOUND?

Please use the Search facility or the FAQ forum for this type of question. It has been posed & answered before. DataStage Server uses an underlying post-relational database system (it used to be identical with UniVerse, now an IBM product) as the foundation for the ETL program suite. Programs ar...