<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name="Microsoft Theme 2.00" content="Ice 011"><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
text-align:justify;
text-justify:inter-ideograph;
font-size:10.5pt;
font-family:SimSun;
color:#003572;}
span.EmailStyle17
{mso-style-type:personal-compose;
color:#003572;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:DengXian;}
/* Page Definitions */
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white background="cid:image001.gif@01D8D1B4.1D256CA0" lang=ZH-CN link="#1F86FF" vlink="#005DC9" style='word-wrap:break-word;text-justify-trim:punctuation'><img src="cid:image001.gif@01D8D1B4.1D256CA0" v:src="cid:image001.gif@01D8D1B4.1D256CA0" v:shapes="_x0000_Mail" width=0 height=0 class=shape style='display:none;width:0;height:0'><!--[if gte mso 9]><xml>
<v:background id="_x0000_s1025" o:bwmode="white" o:targetscreensize="1024,768">
<v:fill src="cid:image001.gif@01D8D1B4.1D256CA0" o:title="background_ice" type="frame" />
</v:background></xml><![endif]--><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-family:"Courier New";color:windowtext'>Hi all:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Courier New";color:windowtext'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Courier New";color:windowtext'>When designing restriction in job_submit.lua, I found there is no member in job_desc struct can directly be used to determine the node number finally allocated to a job. The <b>job_desc.min_nodes </b>seem to be a close answer, but it will be 0xFFFFFFFE when user not specify –node option. Then in such case we think we can use <b>job_desc.num_tasks</b> and <b>job_desc.ntasks_per_node </b>to calculate node number. But again, we find <b>ntasks_per_node</b> may also be default value 0xFFFE if user not specify related option.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-family:"Courier New";color:windowtext'>So what is the complete and elegant way to predict the job node number in job_submit.lua in all case, no matter how user write their submit options?<o:p></o:p></span></p></div></body></html>