DSXchange

I don't recall if you'd have issues or not. The client upgrades may not be required immediately for a minor rev, but you are best off doing it so they are in sync. And there's always the Multi-Client Manager if you want to have both installed at the same time to connect to two different version serv...

Yes, upgrade your clients... and don't worry about the 'Engine' release.

No worries. I'll call the FBI back and tell them "never mind".

Actually, I'd say the support for string manipulation in DataStage is very extensive. 'Better' is a relative word, so perhaps in some instances in some shops there are 'better' ways to do it, but I prefer to stay in the tool if at all possible... and I don't recall the last time that wasn't possible.

No, nothing official. Export and Import is painless and just pretty much runs on its own, why try to circumvent the process? It's only time, after all...

You do know there are other less 'drastic' ways of handling that problem without shutting off that functionality for the entire Sequence job, yes? And that it's documented in the online Help accessable from the help button on the Sequence job's Properties page, yes?

Exactly. One tool to rule them all...

Just do it. There's no 'special settings' there for mainframes. That being said, I'd prefer a more standard scripted approach. Most shops with mainframes have third-party transfer tools, ones I've used in the past but don't recall the names of. They would do automatic stuff like translate from ASCII...

Not positive, but think you need to read up on the 'Omit' option.

Also note that Kim Duke's website (check his sig in any kduke post) is hosting the rather helpful Using the XML Pack - Best Practices document from Ascential for us. Anyone can download it from there.

It could be that your server is just... busier, unless it always seems to take longer to start regardless of what else is going on. That was an issue for us awhile back, one or two runaway processes from another group locked up CPUs for their exclusive use and everyone else's performance went 'in th...

The 'official' answer is to recompile the base job, that will remove all instances of the invocation runs from the Director but not clear the log information. This can be problematical, however, if it is read only as most people have their production jobs, I would think. Unofficially, there's been s...

... and easily done in DataStage as well.

Hey, I knew that! I'm just so used to breaking things up into logical chunks that I espoused that approach here. But now that I think about it, I like your answer more better.

I'll have to keep that in mind for 'next time'.

Have you tried Resetting (not recompiling) the job via the Director? Sometimes that will get you a 'From previous run...' log message and it can have additional (as in helpful) information.