DSXchange

Copy stage.

Note, however, that Peek will not "fill up your log" - it will capture only the sample you specify (by default 10 rows per node).

You've asked the stage to keep (perhaps by failing to ask the stage to drop) these two fields, but have not provided these fields on the output link of the stage. The solution is obvious.

There is no single ideal setup. But, if there were, it would not have disk and scratchdisk resource specified in the default locations; it would have these spread over as many disks as possible and those disks would have plenty of free space.

You must have the conductor node mentioned at least once, and it must really be in the default node pool ("") too.

What Craig suggested is done in the grid on the Columns tab.

It requires that the strings containing the newline characters are quoted.

or

Let's wait to see how fmou fares...

You may be able to hack it (by changing the Tool Version field) in this case, but nothing is guaranteed.

You can not use activity variables as values for parameters, whether they're in parameter sets or not. You need to provide the activity variable reference when setting the value of a parameter, for example within the Job tab of a Job activity or via a -param option on a dsjob command line.

Here's how I would go about it. Search DSXchange for code for OpenSequentialFile, which handles all file opening problems. Some error handling has been omitted for clarity. FUNCTION ReadPartOfFile(aStartPosition, aEndPosition) DEFFUN OpenSequentialFile(FilePath, OpenMode, WriteMode, LogMode) Calling...

The convention here at DSXchange is that, when you resolve a problem, you mark it as resolved AND make a post indicating how it was resolved.

You have done the former but not yet the latter.

Yes. In fact most sites use host names rather than IP addresses in .odbc.ini.

No, because there is no Type2 change to warrant creating a new record.

For ODBC you can have project-based uvodbc.config files. For other database connectivity use project-based environment variables (for example DB2INSTANCE or ORACLE_HOME).