DSXchange

Ray

I never needed it in a loop before so I hadn't tried it but it would work. All you have to do is add loop value to the touch filename and it would work perfect.

Does not work within loops.

You can do it in a DataStage routine. There is a property to tell if a job is multiple instance. There is a call to ask for all the instance ids. Do a search. I think this solution has been posted.

Arg2 = ''

Is an empty string. Not sure what you are really needing. You cannot leave an argument off when calling a routine.

Paul is correct. Cutting and pasting into Designer from Windows is a hit or miss issue. I have seen it break jobs. Underneath the covers in Universe char(13) and char(11) get mixed up with @FM. I have actually fixed these jobs by editing records in DS_JOBS and DS_JOBOBJECTS which I would never recom...

That is part of what I meant Andy. Check-pointing plus automatic handling and the job property settings need to be set properly so DataStage does not handle where to start next run. All that is handled by files. One file per job. You can create these in the sequence after a job runs successfully wit...

The best way to accomplish what you want is what we call touch files. So have a folder we put a sequential file in after each job runs successfully. Each file in a sequence is assigned a file. All files in a sequence start with the same name. All restartability is turned off. So if this file exists ...

You could do it with a CASE statement and a job parameter.

A project is usually one target. Jobs within that project are grouped by source. Usually one source is within one sequence. So the jobs are grouped by sequence. A master sequence may pull from a buncjh of sources but this is the way I do it most of the time.

I had a routine in EtlStats which did what Ray describes. I don't think it works in newer versions. If you are outputting to a sequential file then you can concatenate all columns into one column. Then you could build a html header and footer record from a row generator then output all to a funnel s...

That is the one. Nice work Craig.

Why not take a full export which I assume you do nightly and use the Perl script to cut exports into files and modify it to do table definitions. Do a search for it.It cuts out jobs into one dsx per job. I am sure you can get what you need this way.

I did a Google search and found one posted. Not sure what I did with it. If I find it I will post it.

It is a way to pull folder names. It may be a way too get \\NEXTJOBNUM. Not sure without trying it.

I totally agree with Ray. It confuses more people than it helps anybody. At some point you need to turn it off anyway to drop all columns not going to the target.