70 lines
4.5 KiB
HTML
70 lines
4.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 user identity examples" />
|
||
|
|
<meta name="abstract" content="This topic contains examples that will help you to better understand how the job user identity (JUID) is assigned in different situations." />
|
||
|
|
<meta name="description" content="This topic contains examples that will help you to better understand how the job user identity (JUID) is assigned in different situations." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobcharacter.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="rzaksjobuseridexample" />
|
||
|
|
<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 user identity examples</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksjobuseridexample"><a name="rzaksjobuseridexample"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Job user identity examples</h1>
|
||
|
|
<div><p>This topic contains examples that will help you to better
|
||
|
|
understand how the job user identity (JUID) is assigned in different situations.</p>
|
||
|
|
<ul><li>A job runs under a user profile called USERA. The JUID is USERA. If the
|
||
|
|
job uses the QWTSETP API to switch to USERB, the JUID changes to USERB.<blockquote>In
|
||
|
|
this situation, the Set By value for the JUID is *DEFAULT. Because the job
|
||
|
|
that is running single-threaded, the job user identity is the current user
|
||
|
|
profile under which the initial thread of the job is running (unless, the
|
||
|
|
job user identity was explicitly set by an application). For job queue jobs
|
||
|
|
and completed jobs, the job user identity is the user name from the qualified
|
||
|
|
job name. </blockquote>
|
||
|
|
</li>
|
||
|
|
<li>A single-threaded job runs under user profile USERX. The JUID is USERX.
|
||
|
|
If the job initiates secondary threads, the JUID remains as USERX. If all
|
||
|
|
the threads then swap to USERY, the JUID is still USERX.<blockquote>In this situation,
|
||
|
|
the Set By value for the JUID is *SYSTEM. Because this is an active job which
|
||
|
|
is currently running as a multi-threaded job, the job user identity is implicitly
|
||
|
|
set by the system. The job user identity is set to the name of the user profile
|
||
|
|
under which the job was running when the job became multi-threaded. When the
|
||
|
|
job returns to running single-threaded, the job user identity will be reset
|
||
|
|
to the *DEFAULT value.</blockquote>
|
||
|
|
</li>
|
||
|
|
<li>If a server running under a user profile called SERVER calls the QWTSJUID
|
||
|
|
API, the JUID will be set to SERVER. If the server then calls the Set Profile
|
||
|
|
(QWTSETP) API to set its current user profile to CLIENT while processing work
|
||
|
|
on behalf of that client, the JUID remains as SERVER. Likewise, if the server
|
||
|
|
initiates secondary threads that each call QWTSETP to run under various user
|
||
|
|
profiles, the JUID remains as SERVER.<blockquote>In this situation, the Set By value
|
||
|
|
for the JUID is *APPLICATION. The job user identity is set explicitly by an
|
||
|
|
application using an API. This value applies to both single-threaded and multi-threaded
|
||
|
|
jobs. </blockquote>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksjobcharacter.htm" title="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.">Job characteristics</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|