I have found if a) I have a DataStage Director open on the log detail for a given RTI instance, and b) the job ends, then the records stay. But that instance's log goes away when I click back to the Job Status view. I have six RTI services now and don't really want to keep six DataStage Directors open all the time - and that won't be quite so practical when I'm running 6 x ten instances, so I'm looking for other ideas.
In my case, I started some RTI services four days ago. Each job had min instances=1, max instances = 1 (just logic testing, not load testing yet).
The RTI services I started each have 1 instance running; that is good.
But one of them has a start time from last night, the others have a start time of 4 days ago; that is not so good. Now it seems I am without an evidence trail, and I don't know how to tell why my instance stopped.
I looked through the RTI management console and didn't see anything about "check here to keep job logs."
In SystemOut, I have some error messages bout my RTI EJB's invocation failing,
but no detail about why. The other logs in that folder have pretty stale
timestamps by comparison; no activity after I started testing.
Code: Select all
/usr/WebSphere/AppServer/profiles/AppSrv01/logs/server1/SystemOut.log
John G.