80 lines
5.1 KiB
HTML
80 lines
5.1 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="Domain concepts" />
|
||
|
<meta name="abstract" content="All objects are assigned a domain attribute when they are created." />
|
||
|
<meta name="description" content="All objects are assigned a domain attribute when they are created." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="concept.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="../apis/quscrtuq.htm#uq_domain" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="ExTaskDataque.htm" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="conDomain" />
|
||
|
<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>Domain concepts</title>
|
||
|
</head>
|
||
|
<body id="conDomain"><a name="conDomain"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Domain concepts</h1>
|
||
|
<div><p>All objects are assigned a domain attribute when they are created.</p>
|
||
|
<p>A <em>domain</em> is a characteristic of an object that controls how programs
|
||
|
can access the object. Once set, the domain remains in effect for the life
|
||
|
of the object. The two possible attributes are <em>system</em> and <em>user</em>.</p>
|
||
|
<p>Most object types on the system are created in system domain. When you
|
||
|
run your system at security level 40 or 50, system domain objects can be accessed
|
||
|
only by using the commands and callable APIs provided.</p>
|
||
|
<p>These object types can be either system or user domain. The list includes
|
||
|
the symbolic object type.</p>
|
||
|
<ul><li>User space (*USRSPC)</li>
|
||
|
<li>User index (*USRIDX)</li>
|
||
|
<li>User queue (*USRQ)</li>
|
||
|
</ul>
|
||
|
<p>Objects of the type *USRSPC, *USRIDX, and *USRQ in the user domain can
|
||
|
be manipulated directly by MI instructions without using the system-provided
|
||
|
APIs and commands.</p>
|
||
|
<div class="note"><span class="notetitle">Note:</span> Objects of the type *PGM, *SRVPGM, and *SQLPKG also can be in the user
|
||
|
domain. Their contents cannot be manipulated directly by MI instructions.</div>
|
||
|
<p>Prior to Version 2 Release 3 Modification 0, all user objects were created
|
||
|
into the user domain. Starting in Version 2 Release 3 Modification 0, user
|
||
|
objects can exist in either the user domain or the system domain. The allow
|
||
|
user domain (QALWUSRDMN) system value determines which libraries can contain
|
||
|
user-domain user objects. The default QALWUSRDMN system value is set to *ALL,
|
||
|
but can be changed by system administrators on individual machines to be one
|
||
|
library or a list of libraries. If your application requires direct pointer
|
||
|
access to user-domain user objects in a library that is not specified in the
|
||
|
QALWUSRDMN value, your system administrator can add the library to the system
|
||
|
value.</p>
|
||
|
<p>The ability to create user domain objects on a system with a security level
|
||
|
40 or 50 is controlled by the allow user domain (QALWUSRDMN) system value.
|
||
|
See the User queue domain table in the description of the Create
|
||
|
User Queue (QUSCRTUQ) API for more information.</p>
|
||
|
<div class="note"><span class="notetitle">Note:</span> On a system configured for C2 system security, QALWUSRDMN is set to
|
||
|
QTEMP (only the QTEMP library can contain user-domain user objects).</div>
|
||
|
<p>For more information about C2 security, refer to the <cite>Guide to Enabling
|
||
|
C2 Security</cite> book, SC41-0103.</p>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="concept.htm" title="Describes the underlying concepts that you need to understand to work effectively with APIs. Among the concepts covered are basic concepts, programming considerations, and terminology.">API concepts</a></div>
|
||
|
</div>
|
||
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
<div><a href="../apis/quscrtuq.htm#uq_domain">User queue domain</a></div>
|
||
|
<div><a href="ExTaskDataque.htm" title="Data queues and user queues both provide a means for one or more processes to communicate asynchronously. The queues can be processed FIFO (first-in first-out), LIFO (last-in first-out), or by key.">Examples: Using data queues or user queues</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|