https://m204wiki.rocketsoftware.com/index.php?action=history&feed=atom&title=M204.2460M204.2460 - Revision history2026-04-12T03:58:03ZRevision history for this page on the wikiMediaWiki 1.43.1https://m204wiki.rocketsoftware.com/index.php?title=M204.2460&diff=113126&oldid=prevDmeWiccan: Automatically generated page update2018-03-14T03:46:34Z<p>Automatically generated page update</p>
<p><b>New page</b></p><div>{{Template:M204.2460 skeleton}}<br />
<br />
<P><br />
A global list, foundset, or sortset in this request has a different file context than what was specified in the request that first defined the global object. It is invalid to change the file context of a global list,<br />
foundset, or sortset. If a procedure creates a global object in one file and then resets it to another file, <var>Print</var> and <var>PAI</var> statements attempt to use the field codes from the first file to access the second.</P><br />
<P><br />
All <var>For</var> loops must be compiled to a specific file context. Changing the file context of a global object makes any <var>For</var> loop that references the global object invalid.</P><br />
<P><br />
Model&nbsp;204 detects at evaluation time that the file context in the global does not match the compiled file context, then issues an appropriate error message and restarts the user softly. This error cannot be handled at<br />
compile time, because [[Application Subsystem development|APSY subsystems]] could have procedure1 in file 1 and procedure2 in file 2, and could have both procedures transfer to procedure3 with the same global list, sortset, or foundset.</P><br />
<p><br />
<b>Response:</b> Verify that the file context is the same for all requests that use a global list, foundset, or sortset.</p><br />
{{Template:M204.2460 footer}}<br />
<!-- skeleton as it was in pdf/GLOBAL lstfdset FILE CONTEXT DOES NOT MATCH GLOBAL DEFINITION/--></div>DmeWiccan