66 lines
5.8 KiB
HTML
66 lines
5.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="Work entries" />
|
||
|
|
<meta name="abstract" content="Work entries identify the sources where jobs can enter a subsystem. Specific types of work entries are used for different types of jobs. Work entries are part of the subsystem description." />
|
||
|
|
<meta name="description" content="Work entries identify the sources where jobs can enter a subsystem. Specific types of work entries are used for different types of jobs. Work entries are part of the subsystem description." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssbsd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutautostartentry.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutcommentry.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutjobqentries.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksprestartentryx.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakspjeforservers.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutwrkstationentry.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004-2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004-2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaksaboutworkentries" />
|
||
|
|
<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>Work entries</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksaboutworkentries"><a name="rzaksaboutworkentries"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Work entries</h1>
|
||
|
|
<div><p>Work entries identify the sources where jobs can enter a subsystem.
|
||
|
|
Specific types of work entries are used for different types of jobs. Work
|
||
|
|
entries are part of the subsystem description.</p>
|
||
|
|
<p>The following information describes the different types of work entries
|
||
|
|
and how to manage them. There are five types of work entries; autostart job
|
||
|
|
entries, communication entries, job queue entries, prestart job entries, and
|
||
|
|
workstation entries.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaboutautostartentry.htm">Autostart job entries</a></strong><br />
|
||
|
|
Autostart job entries identify the autostart jobs to start as soon as the subsystem starts. When a subsystem starts, the system allocates several items and starts autostart and prestart jobs before it is ready for work.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaboutcommentry.htm">Communications entries</a></strong><br />
|
||
|
|
The communications work entry identifies to the subsystem the sources for the communications job it will process. The job processing begins when the subsystem receives a communications program start request from a remote system and an appropriate routing entry is found for the request.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaboutjobqentries.htm">Job queue entries</a></strong><br />
|
||
|
|
Job queue entries in a subsystem description specify from which job queues a subsystem is to receive jobs. When the subsystem is started, the subsystem tries to allocate each job queue defined in the subsystem job queue entries.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksprestartentryx.htm">Prestart job entries</a></strong><br />
|
||
|
|
You define the prestart job by using a prestart job entry. A prestart job entry does not affect the device allocation or program start request assignment.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakspjeforservers.htm">Prestart jobs for servers</a></strong><br />
|
||
|
|
In the prestart job model there is one primary listening job, generally called the daemon job or listener job, and multiple server jobs that process the client requests. The daemon job listens on the port for connection requests. When a new connection is received, the daemon does some general work, then gives the socket descriptor to a waiting prestart server job.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaboutwrkstationentry.htm">Workstation entries</a></strong><br />
|
||
|
|
An interactive job is a job that starts when a user signs on to a display station and ends when the user signs off. For the job to run, the subsystem searches for the job description, which may be specified in the workstation entry or the user profile.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakssbsd.htm" title="A subsystem description is a system object that contains information defining the characteristics of an operating environment controlled by the system. The system-recognized identifier for the object type is *SBSD. A subsystem description defines how, where, and how much work enters a subsystem, and which resources the subsystem uses to perform the work. An active subsystem takes on the simple name of the subsystem description.">Subsystem description</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|