DSXchange

Were there any messages in your log indicating that there was a lock held so that BUILD.INDEX could not proceed? That means that you did not have exclusive access to the project. Issue the following command and let us know the outcome. SELECT COUNT(*) FROM DS_JOBS WHERE NAME NOT LIKE '\\%'; ...

The warnings are also buffered. So there may be 10,000 warnings buffered by the time your stop request is received. These will continue to be logged but, don't worry, once they're all in it will stop.

Welcome aboard. :D

MetaStage is capable of generating this kind of report. The process metadata (row counts, etc.) are captured automatically when the job runs and can then be transferred into the MetaStage directory automatically or manually, as you prefer.

A Complex Flat File stage has the inherent capacity to handle most mainframe data types, whether display or computational, including signed and unsigned, zoned, packed, etc.

Make your output column string[10]. As well as a space for the decimal place character you also need a space for the sign.

Compare stage only compares columns identified as Key. Also, you will need a column called diff on the output, to receive the result. The output from a Compare stage consists of three columns, diff, the first input link record as a subrecord, and the other input link record as a subrecord. The Compa...

dsapi.h is in the $DSHOME/dsdk/include directory

A pat on the back always encourages learning.

Particularly if it's low enough and hard enough.

And were these resolved?!!

Somewhere, somehow, it appears to have lost the extract type - showing blank after the "extract type:" in your error message. I think you're going to need to involve IBM support on this one - maybe running the job in debug mode under their guidance will reveal more.

Welcome aboard. :D Mprob is a probability figure; it should be a single number in the range 0 through 1. Yours seems to have a comma (about which the initial complaint seems to be being generated) and a second number. Where are you entering this? Perhaps you didn't successfully erase what was alread...

Use the File Name Column and Row Number Column properties of the Sequential File stage when using multiple File properties or File Pattern - it becomes even easier to drop rows where the row number is 1 or 2.

If it's in a job sequence you can use the system variable @LOGNAME in an expression, or use an Execute Command activity to retrieve the value of the environment variable that contains your user ID. Since you're in the parallel forum, I'm guessing you are on 7.5x2, and can therefore retrieve it from ...

It usually means that the database has rejected those records, perhaps because some constraint has been violated. In the Transformer stage immediately prior to the ODBC stage add an additional output link and mark it able to handle rejects. Create three columns there (all VarChar). SQLState - VarCha...

Have either of you searched the forum for error code -14?