This option specifies the name of the output database file to use if it is different from job-name. The procedure searches for database-file as entered on the command line with the .odb file extension.

This option specifies the name of the file from which Abaqus/Viewer commands are read. The commands in replay-file will execute immediately upon startup of Abaqus/Viewer. If no file extension is given, the default extension is .rpy. You cannot use the replay option to execute a script with control flow statements.

This option specifies the name of the file containing the Python configuration commands to be run at application startup. Commands in this file are run after any configuration commands that have been set in the environment file. Abaqus/Viewer does not echo the commands to the replay file when they are executed.

This option specifies the name of the file containing Python configuration commands to be run at application startup. Commands in this file are run after any configuration commands that have been set in the environment file.

This option specifies that Abaqus/Viewer is to be run without the graphical user interface (GUI). If no file name is specified, an Abaqus/Viewer license is checked out and the Python interpreter is initialized to allow interactive entry of Python or Abaqus Scripting Interface commands.

If a file name is specified, Abaqus/Viewer runs the commands in the file and exits upon their completion. If no file extension is given, the default extension is .py. This option is useful for automating post-analysis processing tasks without the added expense of running a display. Since no interface is provided, the scripts cannot include any user interaction.

This option specifies that all configuration commands in the environment files should not be run at application startup. This option can be used in conjunction with the script command to suppress all configuration commands except those in the script file.

This option specifies that Abaqus/Viewer should not apply the display options settings stored in abaqus_2016.gpr (for example, the render style and the display of boundary conditions). For more information, see “Saving your display options settings,” Section 76.16 of the Abaqus/CAE User's Guide.

This option specifies that Abaqus/Viewer should not apply the GUI settings stored in abaqus_2016.gpr (for example, the size and location of the Abaqus/CAE main window or its dialog boxes).

This option specifies that the Start Session dialog box for Abaqus/Viewer should not be displayed.

This option specifies the name of the file containing Abaqus GUI Toolkit commands. This option executes an application that is a customized version of Abaqus/Viewer. For more information, see Chapter 1, “Introduction,” of the Abaqus GUI Toolkit User's Guide.

This option starts a separate user interface containing the Python development environment along with Abaqus/Viewer. The Python development environment allows you to create, edit, step through, and debug Python scripts. For more information, see Part III, “The Abaqus Python development environment,” of the Abaqus Scripting User's Guide.

You can specify a script as the argument for this option, which prompts Abaqus/Viewer to run a GUI script. Abaqus/Viewer closes when the end of the script is reached.

This option enables you to record your actions in the Abaqus/Viewer user interface in a file named abaqus.guiLog. You can also set this option at startup by using the environment variable ABQ_CAE_GUIRECORD. The guiRecord option cannot be used with the guiTester option.

This option enables you to disable user interface recording when the environment variable ABQ_CAE_GUIRECORD is set.

This option specifies the name of the output database file to use if it is different from job-name. The procedure searches for database-file as entered on the command line with the .odb file extension.

This option specifies the name of the file from which Abaqus/Viewer commands are read. The commands in replay-file will execute immediately upon startup of Abaqus/Viewer. If no file extension is given, the default extension is .rpy. You cannot use the replay option to execute a script with control flow statements.

This option specifies the name of the file containing the Python configuration commands to be run at application startup. Commands in this file are run after any configuration commands that have been set in the environment file. Abaqus/Viewer does not echo the commands to the replay file when they are executed.

This option specifies the name of the file containing Python configuration commands to be run at application startup. Commands in this file are run after any configuration commands that have been set in the environment file.

This option specifies that Abaqus/Viewer is to be run without the graphical user interface (GUI). If no file name is specified, an Abaqus/Viewer license is checked out and the Python interpreter is initialized to allow interactive entry of Python or Abaqus Scripting Interface commands.

If a file name is specified, Abaqus/Viewer runs the commands in the file and exits upon their completion. If no file extension is given, the default extension is .py. This option is useful for automating post-analysis processing tasks without the added expense of running a display. Since no interface is provided, the scripts cannot include any user interaction.

This option specifies that all configuration commands in the environment files should not be run at application startup. This option can be used in conjunction with the script command to suppress all configuration commands except those in the script file.

This option specifies that Abaqus/Viewer should not apply the display options settings stored in abaqus_2016.gpr (for example, the render style and the display of boundary conditions). For more information, see “Saving your display options settings,” Section 76.16 of the Abaqus/CAE User's Guide.

This option specifies that Abaqus/Viewer should not apply the GUI settings stored in abaqus_2016.gpr (for example, the size and location of the Abaqus/CAE main window or its dialog boxes).

This option specifies that the Start Session dialog box for Abaqus/Viewer should not be displayed.

This option specifies the name of the file containing Abaqus GUI Toolkit commands. This option executes an application that is a customized version of Abaqus/Viewer. For more information, see Chapter 1, “Introduction,” of the Abaqus GUI Toolkit User's Guide.

This option starts a separate user interface containing the Python development environment along with Abaqus/Viewer. The Python development environment allows you to create, edit, step through, and debug Python scripts. For more information, see Part III, “The Abaqus Python development environment,” of the Abaqus Scripting User's Guide.

You can specify a script as the argument for this option, which prompts Abaqus/Viewer to run a GUI script. Abaqus/Viewer closes when the end of the script is reached.

This option enables you to record your actions in the Abaqus/Viewer user interface in a file named abaqus.guiLog. You can also set this option at startup by using the environment variable ABQ_CAE_GUIRECORD. The guiRecord option cannot be used with the guiTester option.

This option enables you to disable user interface recording when the environment variable ABQ_CAE_GUIRECORD is set.