This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English verison of the page.

Note: This page has been translated by MathWorks. Please click here
To view all translated materals including this page, select Japan from the country navigator on the bottom of this page.


Set specific user data for job on generic cluster





Cluster object identifying the generic third-party cluster running the job


Job object identifying the job for which to store data


Information to store for this job


setJobClusterData(cluster,job,userdata) stores data for the job job that is running on the generic cluster cluster. You can later retrieve the information with the function getJobClusterData. For example, it might be useful to store the third-party scheduler’s external ID for this job, so that the function specified in GetJobStateFcn can later query the scheduler about the state of the job. Or the stored data might be an array with the scheduler’s ID for each task in the job.

You should call the function setJobClusterData in the submit function (identified by the IndependentSubmitFcn or CommunicatingSubmitFcn property) and call getJobClusterData in any of the functions identified by the properties GetJobStateFcn, DeleteJobFcn, DeleteTaskFcn, CancelJobFcn, or CancelTaskFcn.

For more information and examples on using these functions and properties, see Manage Jobs with Generic Scheduler.

Introduced in R2012a

Was this topic helpful?