The replay file contains ABAQUS/CAE commands that record almost every modeling operation you perform during a session. For more information, see “Replaying an ABAQUS/CAE session,” Section 9.5.1.

The model database file contains models and analysis jobs. For more information, see “What is an ABAQUS/CAE model database?,” Section 9.1.

The journal file contains the ABAQUS/CAE commands that will replicate the model database that was saved to disk. For more information, see “Recreating a saved model database,” Section 9.5.2.

The recover file contains the ABAQUS/CAE commands that will replicate the version of the model database in memory. The model database recovery file contains only the commands that changed the model database since you last saved it. For more information, see “Recreating an unsaved model database,” Section 9.5.3.

ABAQUS/CAE generates an input file that is read by ABAQUS/Standard or ABAQUS/Explicit when you submit a job for analysis. For more information, see “Basic steps for analyzing a model,” Section 18.2.1.

Output database files contain the results from your analysis. You use the Step module's output request managers to choose which variables are written to the output database during the analysis and at what rate. An output database is associated with the job you submit from the Job module; for example, if you named your job FrictionLoad, the analysis creates an output database called FrictionLoad.odb.

When you open an output database, ABAQUS/CAE loads the Visualization module and allows you to view a graphical representation of the contents. You can also import a part from an output database as an orphan mesh. You can save X–Y data objects to an output database file if you open the file with write permission; otherwise, you cannot modify the contents of the output database once it has been created.

The lock file (job_name.lck) is written whenever an output database file is opened with write access, including when an analysis is running and writing output to an output database file. The lock file prevents you from having simultaneous write permission to the output database from multiple sources. It is deleted automatically when the output database file is closed or when the analysis that creates it ends.

The restart file is used to continue an analysis that stopped before it was complete. You use the Step module to specify which analysis steps should write restart information and how often. If you are using ABAQUS/Explicit, the restart information you supply in the Step module controls the data written to the state file (job_name.abq). For more information, see “Configuring restart output requests,” Section 14.13.2.

The data file contains printed output from the analysis input file processor, as well as printed output of selected results written during the analysis. ABAQUS/CAE automatically requests that the default printed output for the current analysis procedure be generated at the end of each step; you cannot use ABAQUS/CAE to exert any additional control over the contents of the data file.

The message file contains diagnostic or informative messages about the progress of the solution. You can control the diagnostic information that is output to the message file using the Step module. For more information, see “Diagnostic printing,” Section 14.5.3.

The status file (job_name.sta) contains information about the progress of the analysis. In addition, you use the Step module to request that the value of a single degree of freedom at a single node be output to the status file. For more information, see “Degree of freedom monitor requests,” Section 14.5.4.

The results file contains selected results from the analysis in a format that can be read by other applications, such as postprocessing programs. A submodel analysis can read the global model results from either an output database or a results file. By default, an analysis from ABAQUS/CAE does not create a results file. For more information, see “Submodeling,” Section 10.2 of the ABAQUS Analysis User's Manual, and “Submodeling,” Section 21.8.

The scratch output database file (job_name.ods) contains a “session step” in which field output variables that you create (by operating on either fields or frames) are saved. This file is deleted automatically when the original output database file (from which the field output originates) is closed or when the ABAQUS/CAE session ends.