DSXchange

Does your logic mean that once a date check fails in the transform, no more rows are to be output? In that case, use a stage variable such as "svFini" with a default of false, setting it to true once the check fails and using "Not(svFini)" as your constraint.

The key point is that DataStage has an auto-purging option, which you probably have turned on; and that was visible in the non-premium portion of the post.

Where exactly are you doing your date check in the job? Is it part of the pre-job processing or in a transform stage? Normally one can find a way to make a transform stage constraint just not output anything, and thereby ending the job without outputting anything.

Does This URL help you any further?

Most likely you have project-level and/or job-level purging enabled to only keep the last 10 runs. Your first log entry will be an informational one with "auto-purge" somewhere in the text (I'm not at a DS client right now to get the exact syntax). You can override this at the job level in...

use the man pages for "tail"; the command I sent skips the first line.

That link states that the buffer size can be increased

...increase the buffer size (up to to 1024K)...

What stages (name and type) are at the left and right ends of "DSLink206"? There seems to be a runtime problem with the interprocess communication here. Also, if you do a "reset" of the aborted job in the director you will get a log entry "from previous run.." and pleas...

If the first line is DD2009 and you wish to ignore it, then skip the first line. The CFF stage doesn't directly let you skip n-lines, but just use the "Filter" option with "tail -n +2"

Thanks for that, Ray. I thought to remember that UUENCODE was used somewhere in the dsx export, perhaps when exporting the binary executables. But I just checked an export file and see that the binaries (at V8) are stored as hex clear texts after all.

Is "ACCOUNT_NO" the first column in the file? The data shown, {c4 c4 f2 f0 f0 f9 ` f1}, is EBCDIC for "DD2009" for the first 6 characters and that does not equate to what a COMP-3 numeric should look like. The "2009" could be part of a PIC x or PIC 9 date field, though.

Your question is impossible to answer using the information given; it is like expecting someone to diagnose a car problem by saying "I hear a strange noise sometimes". Please add some more details to your query: the full error message for a start, what stage is causing the error, if it is ...

DataStage hashed files can only have one physical key. When using composite keys, DataStage just concatenates the components together to form the "real" key. Thus, when you use the UtilityHashLookup() routine you have to put the key components together in order for it to work; i.e. doing K...

Just as some of the old mail systems only process 7 bit data, DataStage allows you to create a .dsx file which can be transmitted through such systems. If I recall correctly it uses the same uuencoding algorithm as does sendmail to ensure that all characters can be represented in 7 bits.

Is this 8.1 - in which case you can redirect the log repository and have you done so?
It sounds like this applies to all jobs - can you tell whether or not the jobs have completed correctly, through looking at output tables or files?