Windows Queuing System 2.1

Sheet Metal Forming
ESI GmbH & ESI Group

To view the full version of this page (or to download files), please log in or create a new account

This tool is to help users to manage the launch of PAM-STAMP simulations up to 16 CPUs/Cores with a queue in Windows up to versions 2018.0


  • Be administrator of your machine and switch off the User Account Control.
  • Execute the ESI_Queuing-System_2.1_setup.exe attached
  • Follow requirements listed in Help button (Readme) according to your platform: .NET Framework is needed: check the document to install the right one.


  • Run as administrator (right click on the shortcut for doing it)
  • Custom the configuration file if needed, to adapt the paths, and others parameters (To find it: check the installation directory)
  • Load a case, select the number of CPU, solver type: SMD or DMP (64Bit only), precision: SP or DP
  • Add it in the queue
  • Start the queue
  • Follow the progress of your calculation
  • Add others cases in the queue


This tool is aimed to be used up to PAM-STAMP 2018.

Since PAM-STAMP 2019.0, it is needed to use Windows Queuing System 2.2. But there is a workaround which consists to replace pamcsm.exe file by the attached pamcsm.exe file in your PAM-STAMP 2019.0 installation in C:\Program Files (x86)\ESI Group\PAM-STAMP\2019.0\Binary-64Bit\Solver\bin, which will allow to still use Queuing System 2.1 with PAM-STAMP 2019.0. In same time this attached pamcsm file allows also to support Japanese characters.

For more information, read the documentation attached.

Download the file(s)
LOG IN FIRST ESI_Queuing-System_Version_2.1.pdf (1.18 MB)
LOG IN FIRST (862.43 KB)
These pieces of software are provided by the copyright holders and contributors “as is” and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright owners or contributors be liable for any direct, indirect incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) However caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this piece of software, even if advised of the possibility of such damage.