DSXchange

I'm still stuck with this situation where a log in Director for a server job is incomplete. (And I'm looking at this because the job just hung until we re-booted the server). Having found the RT_LOG for the job in question I saw there were 4 iterations of messages in it, but the job is only supposed...

The RT_LOG for this job shows 4 copies of the same sequence of severity / events and text, so it shows the same job as having started and finished 4 times. They are copies except that the order in which the transforms are done is different each time. Needless to say, by design the job is meant to be...

Oh, OK. No, there is nothing, the process doesn't finish, there's no terminal Control entry, no error. It just hung and the developer couldn't reset or re-compile because of a locked process, so killed the 'service' which availed naught, then had the server re-booted, then compiled the job again, an...

Thanks, yes. The job number for the server job changed after the problem was resolved, presumably because it was re-compiled, so I've grep'd both job numbers. I've got a match for some (with the date and time for the job from Director), but others that are shown in the Director log, that I've derive...

Trying to locate DSD.RUN files in 1st step to track down why job just cut-off entailing a reboot of the server. Director auto-purged log shows 5 entries, spanning the date when the problem occurred. I used a routine found here to derive the likely file names for all 5. Found 3 but the others don't a...

An update:

Finally tracked down source of warnings to a stage variable expression which used an input column with null values in some rows. All the hash lookup stuff was a red herring.

Issue resolved, thanks.

Cheers

Many thanks. Probably too much coffee here !

chulett wrote:No, that would be a perfectly fine solution. And sorry for the brain fart, forgot the null lookup would generate the same error. Too early here, not enough coffee.

ps. I'd document this in an annotation on the canvas.

Many thanks.

chulett wrote:No, that would be a perfectly fine solution. And sorry for the brain fart, forgot the null lookup would generate the same error. Too early here, not enough coffee.

ps. I'd document this in an annotation on the canvas.

Thanks The source is "N", and the target is "N"", for one row, mid file. Bizarre ?! What next ? Is "N"" value represented that way in your source or the target. If the former, then you don't have a well-formed input file and cannot process it correctly in CSV ...

Thanks. The difference is in the constraint - one has duplicates and the other doesn't. The duplicates are identified by using stage variables to compare the record key of the previous row, and if different to set a value as "NoDupe" or "Dupe". The rows with "NoDupe" ar...

It shows (in Textpad - it's a csv file) as: "N"" when it should be "N" All other values output for this column are "N" The double quote character is specified on the input file and output files. They all have DOS-style line termination (it's the terminal column tha...

OK, thanks. So I've tried this - in the key expression field for the hash file I've done a test e.g: if Not(IsNull(slk_input_file_dara.locode)) then trim(slk_input_file_dara.locode) else 99998 so that a dummy value is used as the key value if it would otherwise be missing. Then in the transform I te...

Hi Please excuse - the error in its entirety in the Director log is, unfortunately, as posted. Presumably there's some other way of detailing the error then ? :oops: And there are no writes to the hash file; it's just used as a lookup. Well... that *is* the most likely cause, writing a null key to a...

The DS job runs successfully, with no warnings to the log, but when I view one of the output (csv) files in DS I get mrg_all_chips_set_1..noDupes_tmds_spi_file.olk_tmdsspi_noDupes_pif_file: read_delimited() - invalid quotes, row 14874 column rfaind = "N"". Sure enough in the output cs...

Hi I get a gazillion warnings in Director log - <Missing or NULL> (<Missing or NULL>): <Missing or NULL> - which I'd like to get rid of so that I can run with 50 warnings limit. The job has several standard transforms looking up values on a hash file to return another code. There don't appear to be ...