MSIR.0844 Previous undefined macro variable

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=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
COUNT	Increments the error count (ERCNT) parameter
ECHO	Displays the line that caused the error

Back to list of messages