Still awaiting an answer to "Can you guarantee that the string-to-be-replaced occurs not more than once in the field?". Arnd's answer is sufficient if the answer is "yes", but not if the answer is "no".
Examine the source code for ExecDOS. It requires that there be some output from the command. Arnd's suggestion, of adding a dir command, forces there to be some output. A hostname command or a cd command (with no command line arguments) would have done as well.
It's the same as anywhere. In what stage type are you attempting to effect this conversion? You might require Char(10) or you might be able to use the regular expression "\n" depending on what stage type you are using.
Go back to IBM and ask for other resellers. I have no idea what the UK price might be, and would be very surprised if any given two customers paid the same amount.
Don't even attempt it. It's an additional and unnecessary layer because, in the routine, you'd be invoking the appropriate operating system command (via DSExecute()). Use an Execute Command activity in a job sequence, or use a before-job subroutine, either ExecDOS or ExecDOSSilent or a clone of eith...
Look at increasing the transaction isolation level in DB2 or find some other means for guaranteeing a consistent snapshot. That done, you can maintain the hashed file in "real time" using a pair of hashed file stages plus "disabled, lock for update" as the read cache setting. The job design in the o...
Look also for opportunities to use conformed dimensions. For example, typically the same time granularity will be used regardless of data source, so that the same time dimension table can be used with all fact tables.
I would like to get feedback from everyone in this forum. Are you sure? There are over 13,000 registered. Your question really boils down to installing everything you need (it's easiest to install all plug-in stage types), making sure there's plenty of resources (CPU, memory and disk space, and mor...
At some point, when nothing else is happening, use uvbackup to take a backup of your project - the backup itself can be discarded - you are interested in the report of whether any files are corrupted in any way. This post will guide you on your way.
That's a good approach; if you understand it and can maintain it, it's probably the right approach. If you can afford to have long-running jobs, you might consider a job sequence that does what you require. Use "All" sequencers to govern what executes when. Seq1 ------> A -------> Seq4 -----> A Seq2...
We answered the question you posed. The "bunch of IDs" in ColA is a new question. It is solved by sorting the input by ColA and using stage variables to detect the changes therein and to accumulate/reset the counter (ColB). The technique has been described a number of times; search the forum for det...