This is nothing to do with batch, and everything to do with workspace transparency. Basically when a parfor loop exists inside a function, it treats any names it sees that are not definitively variables as if they are functions. In other words, the problem is that the function itself does not contain any statements that assign to pth directly.
You could fix this either by converting Paths to be a function returning values as output arguments, or you could push the parfor loop into a function which has specific input arguments which the parfor analysis can understand, like this:
function batchfun(jm)
run('Paths.m') %This creates 'pth' using 'jm'
callParfor(alld, jm, pth)
end
function callParfor(alld, jm, pth)
% All variables accessed here are input arguments to this function, and
% so parfor will understand correctly that they are variables.
parfor vh = 1:length(alld)
parfun01(vh,jm,pth)
end
end
parfor when running in a script (or at the MATLAB command-line) has different behaviour that is less efficient but can see what variables actually exist immediately prior to running the loop.
