DSXchange

On the Server side you have the DIGITS transform but on the PX side I'd just fall back on Convert, I do believe:
Something much like that.

Of what logs do you speak? Why does the subject say "job location", typo?

... and?

The Complex Flat File stage was built to do exactly that.

Simple, perhaps, but problematic. Any issues with that approach and you'll be correcting it manually. You can easily add this "end timestamp capture" function capability into any job that needs it using a Aggregator to ensure that happens last. I'm assuming, however, that you may need to d...

This cannot be done "before job" to the current job. Run the routine via a Routine Activity stage in a Sequence and pass the output to the job that needs it there.

The same way you tested them when you built them originally. You run them and verify the output. Not sure what other advice you might be looking for.

You have to decide if you need to run everything through that gauntlet or if representative samples of each "type" of job is enough.

Well, rather than hijack an older thread here you are in your own topic which you can come back and mark as resolved if you figure out the issue. That or come back and ask more questions.

I'm going to take a wild, crazy guess that you need to add the "-domain" option back in... with a proper domain value. I'm also curious if there are any "special characters" in your userid and/or password.

The normal ones. Director allows a wildcard search, suggest you do that first and then turn off Category display. Otherwise, search DS_JOB from the Administrator:

pandeesh wrote:That will suite your requirement i believe

Not sure there's a "requirement" to be met here, at this point all we have is a question.

jwiles wrote:Where does it say that in the manual? According to the docs, it returned what you asked for (field #1).

I agree and you got exactly what I would have expected. Can you post the verbiage from the documention that you mentioned? Perhaps when it comes to the wording, they choose... poorly.

That's a SIGKILL not an unlock and you need to read about the -9 termination signal. It doesn't allow for any kind of lock release to happen, it just... kills. Without mercy. Try a "ps -ef | head -1" if you want an easy way to see the headers to know which column is what. If you're still n...

Where are you seeing what you posted - in the dsenv file or the job's log? For the former, just change it there. Otherwise, I'd suspect it is in the .profile of the executing user, or whatever userid is used to start the DataStage services.

I'm not going to have the exactly correct terminology but (from what I recall) you can set the Lookup to Fail if a match is not found...