HLASM: V1R6 Language Ref

Model statementsTable 37. Rules for concatenationConcatenated String&FIELD.A&FIELDA▌1▐&DISP.(&BASE)¹ ▌2▐ ▌6▐DCD’&INT..&FRACT’¹▌3▐VariableSymbol&FIELD&FIELDA&DISP&BASE&INT&FRACTValues to beSubstitutedAREASUM100109988ValueAREAASUM100(10)DCGenerated ResultD’99.88’▌4▐DCD’&INT&FRACT’▌7▐DC D’9988’FIELD&A ▌5▐ &A A FIELDA&A+&B*3-D └──┴── ▌6▐&SYM(&SUBSCR)▌8▐Notes:&A&B&SUBSCR&SYM(10)1. The concatenation character is not generated.AB10ENTRYA+B*3-DENTRYConcatenation of fields containing double-byte dataIf the DBCS assembler option is specified, then the following additional rulesapply:v Because ampersand is not recognized in double-byte data, variable symbolsmust not be present in double-byte data.v The concatenation character is mandatory when double-byte data is to follow avariable symbol.v The assembler checks for redundant SI and SO at concatenation points. If thebyte to the left of the join is SI and the byte to the right of the join is SO, thenthe SI/SO pair is considered redundant and is removed.Note: The rules for redundant SI and SO are different for variable substition andlisting display, which are described at “Listing of generated fieldscontaining double-byte data” on page 247.The following example shows these rules:&SYMBOL SETC ’’DBCS DC C’&SYMBOL.’The SI/SO pairs between double-byte characters Db and Dc, and Dd and .&, areremoved. The variable symbol &SYMBOL is recognized between the double-bytestrings but not in the double-byte strings. The result after concatenation is:DBCS DC C’’248 HLASM: V1R6 Language Ref