On the shared filesystem, executables are staged to the workflow specific directory. Separate chmod jobs are added to the workflow that set the x bit on the staged executables.
In case of the shared filesystem setup the staging site is always same as the execution site.

For 3.2, because of the FHS work and the new executables ( pegasus-create-dir ) that the planner normally schedules on the local site, the chmod jobs will now refer to the /bin/chmod instead of relying on pegasus-dirmanager to set the Xbit.

Additionally, these chmod jobs will not be added to the workflow if PegasusLite is enabled, as the xbit is set in the wrapper shell scripts.

The path /bin/chmod may be over-ridden by specifying the
system::chmod transformation in the transformation catalog for a site.