<!-- source-page: 541 -->

# 3.2.43 JOB EXECUTION CONTROL

Products: Abaqus/Standard Abaqus/Explicit Abaqus/CFD

# Reference

• “Execution procedure for Abaqus: overview,” Section 3.1.1

# Overview

The execution procedures for job execution control include abaqus suspend, abaqus resume, and abaqus terminate. These utilities are used to suspend, resume, and terminate Abaqus analysis jobs. Suspending an analysis job will stop its execution and release its license tokens to the free-token pool. Resuming an analysis will reactivate a suspended job and check out license tokens for that job if they are available. The job will be placed in the license queue if license tokens are not available. Terminating an analysis job will stop the executable for the analysis and release its license tokens. A terminated analysis job cannot be resumed.

You can execute these commands remotely; you are not required to execute these commands on the machine running the analysis.

# Command summary

abaqus {suspend | resume | terminate} {job=job-name | host=hostname port=port-number}

# Command line options

# job

This option is used to specify the name of the analysis job to suspend, resume, or terminate. When using this option, the command must be executed from the working directory of the job. The command reads the job-name.cid file to obtain the host name and port number used to signal the job.

# host

This option is used to specify the host name for the connection running the analysis job. This option must be used in conjunction with the port option. The host name can be identified by reading the last line of the job-name.cid file, which lists hostname:port-number.

# port

This option is used to specify the port number for the connection running the analysis job. This option must be used in conjunction with the host option. The port number can be identified by reading the last line of the job-name.cid file, which lists hostname:port-number.

<!-- source-page: 542 -->

<!-- source-page: 543 -->

# 3.2.44 HARDWARE SYSTEM VERIFICATION PROCESS

Products: Abaqus/Standard Abaqus/Explicit Abaqus/CFD

# Reference

• “Execution procedure for Abaqus: overview,” Section 3.1.1

# Overview

The hardware system verification tool provides a way to ensure that the hardware running the Abaqus solvers provides the same results data as that obtained at SIMULIA during Quality Assurance testing. Systems in a shared resource pool may have several variations of hardware and software packages installed to accommodate numerous software applications. This procedure will provide confidence that the Abaqus solver products are running and generating the same results as those obtained at SIMULIA.

Tests can be executed in serial mode or in parallel mode as specified by the cpus option. The tool can be submitted via the queue option to test various resources in the shared pool. Part of the validation is to execute with distributed memory parallel using MPI technology.

# Command summary

abaqus sysVerify

[cpus=number-of-cpus]

[interactive | background | queue[=queue-name] ]

# Command line options

# cpus

This option is used to specify the number of processors to use during the verification. If the cpus option is not defined or is set to 1, only the serial tests are executed during the validation. If the cpus option is set to 4, both serial and parallel tests are executed with the parallel tests using MPI with 2 cores on two nodes.

# interactive

This option is used to run the process interactively with the actual analysis still running in the background. The status of the testing is displayed to the screen as the tests are executed. The default run\_mode can be set in the environment file (see “Using the Abaqus environment settings,” Section 3.3.1).

# background

This option is used to submit the process to run in the background, which is the default. Log file output is saved in the file systemValidation.log in the current directory. The default method for submitting the job can be set in the environment file by using the run\_mode parameter (see “Using the Abaqus environment settings,” Section 3.3.1).

<!-- source-page: 544 -->

# queue

This option is used to submit the process to a batch queue. If the option appears with no value, the process is submitted to the system default queue. Quoted strings are allowed. The available queues are site specific. Contact your site administrator to find out more about local queuing capabilities. Use information=local to see what local queuing capabilities have been installed. The default method for submitting the process can be set in the environment file by using the run\_mode parameter (see “Using the Abaqus environment settings,” Section 3.3.1).

<!-- source-page: 545 -->

# 3.3 Environment file settings

• “Using the Abaqus environment settings,” Section 3.3.1

