Notes

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.

If radiosity surface elements (SURF251 or SURF252) are present in the model, a radiosity mapping data file, Fname.RSM, is also saved when the SAVE command is issued. For more information, see Advanced Radiosity Options in the Thermal Analysis Guide.

This command is valid in any processor.

Menu Paths