116 lines
8.0 KiB
HTML
116 lines
8.0 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="task" />
|
||
|
|
<meta name="DC.Title" content="Debug OPM programs" />
|
||
|
|
<meta name="abstract" content="You can debug your OPM programs by using testing functions." />
|
||
|
|
<meta name="description" content="You can debug your OPM programs by using testing functions." />
|
||
|
|
<meta name="DC.subject" content="job, batch, testing functions, interactive, debugging" />
|
||
|
|
<meta name="keywords" content="job, batch, testing functions, interactive, debugging" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="debugprog.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="stdbg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="pgmin.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="unmsg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="brkpt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="trace.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="dspfu.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="dspva.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="chgva.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="usejobdg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="dbgmi.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="tesec.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="temprmdg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbam6probas.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="uslib.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="opm" />
|
||
|
|
<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>Debug OPM programs</title>
|
||
|
|
</head>
|
||
|
|
<body id="opm"><a name="opm"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Debug OPM programs</h1>
|
||
|
|
<div><p>You can debug your OPM programs by using testing functions. </p>
|
||
|
|
<div class="section"> <p>Testing functions are designed to help you write and maintain
|
||
|
|
your applications. Testing functions let you run your programs in a special
|
||
|
|
testing environment while closely observing and controlling the processing
|
||
|
|
of these programs in the testing environment. You can interact with your programs
|
||
|
|
using the testing functions described in this chapter. These functions are
|
||
|
|
available through a set of commands that can be used interactively or in a
|
||
|
|
batch job. The functions allow you to: </p>
|
||
|
|
<ul><li>Trace a program's processing sequence and show the statements processed
|
||
|
|
and the values of program variables at each point in the sequence.</li>
|
||
|
|
<li>Stop at any statement in a program (called a breakpoint) and receive control
|
||
|
|
to perform a function such as displaying or changing a variable value or calling
|
||
|
|
another user-defined program.</li>
|
||
|
|
</ul>
|
||
|
|
<p>No special commands specifically for testing are contained
|
||
|
|
in the program being tested. The same program being tested can be run normally
|
||
|
|
without changes. All test commands are specified within the job the program
|
||
|
|
is in, not as a permanent part of the program being tested. With the testing
|
||
|
|
commands, you interact with the programs symbolically in the same terms as
|
||
|
|
the high-level language (HLL) program was written in. You refer to variables
|
||
|
|
by their names and statements by their numbers. (These are the numbers used
|
||
|
|
in the program's source list.) In addition, the test functions are only applicable
|
||
|
|
to the job they are set up in. The same program can be used at the same time
|
||
|
|
in another job without being affected by the testing functions set up.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="stdbg.htm">Start debug mode</a></strong><br />
|
||
|
|
Debug mode is a special environment in which the testing functions can be used in addition to the normal system functions.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="pgmin.htm">Display the call stack</a></strong><br />
|
||
|
|
You can use the <span class="cmdname">Display Debug (DSPDBG)</span> command
|
||
|
|
to display the call stack.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="unmsg.htm">Handle unmonitored messages</a></strong><br />
|
||
|
|
In an interactive debug job, when a function check occurs, the system provides default handling and gives you control instead of stopping the program.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="brkpt.htm">Use breakpoints</a></strong><br />
|
||
|
|
A breakpoint is a place in a program at which the system stops
|
||
|
|
program processing and gives control to you at a display station (interactive
|
||
|
|
mode) or to a program specified on the BKPPGM parameter in the <span class="cmdname">Add
|
||
|
|
Breakpoint (ADDBKP)</span> command (batch mode).</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="trace.htm">Use traces</a></strong><br />
|
||
|
|
A trace is the process of recording the sequence in which the statements in a program are processed.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="dspfu.htm">Display testing information</a></strong><br />
|
||
|
|
In debug mode, you can display testing information that lets you review how you have set up your debug job.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="dspva.htm">Display the values of variables</a></strong><br />
|
||
|
|
You can display the values of program variables when you are at a breakpoint.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="chgva.htm">Change the values of variables</a></strong><br />
|
||
|
|
You can change the values of variables while in debug mode.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="usejobdg.htm">Use a job to debug another job</a></strong><br />
|
||
|
|
You may want to use a separate job to debug programs running in another job.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="dbgmi.htm">Debug at the machine interface level</a></strong><br />
|
||
|
|
You can debug your programs at the machine interface (MI) level.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="tesec.htm">Security considerations</a></strong><br />
|
||
|
|
To debug a program, you must have *CHANGE authority to that program.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="temprmdg.htm">Operations that temporarily remove breakpoints</a></strong><br />
|
||
|
|
Breakpoints or statement traces may be temporarily removed from a program while the debug function is running if you use certain control language (CL) commands to specify your library or program.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="debugprog.htm" title="Debugging allows you to detect, diagnose, and eliminate errors in a program. This gives how-to information for debugging ILE and OPM programs.">Debug CL programs and procedures</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="uslib.htm" title="A library is an object used to group related objects and to find objects by name. Thus, a library is a directory to a group of objects.">Use libraries</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbam6probas.htm" title="The operating system includes functions that let a programmer observe operations performed as a program runs.">Parameter values used for testing and debugging</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|