DSXchange

Yes. You can probably use DecimalToString and then get the length of the string and get the substring before . and store it back to Numeric Field.

Yes. You can probably use DecimalToString and then get the length of the string and get the substring before . and store it back to Numeric Field.

Ereplace(MyString, ".", "")

You can probably use the above function to replace "." with nothing.

You can probably write a shell script using dsjob command to stop the job if the DSJ_JOBELAPSED (gets the elapsed time in seconds) > 1800 seconds. What scheduler do u you use to trigger the jobs ?

Source columns of Datatype Decimal(26,11) get converted accurately into Decimal(18,3) & Decimal(18,8) & Decimal(18,7) into three cols seperately. You may need to use
DecimalToDecimal(<col_name>,trunc_zero)
and assign it to the target column length.

Is ur record fixed width or variable ? Need further details about the error.

PROJDEF (Project Defaults) in DEV or any other environment needs to be setup in Datastage Admin Level. Are you talking about the DB Userids and Password ?

I agree with that but every tool / programing has its own pros and cons. I was involved in migrating the COBOL code to Datastage and luckily i was not having a complex loop. But COBOL data loads was taking a day's time but with Datastage or with any relevant ETL tool, it would take a hour or lesser ...

If there is no IPC stage between a passive and active stage, it process the data row by row.

Most of the Switch and Case functionalities can be achieved by IF THEN ELse If in datastage. Am not sure what you mean by that.

It will be much easier if you do it in the SQL query level i.e i mean at the DB level when fetching the data from the table.

Transform routine needs to be used in the basic transformer. I assume you are working with Datastage server edition as you have Iconv function below. First you will be creating a server routine and then calling the routine in your transform and use the transform in the derivation part of your basic ...

If you migrate the code to a different environment, the job status changes to compiled with a date against it if you double click the job at the director level. If you are not migrating high volumes then this may be helpful.

Just to Brief on what ray suggested If CLAT-DIAGN-CD >= 0.0 and CLAT-DIAGN-CD <= 136.9 Then 1 Else If CLAT-DIAGN-CD >=137.0 and CLAT-DIAGN-CD <= 226.9 Then 2 So Forth. You may be writing this in the derivation part of the transformer against the Column CLAT-DIAGN-CTGRY-CD or else you can create stag...

We had the same problem sometime back. Instead of using Stage variable if you switch all your conditions to the derivation part of transformer then it would work fine. I am assuming that you dont have any dependency between the stage variables.