86 lines
7.5 KiB
HTML
86 lines
7.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="Job characteristics" />
|
||
|
|
<meta name="abstract" content="Work management provides a way for you to control the work done on your system through a job's attributes. However, before you can control the various aspects of a job, you need to understand the different characteristics of a job." />
|
||
|
|
<meta name="description" content="Work management provides a way for you to control the work done on your system through a job's attributes. However, before you can control the various aspects of a job, you need to understand the different characteristics of a job." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutjobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobnamesyntax.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobattributes.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobdescription.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobdescnsecurity.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakscallstacks.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutjobclassobj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobuseridentity.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobuseridexample.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksthreadstructure.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakslockedobjstructure.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="rzaksjobcharacter" />
|
||
|
|
<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>Job characteristics</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksjobcharacter"><a name="rzaksjobcharacter"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Job characteristics</h1>
|
||
|
|
<div><p> Work management provides a way for you to control the work done
|
||
|
|
on your system through a job's attributes. However, before you
|
||
|
|
can control the various aspects of a job, you need to understand the different
|
||
|
|
characteristics of a job.</p>
|
||
|
|
<p>The following information describes the characteristics of jobs:</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobnamesyntax.htm">Job name syntax</a></strong><br />
|
||
|
|
To make it easier to control and identify jobs on the system, each job has a unique qualified job name. The qualified job name consists of three parts: the job name (or simple job name), the user name, and the job number.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobattributes.htm">Job Attributes</a></strong><br />
|
||
|
|
Job attributes determine how the system runs each job. Some job
|
||
|
|
attributes are set from the user profile. Other job attributes come from system
|
||
|
|
values, from locales, from a Submit Job (<span class="cmdname">SBMJOB</span>) command,
|
||
|
|
from a job description, and from the Change Job (<span class="cmdname">CHGJOB</span>)
|
||
|
|
command (from which you can change values for attributes while the job is
|
||
|
|
running). </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobdescription.htm">Job description</a></strong><br />
|
||
|
|
The job description allows you to create a set of job attributes that are saved and available for multiple uses. The job description can be used as the source for some of the job attributes that tell the system how to run a job. The attributes tell the system when to start the job, where to get the job from, and how the job will run. You can think of a job description as a template that many jobs can use, thereby reducing the number of specific parameters that you need to set for each individual job.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobdescnsecurity.htm">Job descriptions and security</a></strong><br />
|
||
|
|
Every job in the system uses a job description during job initiation. This controls the various attributes of a job. The USER parameter controls the name of the user profile assigned to the job. A job description that has a user profile name (USER) specified should be authorized only to specific individuals. If not, at security level 30 and below, other users will be able to submit jobs to run under that user profile.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakscallstacks.htm">Call stacks</a></strong><br />
|
||
|
|
The <dfn class="term">call stack </dfn>is the ordered list of all programs
|
||
|
|
or procedures currently running for a job. The programs and procedures can
|
||
|
|
be started explicitly with the CALL instruction, or implicitly from some other
|
||
|
|
event. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaboutjobclassobj.htm">Class object</a></strong><br />
|
||
|
|
A class object contains the run attributes that control the run-time environment of a job. IBM-supplied class objects, or classes, meet the needs of both typical interactive and batch applications. The following classes (by name) are supplied with the system:</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobuseridentity.htm">Job user identity</a></strong><br />
|
||
|
|
The <dfn class="term">job user identity (JUID)</dfn> is the name of the user
|
||
|
|
profile by which this job is known to other jobs. This name is used for authorization
|
||
|
|
checks when other jobs attempt to operate against this job. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjobuseridexample.htm">Job user identity examples</a></strong><br />
|
||
|
|
This topic contains examples that will help you to better understand how the job user identity (JUID) is assigned in different situations.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksthreadstructure.htm">Threads</a></strong><br />
|
||
|
|
The term thread is shorthand for "thread of control". A thread is the path taken by a program while running, the steps performed, and the order in which the steps are performed. A thread runs code from its starting location in an ordered, predefined sequence for a given set of inputs.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakslockedobjstructure.htm">Locked objects</a></strong><br />
|
||
|
|
Jobs and threads use objects to process work.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksaboutjobs.htm" title="All work done on a system is performed through jobs. Each job has a unique name within the system. All jobs, with the exception of system jobs, run within subsystems. A job can enter the subsystem from any of the work entries, such as a job queue entry, workstation entry, communications entry, autostart job entry, or prestart job entry.">Jobs</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|