<!-- source-page: 546 -->

<!-- source-page: 547 -->

# 3.3.1 USING THE Abaqus ENVIRONMENT SETTINGS

Products: Abaqus/Standard Abaqus/Explicit

# Reference

• “Execution procedure for Abaqus: overview,” Section 3.1.1

# Overview

The Abaqus environment settings allow you to control various aspects of an Abaqus job’s execution. For example, you can

• “Tune” Abaqus to improve its performance by changing memory-related parameters.   
• Control where and how scratch files are written.   
• Provide default values for job parameters that would otherwise have to be given on the command line.

Many other aspects of a job’s execution can be configured through the environment settings. Some of these are discussed in this section; others, which are mainly of interest to the Abaqus site manager, are discussed in detail in the Abaqus Installation and Licensing Guide.

# Environment settings hierarchy

Abaqus environment settings are processed in the following order:

1. The host-level environment settings. These settings are applied to all Abaqus jobs run on the designated computer.   
2. The user-level environment settings. These settings are applied to all Abaqus jobs run in your account.

For Abaqus to locate the environment file in your home directory on Windows platforms, the full path to your home directory must be specified using the HOME environment variable or a combination of the HOMEDRIVE and HOMEPATH environment variables.

3. The job-level environment settings. These settings are applied to only the designated Abaqus job.

Environment settings can be specified more than once. The last value processed will be the one used for the setting if it is defined at more than one level or if it is given twice at the same level.

Abaqus environment settings are set using special files in specific directories. The host-level (site-level) settings are set in the solvers\_install\_dir/os/SMA/site/custom\_v6.env file or abaqus\_v6.env file in the Abaqus services (solvers) installation. You can change these settings by creating an environment file named abaqus\_v6.env in your home directory and/or the current directory. Settings in the home directory file will be applied to all jobs that you run. Settings in the current directory file will be applied only to jobs run from the current directory.

<!-- source-page: 548 -->

# Syntax

The entries given in the environment file must be given using Python language syntax. Entries take the form:

# parameter=value

The following is a brief overview of the Python syntax rules:

