DSXchange

Nothing I posted implies fixed width.

I wonder whether END might be a reserved word? Can you try it with a different field name?

What other mechanism (apart from ODBC) do you believe to be available for accessing SQL Server, particularly from a UNIX server?

Make the columns nullable and ensure that the default value is null.

Push back on the arbitrary restriction on your effectiveness. Server jobs are perfectly valid.

I doubt that the IPC stage is helping here - enabling inter-process row buffering would have the same effect. You would probably get better gains pre-sorting the source file using a Filter command in the Sequential File stage and losing the Sort stage altogether.

The file does not exist becase DataStage determined that there was not enough space to create it.
Do you have at least 1623935520 bytes free on D:/IBM/InformationServer/Server/Datasets while the job is running (note that other Data Sets will also need space here)?

In parallel jobs you need to configure for the maximum possible number of columns, assigning null to each unused column and subsequently filtering out the nulls. Or you might consider using a server job and the multi-value handling capabilities of a UniVerse stage to achieve a vertical pivot with an...

To run (without embedding in a DataStage job) you would need to write and compile an appropriate main() function that could be executed independently and which could invoke your routine.

In the messages it states "Contact technical support". I suggest that this is your best option. There are far too many possible causes of failure to load metadata than can easily be canvassed here.

Did the link name in the constraint expression get updated automatically? This does occur for output column derivations; I can not check right now whether it happens in constraint expressions.

Try quote=none rather than quote='none'

Are your UniData services (particular shared memory manager) running?

The bit at the end is a worry, an unneeded comma after quote=none and no terminating semi-colon for the final field definition.

Check for expired licence (whether or not this is true - check the licensing XML files also). Are any other error messages generated? Is the DSHOME environment variable or the /.dshome file intact?

It's all done with operating system groups and DataStage roles. Research these either here or in the manuals.