102 lines
8.5 KiB
HTML
102 lines
8.5 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="Communication jobs" />
|
||
|
|
<meta name="abstract" content="A communications job is a batch job that is started by a program start request from a remote system. Job processing involves a communication request and appropriate specifications." />
|
||
|
|
<meta name="description" content="A communications job is a batch job that is started by a program start request from a remote system. Job processing involves a communication request and appropriate specifications." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobtypeoverview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutautostartjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksbatchjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksinteractivejob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksprestarttype.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksreaderandwriterjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksserverjobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssystemjobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakscommunicationtype.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="rzaksaboutcommunicationjobs" />
|
||
|
|
<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>Communication jobs</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksaboutcommunicationjobs"><a name="rzaksaboutcommunicationjobs"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Communication jobs</h1>
|
||
|
|
<div><p>A communications job is a batch job that is started by a program
|
||
|
|
start request from a remote system. Job processing involves a communication
|
||
|
|
request and appropriate specifications.</p>
|
||
|
|
<p>For a communications batch job to run on an i5/OS™ system, a subsystem description containing
|
||
|
|
a work entry for communications jobs must exist on the system. 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>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Routing data for communication jobs</h4><p>Job routing
|
||
|
|
of communications jobs is determined by the program start request that is
|
||
|
|
received from the remote system. When a program start request is processed
|
||
|
|
on the target system, a fixed-length data stream that is used as routing data
|
||
|
|
is created. Position 25 of the routing data will always contain PGMEVOKE for
|
||
|
|
communications requests. Subsystem routing entries that specify a compare
|
||
|
|
value of PGMEVOKE in position 29 typically have *RTGDTA as the program name.
|
||
|
|
This means that the program name specified in the routing data (from the remote
|
||
|
|
system's program start request) is the program to run.</p>
|
||
|
|
<p>If a special
|
||
|
|
processing environment is required for certain communications jobs, you can
|
||
|
|
add an additional routing entry to the subsystem description, specifying a
|
||
|
|
compare value whose starting position is 37. This compare value should contain
|
||
|
|
the program name for the program start request. The routing entry must have
|
||
|
|
a sequence number lower than the routing entry that uses PGMEVOKE as the compare
|
||
|
|
value. This method allows certain communications jobs to run with a different
|
||
|
|
class or pool specification. </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Security</h4><p>The security on the i5/OS system controls who can use communications
|
||
|
|
devices as well as who can access the commands uses with the associated device
|
||
|
|
descriptions. You should consider additional security measures when writing
|
||
|
|
and running application programs on both remote and target systems.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Job description for communication jobs</h4><p>The job description
|
||
|
|
used for communications jobs is specified on the Add Communications Entry
|
||
|
|
(<span class="cmdname">ADDCMNE</span>) command. The user specified on this job description
|
||
|
|
is ignored. The system gets the user name for communications jobs from the
|
||
|
|
program start request. If the program start request does not specify a user
|
||
|
|
name, the system uses the default user value from the communications entry.
|
||
|
|
To ensure a greater degree of system security, include user information about
|
||
|
|
the program start request rather than specifying a default user in the communications
|
||
|
|
work entry.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakscommunicationtype.htm">Types of communications jobs</a></strong><br />
|
||
|
|
This topic describes the most common types of communication jobs.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksjobtypeoverview.htm" title="The iSeries server processes several different types of jobs.">Job types</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaksaboutautostartjob.htm" title="An autostart job is a batch job doing repetitive work, one-time initialization work that is associated with a particular subsystem, initializes functions for an application, or provides centralized service functions for other jobs in the same subsystem. An autostart job in the controlling subsystem can be used to start other subsystems (as does the IBM-supplied controlling subsystem). The autostart jobs associated with a subsystem are automatically started each time the subsystem is started.">Autostart jobs</a></div>
|
||
|
|
<div><a href="rzaksbatchjob.htm" title="A batch job is a predefined group of processing actions submitted to the system to be performed with little or no interaction between the user and the system. Jobs that do not require user interaction to run can be processed as batch jobs. A batch job typically is a low priority job and can require a special system environment in which to run.">Batch jobs</a></div>
|
||
|
|
<div><a href="rzaksinteractivejob.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 can be specified in the workstation entry or the user profile.">Interactive jobs</a></div>
|
||
|
|
<div><a href="rzaksprestarttype.htm" title="A prestart job is a batch job that starts running before a work request is received. The prestart jobs are started before any other types of jobs in a subsystem. Prestart jobs are different from other jobs because they use prestart job entries (part of the subsystem description) to determine which program, class, and storage pool to use when they are started.">Prestart jobs</a></div>
|
||
|
|
<div><a href="rzaksreaderandwriterjob.htm" title="A reader job is a spooled input job, and a writer job is a spooled output job.">Reader and writer jobs</a></div>
|
||
|
|
<div><a href="rzaksserverjobs.htm" title="Server jobs are jobs that run continuously in the background on the iSeries system.">Server jobs</a></div>
|
||
|
|
<div><a href="rzakssystemjobs.htm" title="System jobs are created by the operating system to control system resources and perform system functions. System jobs run when the iSeries server starts or when an independent disk pool is varied on. These jobs perform a variety of tasks from starting the operating system, to starting and ending subsystems, to scheduling jobs.">System jobs</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|