SAVE, Fname, Ext, --, Slab
Saves all current database information.
FnameFile name and directory path (248 characters maximum, including the characters needed for the directory path). An unspecified directory path defaults to the working directory; in this case, you can use all 248 characters for the file name.
The file name defaults to Jobname.
ExtFilename extension (eight-character maximum).
The extension defaults to DB if Fname is blank.
--Unused field.
SlabMode for saving the database:
ALL | — | Save the model data, solution data and post data (element tables, etc.). This value is the default. |
MODEL | — | Save the model data (solid model, finite element model, loadings, etc.) only. |
SOLU | — | Save the model data and the solution data (nodal and element results). |
Saves all current database information to a file (File.DB). In interactive mode, an existing File.DB is first written to a backup file (File.DBB). In batch mode, an existing File.DB is replaced by the current database information with no backup. The command should be issued periodically to ensure a current file backup in case of a system "crash" or a "line drop." It may also be issued before a "doubtful" command so that if the result is not what was intended the database may be easily restored to the previous state. A save may be time consuming for large models. Repeated use of this command overwrites the previous data on the file (but a backup file is first written during an interactive run). When issued from within POST1, the nodal boundary conditions in the database (which were read from the results file) will overwrite the nodal boundary conditions existing on the database file.
Internal nodes may be created during solution (for example, via the mixed u-P formulation or generalized plane strain option for current-technology elements, the Lagrangian multiplier method for contact elements or the MPC184 elements, or the quadratic or cubic option of the BEAM188 and PIPE288 elements). It is sometimes necessary to save the internal nodes in the database for later operations, such as cutting boundary interpolations (CBDOF) for submodeling. To do so, issue the SAVE command after the first SOLVE command.
In general, saving after solving is always a good practice.
This command is valid in any processor.