DSXchange

Unrelated issue - get the syntax of the timestamp_from_string function correct in your specification - include 'nullable' if needed.

Yes there is. Research the properties of the stage carefully (particularly the available properties to add in each of the properties folder). Report back with your research findings.

You might also Search the forum; I'm fairly sure this has been answered before.

It meas what it says; '10,X' is not a valid SQL token for Teradata. Now you have some detective work to do to determine how such a token came out of your job design to be sent to Teradata.

Since you must nominate the project in which to run a job, the question should be moot. For the -lprojects option, try setting the DSHOME environment variable.

1. If you can find a UNIX-based ODBC driver for Excel you can import the table definition through that. No such driver ships with DataStage. 2. An XLS file is not a delimited file. It's more akin to a database schema, except that every worksheet is presented by the driver as a system table. And work...

Then it was not this call that generated a "not in VOC" error. Please post the entire error message, verbatim (copy/paste, rather than transcribe).

You probably need some single quote characters in the VALUES clause, but that would not be the cause of a "not in VOC" error.

And Search for clues about owning mutex locks.

No idea. Tell us what changed before and after this behaviour. Ask your colleagues, as forcefully as necessary.

Change the Nullable property on the right input and on the output links for this column to "Yes".

Check also whether the file already exists but is (a) owned by someone else and (b) their permissions don't allow your job to overwrite it. Check, too, that you still have write permission to the parent directory. Finally, make sure that all users in the project are in a common group and have a umas...

There is a 'job indicator' column called JOBTYPE.
0 = server job
1 = mainframe job
2 = job sequence
3 = parallel job


Substitute COUNT(*) in the SELECT clause if all you want is the count.

Wrap your job design in [Code] tags so we can see it properly. Add Peek stages on relevant links so you can truly verify where data are and are not flowing. And you need to check the DB2 database (not the DB2 stage) to determine whether anything is locked. Are you, for example, updating one or both ...

Try clearing the log table before invoking the TPUMP utility.

A master job sequence is the one that runs the other job sequences. Within any job sequence a Job activity can run a job sequence (or a server job or a parallel job). So, if your two job sequences are JS1 and JS2, the master job sequence would have two job activities to execute these, together with ...