User`s guide

Troubleshooting and Debugging
6-53
Error using ==> feval
Undefined command/function 'function_name'.
The worker that ran the task did not have access to the function function_name. One
solution is to make sure the location of the function’s file, function_name.m, is included
in the job’s AdditionalPaths property. Another solution is to transfer the function file
to the worker by adding function_name.m to the AttachedFiles property of the job.
Load and Save Errors
If a worker cannot save or load a file, you might see the error messages
??? Error using ==> save
Unable to write file myfile.mat: permission denied.
??? Error using ==> load
Unable to read file myfile.mat: No such file or directory.
In determining the cause of this error, consider the following questions:
• What is the worker’s current folder?
• Can the worker find the file or folder?
• What user is the worker running as?
• Does the worker have permission to read or write the file in question?
Tasks or Jobs Remain in Queued State
A job or task might get stuck in the queued state. To investigate the cause of this
problem, look for the scheduler’s logs:
• Platform LSF schedulers might send emails with error messages.
•
Microsoft Windows HPC Server (including CCS), LSF
®
, PBS Pro, and TORQUE save
output messages in a debug log. See the getDebugLog reference page.
• If using a generic scheduler, make sure the submit function redirects error messages
to a log file.
Possible causes of the problem are:
• The MATLAB worker failed to start due to licensing errors, the executable is not on
the default path on the worker machine, or is not installed in the location where the
scheduler expected it to be.