94 lines
7.0 KiB
HTML
94 lines
7.0 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="reference" />
|
||
|
|
<meta name="DC.Title" content="ALCOBJ (Allocate Object) command" />
|
||
|
|
<meta name="abstract" content="When the name of a DDM file is specified on the Allocate Object (ALCOBJ) command on the source server, the command allocates the DDM file on the source server and its associated file or file member on a target server." />
|
||
|
|
<meta name="description" content="When the name of a DDM file is specified on the Allocate Object (ALCOBJ) command on the source server, the command allocates the DDM file on the source server and its associated file or file member on a target server." />
|
||
|
|
<meta name="DC.subject" content="command, DDM-related, CL command considerations, ALCOBJ (Allocate Object), command, CL, ALCOBJ (Allocate Object), command, Allocate Object (ALCOBJ), command, CL, Allocate Object (ALCOBJ), object, allocating, DDM file, locking considerations" />
|
||
|
|
<meta name="keywords" content="command, DDM-related, CL command considerations, ALCOBJ (Allocate Object), command, CL, ALCOBJ (Allocate Object), command, Allocate Object (ALCOBJ), command, CL, Allocate Object (ALCOBJ), object, allocating, DDM file, locking considerations" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5cmdcnsd.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5memnames.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5lock.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5alctime.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5allocatecom.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbae5alcobj" />
|
||
|
|
<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>ALCOBJ (Allocate Object) command</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5alcobj"><a name="rbae5alcobj"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1"><span class="cmdname">ALCOBJ (Allocate Object)</span> command</h1>
|
||
|
|
<div><p>When the name of a DDM file is specified on the <span class="cmdname">Allocate
|
||
|
|
Object (ALCOBJ)</span> command on the source server, the command allocates
|
||
|
|
the DDM file on the source server and its associated file or file member on
|
||
|
|
a target server.</p>
|
||
|
|
<div class="section"><p>The command places locks on both the DDM file and the remote file
|
||
|
|
in each pair. (These files are locked on both servers to ensure that they
|
||
|
|
are not changed or deleted while the files or members are locked.) One
|
||
|
|
or more pairs of files (DDM files on the source server and remote files on
|
||
|
|
one or more target servers) can be allocated at the same time.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Each DDM file is always locked with a shared-read (*SHRRD) lock.
|
||
|
|
Shared-read is used for the DDM files regardless of the lock types that might
|
||
|
|
have been specified on the command to lock other local files at the same time.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>The lock placed on the <em>remote file</em> depends on the type
|
||
|
|
of target server:</p>
|
||
|
|
<ul><li>When the target is an <span class="keyword">iSeries™ server</span> or
|
||
|
|
a <span class="keyword">System/38™</span>, the resulting locks
|
||
|
|
on the remote file are the same as if the file is a local database file. That
|
||
|
|
is, the <span class="keyword">iSeries</span> or the <span class="keyword">System/38</span> remote file is also locked
|
||
|
|
with a shared-read lock, and the member (the one specified, or the first one)
|
||
|
|
is locked with the lock type specified on the command.</li>
|
||
|
|
<li>When the target is <em>not</em> an <span class="keyword">iSeries server</span> or
|
||
|
|
a <span class="keyword">System/38</span>, the remote file
|
||
|
|
is locked with the specified lock type, except that some non-<span class="keyword">iSeries</span> target
|
||
|
|
servers might use a stronger lock than was specified on the command. If an <span class="cmdname">ALCOBJ</span> command
|
||
|
|
specifies multiple DDM files, and one or more are on non-<span class="keyword">iSeries</span> target
|
||
|
|
servers, those remote files are locked with the lock type specified on the
|
||
|
|
command. If a member name is specified for a remote server that does not support
|
||
|
|
members, the lock request is rejected with an error message, unless the member
|
||
|
|
name is the same as the DDM file name.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5memnames.htm">Member names and iSeries target servers on the ALCOBJ command</a></strong><br />
|
||
|
|
If a member name is specified with the DDM file name on an <span class="cmdname">ALCOBJ</span> command,
|
||
|
|
the member (in the remote file) is locked with the lock type specified on
|
||
|
|
the command.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5lock.htm">Lock multiple DDM files with the ALCOBJ command</a></strong><br />
|
||
|
|
One <span class="cmdname">ALCOBJ</span> command can be used to specify multiple
|
||
|
|
DDM files that are associated with remote files located on multiple target
|
||
|
|
servers. If it is not possible to lock all the files on all the servers, none
|
||
|
|
are locked.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5alctime.htm">ALCOBJ command completion time with DDM</a></strong><br />
|
||
|
|
When DDM-related files are being allocated, a longer time will be required for the command to complete because of the additional time required for communications to occur between the source and target servers.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5cmdcnsd.htm" title="This topic collection describes DDM-related specifics about iSeries CL commands when they are used with DDM files. These topics discuss running the commands on the source server and do not discuss them being submitted to run on the target server by the Submit Remote Command (SBMRMTCMD) command.">DDM-related CL command considerations</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rbae5allocatecom.htm" title="The ALCOBJ command locks DDM files on the source server and the associated remote files on the target servers.">Allocate Object (ALCOBJ) and Deallocate Object (DLCOBJ) commands</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|