Pegasus while staging out data to an output site , picks up the file server for the output site scratch file system instead of the storage filesystem from XML3 version of the site catalog.

For e.g. the user wants to stage data to local site
and hte entry in the site catalog is as follows for local site

<site handle="local" arch="x86" os="LINUX">
<head-fs>
<scratch>
<shared>
<file-server protocol="gsiftp" url="gsiftp://localhost-scratch-shared/" mount-point="/home/rynge/pegasus" />
<internal-mount-point mount-point="/home/rynge/pegasus" free-size="100G" total-size="30G"/>
</shared>
</scratch>
<storage>
<shared>
<file-server protocol="gsiftp" url="gsiftp://localhost-storage-shared" mount-point="/home/rynge/pegasus" />
<internal-mount-point mount-point="/home/rynge/pegasus" free-size="100G" total-size="30G"/>
</shared>
</storage>
</head-fs>
<replica-catalog type="RLS" url="rls://replica.isi.edu">
<alias name="local"/>
</replica-catalog>
<profile namespace="env" key="GLOBUS_LOCATION" >/opt/osg/current/globus</profile>
<profile namespace="env" key="LD_LIBRARY_PATH" >/opt/osg/current/globus/lib</profile>
<profile namespace="env" key="PEGASUS_HOME" >/opt/pegasus/2.4.1</profile>
</site>

the stageout job will have destination urls referring to gsiftp://localhost-scratch-shared/ instead of gsiftp://localhost-storage-shared/