DSXchange

This fact was mentioned in the original post.

Welcome aboard.

How is the property "Transaction Isolation Level" set?

Still no error message? If there is one, please post it. There are too many possibilities to waste time guessing.

You should be able to. Go to the Licensing screen in the Administrator client.

It can also mean that the job is Aborted/Stopped and has not been reset.

It may also, but not in this case, mean that the job has not been compiled since it was most recently modified.

The next thing to check is the firewall. Is port number 31538 open? This is the one needed for dsrpcd - the one on which it listens for inbound connection requests.

The NLS code page specifies how the data are encoded OUTSIDE of DataStage, for example in files and database tables. The NLS map translates from this encoding into the Unicode representation used internally by DataStage when reading. Or vice versa if writing.

All jobs that are designed in a sequence, or all jobs that were executed in a particular run of the sequence? (The latter may be a subset of the former, depending on the particular logic of the sequence.) Both answers are available by searching. The latter answer involves interrogating the job seque...

Or change the format of the cells if they really must be Number.

It's NOT a DataStage issue.

If you want different behaviour WITHIN the old routine then your way is to be preferred.

An alternative might be to load the sixth value into the job's user status area and have the routine pick it up from there.

Have the Director window maximized and the Manager window about one-quarter screen size, it's then really easy.

Once you get to version 8 you will have Quick Find and Advanced Search and you can select any combination from these tools. Advanced Search allows filtering by date/time modified.

Have you searched for

The number of reject datasets "0" is less than the number of input datasets "1".

Yes I can, but I won't.

Premium membership is not expensive, at less than 30c (Rs12) per day, and is one of the ways that the hosting and bandwidth costs of DSXchange are met.

I do not propose to set any precedent that might undermine the ongoing viability of DSXchange.

Multi-client Manager should be what you require. (In earlier versions this was called Client Switcher.)

You can not have both client versions active simultaneously, since they use identically named, but different, DLL and other support files.

Method 1. Use Director client Schedule view. This is an interlude to the operating system's scheduler.

Method 2. Use any third-party scheduler (or the operating system scheduler) and the dsjob command line interface to request your job runs.