DSXchange

In 50 minutes only? You are a very fast reader indeed!

It's taken me years.

Or you can use SQLExecDirect() with @HSTMT as the statement handle.

Or, since you're on Windows, use Ereplace() to replace each";" with carriage return and line feed.

True, if that's what you want to do. But the subject is "failing to connect to UniData 6 database".

There is a column called JOBTYPE (or JOBTYPEIND) in the DS_JOBS table.

Search DSXchange for "vertical pivot".

Determine your job number then look in RT_SCnnnn directory (a sub-directory in the project on the server) where nnnn is the job number.

Fix your data types.

Choice of user-defined over generated SQL will make no difference if the SQL is the same. Therefore it must be something in your "special" SQL that is causing the slowdown.

Checking disk space after the event is a waste of time. You must be monitoring it when the problem occurs. Scratch disk fills and empties.

Put the environment variables into the project's environment variables.

The best place is the IBM class UV910 UniVerse Theory and Practice.

It's not really well documented anywhere but the UniVerse manuals are your best bet.

Search - this has been asked - and answered - more than once already.

The routine does not return 0 and is therefore considered to have failed (aborted) for the purposes of checkpointing. You need to create an explicit Failure trigger on the Routine activity to prevent this.

I'm not asking anything. I am observing that the job design has a partitioning algorithm specified, and that it is that which is triggering the alert message.