DEFINE

 — 

Issuing the command specifies how frequently the .Xnnn restart files are written for a load step (default).

FILE_SUMMARY

 — 

Issuing the command prints the substep and load step information for all .Xnnn files for the current jobname in the current directory. If this option is specified, all other arguments are ignored.

STATUS

 — 

Issuing the command lists the current status in the tables of restart controls specified previously by RESCONTROL. If this option is specified, all other arguments are ignored.

NORESTART

 — 

Issuing the command cleans up some of the restart files after a Distributed ANSYS solution. The host process will not have the following files in the working directory at the end of the run: .ESAV, .OSAV, .Xnnn, .RDB, .LDHI. The slave processes will not have the following files in the working directory at the end of the run: .ESAV, .OSAV, .Xnnn, .RST (or .RTH, etc.). Some of the restart files are never written, some are removed upon leaving /SOLU (for example, upon FINISH), and some are removed upon exiting the program.

This option is useful for cleaning up files written by all of the Distributed ANSYS processes, particularly when you know that these restart files will not be needed later on. If this option is specified, all other arguments are ignored.

If this option is used in shared-memory parallel ANSYS, most of the restart files in the working directory are removed. It has the same effect as issuing RESCONTROL,,NONE.

LINEAR

 — 

Issuing the command specifies the same actions as Action = DEFINE. However, this option is intended for linear static applications. For a linear static analysis, the restart capability is normally not needed. However, it is typically needed when a subsequent linear perturbation analysis is desired. By default, none of the restart files are written for a linear static analysis.

DELETE

 — 

Delete the restart control specification corresponding to the Ldstep label on a previous RESCONTROL,DEFINE command.

ALL

 — 

Write the .Xnnn files at the same substep Frequency for all load steps; write the load history information to the .LDHI file for all load steps.

LAST

 — 

Write the .Xnnn files for the last load step only; write load history information to the .LDHI file for the last load step only. This option is the default for nonlinear static and full transient analyses. The remaining arguments are ignored.

N

 — 

Number that indicates how often the .Xnnn file is written.

Input a positive number to write the .Xnnn files at the substep Frequency indicated only for load step N. Other load steps will be written at the default substep frequency or at a frequency defined by a previous RESCONTROL specification. Load history information is written to the .LDHI file only for load steps N.

Input a negative number (-N) to write the .Xnnn files for every Nth load step at the specified substep Frequency. The load history information is written to the .LDHI file every Nth load step. This option is suitable for restart applications in which more than a few hundred load steps are required. Compared to the ALL and positive N options, it can save disk space since the .LDHI file is smaller and fewer .Xnnn files are written.

If Ldstep = -N, all other Ldstep options specified by RESCONTROL are ignored and the program follows the -N option (write load history information every Nth load step). If you want to change this pattern, issue RESCONTROL,DELETE, -N and then issue another RESCONTROL command with the desired Ldstep option.

NONE

 — 

No multiframe restart files (.RDB [restart database file], .LDHI [load history file], .Xnnn) are created. This option is the default for mode-superposition analyses. The remaining arguments are ignored.

For nonlinear static, linear static, and full transient analyses, this option allows a restart to be done at the last or abort point using the same procedure as in ANSYS 5.5 or earlier (using the .EMAT, .ESAV or .OSAV, and .DB files).

For mode-superposition transient analyses, this option allows a restart from the last point using the .RDSP file and the .DB file.

NONE

 — 

Do not write any .Xnnn files for this load step.

LAST

 — 

Write the .Xnnn files for the last substep of the load step only (default for nonlinear static and full transient analyses).

N

 — 

If N is positive, write the .Xnnn file every Nth substep of a load step. If N is negative, write N equally spaced .Xnnn files within a load step.

In nonlinear static and full transient analyses, negative N is valid only when AUTOTS,ON.

In mode-superposition analyses, negative N is always valid.

-1

 — 

Overwrite existing .Xnnn files (default). The total maximum number of .Xnnn files for one run is 999. If this number is reached before the analysis is complete, the program will reset the .Xnnn file numbering back to 1 and continue to write .Xnnn files; the program keeps the newest 999 restart files and overwrites the oldest restart files. For this option, the maximum number of files can be changed to a number less than 999 by setting the MAXTotalFiles argument.

0

 — 

Do not overwrite any existing .Xnnn files. The total maximum number of .Xnnn files for one run is 999. If this number is reached before the analysis is complete, the analysis continues but no longer writes any .Xnnn files.

N

 — 

The maximum number of .Xnnn files to keep for each load step. When N .Xnnn files have been written for a load step, the program overwrites the first .Xnnn file of that load step for subsequent substeps. The value of N cannot exceed 999. If a total of 999 restart files is reached before the analysis is complete, the analysis continues but no longer writes any .Xnnn files.