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.

User subroutine or other special-purpose C file.

User subroutine or other special-purpose C++ file.

User subroutine or other special-purpose C++ file.

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 and Abaqus/CFD do not write analysis results to this file.

User subroutine or other special-purpose Fortran file.

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 “ASCII translation of results (.fil) files,” Section 3.2.14.) 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, Abaqus/Explicit, or Abaqus/CFD 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.

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

Model file, used by Abaqus/Standard and Abaqus/Explicit. It is written by the datacheck option. 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, Abaqus/Explicit, and Abaqus/CFD. It is read by the Visualization module in Abaqus/CAE (Abaqus/Viewer) and by the convert=odb option. This file is required for restart.

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, used by Abaqus/Standard and Abaqus/Explicit. 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 and is used by Abaqus/Standard and Abaqus/Explicit. The restart file is written by the analysis, datacheck, and continue options. It is read by any restarted analysis.

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.

Model and results file, used by Abaqus/CFD. It is also used by Abaqus/Standard and Abaqus/Explicit when the resultsformat=sim or both option is specified. It is written by the datacheck option. It is read and can be written by the analysis and continue options. This file is required for restart.

Linear dynamics data file, used by Abaqus/Standard when the resultsformat=odb option is specified. It is written during the frequency extraction procedure in SIM-based linear dynamics analyses (see “Using the SIM architecture for modal superposition dynamic analyses” in “Dynamic analysis procedures: overview,” Section 6.3.1, for details) and is used to store eigenvectors, substructure matrices, and other modal system information. This file is required for restart.

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, used by Abaqus/Standard and Abaqus/Explicit. It is written by the analysis and datacheck options and is read by the analysis and continue options.

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.

User subroutine or other special-purpose C file.

User subroutine or other special-purpose C++ file.

User subroutine or other special-purpose C++ file.

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 and Abaqus/CFD do not write analysis results to this file.

User subroutine or other special-purpose Fortran file.

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 “ASCII translation of results (.fil) files,” Section 3.2.14.) 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, Abaqus/Explicit, or Abaqus/CFD 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.

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

Model file, used by Abaqus/Standard and Abaqus/Explicit. It is written by the datacheck option. 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, Abaqus/Explicit, and Abaqus/CFD. It is read by the Visualization module in Abaqus/CAE (Abaqus/Viewer) and by the convert=odb option. This file is required for restart.

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, used by Abaqus/Standard and Abaqus/Explicit. 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 and is used by Abaqus/Standard and Abaqus/Explicit. The restart file is written by the analysis, datacheck, and continue options. It is read by any restarted analysis.

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.

Model and results file, used by Abaqus/CFD. It is also used by Abaqus/Standard and Abaqus/Explicit when the resultsformat=sim or both option is specified. It is written by the datacheck option. It is read and can be written by the analysis and continue options. This file is required for restart.

Linear dynamics data file, used by Abaqus/Standard when the resultsformat=odb option is specified. It is written during the frequency extraction procedure in SIM-based linear dynamics analyses (see “Using the SIM architecture for modal superposition dynamic analyses” in “Dynamic analysis procedures: overview,” Section 6.3.1, for details) and is used to store eigenvectors, substructure matrices, and other modal system information. This file is required for restart.

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, used by Abaqus/Standard and Abaqus/Explicit. It is written by the analysis and datacheck options and is read by the analysis and continue options.