11.07.2015 Views

HLASM: V1R6 Language Ref

HLASM: V1R6 Language Ref

HLASM: V1R6 Language Ref

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Assembler language coding conventions16 <strong>HLASM</strong>: <strong>V1R6</strong> <strong>Language</strong> <strong>Ref</strong>v GBLA, GBLB, and GBLC conditional assembly statements, see “Alternativeformat for GBLx statements” on page 341v LCLA, LCLB, and LCLC conditional assembly statements, see “Alternativeformat for LCLx statements” on page 343v Macro instruction statement, see “Alternative formats for a macro instruction”on page 296v Prototype statement of a macro definition, see “Alternative formats for theprototype statement” on page 244v SETA, SETB, SETAF, SETCF and SETC conditional assembly statements, see“Alternative statement format” on page 381Examples of the alternative statement format for each of these instructions aregiven with the description of the individual instruction.Continuation of double-byte dataNo special considerations apply to continuation:v Where double-byte data is created by a code-generation program, andv There is no requirement for double-byte data to be readable on a device capableof presenting DBCS charactersA double-byte character string may be continued at any point, and SO and SI mustbe balanced within a field, but not within a statement line.Where double-byte data is created by a workstation that has the capability ofpresenting DBCS characters, such as the IBM 5550 multistation, or wherereadability of double-byte data in High Level Assembler source input or listings isrequired, special features of the High Level Assembler language may be used.When the DBCS assembler option is specified, High Level Assembler provides theflexibility to cater for any combination of double-byte data and single-byte data.The special features provided are:v Removal of redundant SI/SO at continuation points. When an SI is placed in theend column of a continued line, and an SO is placed in the continue column ofthe next line, the SI and SO are considered redundant and are removed from thestatement before statement analysis.v An extended continuation-indicator provides a flexible end column on aline-by-line basis to support any alignment of double-byte data in a sourcestatement. The end column of continued lines may be shifted to the left byextending the continuation-indicator.v To guard against accidental continuation caused by double-byte data ending inthe continuation-indicator column, neither SO nor SI is regarded as acontinuation-indicator. If either is used, the following warning message is issued:ASMA201W SO or SI in continuation column - no continuationassumedThe examples below show the use of these features. <strong>Ref</strong>er to “Double-bytecharacter set notation” on page xii for the notation used in the examples.Source input considerations:v Extended continuation-indicators may be used in any source statement,including macro statements and statements included by the COPY instruction.This feature is intended for source lines containing double-byte data, however itbecomes available to all lines when the DBCS option is set.v On a line with a non-space continuation-indicator, the end column is the firstcolumn to the left of the continuation-indicator which has a value different fromthe continuation-indicator.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!