91 lines
6.7 KiB
HTML
91 lines
6.7 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="Threads on i5/OS" />
|
||
|
|
<meta name="abstract" content="All programs have at least one thread, referred to as the initial thread. In a program with multiple threads, each thread runs its code independently of the other threads in the program." />
|
||
|
|
<meta name="description" content="All programs have at least one thread, referred to as the initial thread. In a program with multiple threads, each thread runs its code independently of the other threads in the program." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwovepo.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwkerco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwrogco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwourco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwcesco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahweadco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwgrxco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwcmnco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwdbcco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwdmcco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwfscco.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahwprcco.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="rzahwas4-as4co" />
|
||
|
|
<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>Threads on i5/OS</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahwas4-as4co"><a name="rzahwas4-as4co"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Threads on <span class="keyword">i5/OS™</span></h1>
|
||
|
|
<div><p>All programs have at least one thread, referred to as the <em>initial
|
||
|
|
thread</em>. In a program with multiple threads, each thread runs its code
|
||
|
|
independently of the other threads in the program.</p>
|
||
|
|
<p>A <em>process</em> is the container for the
|
||
|
|
memory and resources of the program. On IBM<sup>®</sup> <span><img src="eserver.gif" alt="eServer" /></span> iSeries™ systems,
|
||
|
|
a job represents a process. Each process has at least one thread (task) in
|
||
|
|
which the program runs its code. The first thread in a process is referred
|
||
|
|
to as the initial thread. Some processes are capable of supporting additional
|
||
|
|
threads, which are called secondary threads. </p>
|
||
|
|
<p>The concepts that are described here pertain to all programming languages.
|
||
|
|
For details about how each language enables a concept, refer to the programmer's
|
||
|
|
guide for that specific language.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwkerco.htm">Thread models</a></strong><br />
|
||
|
|
There are different models of thread usage: user threads and kernel threads.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwrogco.htm">Thread program models</a></strong><br />
|
||
|
|
There are different models for creating multithread programs.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwourco.htm">Jobs and job resources</a></strong><br />
|
||
|
|
A <em>job</em> is a container for storage and other resources. A
|
||
|
|
job cannot run by itself. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwcesco.htm">Thread-private data and thread-specific data</a></strong><br />
|
||
|
|
Threads cannot share certain resources. Data that threads cannot share between themselves are called thread-private data.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahweadco.htm">Multithreaded program startup commands</a></strong><br />
|
||
|
|
To call a multithreaded Integrated Language
|
||
|
|
Environment<sup>®</sup> (ILE) program, the job in which the program is called must
|
||
|
|
be capable of supporting multiple threads (multithread-capable). Multithreaded Java™ programs
|
||
|
|
can be called in most jobs (some system jobs restrict the types of programs
|
||
|
|
that can be called).</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwgrxco.htm">Activation groups and threads</a></strong><br />
|
||
|
|
All programs and service programs are activated within a substructure of a job that is called an activation group. This substructure contains the resources necessary to run the programs, including static and heap storage, and temporary data management resources.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwcmnco.htm">Communications considerations for multithreaded programming</a></strong><br />
|
||
|
|
The only threadsafe communications protocol supported on <span class="keyword">i5/OS™</span> is sockets.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwdbcco.htm">Database considerations for multithreaded programming</a></strong><br />
|
||
|
|
You should consider these items when using databases in multithreaded programs.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwdmcco.htm">Data management considerations for multithreaded programming</a></strong><br />
|
||
|
|
You should consider several topics when managing data in a multithreaded program.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwfscco.htm">File system considerations for multithreaded programming</a></strong><br />
|
||
|
|
You should consider several topics when working with file systems in multithreaded programs.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahwprcco.htm">Printer file considerations for multithreaded programming</a></strong><br />
|
||
|
|
Only printer files opened with SPOOL(*YES) are allowed in a job that is capable of multithread operations.</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>
|