State file, only used by ABAQUS/Explicit. It is written by the analysis, continue, and recover options. It is read by the convert and recover options. This file is required for restart.

Symmetric model data file, only used by ABAQUS/Standard. It is written during symmetric model generation by the datacheck and analysis options.

Text file containing beam cross-section properties for meshed section profiles. It is written by ABAQUS/Standard during meshed beam cross-section generation.

Auto-release file, which contains information needed for license recovery and suspension.

Command file, created by the ABAQUS execution procedure.

Printed output file. It is written by the analysis, datacheck, parametercheck, and continue options. ABAQUS/Explicit does not write analysis results to this file.

Lanczos eigenvector file. This is a temporary scratch file that is used to store the eigenvectors calculated by the Lanczos eigensolver during the solution procedure.

User subroutine or other special-purpose FORTRAN file.

Sparse solver factor files. These temporary scratch files are used by the sparse solver in ABAQUS/Standard. The uft file is created only when the unsymmetric solver is used.

Results file. It is written by the analysis and continue options in ABAQUS/Standard and by the convert=select and convert=all options in ABAQUS/Explicit.

Results file created when changing the format of the .fil file using the abaqus ascfil command. It can be in either ASCII or binary format. (See “Execution procedure for ASCII translation of results (.fil) files,” Section 3.2.9.) The ASCII format is convenient for data transfer between machines that do not have compatible binary data formats.

Analysis input file. It is read when the analysis, datacheck, and parametercheck options are selected.

Interprocess message file. It is written when an analysis is run from ABAQUS/CAE, and it contains a log of all messages sent from ABAQUS/Standard or ABAQUS/Explicit to ABAQUS/CAE.

Lock file for the output database. This file is written whenever an output database file is opened with write access; it 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 ask_delete environment file parameter setting will not affect the lock file.

Lanczos vector file. This is a temporary scratch file that is used to store the Lanczos vectors and weighted Lanczos vectors.

Log file, which contains start and end times for modules run by the current ABAQUS execution procedure.

Model file. It is written by the datacheck option in ABAQUS/Standard and ABAQUS/Explicit. It is read and can be written by the analysis and continue options in ABAQUS/Standard. It is read by the analysis and continue options in ABAQUS/Explicit. Multiple model files may exist if the element operations are executed in parallel in an ABAQUS/Standard analysis. In such a case a process identifier is attached to the file name. This file is required for restart.

Message file. It is written by the analysis, datacheck, and continue options in ABAQUS/Standard and ABAQUS/Explicit. Multiple message files may exist if the element operations are executed in parallel in an ABAQUS/Standard analysis. In such a case a process identifier is attached to the file name.

Nickname file used by ABAQUS/Standard. It stores a set of internal identifiers for the degrees of freedom in a model.

Output database. It is written by the analysis and continue options in ABAQUS/Standard and ABAQUS/Explicit. It is read by the Visualization module in ABAQUS/CAE (ABAQUS/Viewer) and by the convert=odb option. This file is required for restart.

Sparse solver operator file, which is a temporary scratch file used by the sparse solver in ABAQUS/Standard.

Package file, which contains model information and is used by ABAQUS/Explicit only. It is written by the analysis and datacheck options. It is read by the analysis, continue, and recover options. This file is required for restart.

Modified version of original parametrized input file showing input parameters and their values.

Modified version of original parametrized input file showing input free of parameter information (after input parameter evaluation and substitution has been performed).

Parameter evaluation and substitution message file. It is written when the input file is parametrized.

Part file. This file is used to store part and assembly information and is created even if the input file does not contain an assembly definition. The part file is required for restart, import, sequentially coupled thermal-stress analysis, symmetric model generation, and underwater shock analysis, even if the model is not defined in terms of an assembly of part instances. This file may also be needed for submodeling analysis.

Python scripting file. You must create this type of file to define a parametric study.

Restart file, which contains information necessary to continue a previous analysis. The restart file is written by the analysis, datacheck, and continue options. It is read by any restarted analysis.

Lanczos scratch file. This is a temporary scratch file that is used to hold temporary information required by the Lanczos solver.

Sparse solver database file. This is a temporary file that is used by the sparse solver.

Selected results file, used by ABAQUS/Explicit. It is written by the analysis, continue, and recover options and is read by the convert=select option. This file is required for restart.

Sparse solver file used to store the solution vectors for a problem. This file is a temporary file used by the sparse solver in ABAQUS/Standard.

Sparse solver scratch file. This temporary scratch file is used by the sparse solver in ABAQUS/Standard.

Status file. ABAQUS writes increment summaries to this file in the analysis, continue, and recover options.

State file. It is written by the datacheck option in ABAQUS/Standard and ABAQUS/Explicit. It is read and can be written by the analysis and continue options in ABAQUS/Standard. It is read by the analysis and continue options in ABAQUS/Explicit. Multiple state files may exist if the element operations are executed in parallel in an ABAQUS/Standard analysis. In such a case a process identifier is attached to the file name. This file is required for restart.

Substructure file, used by ABAQUS/Standard.

File containing information about the input file variations generated by a parametric study.

Communications file. It is written by the analysis and datacheck options and is read by the analysis and continue options.