DSXchange

Why, so you did. I didn't bother to scroll back that far.

Interesting.

Put them in a delimited string and then parse it back into the component pieces after fetching it from the user status area.

You're certain both B & C output links (assuming there are two) are set to a Transaction Size of 0?

I can't imagine this is different in mainfraime jobs but transaction size is a link property everywhere else. That is, each output link will check the number of rows down it and commit as needed.

Your choice. That's the 'dynamic' aspect of it,.

That happens when you reindex the project and not everyone is out of it. You need to ensure yours is the only connection active or otherwise, there are no running jobs, etc etc. Only then rerun the reindex.

Which? 'Command Line' impying from the O/S or 'DataStage Command Language'? If the latter, you'd need to explain what you mean by that - the TCL prompt?

They stated "5 months and 2 weeks", not days. And yes, does seem like a curious interval and dependant on their definition of a month in this case.

No probably about it. That's the perils of using a relative path.

You'll need to 'remove' the time portion, work the magic on the date portion and then pop the two pieces back together, AFAIK.

Search for DaysFromDateSince. And then decide what "5 months and 2 weeks" means - 154 days? And is it a date or a timestamp?

ArndW wrote:No, the project level setting would only allow users to create multiple instance jobs.

There's no project level setting for this that I am aware of.

Never mind the fact that I've already explained what you need to do to make this work. Can't believe we're still going round and round and up to 3 pages now.

Does the "Multi-Job Compiler" no longer exist under 8.x?