DSXchange

Convert all your output columns to VarChar, and derive them with begin and end element tags. That will get you very close.
Optionally use before-job and after-job subroutines to create headers and trailers.

Verify in Diretor that the job ran in this queue. Verify in Ops Console dashboard view, by drilling through to the job, that it ran n the high priority queue. What do you expect to see on the Workload Management tab? This is really for managing queues. If the job has already started, it is no longer...

What error/warning messages were logged?

You don't add your job to a queue in WLM, you add it when you make a job run request.

Specify the queue name in the dsjob command line, or in the Job Run Options dialog when you submit a run request from Director or Designer client.

You might also like to research Optim data masking and the DataStage data masking stage that can leverage it.

There's nothing automatic. We prefer a well-governed process where proposed changes to tables are also advised to the ETL team, who can perform an impact analysis to see what jobs are affected. Subsequently revised table definitions are imported, overwriting the old ones (which have been exported or...

Process table full? Check with your Windows administrator.

You say that permissions should be allowed for all users, but are they? Have you checked?

There are activity variables that capture the command output ($CommandOutput) and the exit status ($ReturnValue) from the command (script). These are available anywhere downstream of the Execute Command activity. So, in your Job activity, you might set the value of a job parameter to be Convert(@FM,...

Use a similar activity variable expression for the job parameter in the Job activity.

Maybe Field() function or substringing to extract the header, trailer and the remainder.

You're passing it a time (00:00:00) rather than a timestamp.

Begin by documenting the rules for producing the output. I don't understand, for example, where the 10 comes from in the fifth line of your output.

The result of the Execute Command activity is available as an activity variable that you can use to populate the job parameter in the Job activity.

Note that you may need to trim a trailing field mark character.

To reprise my earlier answer:

(Auto) is guaranteed always to work (to deliver correct results, all else being equal).

(Auto) is not guaranteed to be optimally efficient in all cases. This is where someone with some knowledge can get a job to perform better (finish faster).