GOFF


   .-NOGOFF------------.   
>>-+-------------------+---------------------------------------><
   |      .-(NODATA)-. |   
   '-GOFF-+----------+-'   
          '-(ADATA)--'

Default: NOGOFF
Abbreviations: None
Restrictions: You cannot specify this option on *PROCESS statements.
GOFF: Instructs the assembler to produce a Generalized Object File format (GOFF) data set. You define this data set with the SYSLIN or SYSPUNCH ddname.
Note: For more information about the GOFF format, refer to z/OS DFSMS Program Management.
NOADATA: The same as GOFF without a suboption.
ADATA: Instructs the assembler to produce a Generalized Object File format data set, and include ADATA text records.
NOGOFF: Instructs the assembler not to produce a Generalized Object File format data set.

Notes:

Specify the LIST(133) option when you specify the GOFF option. If the logical record length of the listing data set is less than 133, the assembler truncates the listing lines.
The generalized object format does not support TEST (SYM) records. If you specify the TEST option with the GOFF option, the assembler issues a diagnostic error message.
The assembler option XOBJECT is treated as a synonym for the GOFF option and accepts the same subparameters as GOFF.

For more information on the 133-character format, see Source and object.

When the GOFF option is not specified a control section is initiated or resumed by the CSECT, RSECT, and COM statements. Any machine language text created by statements that follow such control section declarations belongs to the control section, and is manipulated during program linking and binding as an indivisible unit.

When the GOFF option is specified, the behavior of statements like CSECT is different. By default, the assembler creates a definition of a text class named B_TEXT, to which subsequent machine language text belongs if no other classes are declared. If you specify other class names using the CATTR statement, machine language text following such CATTR statements belongs to that class.

The combination of a section name and a class name defines an element, which is the indivisible unit manipulated during linking and binding. All elements with the same section name are "owned" by that section, and binding actions (such as section replacement) act on all elements owned by a section.

When the GOFF option is specified, and if no CATTR statements are present, then all machine language text is placed in the default class B_TEXT, and the behavior of the elements in the bound module is essentially the same as the behavior of control sections when the OBJECT option is specified. However, if additional classes are declared, a section name can best be thought of as a "handle" by which elements within declared classes are owned.