DSXchange

Every example could be real time.

One of my favourites receives an error code, decodes it, enriches that with the job name, start time, user ID and various other things, and writes the lot into a standard error table.

It's clear that I don't understand your logic - my guess was off the mark. Please write out a specification in English of what is supposed to happen - don't mention DataStage, hashed files or anything else in the specification. For now I will ignore the question about the hashed file. Have you ever ...

Fine. Then, provided your source file is correctly named in the Investigate stage, and exists in the Data folder for your project, all should be well. Note that you require write permission to the Data folder so that the stage outputs can be written there.

Maybe it's objecting to CRLF because you're on a UNIX platform and CRLF is not the line terminator. Most XML parsers would still recognize and be able to ignore CRLF, but the one you get with the XML stages has manifested other weird behaviours in the past, so who knows? Can you try pre-processing t...

Sequencers don't have instances. I will assume, therefore, that you mean "job sequences". A job sequences is just a regular job, therefore dsjob with the -jobinfo option, executed before a run request is issued, will return the previous status.

What is your "master project directory" set to? This is a folder on the server, which contains one folder for each project. Within each project folder there exist Data and several other folders. It is in this Data folder that QualityStage stages expect to find files.

The flat file format for an Investigate stage needs to be exactly as described in the data file definition you have set up in QualityStage, and in particular must be in fixed-width format. (There are other stage types that can read delimited format and produce fixed-width format.)

So which disk filled? Looks like you need to monitor all file systems.

You can do it from the same sequential file, but not from the same Sequential File stage - you will need two Sequential File stages (one on the stream input the other on the reference input to the Lookup stage) each referring to the same file.

If you convert the data type with a Modify stage you don't need SQL and can use Write write mode.

There's nothing in dsenv.

There is another thread open on this question - see if reading that helps your diagnosis.

What is the value of USER environment variable in the second log event (environment variables) for the job?

Does it run if you are not simultaneously viewing data on the source?

DateStage (UniVerse) uses a pattern matching regime that is neither SQL wildcards nor regular expressions. It includes the ability to match character type (alphabetic, numeric, "don't care"). Either "0X" or "..." in a match pattern matches "any characters". Therefore another solution is Input.Code M...

What are the values (from the "job starting" log message) for the job parameters jpFilePath, jpProject and jpSequence ?