DSXchange

Use the DataStage role Super Operator which offers exactly this combination of privileges.

Check on the server that the record for this stage in the DS_STAGETYPES table is not locked. Use the LIST.READU command or Cleanup Resources in Director to view all locks.

Yes, and in exactly the same way (moving the same files) as for an unprotected project. You do, of course, need to have appropriate permission to the project/Engine directories.

Yes, via the DS_AUDIT table on Server B.

Administrator client Command window, or a dssh shell on the server.

You need to be more selective about which groups are associated with which projects, and make sure that "other" is suitable restricted in each process. In particular, the dstage group is not associated with any project. In addition, you need to tighten the relationship between DataStage roles and gr...

I cannot brain today; I have the dumb.

Add the user to dstage1 AND dstage groups.

Use your Administrator client Command window.

You need to learn how to drive dsjob which is why I provided the manual reference. This command can be asked to set its exit status to that of the job that was requested to be run.

We don't wave magic wands. With no idea about what your job design does and how it does it, it's impossible to suggest anything.

Have a different group associated with each project. The general group (dstage) controls access the the DataStage software, not to projects.

Suddenly? What has been changed?

They work as ordinary client applications as far as the database server is concerned. API stages use the native API for the database, ODBC stage (and DRS with ODBC set) use ODBC protocols via an ODBC driver.

Welcome aboard. The command is dsjob - you can search DSXchange or the Server Job Developer's Guide (look for Command Line Interface) for examples of how to use it.