When JAMS runs a JD Edwards Job, it looks at the Processing Options to see if the ID matches the name of a JAMS Parameter in the Job Definition. If a match is found, JAMS replaces the Value of that Member with the Value of the JAMS Parameter.
If it is unclear what the ID names for the Processing Options are, Submit the JAMS Job using PowerShell and add the -RunDebug switch to the Submit-JAMSEntry cmdlet. That will tell JAMS to leave behind the XML files that are generated by RunUBEXml. From there, look at the <PROCESSING_OPTIONS> and see what the ID of each <MEMBER> is.
It is also possible to get those XML files by running RunUBEXml manually if a user is familiar with doing that.
Here is a portion of an XML file used by RunUBEXml to launch a Job. It shows the Processing Options and Members. It includes the Members that JAMS matches up with Parameters.
<PROCESSING_OPTIONS_TEMPLATE_NAME VALUE="T10111B" />
<MEMBER ID="mnPeriodNoGeneralLedge" NAME="Period Number" VALUE="0" />
<MEMBER ID="szFiscalYear9" NAME="Fiscal Year" VALUE="" />
<MEMBER ID="cActLevelOfDetailEnd" NAME="Account Level Of Detail " VALUE="7" />
<MEMBER ID="mnFinancialReportingReverseSign" NAME=" Reverse Sign" VALUE="0" />
<MEMBER ID="cCalculateYTDNetIncome" NAME="Calculate YTD Net Income" VALUE="1" />
<MEMBER ID="cPrintHeadings" NAME="Print Headings" VALUE="1" />
<MEMBER ID="cDateTitleType9" NAME="Date Title Type" VALUE="B" />