DSXchange

I think all utilities which runs on mainframes work the same way. even when datastage runs in unix. it translates the code into a language (orchestrate) unix understands.

which other way you expecting datastage to run:-P lol

If you red the "installation and upgrade guide" provided with your datastage installation, you can get some pointers.

It says that there exists a "enterpirise MVS edition" of datastage which will allow you to develop jobs in mainframes.


Please read it for further information

no it will not make it a fixed width file but it will fix the length of your columns.

you can get rid of the quote character by typing 000 instead of quote

are you sure no nulls are being passed to a field which is not null? this happens when datstage drops the records but sometimes you still see all the rows traversing to next stage.

keep the delimiter as comma and use char instead of varchars.

you can fire it from mainframe using CA7 or any other mainframe scheduling tool.

why dont you do all your joins at the database side and populate a final view. use datastage to extract data from there. would be much faster

perfectly agree with ray. this site can bail you out of trouble but cannot teach you how to walk.

learn how to walk and we will help you learn how to run:-)

SOS roy.

is there nothing in pallete that can help me?

something which transfers the loop to the job next in sequence?

just curios.

is anyone else using the same file...maybe for testing or just by mistake?

I can suggest you two solutions: 1. write a SQL query in the ODBC stage aggregating your columns and sending the output to the new columns. something like: select Region,Dept,Dep_Sal_Total,Region_Sal_Total from <table> where Dep_Sal_Total in (select dept,Sum(Sal) from <table> group by dept) and Regi...

I have around 20 jobs in one sequence. It looks rather clumsy connecting all of them to one.

this is the way its currently designed. I was looking into the possibility of another design to improove the legibility of the sequence

Hi,

I want to write a sequencer which ivokes a exception handler when a job fails and continues to run the next job.

setting trigger to uncoditional in job1 is of no help as once the control moves to exceptional handler it doesnot goto job 2

i changed the job design to job1 - Job 2 Exception handler - notify (sequence) - Notify (job fail) and its working The issue now is when i say that job2 should run after job1 unconditionally and job1 fails, i want the control to pass to job2. ofcourse i need the exceptional handler to work too for j...