112 lines
9.9 KiB
HTML
112 lines
9.9 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="Interactive jobs" />
|
||
<meta name="abstract" content="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." />
|
||
<meta name="description" content="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." />
|
||
<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="rzaksaboutcommunicationjobs.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="rzakshowintactivejobstarts.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzakshowintjobend.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaksi0errorjobrecovery.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaksinteractivejobnrouting.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaksintactvjbroutingcontrol.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaksintjbrtngwrkstationvsuserbased.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaksjobsendatsametime.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="rzaksinteractivejob" />
|
||
<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>Interactive jobs</title>
|
||
</head>
|
||
<body id="rzaksinteractivejob"><a name="rzaksinteractivejob"><!-- --></a>
|
||
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
<h1 class="topictitle1">Interactive jobs</h1>
|
||
<div><p>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.</p>
|
||
<p>Interactive jobs require continual two-way communications between the user
|
||
and the iSeries™ to
|
||
perform a task. An interactive job begins when a user signs on to a system.
|
||
The system requests signon information. If the signon request is accepted
|
||
by the system, then the system creates the interactive job. The system then
|
||
asks the user to supply a request. The user enters a request, and the system
|
||
responds by processing the request. This pattern is repeated until the user
|
||
ends the interactive job by signing off the system, or the job ends due to
|
||
an application exception or device error recovery.</p>
|
||
<p>If an interactive job is part of a group of jobs or a pair of jobs, then
|
||
it will have one of the following job types:</p>
|
||
<dl><dt class="dlterm">Interactive - Group</dt>
|
||
<dd>An Interactive - Group job is part of a group of jobs that is associated
|
||
with a single display device.</dd>
|
||
</dl>
|
||
<dl><dt class="dlterm">Interactive - System request</dt>
|
||
<dd>An Interactive - System request job is one of a pair of jobs that is associated
|
||
with each other by the system request function.</dd>
|
||
</dl>
|
||
<p><strong>Did you know? </strong>You can sign on to the system in two ways. You can
|
||
manually enter the system by using a user id and password. You can also create
|
||
a program to automatically send the user id and password to the server, thereby
|
||
bypassing the signon screen.</p>
|
||
</div>
|
||
<div>
|
||
<ul class="ullinks">
|
||
<li class="ulchildlink"><strong><a href="rzakshowintactivejobstarts.htm">How an interactive job starts</a></strong><br />
|
||
When a user signs on to the system, the subsystem gathers information from several system objects before the interactive job is ready.</li>
|
||
<li class="ulchildlink"><strong><a href="rzakshowintjobend.htm">Disconnect interactive jobs</a></strong><br />
|
||
When the Disconnect Job (<span class="cmdname">DSCJOB</span>) command is
|
||
called, the job is disconnected and the signon display is shown again. To
|
||
connect with the job again, sign on to the same device from which you disconnected.
|
||
Another interactive job may be started on the device under a different user
|
||
name.</li>
|
||
<li class="ulchildlink"><strong><a href="rzaksi0errorjobrecovery.htm">I/O error for job requester device</a></strong><br />
|
||
A requester device is a workstation from which a user can log on
|
||
to a domain and use network resources. The Device Recovery Action (<span class="cmdname">DEVRCYACN</span>)
|
||
job attribute specifies what action to take when an I/O error occurs for a
|
||
job’s requester device. </li>
|
||
<li class="ulchildlink"><strong><a href="rzaksinteractivejobnrouting.htm">Interactive jobs and routing steps</a></strong><br />
|
||
Before the initial menu is called the routing data is compared with the routing entries in the subsystem description. When a match is made, the program specified in the routing entry is called and the routing step is started.</li>
|
||
<li class="ulchildlink"><strong><a href="rzaksintactvjbroutingcontrol.htm">Programs that control the routing step</a></strong><br />
|
||
To determine the best approach for a particular job, you must first determine which program should control the routing step.</li>
|
||
<li class="ulchildlink"><strong><a href="rzaksintjbrtngwrkstationvsuserbased.htm">Workstation versus user based routing</a></strong><br />
|
||
After you have determined which program controls the routing step, you must determine if routing is to be based on the workstation from which the job was started, or on the user (user profile) who signed on.</li>
|
||
<li class="ulchildlink"><strong><a href="rzaksjobsendatsametime.htm">When jobs end at the same time</a></strong><br />
|
||
Sometimes, jobs end at the same time. For example, a network error occurs and the job attributes are set to *ENDJOB or *ENDJOBNOLIST. In addition to the job ending, the following device recovery actions occur.</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="rzaksaboutcommunicationjobs.htm" title="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.">Communication 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> |