DSXchange

If you want to pursue the "store the logs elsewhere" train of thought, search the forums here for "ETLStats", the fruits of Brother Kim's labor which he kindly provides for free. You can either use it outright or treat it as a template, a huge leg-up starting off point for rollin...

Read my post again. Purged is purged so they are gone. With no filter in place on the Director, you are seeing everything in the log. If you want to store these "historical" log entries, you're going to have to build an entire system to do that on a regular basis before they're purged - re...

Did you check the Filter setting as I mentioned? There's no need to go down the path you've chosen, it just unnecessarily complicates things.

Use the "Print to File" option in the Director, that's why it's there.

Make sure you understand that will reset the status to show the job is not running even if it is. That's why it asks you twice "Are you sure?".

No, the "Auto Purge" setting for each job controls that. And there is a Filter to limit the number of log entries to show in the Director, make sure that's not set and preventing you from seeing everything. From the "Log" view, go to "View / Filter Entries..." from the ...

The Administrator is a client tool installed on your PC like the Designer. Start it, select the project from the Projects tab and then click the Command button.

Typically one would look at the log of a job using the Director client. That not what you are looking for here? Going under the covers needs some idea about the structures and relationships in the repository to accomplish, for example understanding how to equate a job name to the internal job number...

I'm curious what you mean by "complex sql" and what this "straight extract sql" is that works in the job where the allegedly complex stuff doesn't. Any chance you can post both user-defined queries so we can see them?

No, that's not true and I believe we've had this conversation before. The filename property is required, is not ignored and it works just fine as I posted as the stage automatically combines the two. Come on, give it a try, you'll see.

Curious why you would think you'd need to edit the generated job control.

I've already noted that and they've shown they are using a full path to the file: Commands Used: Filename: <full path>/Test.txt Filter command: tail -1 They've also noted that removing the filter and just using the full path works fine and reads all records. So hopefully we're past the invalid path ...

All things are possible, but think about it. Out of the box the only values that may match to the char(1) are 1 character values in the char(3) field, is that what you need? Or are they a match if the first character is the same in both fields? You'd have to tell us what your match rules are.

So, the original 7.5.0 release and not something "more recent" like 7.5.1a? If so, you may need a patch or to upgrade for this to work. Check with your official support provider.

:lol: "Grognard" is French for "grumbler" and something Napoleon called his Old Guard, his grizzled veterans. I mean some of the folks here who've been involved with DataStage since Day 1 and actually worked for the various companies involved, authored some of this stuff... peopl...

Is there an escape character for DOS? (like backslash in Unix) From what I recall, it's the "^" (what we used to call the "hat" or "tee-pee" but now is some kind of vegetable) but I don't think that's going to help as you really do want the metacharacter and not the li...