SIZE_BIO is the size of each file buffer: 1024 to 41943041073741824 integer words (4 KB to 3814 TB). It
defaults to 16384 and can be changed (on most systems) at the Begin level with the /CONFIG,SZBIO
command. See NUM_BUFR for details.
VIRTM_MB is the amount of total program work space requested for the current session. It defaults to
1 GB (1024 MB) for 64-bit machines or 512 MB for 32-bit machines; it can be changed with the work
space entry option, as explained in the basic concepts section earlier in this chapter. (See Fig-
ure 21.5: Memory Diagram in Terms of Configuration Keywords (p. 333).) You can also use VIRT_MEM in
place of VIRTM_MB to specify the work space in integer words.
NUM_VPAG is the maximum number of database pages in memory, ranging from 16 to 8192.The default
value is 8192 for 64-bit machines or 4096 for 32-bit machines. You can change NUM_VPAG or SIZ_VPAG
(or both) to change the amount of database space; see How and When to Perform Memory Manage-
ment (p. 329) in this chapter, and Figure 21.5: Memory Diagram in Terms of Configuration Keywords (p. 333).
Figure 21.5: Memory Diagram in Terms of Configuration Keywords
SIZ_VPAG is the size of each database page: 4096 to 4194304 integer words (16 KB to 16 MB), defaults
to 16384 (64 KB).You can change SIZ_VPAG or NUM_VPAG (or both) to change the amount of database
space. SIZ_VPAG also affects the size of the page file; see NUM_DPAG.
NUM_DPAG is the number of database pages on disk: NUM_DPAG defaults to 16777212 (the maximum).
This number times SIZ_VPAG determines the maximum size of the page file (Jobname.PAGE), which
is written only if the database becomes too large to fit in the database space in memory. If the page
file is written, sufficient disk space must be available to accommodate it, or the program will abort.
MEM_GROW is the starting size of the memory block (in MB) that the program will attempt to allocate
should a problem grow larger than will fit in the current scrat ch space allocation. If the program attempts
to allocate additional scrat ch space, it will start with a memory block size equal to MEM_GROW and
then reduce this by halves until it can allocate additional memory. If not specified, MEM_GROW defaults
to one-half the initial scrat ch space. To turn off dynamic memory allocation (use a fixed-memory model),
set MEM_GROW=0.
LOCALFIL is a key that determines when files are to be closed: 0 (globally closed) or 1 (locally closed).
It defaults to 0 (globally closed) and can be changed at the Begin level with the /CONFIG,LOCFL com-
mand. This key is applicable only to the EROT,ESAV,EMAT, and FULL files. Locally closed files (LOCAL-
FIL=1) may be deleted earlier during solution if requested with the /FDELE command. This may be
helpful while running large problems. Globally closed files are closed at the end of the run and are not
opened and closed each substep. This saves time in analyses with many substeps.
Release 15.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential informationUsing the Configuration File