02.07.2013 Views

Type III C lass A Program

Type III C lass A Program

Type III C lass A Program

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ASSEMBLE<br />

Format:<br />

I // ASSEMBLE 1 «optionl ••• optionN» I<br />

I I· I<br />

filename specifies the name of the file which contains the<br />

cards following the // ASSEMBLE control card up to<br />

the next control card. The filetype is SYSIN.<br />

• If no parameters are specified. a<br />

chosen by the system and the default<br />

taken.<br />

Options:<br />

LIST creates the LISTING file.<br />

NOLIST suppresses creation of the LISTING file.<br />

XREF creates the cross-reference symbol table<br />

LISTING file.<br />

NOXREF suppresses the creation of the symbol<br />

option is ignored if the NOLIST<br />

specified.<br />

filename is<br />

options are<br />

within the<br />

table. This<br />

option was<br />

RENT causes the assembler to generate messages in the<br />

LISTING file if nonreentrant coding is found in the<br />

assembled program.<br />

NORENT suppresses the generation of messages in the LISTING<br />

file if nonreentrant coding is found in the<br />

assembled program.<br />

Usage:<br />

All cards following the // ASSEMBLE control card up to the<br />

next control card are assumed to be Assembly Language source<br />

cards. These cards are read and stored as a file and<br />

translated using the F-level Assembler and the specified<br />

options. The source cards may contain any number of<br />

routines, each delimited by an END statement. If a filename<br />

is specified, the source cards are stored as a file with<br />

this filename and the filetype of SYSIN. If filename is not<br />

specified, the system chooses a unique name. The options<br />

specified govern the translation of the source cards. Any<br />

combination of options may be specified in any order.<br />

An assembly generates a LISTING and a TEXT file.. The<br />

LISTING is automatically written out on sysout. The TEXT<br />

file (that is, object module) can be punched using a //<br />

PUNCH control card. The filename of the TEXT file is the<br />

same as the filename of the Assembly Language source file.<br />

Object modules are loaded into core and executed when the //<br />

530 CMS Batch Monitor

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

Saved successfully!

Ooh no, something went wrong!