58 lines
3.8 KiB
HTML
58 lines
3.8 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="concept" />
|
||
|
<meta name="DC.Title" content="Precautions to take when coding trigger programs" />
|
||
|
<meta name="abstract" content="Trigger programs can be very powerful. But you must take caution when coding trigger programs." />
|
||
|
<meta name="description" content="Trigger programs can be very powerful. But you must take caution when coding trigger programs." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbaforzahftrb2.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbafotrgfn.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbafotrgncmd.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="rbaforzahftre" />
|
||
|
<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>Precautions to take when coding trigger programs</title>
|
||
|
</head>
|
||
|
<body id="rbaforzahftre"><a name="rbaforzahftre"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Precautions to take when coding trigger programs</h1>
|
||
|
<div><p>Trigger programs can be very powerful. But you must take caution
|
||
|
when coding trigger programs. </p>
|
||
|
<p>Be careful when designing trigger programs that access a system resource,
|
||
|
such as a tape drive. For instance, a trigger program that copies record changes
|
||
|
to tape media can be useful, but the program itself cannot detect if the tape
|
||
|
drive is ready or if it contains the correct tape. You must take these kinds
|
||
|
of resource issues into considerations when designing trigger programs.</p>
|
||
|
<p>In addition, use read triggers with extreme caution. Using
|
||
|
a read trigger causes a trigger to be called for every record that is read.
|
||
|
During a query, this means that triggers can be called many times as records
|
||
|
are processed multiple times by the query. This can impact system performance.</p>
|
||
|
</div>
|
||
|
<div>
|
||
|
<ul class="ullinks">
|
||
|
<li class="ulchildlink"><strong><a href="rbafotrgfn.htm">Functions to use with care in trigger programs</a></strong><br />
|
||
|
Some control language (CL) commands and functions are not recommended in a trigger program and need to be carefully considered if they are to be used.</li>
|
||
|
<li class="ulchildlink"><strong><a href="rbafotrgncmd.htm">Commands, statements, and operations that you cannot use in trigger programs</a></strong><br />
|
||
|
A trigger program cannot include some commands, statements, and operations.</li>
|
||
|
</ul>
|
||
|
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbaforzahftrb2.htm" title="These topics discuss recommendations, precautions, and error messages for trigger programs. Information about monitoring and commitment control is also included.">Other important information about working with triggers</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|