DSXchange

Easiest to use would be a sequence with a WaitForFile activity.

Next easiest would be a before-job subroutine using ExecSH to execute a command to check for the file's existence.

The first set are the status of the term. There are four possible values: Candidate, Accepted, Standard, Deprecated. The second set indicates whether the term exists only in the Development Glossary or exists in both the Development and Published Glossary. You implement a governance process in which...

Do you mean all the jobs designed to be called in the sequence, or the jobs actually called when the sequence runs (which may not be all of the jobs in the design, depending on the sequence's logic)? The first is most easily accomplished by querying the DS_JOBOBJECTS table. The second is most easily...

Impossible to say now that they have been deleted and re-imported.

Did you refresh the Repository view in Designer? It does not auto-refresh. Find Refresh option on the Repository menu.

Gee, it would have been useful had you mentioned that originally.

Never mind, it doesn't add much complexity. How do you know that the end of a group has occurred?

Try cutting the length in the metadata back to a sufficient length (4000 probably).

You can type BYTELEN in. It will be red but will compile, as it is a part of the language. However not every function in the language is in the list of available functions stored in DSParams. Do you know what these characters actually are? Are you using an NLS map when reading the file and, if so, w...

Available date formats can be found here as well as in the manuals.

Was the first import selective (and did you select only the executables, not the job designs)?

You need to provide a format string that handles all possible date formats that will occur in your data.

You might try CAST (columname AS LONG VARCHAR2(20000)) in your user-defined query.

Does the SQL involve anything that will take a long time for MYSQL to respond to, such as an ORDER BY or HAVING clause?

You need to create the environment variable (using DataStage Administrator client) and bring that into the job as a parameter. The parallel execution engine is looking for an environment variable.

Something like this will do the task. Error handling has been omitted for clarity. FUNCTION TimestampDiff(Timestamp1,Timestamp2) Day1 = Field(Timestamp1, " ", 1, 1) Day2 = Field(Timestamp2, " ", 1, 1) Time1 = Field(Timestamp1, " ", 2, 1) Time2 = Field(Timestamp2, "...