DSXchange

This is a problem with their scheduling system that submits jobs. They have escalated to vendor.

Welcome aboard.

Their reason may be purely political or it may be a bad experience they once had where two huge jobs swamped the server or locked rows, pages or tables in the database. You need to discover the reason.

DataStage has no limits on the number of jobs running simultaneously except that any single job can not be started if it is already running. To get around that, jobs can be made "multi-instance capable" so that clones of the job with unique "invocation IDs" can be run at the same time.

Beware, of course, that every job running will demand resources. Things will be good only so long as the system can deliver those resources.