By default, survey data is saved in a different file than reaction time data because the kinds of analyses done on these types of data are typically very different.
With surveys, it's usually much more convenient to have 1 row of data per subject, with responses from each survey item in a separate column.
With reaction time data, you are typically computing metrics such as means, medians, Cohen's D, d prime, etc. based on very large sets of trials grouped by various treatment conditions. You may often want to discard particular trials with excessively high or low latencies. These kinds of analyses would be extremely cumbersome (dare I say impossible) if all of the data from each trials (response, latency, treatment conditions) were somehow put into a single enormous row for each subject.
You can record your survey data in the same file as your reaction time data, however. Each <surveypage> is a specialized kind of <trial>, so you can insert survey pages in your /trials list of your <block> elements. When a surveypage is run as a trial in a <block> (as opposed to a page in a <survey>), its data are recorded in the the main data file (i.e., IAT.dat in your case), with each survey item appearing as a separate row.
If you want separate files, and you are recycling the same subject numbers across different subjects, then you'll need to rely on some additional cues to correlate the two data files. Specifically, you should be able to match up most of the files using the subject number, date, and time columns. In the event those values are the same for multiple participants, you could disambiguate them using the ip address, which is saved in the name of the data file.
-Sean