81 lines
5.5 KiB
HTML
81 lines
5.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="copyright" content="(C) Copyright IBM Corporation 2005" />
|
|
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
|
|
<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="Authorities, user profiles, and file capabilities of the to-file created by Copy File (CPYF)" />
|
|
<meta name="abstract" content="When the Copy File (CPYF) command creates the local physical file, the from-file gives the created to-file all the authorities of the from-file. These authorities include public, private, and authorization lists." />
|
|
<meta name="description" content="When the Copy File (CPYF) command creates the local physical file, the from-file gives the created to-file all the authorities of the from-file. These authorities include public, private, and authorization lists." />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3copyto.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3copyto.htm" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rbal3copyauth" />
|
|
<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>Authorities, user profiles, and file capabilities of the to-file created
|
|
by Copy File (CPYF)</title>
|
|
</head>
|
|
<body id="rbal3copyauth"><a name="rbal3copyauth"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Authorities, user profiles, and file capabilities of the to-file created
|
|
by Copy File (CPYF)</h1>
|
|
<div><p>When the Copy File (CPYF) command creates the local physical file,
|
|
the from-file gives the created to-file all the <dfn class="term">authorities</dfn> of
|
|
the from-file. These authorities include public, private, and authorization
|
|
lists. </p>
|
|
<p>When <a href="../cl/cpyfrmqryf.htm">CPYFRMQRYF</a> creates the local physical file, the authorities
|
|
given are of the first file that is specified on the FILE parameter of the
|
|
corresponding <a href="../cl/opnqryf.htm">Open
|
|
Query File (OPNQRYF)</a> command. The authorities include public, private,
|
|
and authorization lists.</p>
|
|
<p>In both cases, the owner of the created to-file is the <dfn class="term">user profile</dfn> running
|
|
the copy command. The user running the copy command inherits *ALL authority
|
|
to the object. This is true unless the user is a member of a group profile
|
|
and has OWNER(*GRPPRF) specified for the profile.</p>
|
|
<p>If you specify OWNER(*GRPPRF), the group profile becomes the owner of the
|
|
to-file. In this case, if the user profile running the copy command does not
|
|
have authority to add a member or write data to the new file, the copy command
|
|
fails.</p>
|
|
<div class="p">The created to-file does not maintain the file capabilities of the from-file.
|
|
The to-file allows update, delete, read, and write operations, regardless
|
|
of whether the from-file allowed these operations. Following are special considerations
|
|
for the new to-file: <ul><li>If the number of records copied into a member is greater than the maximum
|
|
size of the created to-file, the to-file is extended without intervention
|
|
by the system operator.</li>
|
|
<li>If the from-file is an SQL table, view, or index, the created to-file
|
|
will be a physical file that is not an SQL table. However, when the from-file
|
|
contains LOBs, datalinks, or user-defined types, the created to-file is an
|
|
SQL table.</li>
|
|
<li>If the from-file is an SQL table, the default values are not preserved.
|
|
The default data type value will apply to the created physical file.</li>
|
|
<li>If the from-file has a trigger program associated with it, the <a href="../cl/cpyf.htm">CPYF</a> and <a href="../cl/cpyfrmqryf.htm">CPYFRMQRYF</a> commands do not copy the trigger information
|
|
to the to-file when the CRTFILE parameter is used.</li>
|
|
<li>If you create a new file (CRTFILE(*YES)) from a file with constraints,
|
|
the constraint definitions do not copy to the new file.</li>
|
|
<li>If you create a new file (CRTFILE(*YES)) from a file with user-defined
|
|
functions, the user-defined functions do not copy to the new file.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal3copyto.htm" title="To copy a physical or logical file when no to-file exists to receive the data, you can create the to-file by specifying CRTFILE(*YES).">Create the to-file (CRTFILE parameter)</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rbal3copyto.htm" title="To copy a physical or logical file when no to-file exists to receive the data, you can create the to-file by specifying CRTFILE(*YES).">Create the to-file (CRTFILE parameter)</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |