The program searches for the config150.ans file first in the current (working) directory, next in the
login (home) directory, and finally in the /apdl directory. The search path for config150.ans is
identical to the start150.ans and stop150.ans files.
The configuration file is a fixed-format file, consisting of a list of keywords followed by an equal (=) sign
and a number. The keyword must begin in column 1, the equal sign must be in column 9, and the
number must begin in column 10. A sample config150.ans file is shown next, followed by a brief
explanation of each of the keywords.
Sample config150.ans File
NO_RSTGM=1
NO_ELDBW=0
NUM_BUFR=2
SIZE_BIO=4096
VIRTM_MB=512
NUM_VPAG=128
SIZ_VPAG=16384
NUM_DPAG=8192
MEM_GROW=12
LOCALFIL=0
CONTACTS=1000
ORDERER_=2
MX_NODES=5000
MX_ELEMS=2000
MX_KEYPT=500
MX_LINES=1000
MX_AREAS=300
MX_VOLUS=200
MX_REALS=10
MX_COUPS=10
MX_CEQNS=10
FILESPLT=128NoteSince many of the values for config150.ans are dependent on the system being used, a
range of values for each keyword is provided. Note that on most computer systems, 1 integer
word = 4 bytes.NO_RSTGM is a key that determines whether or not the geometry data will be written to the results
file: 0 (write the data) or 1 (do not write the data). This is especially useful for large, complex analyses
where the results file would become excessively large during the solution.
NO_ELDBW is a key that determines whether or not to write results into the database after a solution.
When VALUE = 0, write results into the database. When VALUE=1, do not write results into the database.
It defaults to 0 and can be changed at the Begin level with the /CONFIG,NOELDB command.
NUM_BUFR is the number of buffers per file stored in scrat ch space: 1 to 32. A buffer is a chunk of space
used to "hold" data in memory before they are written to the hard disk.The program waits for the
buffer to be completely "filled up" and only then "empties" it onto the hard disk.This prevents frequent
disk input-output activity, which can be time consuming.
NUM_BUFR defaults to 4 and can be changed at the Begin level with the /CONFIG,NBUF command. It
is used for the EROT,ESAV,EMAT, and FULL files. On systems with a large amount of real memory,
you can increase NUM_BUFR or SIZE_BIO (or both) to keep the program solution files in memory rather
than on disk.This can save a significant amount of disk input-output activity and may be practical for
small problems with many substeps.
Release 15.0 - © SAS IP, Inc. All rights reserved. - Contains proprietary and confidential informationMemory Management and Configuration