DSXchange

Then please mark your post as Resolved using the button at the top of the page.

Please answer both questions.

However, depending on a field in the same place, the whole file could be written to either 1 or many output directories. Sorry, a little lost here. What is 'the same place' - the field is in the input data stream? If so, can it have multiple values or will it be a constant value per data file? And ...

'Released' is different from a simple 'export-import', are you actually releasing your jobs or just exporting executables? The job name would have 'rel' and a number appended to it for the former.

Of course, the schedule information is not a DataStage 'thing' but rather was part of the server 'at' information that was nuked with XP that DataStage simple looks up. Meant to mention that you'd need to redo that regardless, but forgot. In other words, you lost all scheduled tasks, not just those ...

This is one of the dangers of using your own sql. As noted, make sure the columns defined in the stage match exactly with the columns selected in the query.

I haven't done that but was wondering if that was the way to go. So, probably best to uninstall the Server and reinstall it so it can hook back up to your project. Way too much involved under the covers to do that after the fact...

So... I'm assuming you do not have an export of the project? And when you reinstalled the server component, what did you specify as your projects path - the old path or a new one?

Don't those "pathnames" also include the system name and/or IP address?

You need to start by 'sourcing' your dsenv file first to set the environment properly:
If $DSHOME isn't set, you may be able to get there this way:
Or just cd to your DSEngine directory.

How many nodes are you running the job on? Do you have the same issue if you run on a single node?

The 'host' would be where the server component was installed.

What's your MFILES setting in the uvconfig file?

Can you give us a better idea about what kind of jobs we're talking about here, design function etc? And while I can guess what 'running in a loop for quite a while' means, but I'd rather not.

It's not DataStage, it's something Oracle does. Search here for $APT_ORACLE_PRESERVE_BLANKS to find previous conversations on the subject.