DSXchange

Kim, you're right in that if that 'unstoppable' process is database related (say like a cursor is still being gathered) then the best approach is to have a DBA kill it and that will certainly get the job's attention. But knowing the post that brought about this question, it is about non-db type hang...

The return value is actually a dynamic array, so one other solution would be to take just the first element from it: ExecuteCmd.$CommandOutput<1> Another would be to strip the Field Mark that is added to the return value: Convert(@FM,"",ExecuteCmd.$CommandOutput) Both of those solutions wo...

It is *a* correct approach, yes. However, it seems your second job doesn't like the timestamp format you've passed in.

You'd have to post your abort message and be specific about which job is aborting if you wanted anyone to be able to help.

Not all operations are easily 'stoppable', you may need to find the process and kill it directly, and I'm assuming you'd use the Task Manager for that on a Windows server but not sure if there is a 'better' or more proper way to do that.

The "invocation id" is something else entirely. Please be precise about what exactly it is you tried so people can help.

Can't check but off the top of my head, there should be a function to return the "controller" or "controlling" process, that should get you there.

Dang, that's right. Informatica is rotting my brain.

Ah... that makes sense. I've also seen issues of this nature where a simple rerun, much like the recompile in your case, 'fixes' things because by then the timing issue is no longer an issue.

Thanks for posting your resolution.

Don't have any DS access, so from memory... Manager, connect to Project, go to Properties and there should be an option near the bottom for Environment Variables? Something like that.

dsusersaj wrote:I searched the docs.But couldnt find PROJDEF info in it.

Search harder, it and its friends $ENV and $UNSET are definitely out there.

anbu wrote:Delete the variable and re add it in the job to see the value.

That would only work if you were in a job that used it, I specifically said to use the Manager client which is where they are defined.

By checking the DEV project, should be right there. You can also check the second log entry for any job that uses it, that one lists all environment variables in play at the time the job ran.

So... this is how you take a break, eh?

From the Manager client, connect to the project in question and then investigate the environment variables there, in particular the 'user-defined' ones.