67 lines
6.8 KiB
HTML
67 lines
6.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="Communications entries" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutworkentries.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutautostartentry.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="DC.Relation" scheme="URI" content="rzaksaddcommunentry.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakschgcommunentry.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksrmvcommunentry.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="rzaksaboutcommentry" />
|
|
<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>Communications entries</title>
|
|
</head>
|
|
<body id="rzaksaboutcommentry"><a name="rzaksaboutcommentry"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Communications entries</h1>
|
|
<div><p>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.</p>
|
|
<p> For performance reasons, instead of starting a communications job each
|
|
time a program start request is received, you can configure a prestart job
|
|
to handle a program start request from a remote system. For a
|
|
communications batch job to run on an iSeries™ system, a subsystem description
|
|
containing a work entry for communications work must exist on the system. </p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksaboutworkentries.htm" title="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.">Work entries</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzaksaboutautostartentry.htm" title="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.">Autostart job entries</a></div>
|
|
<div><a href="rzaksaboutjobqentries.htm" title="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.">Job queue entries</a></div>
|
|
<div><a href="rzaksprestartentryx.htm" title="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.">Prestart job entries</a></div>
|
|
<div><a href="rzakspjeforservers.htm" title="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.">Prestart jobs for servers</a></div>
|
|
<div><a href="rzaksaboutwrkstationentry.htm" title="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.">Workstation entries</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzaksaddcommunentry.htm" title="Each communication entry describes one or more communication device, device types, or remote location for which the subsystem will start jobs when program start requests are received. The subsystem can allocate a communication device if the device is not currently allocated to another subsystem or job. A communications device that is currently allocated may eventually be de-allocated, making it available to other subsystems. To add a communications entry to the subsystem description, use the character-based interface.">Add communications entries</a></div>
|
|
<div><a href="rzakschgcommunentry.htm" title="You can change the attributes of an existing communications entry in an existing subsystem description by using the character-based interface.">Change communication entries</a></div>
|
|
<div><a href="rzaksrmvcommunentry.htm" title="You can remove communication entries from the subsystem description by using the character-based interface. All jobs that are active through the communications entry being removed must be ended before this command can be run.">Remove communication entries</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |