DSXchange

Yes you need to create a job. Use a UV stage or a Hashed File stage to extract rows from DS_JOBS. The table is DS_JOBS, the two VarChar columns are NAME and CATEGORY and the selection criterion is that NAME does not begin with a slash or backslash character. In a UV stage this is a WHERE clause on t...

That's not the same as not generating the warnings in the first place!
When you use the Modify stage add an additional specification containing the single word NOWARN.
This is not in the Parallel Job Developer's Guide but you can find it in the Orchestrate Operators manual.

What's in a name? Close in some stages, After in others.

Doesn't need it. 5.2 is UniVerse, 7.x isn't. Easy.

Joshy started it!!!

There are at least four different ways to generate sequence numbers. You need to be quite specific about the technique that you are using.

No, it's actually an Oracle bug. It does not give correct responses to standard function calls such as SQLColumns().

Imagine you have a Word investigation job called IAHNAME containing an Investigate stage also called IAHNAME. In the Controls directory there will be a file called IAHNAMEI (the final I means it's an Investigate job) with overall properties - seplist, striplist, the field to be investigated, how the...

OpenSeq, ReadSeq, WriteSeq and CloseSeq are the BASIC statements for working with line-based text files. However, you can't update. Instead you could open the parent directory as a table and read the file as a "record" whose "key" is the file name. The variable into which you read the file is a dyna...

In the Columns grid right click on that particular column definition then choose Edit Row from the menu. This will open the extended properties dialog where you can, among other things, supply a default value for the data type and a value that will be used in the file to represent NULL.

Invocation ID

You also must not break any rules, such as having multiple jobs (job instances) writing to the same text file.

Re-compile is only required if you have changed the job design.

If you have not changed the job design, you do not need to re-compile. Reset is sufficient if the job has aborted and its design is not changed.

A timestamp format string must have both a date portion and a time portion. Yours just has a date portion.

You can do either. That's my point. Whichever you do you get TWO virtual Data Sets. It's got nothing whatsoever with sparse lookup - it's how normal lookups work.

And, indeed, that's where I was headed with my question. Do let us know whether this change fixes the problem and, if it does, mark the thread as resolved.