DSXchange

What is it you are viewing in "RT_BP subdirectory" (and, for that matter, which RT_BP subdirectory)? Where does the Hashed File stage specify that the hashed file is? This error would not have occurred if a job had not attempted to write a record into a hashed file for which the key value (the total...

"Someone" (you or a local administrator) tightened up the permissions. More than that I can not say from here.

You don't need to specify lengths when importing the table definition for a delimited file. Only for a fixed-width-format delimited file. Indeed, the field for doing so should be disabled when the file type is specifed as not fixed-width.

Change your requirement (at least that part of it that prescribes updating the same table from which you are reading). You risk causing a self-deadlock situation.

Use two jobs, staging the data in a Data Set.

lsnovick, can you please set up just this expression in a Routine, and test it with the Test button, and post the actual result (double click on the Result cell)?

Pre-process the file so that each line has 256 ";" characters. You could even do this in DataStage; read the line as a single VarChar field, add the appropriate number of semi-colons InField : Str(";",256-Count(InField,";")) then re-parse using Column Import stage.

That's all correct. 00:00:05 is five minutes. You need a Failure trigger on the WaitForFile activity. StartLoop ---> WaitForFile ---------> EndLoop | Failure | Success | | | | V V JobActivity -------------> Sequencer ---> AnythingElse

You're not on version 5.x

A loop with six iterations including a WaitForFile activity with a ten minute wait.

Same approach as I outlined earlier. Split into (MAX) columns, filling with in-band nulls, pivot, then filter out un-needed rows.

You're using a fixed-width dat file - these positions have to be filled with something. What value do you have for APT_STRING_PADCHAR ?

Or even hardware support - have them check whether any of your memory chips has developed a fault.

You will get an error. In parallel Transformer stage arithmetic operators apply only to arithmetic operands. Data types are strictly enforced. (If you are using a BASIC Transformer stage, data types are not enforced so, if the data in each string is numeric, then arithmetic will succeed and, if the ...

How was this resolved?

What do you receive on the valid data link? And is any warning logged?