M204.2158 Global token definition doesn't match value in GTBL, token2, name hash=hexValue
The request has referred to a global Screen, Menu, or Image for the first time. The global object was located in GTBL (it was placed there by a previous request), but the definition of the object in the current request is not identical to the previous request's definition. The definitions may differ in terms of the content or in terms of the TEMP or PERM GLOBAL attribute.
- Looking for TEMP GLOBAL, found PERM GLOBAL: The current request has a TEMP GLOBAL screen/menu/image, but the object previously saved in GTBL is a PERM GLOBAL.
- Looking for PERM GLOBAL, found TEMP GLOBAL: The current request has a PERM GLOBAL screen/menu/image, but the object previously saved in GTBL is a TEMP GLOBAL.
- VALUE HASH mismatch: The hash code generated from the compiled screen/menu/image does not match the code in the identically named object previously saved in GTBL.
The probable causes are:
- The two requests have inadvertently selected the same name for two functionally different global objects.
- The definitions of the global objects are coded in the body of the request instead of in a common included procedure.
Response: Change the name of the global object to avoid the naming conflict, or else correct the definition.
System manager response: Consider establishing naming and coding conventions for global screens, menus, and images. Require that global definitions be coded in separate commonly included procedures.
|RETCODEO=0||Sets online return code|
|RETCODEB=4||Sets batch (single user) return code|
|CLASS=E||Error class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter|
|AUDITER||Writes the message with line type ER to the audit trail|
|CANCEL||Cancels the user's request|
|COUNT||Increments the error count (ERCNT) parameter|