69 lines
4.6 KiB
HTML
69 lines
4.6 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="Language access and threads" />
|
||
|
|
<meta name="abstract" content="Learn how different languages support threads on i5/OS. This information can help you evaluate how threads can be implemented in your own application." />
|
||
|
|
<meta name="description" content="Learn how different languages support threads on i5/OS. This information can help you evaluate how threads can be implemented in your own application." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwovepo.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwjavco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwceeco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwcppco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwileco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwopmco.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="rzahwlan-lanco" />
|
||
|
|
<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>Language access and threads</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahwlan-lanco"><a name="rzahwlan-lanco"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Language access and threads</h1>
|
||
|
|
<div><p>Learn how different languages support threads on <span class="keyword">i5/OS™</span>.
|
||
|
|
This information can help you evaluate how threads can be implemented in your
|
||
|
|
own application.</p>
|
||
|
|
<p>The concepts that are described in this section pertain to all programming
|
||
|
|
languages. To determine how each language enables these concepts, refer to
|
||
|
|
the <a href="../rzahg/rzahglanguages.htm">Language</a> topic
|
||
|
|
in the information center for the specific language.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwjavco.htm">Threads considerations for Java language</a></strong><br />
|
||
|
|
You can take advantage of <span class="keyword">i5/OS</span> kernel
|
||
|
|
threads using the <span class="filepath">java.lang.Thread</span> class. Java™ threads
|
||
|
|
operate on top of the <span class="keyword">i5/OS</span> kernel
|
||
|
|
threads model. Each Java™ thread is one of many tasks that runs
|
||
|
|
in the process.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwceeco.htm">Threads considerations for C language</a></strong><br />
|
||
|
|
You must evaluate existing C applications for thread safety before calling them in a multithreaded job. If your C program is not threadsafe, techniques are available for calling programs that are not threadsafe from multithreaded jobs.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwcppco.htm">Threads considerations for C++ language</a></strong><br />
|
||
|
|
The C++ runtime functions new, delete, try, catch, and throw are threadsafe.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwileco.htm">Threads considerations for ILE COBOL and RPG language</a></strong><br />
|
||
|
|
You can create an Integrated Language Environment<sup>®</sup> (ILE)
|
||
|
|
COBOL or ILE RPG module that will run safely in a multithreaded environment
|
||
|
|
by serializing access to the module.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwopmco.htm">Threads considerations for OPM language</a></strong><br />
|
||
|
|
Original program model (OPM) programs are not threadsafe.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahwovepo.htm" title="A thread is the path taken by a program while running, the steps performed, and the order in which the steps are performed.">Multithreaded applications</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|