• The parameter must always have a value. The value can be any valid Python constant or expression.   
• A string value must be enclosed in a pair of double or single quotes.   
• Comments are preceded by a number sign (#). All characters following a number sign on a line are ignored. Number signs within a quoted string are part of the string, not the beginning of a comment.   
• Blank lines are ignored.   
• Embedded single quotes do not require special handling if they are placed within a double quoted string. For example, "my value’s" is translated as my value’s. The same holds true for double quotes embedded in a single quoted string. Quotes of the same type as the enclosing quotes can be embedded if they are prefixed by the backslash (\) character.   
• Triple quoted (""") strings can span more than one line, and no special treatment of quotes within the string is necessary. Entries take the form:

```txt
parameter="" multi-line value "" 
```

• Lists must be enclosed in parentheses (( )) or square brackets ([ ]). Individual items in the list are separated by commas. If the list is enclosed in parentheses and contains only one value, a comma has to follow the value. String list items must be enclosed in quotes. Entries take the form:

```txt
parameter=(value1, value2, value3) 
```

# Troubleshooting

Problems caused by faulty environment settings can be diagnosed by using the command

abaqus information=environment

This command prints all of the current environment settings.

# Command line default parameters

The following parameters provide default values for various settings that would otherwise have to be specified on the command line (see “Abaqus/Standard, Abaqus/Explicit, and Abaqus/CFD execution,” Section 3.2.2, and “Abaqus/Standard, Abaqus/Explicit, Abaqus/CFD, AND FMU co-simulation

<!-- source-page: 549 -->

execution,” Section 3.2.4). Values given on the command line override values specified in the environment files.

# cpus

Number of processors to use if parallel processing is available. The default is 2 for the co-simulation execution procedure; otherwise, the default is 1.

# domains

The number of parallel domains in Abaqus/Explicit. If the value is greater than 1, the domain decomposition will be performed regardless of the values of the parallel and cpus parameters. However, if parallel=domain, the value of cpus must be evenly divisible into the value of domains. If this parameter is not set, the number of domains defaults to the number of processors used during the analysis run if parallel=domain or to 1 if parallel=loop.

# double\_precision

The default precision version of Abaqus/Explicit to run if you do not specify the precision version on the abaqus command line. Possible values are EXPLICIT (only the Abaqus/Explicit analysis is run in double precision), BOTH (both the Abaqus/Explicit packager and analysis are run in double precision), CONSTRAINT (the constraint packager and constraint solver in Abaqus/Explicit are run in double precision, while the Abaqus/Explicit packager and analysis continue to run in single precision), or OFF (both the Abaqus/Explicit packager and analysis are run in single precision). The default is OFF.

# parallel

The default parallel method in Abaqus/Explicit if you do not specify the parallel method on the abaqus command line. Possible values are DOMAIN or LOOP; the default value is DOMAIN.

# run\_mode

Default run mode (interactive, background, or batch) if you do not specify the run mode on the abaqus command line. The default for abaqus analysis and abaqus sysVerify is "background", while the default for abaqus viewer is "interactive".

# scratch

Directory to be used for scratch files. This directory must exist (i.e., it will not be created by Abaqus) and must have write permission assigned. On Linux platforms the default value is the value of the \$TMPDIR environment variable or /tmp if \$TMPDIR is not defined. On Windows platforms the default value is the value of the %TEMP% environment variable or \TEMP if this variable is not defined. During the analysis a subdirectory will be created under this directory to hold the analysis scratch files. The name of the subdirectory is constructed from your user name, the job id, and the job’s process identifier. The subdirectory and its contents are deleted upon completion of the analysis.

<!-- source-page: 550 -->

# standard\_parallel

The default parallel execution mode in Abaqus/Standard if you do not specify the parallel mode on the abaqus command line. If this parameter is set equal to ALL, both the element operations and the solver will run in parallel. If this parameter is set equal to SOLVER, only the solver will run in parallel. The default parallel execution mode is ALL.

# gpus

The GPGPU direct solver acceleration setting in Abaqus/Standard if you do not specify the GPGPU solver acceleration option on the abaqus command line. By default, GPGPU solver acceleration is not activated. The value of this parameter is the number of GPGPUs to be used in an Abaqus/Standard analysis. In an MPI-based analysis, this is the number of GPGPUs to be used on each host.

# unconnected\_regions

If this variable is set to ON, Abaqus/Standard will create element and node sets in the output database for unconnected regions in the model during a datacheck analysis. Element and node sets created with this option are named MESH COMPONENT N, where N is the component number. The default value is OFF.

# order\_parallel

The ordering mode for the direct sparse solver in Abaqus/Standard if you do not specify the ordering mode on the abaqus command line. If this parameter is set equal to OFF, the ordering procedure will not run in parallel. If this parameter is set equal to ON, the ordering procedure will run in parallel. The default ordering mode is ON.

# System resource parameters

The following environment file variable can be set after the code has been installed to change the resources used by Abaqus and, therefore, to improve system performance. By default, Abaqus detects the physical memory on a machine (or on each compute node in a cluster) and allocates a percentage of the available memory based on the machine platform (for details, refer to the Dassault Systèmes Knowledge Base at www.3ds.com/support/knowledge-base). You can override the default percentage by specifying a number followed by the percentage sign. The variable can also be defined as the number of megabytes or the number of gigabytes. More detailed information about changing the system resources used by Abaqus is given in “Managing memory and disk use in Abaqus,” Section 3.4.1.

# memory

Maximum amount of memory or maximum percentage of the physical memory that can be allocated during the input file preprocessing and during the Abaqus/Standard analysis phase. For parallel execution on computer clusters, this memory limit specifies the maximum amount of memory that can be allocated on each process.
