Previous Page | Next Page

Graphics Options and Device Parameters Dictionary

RENDER



Controls the creation and disposition of rendered Bitstream fonts.
Used in: GOPTIONS statement
Default: MEMORY
Restriction: not supported by Java or ActiveX
See also: RENDERLIB

Syntax
Details

Syntax

RENDER=APPEND | DISK | MEMORY | NONE | READ

APPEND

creates files to store rendered versions of Bitstream fonts if the files do not already exist, reads previously rendered characters from the font files, and appends rendered versions of new characters to the font files when the SAS/GRAPH procedure terminates.

DISK

creates files to store rendered versions of Bitstream fonts if the files do not already exist, reads previously rendered characters from the font files, and appends rendered versions of new characters to the font files as they are encountered. This method is slower on some hosts, but it can work in memory-constrained conditions where the other rendering methods fail.

MEMORY

renders all fonts in memory without creating any font files on disk. Font files are not used even if they already exist. New characters are not written to existing font files when SAS/GRAPH procedures terminate.

This is the default and should be the fastest method on hosts that support virtual memory.

NONE

disables the font rendering features.

READ

reads existing rendered font files but does not create new font files or write new characters to existing font files. This is useful only when font files already exist in the rendered font library.


Details

The memory capacity and input/output characteristics of your host system determine which value for the RENDER= option provides the best performance.

Previous Page | Next Page | Top of Page