Accelerator Manual (G06.27+, H06.04+, J06.03+)

Using the Accelerator
Accelerator Manual—527303-003
4-12
Comments
In the Guardian environment, you specify an obey file as a run-option within the
slashes that optionally follow the keyword AXCEL, as in this example:
AXCEL /in fred/ input-file, output-file
or in the AXCEL-options part of the command, following the semicolon:
AXCEL input-file, output-file; obey fred
In the OSS environment, you specify an obey file in the -WAXCEL flag to the c89 utility.
For example, to direct the Accelerator to read the obey file pathname
/usr/project1/obeyme, specify:
c89 [-o outfile] -Waxcel="OBEY /usr/project1/obeyme" infile
The Accelerator resolves partially qualified pathnames using the current working
directory. Unlike Guardian file names, OSS pathnames are case sensitive.
Obey files can contain any number of Accelerator options. The list of options can be as
long as you like, with any number of comma-separated options on each line. Options
that take an indefinite number of arguments can be followed by a blank-separated list
of such arguments. Each option, together with all its arguments, must appear in its
entirety on a single line, and not be continued onto a following line.
Comments
You can use comments in obey files to annotate the commands you specify to the
Accelerator. (You cannot use comments on the AXCEL command line.) A comment
can be on any line of an obey file, whether or not that line contains an option. A
comment is any string introduced by two dashes (--) and it is terminated by the end of
the line.
The following is a sample obey file with comments:
-- Accelerator options for FileSys module
UC
StmtDebug -- Use ProcDebug for production version
InheritsCC_On
ReturnValSize File_Buffer_Read 2
-- MOREOPTS file contains options for user libraries
Obey MOREOPTS
Scoping Directives
You can use scoping directives in obey files to indicate the code space to which a set
of options apply. (You cannot use scoping directives on the AXCEL command line.) By
default, options have a scope of all four code spaces: user code, user library, system
code, and system library.
A scoping directive introduces a list of options and associates that list with a code
space. The list of one or more options immediately follows the scoping directive. The
scope declared by the directive is in effect until the next appearance of a scoping
directive, the invocation of a new obey file, or the end of the present obey file.