DSXchange

Well... to get this off the table right away, have you tried setting the Auto Purge option for the base job to keep 5 days worth of runs? Did that not work for you?

No worries! Just wanted to add that little tidbit.

Before anyone else gets the brilliant idea to post links to their site where they sell the exam answers - I'm going to delete them as I did the two that just showed up. Pardon my French but we don't allow that kind of bullshit here.

The problem with the command line is i have to give one character at a time.. With tr yes but that's not an issue with awk or sed which is why I mentioned them, the latter of which would probably be the easiest to set up assuming you have a familiarity with regular expressions. Have you looked into...

UserStatus is not just a variable, it's a storage area inside a job's internal structure. Do an exact search here for DSSetUserStatus and the "interlude" routine you need to create to call it.

FYI - a search here would have turned that information up.

Split to your own post.

ArndW wrote:I would guess that they are akin to stage variables, which cannot contain nulls

That hasn't been true for awhile from what I recall. The 'cannot contain nulls' part.

Sounds like you should talk to Kumar.

viewtopic.php?t=148701

No problem. Keep in mind the fact that you may need to temporarily disable automatic refresh in the Director to make this less crazy making with a large number of jobs.

What have you tried? Looks like a vertical pivot to me with an extra step to contatenate the new columns into a single one, perhaps with a newline between them. Or if you are on 8.5 or higher, transformer looping.

Get the listing that you want, perhaps turning off the Category display to do that. Then choose 'Print' and enable the 'Print to File' option.

It has no idea what DSGetStageLinks is as it has never been defined in your routine. In order to define it, you need to include the "header" file that has that definition in it and all of its siblings. Add this line to the top of your routine:

$INCLUDE DSINCLUDE JOBCONTROL.H

There's nothing in XMETA that I'm aware of that isn't also in the Director. And you don't need to be keeping "40 days" of history to be able to do what Arnd suggested, you just need to get the information from the last run of each job and check the date is within your 40 day window. You co...

I got the impression that he found it but wasn't sure how to use it.

If you are not fluent in C++ coding and how to integrate that into DataStage, I would suggest sticking with the external command line approach we've been discussing.