M204.2460

From m204wiki
Revision as of 03:46, 14 March 2018 by DmeWiccan (talk | contribs) (Automatically generated page update)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

M204.2460  Global token context does not match global definition

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, foundset, or sortset. If a procedure creates a global object in one file and then resets it to another file, Print and PAI statements attempt to use the field codes from the first file to access the second.

All For loops must be compiled to a specific file context. Changing the file context of a global object makes any For loop that references the global object invalid.

Model 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 compile time, because 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.

Response: Verify that the file context is the same for all requests that use a global list, foundset, or sortset.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
CANCELCancels the user's request
COUNTIncrements the error count (ERCNT) parameter

Back to list of messages