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.

Key that determines whether or not to write results into the database after a solution. When VAL = 0 (default), write results into the database. When VAL = 1, do not write results into the database. This key can be changed at the Begin level via the /CONFIG,NOELDB command.

Number of buffers per file stored in scratch 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.

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.

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.

Amount of total program work space requested for the current session. It defaults to 2 GB (2048 MB); it can be changed with the work space entry option, as explained in the basic concepts section earlier in this chapter. (See Figure 20.5: Memory Diagram in Terms of Configuration Keywords.) You can also use VIRT_MEM in place of VIRTM_MB to specify the work space in integer words.

Maximum number of database pages in memory, ranging from 16 to 16384. The default value is 16384. You can change NUM_VPAG or SIZ_VPAG (or both) to change the amount of database space; see How and When to Perform Memory Management in this chapter, and Figure 20.5: Memory Diagram in Terms of Configuration Keywords.

Figure 20.5: Memory Diagram in Terms of Configuration Keywords

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.

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.

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 scratch space allocation. If the program attempts to allocate additional scratch 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 scratch space. To turn off dynamic memory allocation (use a fixed-memory model), set MEM_GROW=0.

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 command. This key is applicable only to the erot, esav, emat, and full files. Locally closed files (LOCALFIL=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.

Number of contact elements that are expected to be in contact at any given time. It defaults to 1000 and can be changed at the Begin level with the /CONFIG,NCONT command. This is not the same as the total number of contact elements in the model.

Maximum number of nodes. You can change the value (on most systems) at the Begin level with the /CONFIG,MXND command.

Maximum number of elements. You can change the value (on most systems) at the Begin level with the /CONFIG,MXEL command.

Maximum number of keypoints. You can change the value (on most systems) at the Begin level with the /CONFIG,MXKP command.

Maximum number of lines. You can change the value (on most systems) at the Begin level with the /CONFIG,MXLS command.

Maximum number of areas. You can change the value (on most systems) at the Begin level with the /CONFIG,MXAR command.

Maximum number of volumes. You can change the value (on most systems) at the Begin level with the /CONFIG,MXVL command.

Maximum number of sets of real constants (element attributes). You can change the value (on most systems) at the Begin level with the /CONFIG,MXRL command.

Maximum number of sets of coupled degrees of freedom. You can change the value (on most systems) at the Begin level with the /CONFIG,MXCP command.

Maximum number of constraint equations. You can change the value (on most systems) at the Begin level with the /CONFIG,MXCE command.

Integer value indicating the file split point in megawords. A megaword is 1024*1024 4-byte words, or 4 MB. All files that are eligible for splitting will be split into a new file every increment of xxxx megawords (where xxxx is the value specified with this keyword). You can change the value (on most systems) at the Begin level with the /CONFIG,FSPLIT command. For more information about file splitting, see Splitting Files Across File Partitions in the Operations Guide.

Key that determines whether or not the number of file buffers for each binary file (.esav, .emat, .full, and so on) will automatically grow as needed. By default (GRW_NBUF = 0), the logic is program-controlled and the number of file buffers may or may not grow automatically. When GRW_NBUF = 1, the number of file buffers automatically grows for most binary files to reduce the amount of I/O. This option may require a significantly greater amount of memory than the default setting. Also, when GRW_NBUF = 1, the number of file buffers for the results file will not grow, and files written by the sparse and PCG equation solvers are not affected. When GRW_NBUF = -1, the number of file buffers does not grow automatically for any file.

Key to control automatic checkout of a Mechanical batch license during solve when the capability is not enabled, useful for PrepPost sessions. When MEBA_LIC = 0 (default), automatic license checkout occurs. When MEBA_LIC = 1, automatic license checkout is bypassed. This key can be changed at the Begin level via the /CONFIG,MEBA_LIC command.