<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE html
  SYSTEM "about:legacy-compat">
<html xmlns:mml = "http://www.w3.org/1998/Math/MathML" lang = "en"><head><meta charset = "UTF-8"/><meta name = "copyright" content = "(C) Copyright 2020"/><meta name = "DC.rights.owner" content = "(C) Copyright 2020"/><meta name = "DC.type" content = "concept"/><meta name = "abstract" content = "An indication of where the program terminated can be found in TOSCA.OUT."/><meta name = "description" content = "An indication of where the program terminated can be found in TOSCA.OUT."/><meta name = "DC.format" content = "HTML5"/><meta name = "DC.identifier" content = "tso-c-usr-trouble-detPointProTerm"/><meta name = "DC.language" content = "en"/><link rel = "stylesheet" type = "text/css" href = "../DSDocUI_XML34.css"/><title>About Determining the Point of Program Termination</title>
<script type = "text/javascript" src = "../DSDocUI_Highlight34.js">
  	/* */
  	</script></head><body onLoad = "highlightSearchTerms();" id = "tso-c-usr-trouble-detPointProTerm">
<a name = "hj-top"> </a><table class = "table1" id = "table11"><tr><td><table class = "DocHeader"><tr><td class = "DocHeader1" colspan = "2"><h1>About Determining the Point of Program Termination</h1></td></tr><tr><td class = "DocHeader4" colspan = "2"/></tr><tr><td class = "DocHeader3" colspan = "2"><table class = "DocThemeIntro" id = "table12"><tr><td class = "Intro1Only"><p class = "header"><p class = "abstract">
<span class = "shortdesc">An indication of where the program terminated can be found in
            <code class = "ph codeph">TOSCA.OUT</code>.</span>
</p>

</p></td></tr></table></td></tr></table>




<div class = "body conbody">
<p><br/><img class = "image" src = "../TsoUserImages/xx0c770b.jpg" width = "585" height = "447"/><br/></p>
<p>Trouble shooting in <code class = "ph codeph">TOSCA.OUT</code>. Here, the result reader
                <code class = "ph codeph">RES_2_VTM</code> stops because of missing results files. The reason for
            this error can be found in the logfiles of the FE-solver that has terminated
            incorrectly.</p>
<p>The following four points of the optimization process are known to be the
most frequent in which an error might occur:</p>
<ol class = "ol">
<li class = "li">Stop at the start of the program (configuration, licensing, and control start).</li>
<li class = "li">Stop in a preprocessing step (<code class = "ph codeph">FEM_INCLUDE, FEM_2_ONF, TOSCA_PREP</code>).</li>
<li class = "li">Stop during a FE analysis.</li>
<li class = "li">Stop in an optimization step (<code class = "ph codeph">RES2VTM, TOSCA_OPT, FEM_MODIF</code>).</li>
</ol>
<p>For a more detailed description of the program sequence, see the figure in <a class = "xref" href = "tso-c-usr-control-dataFlow.htm#tso-c-usr-control-dataFlow" title = "The program sequence of an optimization is the same independent of how Tosca Structure is started. You can either use Tosca Structure.gui or start Tosca Structure even in batch modus on the command line.">Program Sequence and Data Flow of Tosca Structure</a>. When the program is
            started, the configuration is first loaded and the licenses are checked. Information
            regarding this can be found in the protocol file authorization.log (see also <a class = "xref" href = "tso-c-usr-control-logging.htm#tso-c-usr-control-logging__tso-c-usr-control-logging-specLogFiles">Special Logfiles</a>).</p>
<p>Afterwards, the <span class = "ph">Tosca Structure</span>
control program will be started. Protocol information will be printed
to the display and to the file <code class = "ph codeph">TOSCA.OUT</code>.</p>
<br/><img class = "image" src = "../TsoUserImages/xx0c40e6.jpg" width = "585" height = "677"/><br/><p>The sequence of configuration
files that are read in the beginning of the optimization will be logged
to <code class = "ph codeph">TOSCA.OUT</code>:</p>
<br/><img class = "image" src = "../TsoUserImages/xx0c410c.jpg" width = "585" height = "93"/><br/><p>For each module that
is started by the control program and finishes, an entry with information
concerning the running time of the module can be found. For example,
in <code class = "ph codeph">TOSCA.OUT</code> in the fourth iteration:</p>
<br/><img class = "image" src = "../TsoUserImages/xx0c4120.jpg" width = "585" height = "34"/><br/><p>The course of the
individual processes and cycles can be seen in the following figure and can be followed in the protocol file <code class = "ph codeph">TOSCA.OUT</code>.
</p>
<p>Several points should be checked depending on where the program stop occurred. These are
            illustrated in the diagram below together with the protocol files where the error
            messages are saved. Different error messages, their causes, and possible ways of
            correcting these errors are also described in the following section. A description of
            which files contain error messages is also given.</p><p><br/><img class = "image" src = "../TsoUserImages/trouble_detPointProgtTerm.png"/><br/></p>
</div>
</td></tr></table><script type = "text/javascript" src = "../DSDocUI_Bottom34.js">/* */</script></body>
</html>
