◄Example► ◄Up► ◄Contents► ◄Index► ◄Back► ─────SEGMENTS Statement───────────────────────────────────────────────────── Syntax: SEGMENTS segmentdefinitions This statement defines attributes of one or more individual segments. The attributes specified for a specific segment override defaults set in CODE and DATA statements (except as noted). The total number of segment definitions cannot exceed the number set using LINK's /SEG option. (The default without /SEG is 128.) See: ◄CODE Statement► ◄DATA Statement► ◄/SEG Option► The SEGMENTS keyword marks the beginning of segment definitions, each on a separate line. SEGMENTS must appear once before the first specification (on the same or preceding line) and can be repeated before each additional specification. SEGMENTS statements can appear more than once in the file. Segment-Definition Syntax [']segmentname['] [CLASS 'classname'] [attribute...] Each segment definition begins with <segmentname>, optionally enclosed in single or double quotation marks (' or "). The quotation marks are required if <segmentname> is a reserved word. See: ◄Reserved Words► CLASS <classname> optionally specifies the class of the segment and must be enclosed in single or double quotation marks. The default class is CODE. One or more attributes can be specified. Each can appear once, in any order. Attribute Purpose ◄<conforming>► Sets protected-mode conformance ◄<discard>► Sets whether segment is discardable ◄<executeonly>► Sets execute status ◄<iopl>► Sets I/O privilege level ◄<load>► Sets when segment is loaded ◄<movable>► Sets whether segment is movable ◄<readonly>► Sets read status ◄<shared>► Sets whether segment is shareable -♦-