HLASM Language Reference
HLASM Language Reference HLASM Language Reference
MNOTE Instruction When two literals specifying identical A-type, Y-type or S-type address constants contain a reference to the value of the location counter (*), both literals are assembled into the literal pool. This is because the value of the location counter may be different in the two literals. Even if the location counter value is the same for both, they are still both assembled into the literal pool. The following examples show how the assembler stores pairs of literals, if the placement of each pair is controlled by the same LTORG statement. =X'F' Both are =C'' stored =XL3'' =HL3'' =A(+4) =A(+4) =X'FFFF' =X'FFFF' Both are stored Both are stored Identical, only one copy is stored MNOTE Instruction The MNOTE instruction generates your own error messages or displays intermediate values of variable symbols computed during conditional assembly. The MNOTE instruction can be used inside macro definitions or in open code, and its operation code can be created by substitution. The MNOTE instruction causes the generation of a message that is given a statement number in the printed listing. ►►──┬─────────────────┬──MNOTE───┬───────────┬─message─────────────►◄ └─sequence_symbol─ ┘ ├ ─severity,─┤ ├─,────────┤ └─,─────────┘ sequence_symbol is a sequence symbol. severity is a severity code. The severity operand may be any absolute expression allowed in the operand field of a SETA instruction. The term must have a value in the range 0 through 255. The severity code is used to determine the return code issued by the assembler when it returns control to the operating system. The severity may also change the value of the system variable symbols &SYSM_HSEV and &SYSM_SEV (see “&SYSM_HSEV System Variable Symbol” on page 279 and “&SYSM_SEV System Variable Symbol” on page 280). message is the message text. It may be any combination of characters enclosed in single quotation marks. The rules that apply to this character string are as follows: 196 HLASM V1R5 Language Reference
MNOTE Instruction Variable symbols are allowed. The single quotation marks that enclose the message can be generated from variable symbols. Two ampersands and two single quotation marks are needed to generate an ampersand or a single quotation mark, respectively. If variable symbols have ampersands or single quotation marks as values, the values must be coded as two ampersands or two single quotation marks. If the number of characters in the character string plus the rest of the MNOTE operand exceeds 1024 bytes the assembler issues diagnostic message | Note: The maximum length of the second operand is three less than the | maximum supported length of SETC character string. ASMA62E Illegal operand format The notation can be used as a continuation. Here is an example taken from a CICS® macro: MNOTE 8,'FIELD IS DEFINED OUTSIDE OF THE SIZE OPERAND' MNOTE ,'PARAMETERS SPECIFIED IN THE DFHMDI MACRO,' MNOTE ,'MACRO REQUEST IS IGNORED.' A further advantage of this approach is that only one severity 8 error is seen instead of three. Double-byte data is permissible in the operand field when the DBCS assembler option is specified. The double-byte data must be valid. The DBCS ampersand and apostrophe are not recognized as delimiters. A double-byte character that contains the value of an EBCDIC ampersand or apostrophe in either byte is not recognized as a delimiter when enclosed by SO and SI. Remarks: Any remarks for the MNOTE instruction statement must be separated by one or more spaces from the single quotation mark that ends the message. If severity is provided, or severity is omitted but the comma separating it from message is present, the message is treated as an error message; otherwise the message is treated as comments. The rules for specifying the contents of severity are: The severity code can be specified as any arithmetic expression allowed in the operand field of a SETA instruction. The expression must have a value in the range 0 through 255. Example: MNOTE 2,'ERROR IN SYNTAX' The generated result is: 2,ERROR IN SYNTAX If the severity code is omitted, but the comma separating it from the message is present, the assembler assigns a default value of 1 as the severity code. Example: MNOTE ,'ERROR, SEV 1' The generated result is: Chapter 5. Assembler Instruction Statements 197
- Page 166 and 167: DC Instruction—Graphic Constant r
- Page 168 and 169: DC Instruction—Fixed-Point Consta
- Page 170 and 171: DC Instruction—Fixed-Point Consta
- Page 172 and 173: DC Instruction—Decimal Constants
- Page 174 and 175: DC Instruction—Address Constants
- Page 176 and 177: DC Instruction—Address Constants
- Page 178 and 179: DC Instruction—Offset Constant re
- Page 180 and 181: DC Instruction—Length Constant Le
- Page 182 and 183: DC Instruction—Hexadecimal Floati
- Page 184 and 185: DC Instruction—Hexadecimal Floati
- Page 186 and 187: DC Instruction—Hexadecimal Floati
- Page 188 and 189: DC Instruction—Binary Floating-Po
- Page 190 and 191: DC Instruction—Binary Floating-Po
- Page 192 and 193: DROP Instruction DROP Instruction T
- Page 194 and 195: DS Instruction USING DSECTA,14 ALBL
- Page 196 and 197: DS Instruction The size of a storag
- Page 198 and 199: DSECT Instruction DSECT Instruction
- Page 200 and 201: DXD Instruction ASEMBLY2 CSECT USIN
- Page 202 and 203: END Instruction change but no addit
- Page 204 and 205: EQU Instruction EQU Instruction The
- Page 206 and 207: EQU Instruction 5. The length attri
- Page 208 and 209: EXITCTL Instruction sequence_symbol
- Page 210 and 211: ISEQ Instruction must be greater th
- Page 212 and 213: LOCTR Instruction A CSECT , See not
- Page 214 and 215: LTORG Instruction If symbol is an o
- Page 218 and 219: OPSYN Instruction ,ERROR, SEV 1 An
- Page 220 and 221: ORG Instruction AFTER is defined in
- Page 222 and 223: ORG Instruction If you specify mult
- Page 224 and 225: POP Instruction POP Instruction The
- Page 226 and 227: PRINT Instruction Note: If the next
- Page 228 and 229: Process Statement Process Statement
- Page 230 and 231: REPRO Instruction NOPRINT instructs
- Page 232 and 233: RSECT Instruction 4. AMODE or RMODE
- Page 234 and 235: START Instruction START Instruction
- Page 236 and 237: TITLE Instruction The name value is
- Page 238 and 239: USING Instruction Only the characte
- Page 240 and 241: USING Instruction Base Registers fo
- Page 242 and 243: USING Instruction If register 0 is
- Page 244 and 245: USING Instruction A variable symbo
- Page 246 and 247: USING Instruction In this MVC instr
- Page 248 and 249: USING Instruction Range of a Depend
- Page 250 and 251: XATTR Instruction external_symbol i
- Page 252 and 253: XATTR Instruction SCOPE ►►─
- Page 254 and 255: XATTR Instruction 234 HLASM V1R5 La
- Page 256 and 257: Part 3. Macro Language &SYSDATC Sys
- Page 258 and 259: Introduction to Macro Language Chap
- Page 260 and 261: Introduction to Macro Language The
- Page 262 and 263: Introduction to Macro Language Macr
- Page 264 and 265: MACRO and MEND Statements The assem
MNOTE Instruction<br />
Variable symbols are allowed. The single quotation marks that enclose the<br />
message can be generated from variable symbols.<br />
Two ampersands and two single quotation marks are needed to generate<br />
an ampersand or a single quotation mark, respectively. If variable symbols<br />
have ampersands or single quotation marks as values, the values must be<br />
coded as two ampersands or two single quotation marks.<br />
If the number of characters in the character string plus the rest of the<br />
MNOTE operand exceeds 1024 bytes the assembler issues diagnostic<br />
message<br />
| Note: The maximum length of the second operand is three less than the<br />
| maximum supported length of SETC character string.<br />
ASMA62E Illegal operand format<br />
The notation can be used as a continuation.<br />
Here is an example taken from a CICS® macro:<br />
MNOTE 8,'FIELD IS DEFINED OUTSIDE OF THE SIZE OPERAND'<br />
MNOTE ,'PARAMETERS SPECIFIED IN THE DFHMDI MACRO,'<br />
MNOTE ,'MACRO REQUEST IS IGNORED.'<br />
A further advantage of this approach is that only one severity 8 error is<br />
seen instead of three.<br />
Double-byte data is permissible in the operand field when the DBCS<br />
assembler option is specified. The double-byte data must be valid.<br />
The DBCS ampersand and apostrophe are not recognized as delimiters.<br />
A double-byte character that contains the value of an EBCDIC ampersand<br />
or apostrophe in either byte is not recognized as a delimiter when enclosed<br />
by SO and SI.<br />
Remarks: Any remarks for the MNOTE instruction statement must be separated<br />
by one or more spaces from the single quotation mark that ends the message.<br />
If severity is provided, or severity is omitted but the comma separating it from<br />
message is present, the message is treated as an error message; otherwise the<br />
message is treated as comments. The rules for specifying the contents of severity<br />
are:<br />
The severity code can be specified as any arithmetic expression allowed in the<br />
operand field of a SETA instruction. The expression must have a value in the<br />
range 0 through 255.<br />
Example:<br />
MNOTE 2,'ERROR IN SYNTAX'<br />
The generated result is:<br />
2,ERROR IN SYNTAX<br />
If the severity code is omitted, but the comma separating it from the message<br />
is present, the assembler assigns a default value of 1 as the severity code.<br />
Example:<br />
MNOTE ,'ERROR, SEV 1'<br />
The generated result is:<br />
Chapter 5. Assembler Instruction Statements 197
Change language