DSXchange

Is this still true? And is the error exactly the same? If not, post it.

This code is working fine for case: 1,2,3,4,5 but in the case of 6,30 my job get aborts

Kind of funny... when I first started I had *no* idea that a single job could be scheduled multiple times, for whatever reason I figured that once you 'added it to schedule' that was it. So I created identical copies of job and scheduled them. Thought there must be a better way and so asked here, af...

"System.OutOfMemoryException"

Somehow, I think Arnd got it right.

'Add to Schedule' multiple times from the Director, once for each 2 hour starting point - and hope it doesn't take longer than that to run.

If you have the 'Enterprise Edition' you have the MKS Toolkit installed and have full 'UNIX-like' scripting capabilities. Or convert it to a DOS equivalent.

Write a routine. There you can do the 'attach' to get the handle, query for the information you want and then detach properly. And you can do a better job of handling any problems that way.

What about via an IWay Software adapter, they have what seems like full support for Microfocus C-ISAM but don't know about that exact version. Fairly sure that your "index format" files are equivalent to C-ISAM. If not, I would think they're still something supported.

"Multiple Lines" pivots to one output line. Input/Format/Delimiter for what goes between fields. Set the Stage/LineTermination value to UNIX and then in a transformer use CONVERT to turn each LF to a comma. Done.

Sorry, figured it would be obvious to you once I pointed that out - it's the one named IBM DataStage TX (scroll down to see it) but here's a direct link to it:

viewforum.php?f=43

There is a specific forum for TX questions and the people that answer them really only check that forum, I do believe. So I'd suggest you mark this one as Resolved and repost it over there. Sorry.

Yes, that's what it is for and it is not optional. Use of DB2 is optional but you must have an approved RDBMS for the repository, either existing or newly created.

No clue, not a Windows admin. Check with whomever administers that box about AT access.

The scheduling user needs to have permissions to the AT scheduler on Windows.

Both the where and the how are there in that post.

I would suggest the "after job custom subroutine" approach, but that does mean you'll need to whip up some BASIC code.

So, I'm assuming the jobs are running but not logging where you expect them to. Check this post and see if it helps.