MSIR.0584 Invalid expression: Difference between revisions
Jump to navigation
Jump to search
(Created page with "An expression that did not end correctly was specified in an HTML or TEXT block. Most likely, this is a case of the expression start character occurring in an HTML or TEXT block ...") |
(Automatically generated page update) |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
An expression that did not end correctly was specified in an HTML or TEXT block. Most likely, this is a case of the expression start character occurring in an HTML or TEXT block for something other than an expression, or the expression end characters being mis-typed or left off by mistake. The former case is most likely to happen with the default expression start of "{" when the HTML or TEXT block contains code from a programming language such as JavaScript. I such a case, either specify NOEXPR on the HTML/TEXT statement or specify a different expression start character using the EXPRSTART parameter. | An expression that did not end correctly was specified in an HTML or TEXT block. Most likely, this is a case of the expression start character occurring in an HTML or TEXT block for something other than an expression, or the expression end characters being mis-typed or left off by mistake. The former case is most likely to happen with the default expression start of "{" when the HTML or TEXT block contains code from a programming language such as JavaScript. I such a case, either specify NOEXPR on the HTML/TEXT statement or specify a different expression start character using the EXPRSTART parameter. | ||
[[Category: | {{Template:MSIR.0584 footer}} | ||
[[Category:MSIR.0400 - MSIR.0599]] |
Latest revision as of 23:13, 3 March 2017
An expression that did not end correctly was specified in an HTML or TEXT block. Most likely, this is a case of the expression start character occurring in an HTML or TEXT block for something other than an expression, or the expression end characters being mis-typed or left off by mistake. The former case is most likely to happen with the default expression start of "{" when the HTML or TEXT block contains code from a programming language such as JavaScript. I such a case, either specify NOEXPR on the HTML/TEXT statement or specify a different expression start character using the EXPRSTART parameter.
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 |