User`s guide

6 Programming Overview
6-54
• MATLAB could not read/write the job input/output files in the scheduler’s job storage
location. The storage location might not be accessible to all the worker nodes, or the
user that MATLAB runs as does not have permission to read/write the job files.
• If using a generic scheduler:
• The environment variable MDCE_DECODE_FUNCTION was not defined before the
MATLAB worker started.
• The decode function was not on the worker’s path.
No Results or Failed Job
Task Errors
If your job returned no results (i.e., fetchOutputs(job) returns an empty cell array), it
is probable that the job failed and some of its tasks have their Error properties set.
You can use the following code to identify tasks with error messages:
errmsgs = get(yourjob.Tasks, {'ErrorMessage'});
nonempty = ~cellfun(@isempty, errmsgs);
celldisp(errmsgs(nonempty));
This code displays the nonempty error messages of the tasks found in the job object
yourjob.
Debug Logs
If you are using a supported third-party scheduler, you can use the getDebugLog
function to read the debug log from the scheduler for a particular job or task.
For example, find the failed job on your LSF scheduler, and read its debug log:
c = parcluster('my_lsf_profile')
failedjob = findJob(c, 'State', 'failed');
message = getDebugLog(c, failedjob(1))
Connection Problems Between the Client and MJS
For testing connectivity between the client machine and the machines of your compute
cluster, you can use Admin Center. For more information about Admin Center, including