DSXchange

It's 32bit software that "tolerates" 64bit Windows, hence your issue. Bit of a downgrade for you, I'm afraid. There's no setting that can change that fact.

DataStage comes in 32bit and 64bit flavors depending on platform, so it's not "Windows v. Linux" but rather "32bit v. 64bit" as you noted. And I'm kind of surprised there isn't a 64bit Windows version but support shows "64 - Tolerate" meaning still 32bit for part of all...

Working properly now, wasn't before.

In your version, the only answer I've seen here over the years is coding something up using Java. I believe you need to get up to 11.3 for HTTP as a source to 'go native' so to speak.

Parameter values? No they cannot. That doesn't mean, however, that you can't assign them to other variables and then change those.

Start your own topic.

Yes, being very careful of what exactly you change of course. And with good backups.

Do it in the source SQL... unless, of course, they don't all live together.

What are your join rules, how do you determine which 'few records' get which combination of keys?

OK, I'll ask. Can you share for us why you are looking into this? There is some concern that with your limited knowledge of the tool that you might be making a decision that is not in your best interest long term. A full explanation could help arrive at a more proper solution. Pet Peeve Alert: We se...

no corresponding cron entry is created So which is it? There's no cron entry or the job does not run? As has been repeated here many times, for a non-repeating schedule there will be no cron entry created as it will be handled by the at scheduler. Just want to make sure you're not assuming that jus...

Not using the "wait" is the only way to come close to the at once requirement. And the sleep is just a suggestion to avoid overloading the server during startup, space out the job invocations a wee bit.

... and then you'll still have to deal with the library path issue.

Thanks for coming back and posting the resolution.

We are unable to access the DataStage server. Therefore, shell scripting is not an option. Can shell scripts be created but then 'installed' and/or run on the server by someone else, an admin perhaps? If they are completely off the table, you've lost a very important tool from your ETL toolbox. IMH...