Copy stage

The copy stage is virtually a virtual stage (could not pass the pun 😉), i. e. at compile time it gets eliminated and its functionality integrated into the preceding stage element. There are actually two purposes to the copy stage:
  1. Forking the data stream into several streams. This could be achieved by using multiple output links in other stages. However, e. g. for the transformer one possibly would need to multiply code to get the effect in several outputs.
  2. Change the character of jobs optically.

Kommentare

Kommentar veröffentlichen

Beliebte Posts aus diesem Blog

Error when checking operator: Could not find input field 'field_name'

Well, you checked and double-checked the existence of respective field and it is there! Yeah, stumbled over it again. And again! Possible solutions You need to compile jobs explicitly. You're done then. Try it. Go! What are you waiting for? If you are really extra sure compiled the job, then double-check the presence of the respective field again, but not in the stage DS tells you but in the very source at the start of the dataflow where this field comes from. It happens that if the column name of your SQL is not identical to the field name propagated. I do absolutely not know why: compilation does not reveal the problem DataStage misses the correct problem location by far
Mehr anzeigen

Missing record delimiter "\n", saw EOF instead

Actually, this warning is quite simple to fix. Apparently, DS expects the last record of a file to terminate with the record delimiter in any case - maybe there is a setting to alter this behaviour but I did not deem worthwhile the effort to look for it. So the solution is just to terminate the file on a single empty line. Obviously, this case is for Unix like line breaks. The others delimiters are handled analogously.
Mehr anzeigen