MSIR.0844 Previous undefined macro variable

From m204wiki
Revision as of 18:31, 12 July 2016 by JALWiccan (talk | contribs) (Automatically generated page update)
Jump to navigation Jump to search

When the first macro statement was encountered in a request, a possible macro variable (something that begins with ?!) had already been bypassed. For backward compatibility with existing applications, a ?! is assumed not to be a macro variable if no macro statements are encountered. Encountering a macro statement after such a variable has been bypassed suggests that assumption might have been incorrect.

If, indeed, the ?! was simply meant as a literal, it must be changed if macro statements are to be used. If the ?! appears in a comment, it can simply be removed. Otherwise, such a literal must be "disguised," perhaps by breaking it up into two strings that are concatenated using the With operator.


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
COUNTIncrements the error count (ERCNT) parameter
ECHODisplays the line that caused the error

Back to list of messages