The final step in coupling an EASAP to underlying software applications after manipulating user inputs and creating template batch files is to actually run the software applications using the appropriate commands.

These commands are contained within PROCESS.

If an EASAP requires that more than one software application be executed, then multiple PROCESS's can be created on the PROCESSES branch, one for each software application. An example case for multiple PROCESS's is presented below:

• process1: Run CAD package to generate model geometry
• process2: Run mesh generator to generate mesh
• process3: Run solver to compute analysis results
• process4: Run graphics package to generate output

Other PROCESS tasks might include:

• Executing operating system commands to perform tasks such as copying or deleting files
• Running a VB script to drive a Microsoft® Office product, such as Excel® or Word®.

PROCESS is Parent to a number of Child objects which help define the behaviour of the PROCESS execution.

Object	Description
PROCESS	Issues the commands used to run the underlying software applications.
	CLEAR FILESPACE	Minimizes the disk space of files created during a run.
	DATA PROCESSING	Parent to data processing tools
	FAILED IF	Conditions that define 'failed' status for a run.
	MONITOR	Monitors the progress of a submitted process in the EASAP queue.
	REPLACEMENT	Establishes a search-and-replace, replacing an object with its value.

The order of execution within a PROCESS is always:

1. DATA PROCESSING objects such as MAP, EXPAND, COMPUTE, EXTRACT
2. Any REPLACEMENT's in the order specified on the Tree
3. Commands specified in the Run Using: parameter of a PROCESS
4. Any MONITOR's
5. Following completion of commands specified in Run Using: parameter, run any FAILED IF's.
6. CLEAR FILESPACE to delete temporary files

Therefore the order of objects on the Tree within a PROCESS is not important. However, the order of execution of multiple PROCESS objects is based on their order on the Tree, occurring from top to bottom.

When a user clicks on the Stop button () for a run on their My Results page, the run is stopped using the default method as defined in the Compute Server Configuration. This method usually involves the killing of a Process ID (PID). In this case, the run will end abruptly and no results will be generated. However, many software applications support methods of stopping them in a friendlier manner, in which a results file can still be generated. To support the existence of special stopping methods available within software packages EASA provides STOP which is a Parent to one or more STOP PROCESS's.

Another benefit that can be achieved with EASA is to minimize the disk space used in storing results by automatically deleting any very large unneeded files generated by the underlying software applications. The deletion of unwanted files can be accomplished either during the execution of an EASAP run using CLEAR FILESPACE and FILE MANAGEMENT.

The linked page below is a historical list of software that has been run within a PROCESS object.

Syntax of the Run Using: parameter is provided.

• Batch Applications and EASA