DSXchange

The function DaysSinceFromDate will give you the number of days between the two dates. Divide by 365 and you should be good to go. Does the one day, 0.00274 of a year, really make a difference if you round to one decimal place?

Craig's solution is even simpler and more foolproofer

He means that job parameters could also be looked at as having a global scope, but since their values cannot be changed in the job at runtime they are not really variables, but more like constants.

Declare your source file to have just one column, an unterminated VarChar. If "INDEX(In.BigColumn,',',1)" is true then the line has one or more commas and then you can parse the columns using "FIELD(In.BigColumn,",",1)", "FIELD(In.BigColumn,",",2)", ...

While one can store values from previous records using stage variables, one cannot change output value from a previous record depending on a computation in the current one. You will need to re-sort your data in descending key-column in order to make this type of processing work.

Just declare "dollar_cd" in the input link of the transform stage with the appropriate data type length and then you can work with that column, assuming that it is being delivered via RCP. You can check this by turning on OSH_PRINT_SCHEMAS to see which columns are being pushed through each...

I mentioned the "istool" because I think one can do category-level exports from the command line but can't confirm that right now - it is documented in pdfs.

I recall reading that sftp doesn't allow remote file actions such as delete, just local ones, so I don't think that this can be done, but it would certainly be worth a try - at worst there will be some error message and best case would be a solved problem!

You have a variable called @INROWNUM that gives you the input row number, or you can use the stage variable "initial" value to give you a value for the first row. In your case you need to use values from the previous row, so you will need to store these in stage variables. I am not quite s...

a filename ending in ".dat" doesn't real many anything to anyone here - it can be any format. Even simple files can be read with the complex flat file stage, just point the stage at the file and define your columns.

What have you tried so far and what were your problems?

DataStage stages are designed so that they execute one row at a time, so your requested approach poses some difficulties so that it doesn't get executed once per row. The best was has alread been suggested, to get the count in a job sequence and then pass that value as a parameter to your job. In yo...

Hello Balu6 and welcome to DSXChange. As part of the signup process and before posting to a new forum one should follow the recommendations, amongst which is this post The Search function is indeed powerful and entering "backup by category" or "istool" or merely "backup"...

in pull mode you can't execute remote commands so you will have to "ssh" the delete command some other way in your job. Either as an after-job shell call or from the calling job sequence.

What is not working in the job sequence checking for the return code? That functionality is often used and unlikely to be buggy, perhaps your shell script / SQL code is not returning a non-zero return value? Since you can read stdout into a variable in your sequence you might be able to parse that s...

I'm currently not at a DataStage client where I can post the exact steps, perhaps someone else might post the steps or you could look at the documentation for the CFF where the procedure is described. Just as in a COBOL program, you use one field to determine which record type is being used in that ...