<!doctype HTML public "-//W3C//DTD HTML 4.0 Frameset//EN">

<html>

<!--(==============================================================)-->
<!--(Document created with RoboEditor. )============================-->
<!--(==============================================================)-->

<head>

<title>The Post Debugging Tool</title>

<!--(Meta)==========================================================-->

<meta name=generator content="RoboHELP by eHelp Corporation - www.ehelp.com">
<meta name=generator-major-version content=0.1>
<meta name=generator-minor-version content=1>
<meta name=filetype content=kadov>
<meta name=filetype-version content=1>
<meta name=page-count content=1>
<meta name=layout-height content=2260>
<meta name=layout-width content=666>
<meta name=date content="10 24, 2005 8:52:24 AM">


<!--(Links)=========================================================-->

<link rel="StyleSheet" href="../../css/main_styles.css">



<!--(Style Sheet)===================================================-->

<style>
<!--
body {background-color: #ffffff;}
-->
</style>


</head>

<!--(Body)==========================================================-->


<body class="bodydocs" onLoad="top.pageLoader()" bgcolor="#FFFFFF">


<h1>The Post DebuggingTool</h1>

<h2>The Debugging Tool</h2>

<p CLASS=Paragraph>There is a debugging tool to assist you in debugging 
 your Post postprocessor.</p>

<p CLASS=Paragraph>The debugging tool can be found in the TCL file named 
 <span style="font-weight: bold;">mom_debug.tcl</span>.</p>

<p CLASS=Paragraph>The Post debugging tool allows you to see the events 
 and their associated variables as they are triggered while postprocessing. 
 You can step through all the events as they are triggered one by one and 
 see the values assigned to associated variables in the events while postprocessing.</p>

<h2>Activating the Debugging Tool</h2>

<p CLASS=Paragraph>To activate the debugging tool, two things must be done.</p>

<p CLASS=Paragraph>First, the file <span style="font-weight: bold;">mom_debug.tcl</span> 
 must be &quot;sourced&quot; at the beginning of the event handler file. 
 This file contains the event debugging tool and should be specified with 
 the complete path, as shown in the following example:</p>

<p CLASS=ListBulletTxt>source /usr/eds105/mom_tools/mom_debug.tcl</p>

<p CLASS=Paragraph>Second, the debug mode must be turned on by placing 
 the following command immediately after the &quot;source mom_debug.tcl&quot; 
 statement in the event handler.</p>

<p CLASS=ListBulletTxt>MOM_set_debug_mode ON</p>

<p CLASS=Paragraph>To have the debugger available at all times in the event 
 handler, place these statements in the script, but outside of any proc.</p>

<p CLASS=Paragraph>The debugging tool creates a trace that lists the values 
 of addresses and variables that are loaded for each event. Refer to Error 
 Messages for an example of an Output File that was created with the debug 
 feature activated.</p>

<h2>Using the Debugging Tool</h2>

<p CLASS=Paragraph>After after activating the debugger as described above, 
 the dialog shown in the following figure is displayed when the postprocessor 
 is executed.</p>

<h1><a NAME=debug_dialog></a>The Debug Dialog</h1>

<p CLASS=Image>The Debug dialog allows you to specify the type of information 
 that you want to see for each event.<span style="text-align: left; margin-left: 320px;"><img 
 src="../graphics/debug_evenfi02.gif"
	x-maintain-ratio=true
	style="border-style: none;
			width: 193px;
			height: 236px;
			float: none;"
	width=193
	height=236
	border=0></span></p>

<p CLASS=Figure><span style="text-align: left; margin-left: 360px;">Debug 
 Dialog</span></p>

<p CLASS=Paragraph>The Debug dialog options are described as follows:</p>

<h2>Variables</h2>

<p CLASS=Paragraph>When toggled ON, the variables associated with the current 
 event, and their values, are written out to the Debug information window.</p>

<h2>Addresses</h2>

<p CLASS=Paragraph>When toggled ON, the addresses associated with the current 
 event, and their values, are written out to the Debug information window.</p>

<p CLASS=Paragraph>The default status of this button is ON.</p>

<h2>Display Event Numbers</h2>

<p CLASS=Paragraph>When toggled ON, the event number associated with the 
 current event is written out to the Debug information window.</p>

<p CLASS=Paragraph>The default status of this button is OFF.</p>

<h2>Debug in Range</h2>

<p CLASS=Paragraph>By switching this toggle button ON and specifying the 
 &quot;From&quot; event number and &quot;To&quot; event number and choosing 
 <span style="font-style: italic;"><span style="font-style: normal;">OK</span></span>, 
 you can debug the events occurring within the specified range. The information 
 related to events occurring outside of the specified range will not be 
 displayed debug information window.</p>

<p CLASS=Paragraph>When toggled ON, the event number associated with the 
 current event is written out to the Debug information window.</p>

<p CLASS=Paragraph>The default status of this button is OFF.</p>

<h2>OK</h2>

<p CLASS=Paragraph>This executes Post in debug mode.</p>

<h2>Cancel</h2>

<p CLASS=Paragraph>This executes Post without debug mode.</p>

<h1><a NAME=infor_window></a>The Debug Information Window</h1>

<p CLASS=Image><img src="../graphics/debug_evenat05.gif"
					x-maintain-ratio=true
					style="border-style: none;
							margin-top: 0px;
							margin-bottom: 0px;
							margin-left: 0px;
							margin-right: 0px;
							width: 525px;
							height: 330px;
							float: none;"
					width=525
					height=330
					border=0></p>

<p CLASS=Figure>Debug Information Window</p>

<h2>Step</h2>

<p CLASS=Paragraph>Selecting <span style="font-weight: bold;">Step</span> 
 causes Post to execute the next event and write specified information 
 to the Debug information window. The figure above illustrates how the 
 Debug information might look with the Variables, Addresses and Display 
 event numbers options all active.</p>

<h2>Go</h2>

<p CLASS=Paragraph>Selecting Go causes Post to execute to completion without 
 further display of individual event information.</p>

<ul>
	
	<li class=kadov-P-CNote><p CLASS=Note>The Post debugging tool also 
 creates a file &quot;mom_debug_all.out&quot;. This file is created in 
 the directory where the NX session was started. This file contains a listing 
 of all the events, associated variables, and addresses that have been 
 triggered during postprocessing. This file is overwritten every time the 
 Post debugging tool is executed.</p></li>
</ul>

<p>&nbsp;</p>

<h1 CLASS=Section
	style="margin-bottom: 0;">&nbsp; </h1>

</body>

</html>
