DSXchange

Please always start a new topic when you have a problem of your own, even when it's the "exact same problem". If you really feel the need, link back to the other post as I've done in your post.

Thanks.

Talk to your DBA about the limits they have configured, there are several possible. Connections can be limited by user, there's an overall limit as well. There are also O/S limits that can come into play.

No there isn't... not for the 'legacy' repository nor XMETA.

That document is still on Kim's site in his Tips section.

Yes. Of course you could always remove it and check for yourself.

Doesn't really answer why the error is being thrown unless the value is being corrupted somehow. And you'd only know that if you log it. As to your question - yes, you can call it in a MI job. However, should you? Keep in mind the fact that there's only really one job under the covers and if you run...

As noted, calling DSLogInfo() in the routine to record the value being passed will go a long way towards solving this.

You cannot set any sort of "job status" in the trigger. However, you can check $ReturnValue <>0 and branch to a Terminator to abort the Sequence if that's what you want.

vikas gupta wrote:ADMU3011E: Server launched but failed initialization. startServer.log, SystemOut.log(or job log in zOS) and other log files under /u01/app/datastage/product/IBM/WebSphere/AppServer/profiles/InfoSphere/logs/server1 should contain failure information.

Your next step seems pretty obvious to me.

Write a small Server job to update the status, I'm assuming passing in the filename will allow you to find the row again. Run it via another Job Activity stage inside the loop after your processing job. The loop will end automatically when it runs out of things in its "list of things" and ...

First advice is always to try Resetting the aborted job from the Director and seeing if a "From previous run..." entry is added to the log. If it is, please post the contents.

You need to check the return status between the Execute Command stages and decide what to do if they "fail". What is your trigger expression? Or at least answer Ray's questions.

Sorry but I already did.

... unless it's a Sequence job that is restartable.

FYI - you loop or pivot, not both... just in case you were trying both, hard to tell from your post.