Hi Wu,

As the name itselff suggests, job_desc_msg_t structure is used to communicate 
the data about job between different components of slurm. job_record_t is the 
one that is used by slurm to store the data about a job locally. I hope this 
explanation helps.

It depends, if updating one effects the values of the other, upon when the 
changes are made. If a job_rec_t is being created from update job_desc_msg_t 
instance then of course its values will be new ones and vice versa.


Best regards.

--------------------
Zia Ul Huda
Forschungszentrum Jülich GmbH
Institute for Advanced Simulation (IAS)
Jülich Supercomputing Centre (JSC)
Wilhelm-Johnen-Straße
52425 Jülich, Germany

Phone: +49 2461 61 96905
E-mail:  z.h...@fz-juelich.de<mailto:z.h...@fz-juelich.de>

WWW: http://www.fz-juelich.de/ias/jsc/


JSC is the coordinator of the
John von Neumann Institute for Computing
and member of the
Gauss Centre for Supercomputing

--------------------

On 17. Nov 2020, at 05:39, Kaiyue Wu 
<kaiyu...@sjtu.edu.cn<mailto:kaiyu...@sjtu.edu.cn>> wrote:

Hello,

We see there are two job data structures job_desc_msg_t and job_record_t, and 
are wondering the relation between them. What is each of them used for or how 
are them used? If we update the value of one of the entries in job_desc_msg_t, 
will the corresponding value change in job_record_t?

Thank you and look forward to your reply.

Best wishes,
Kaiyue Wu




------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Volker Rieke
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Reply via email to