DSXchange

You can speed up the import by checking "overwrite without query" and deleting the existing (old) versions first. Make sure that you have a backup, of course. You can speed up the compilation by having more than one Multi-Job Compile session running, each compiling a disjoint set of the jobs. Takes ...

Ask whoever installed it. Look in the system log - the documentation of all changes to the system. Properly done it should be a book chained to the console.

Of course you don't. @INROWNUM does not become 1 until the first row appears on the input link, triggering generation of an output row (depending upon the constraint(s) you may have set).

You definitely need to re-think your design. What is the source of data?

Because the file is defined as fixed width, the Null Field Value must have the same number of characters as a non-null value in that field. In this case, apparently, 19 characters. Nineteen space characters would do. Twenty-three character timestamp would NOT do. A zero-length string (""), which is ...

Welcome aboard. :D

Since these stage types do not have identical properties you will need to effect the changes one at a time.

MetaStage is not a tool for promoting or compiling jobs. The tool you need for that is Version Control.

How do you attempt to run the job, and what error message is generated?

Is this a MetaStage question or a Version Control question? There's no concept of rollback of an individual job in MetaStage (since that's the forum in which you've chosen to post) unless you've elected to create a new version of the directory with just that job (unlikely). You can "roll back" - not...

Try changing the view to MetaStage view.

Most of what you need is here - doesn't your Search button work?

Saddened to note the passing, within eight days of each of other, of Brant Parker and Johnny Hart, the originators of The Wizard of Id


Galoop.. galoop.. galoop.. the king is a fink!!
-- The Lone Haranguer

Doubtless your "Lookup Failed" rule is "Continue" and the Lookup stage is therefore behaving as documented.

Welcome aboard. :D

The situation here appears to be that some of the project is present, and some is missing.

Your absolute assertion is misguided and misguiding.

Etiquette Note
Incidentally, there's no need to quote the previous post - it only wastes valuable space on the server.

Warnings are also possible. For example, if data are truncated.

Should be, would be, could be... Show us (a) what the dates look like and (b) the data types (not just VarChar, the precision also). Show us the record schema from the stream input link and the reference input link to the Lookup stage. Tell us which columns are identified as Key. Otherwise we're gue...

Probably, at least from those parts that have not been deleted as part of a partial deletion of the project.

But there's no generic answer - it has to be done by a specialist.