76 lines
4.4 KiB
HTML
76 lines
4.4 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="reference" />
|
||
|
|
<meta name="DC.Title" content="Use the STEP debug command" />
|
||
|
|
<meta name="abstract" content="The default number of statements to run, using the STEP debug command, is one. However you can change the step number." />
|
||
|
|
<meta name="description" content="The default number of statements to run, using the STEP debug command, is one. However you can change the step number." />
|
||
|
|
<meta name="DC.subject" content="command, STEP debug" />
|
||
|
|
<meta name="keywords" content="command, STEP debug" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="cldbinstruction.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="clstepthrdg" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Use the STEP debug command</title>
|
||
|
|
</head>
|
||
|
|
<body id="clstepthrdg"><a name="clstepthrdg"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Use the STEP debug command</h1>
|
||
|
|
<div><p>The default number of statements to run, using the STEP debug command,
|
||
|
|
is one. However you can change the step number.</p>
|
||
|
|
<div class="section"><p>To step through a program object using the STEP
|
||
|
|
debug command, type the following on the debug command line:</p>
|
||
|
|
<pre>STEP number-of-statements</pre>
|
||
|
|
<p><span class="synph"><span class="var">Number-of-statements</span></span> is the number
|
||
|
|
of statements of the program object that you want to run in the next step
|
||
|
|
before the program object is stopped again. For example, type the following
|
||
|
|
on the debug command line:</p>
|
||
|
|
<pre>STEP 5</pre>
|
||
|
|
<p>The next five statements of your program object are run, then
|
||
|
|
the program object is stopped again and the Display Module Source display
|
||
|
|
is shown.</p>
|
||
|
|
<p>Alternatively, you can use the STEP OVER debug command to
|
||
|
|
step over a called program object in a debug session. To use the STEP OVER
|
||
|
|
debug command, type the following on the debug command line: </p>
|
||
|
|
<pre>STEP number-of-statements OVER</pre>
|
||
|
|
<p>If one of the statements that are run contains a CALL statement
|
||
|
|
to another program object, the ILE source debugger steps over the called program
|
||
|
|
object.</p>
|
||
|
|
<p>You can also use the STEP INTO debug command to step into a
|
||
|
|
called program object in a debug session. To use the STEP INTO debug command,
|
||
|
|
type the following on the debug command line: </p>
|
||
|
|
<pre>STEP number-of-statements INTO</pre>
|
||
|
|
<p>If one of the statements that are run contains a CALL statement
|
||
|
|
to another program object, the debugger steps into the called program object.
|
||
|
|
Each statement in the called program object is counted in the step. If the
|
||
|
|
step ends in the called program object then the called program object is shown
|
||
|
|
in the Display Module Source display. For example, type the following on the
|
||
|
|
debug command line:</p>
|
||
|
|
<pre>STEP 5 INTO</pre>
|
||
|
|
<p>The next five statements of the program object are run. If
|
||
|
|
the third statement is a CALL statement to another program object, then two
|
||
|
|
statements of the calling program object are run and the first three statements
|
||
|
|
of the called program object are run.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="cldbinstruction.htm" title="After a breakpoint is encountered, you can run a specified number of statements of a program object, then stop the program again.">Use instruction stepping</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|