If you will updating the varchar columns, then it might be better to move them. There are two concerns here: whether they will fit back on the same page if the data is nade larger because of an update, and the issue of logging the changes from the point of column that was changed to the end of the row.
Also, the more rows you can fit on a page at one time, usually this is best for perfomance. If the large varchar columns are in the same table with the other data, this will either reduce the number of rows per page, or require a larger page size. Larger page sizes have buffer pool implications. But it really depends on how often the large varchar columns are accessed compared to the other columns on the row. If they are always accessed together, then it may be better to leave them together on the same table.
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390