DSXchange

Take a look in the job log at the environment variables to determine the user under whose ID the job is actually executed. It is this user (reported as $USER) whose ulimit needs to be raised.

Welcome aboard. :D There is nothing automatic except within one job. There you could make all rows a single transaction. But multiple jobs you will need to design a strategy for "reversing". You could commit to temporary tables until all jobs were completed, then transfer the rows to the real tables...

Capture the short rows in the reject link as a raw string. Run this through a Column Import stage to parse it into the eleven columns, then through a Column Generator stage to add the twelfth column. Bring both streams together using a Funnel stage.

You don't need to browse for job parameters in a DataStage job sequence - they're all populated into a list, and you can choose them from that. The list also includes all activity and user variables from all upstream activities, so everything you might need is all in one place. No need to search.

Administrator client. Job properties. Environment...

Add them in the User area.

(Or you can add them to DSParams using a text editor.)

You DO have BASIC Transformer stage.

It's in the Stage Types branch of your Repository.

Correct. It isn't in VOC. Your copying skills aren't very good. DOS is a command, /C is a switch for that command. But, even then, Desktop is not a "command". Nor is it a "batch file". So that won't work. You need the full pathname of the BAT file. What are you trying to accomplish? If you cannot pr...

Use a BASIC Transformer stage (the overhead for one row can be ignored) and use the DSSetUserStatus() function in a constraint or derivation expression. Search the forum for examples.

I am completely agnostic about schedulers; whatever my clients choose is their call. I do not offer "this is better than that" advise ever, because such comparisons can change over time.

Only uninstall and install the lower version. You may be able to import 7.5.2 jobs into 7.5.1 but, in general, importing from a higher version into a lower version doesn't work.

From the DataStage Administrator client Command window it's where pathname is the pathname of the BAT file.

Still don't understand what you're trying to accomplish.

Run in a separate job, store the result in a file or in the job's user status area. Pick that up in the job sequence and feed its value to your job parameter in the Job activity.

Third party scheduling tools use DataStage's command line interface dsjob to execute DataStage jobs.

Look where I guided you. There are scripts there to create the requisite tables in Oracle.

Look in the Orchestrate Administrator manual for all options to orchadmin (or simply execute orchadmin with no command line arguments).