80 lines
5.3 KiB
HTML
80 lines
5.3 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="Specify CRTFILE(*YES) on either the CPYF or CPYFRMQRYF command" />
|
||
|
<meta name="abstract" content="You get different results while specifying CRTFILE(*YES) on the CPYF command and the CPYFRMQRYF command." />
|
||
|
<meta name="description" content="You get different results while specifying CRTFILE(*YES) on the CPYF command and the CPYFRMQRYF command." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbal3copyto.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbal3copyto.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbal3copysel.htm" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="rbal3eitheror" />
|
||
|
<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>Specify CRTFILE(*YES) on either the CPYF or CPYFRMQRYF command</title>
|
||
|
</head>
|
||
|
<body id="rbal3eitheror"><a name="rbal3eitheror"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Specify CRTFILE(*YES) on either the CPYF or CPYFRMQRYF command</h1>
|
||
|
<div><p>You get different results while specifying CRTFILE(*YES) on the
|
||
|
CPYF command and the CPYFRMQRYF command.</p>
|
||
|
<p><strong>If you specify CRTFILE(*YES) on the <a href="../cl/cpyf.htm">CPYF</a> command</strong>, the to-file that is created has the
|
||
|
same record format and type of access path as the from-file. The file level
|
||
|
and the format level identifiers of the new to-file are identical to the file
|
||
|
level and the format level identifiers of the from-file. The text of from-file
|
||
|
members that are copied is used as the text of any to-file members that are
|
||
|
created.</p>
|
||
|
<p>When the from-file is a logical file, the server assigns the
|
||
|
following physical file attributes: SIZE(*NOMAX), ALLOCATE(*NO), and CONTIG(*NO).
|
||
|
If the from-file is a logical file with multiple record formats, the to-file
|
||
|
is created with the format that is specified on the RCDFMT parameter on the
|
||
|
CPYF command.</p>
|
||
|
<p><strong>If you specify CRTFILE(*YES) on the <a href="../cl/cpyfrmqryf.htm">CPYFRMQRYF</a> command</strong>, the file level and the format
|
||
|
level identifiers of the new to-file are generated at the time the new to-file
|
||
|
is created. Furthermore, the physical file's attributes match the first file
|
||
|
that is specified on the FILE parameter of the corresponding <a href="../cl/opnqryf.htm">Open Query File (OPNQRYF)</a> command.
|
||
|
However, the server assigns some of the attributes. The file is created with
|
||
|
CONTIG(*NO), SIZE(*NOMAX), ALLOCATE(*NO), AUT(*NORMAL) and FILETYPE(*DATA).</p>
|
||
|
<p>The name, type, length, null capability, date, or time format, separators,
|
||
|
and decimal positions attributes of each field on the format that is specified
|
||
|
are used. The file is created without key fields and is an arrival sequence
|
||
|
physical file.</p>
|
||
|
<div class="p">In some cases, the OPNQRYF command changes the format of the format that
|
||
|
is specified on the new to-file. The new to-file format might become null-capable
|
||
|
when the OPNQRYF command uses one of the following grouping functions: <ul><li>%STRDEV</li>
|
||
|
<li>%VAR</li>
|
||
|
<li>%SUM</li>
|
||
|
<li>%AVG</li>
|
||
|
<li>%MIN</li>
|
||
|
<li>%MAX</li>
|
||
|
</ul>
|
||
|
<div class="note"><span class="notetitle">Note:</span> A new to-file with a changed format has a format level identifier
|
||
|
that is different from the format level identifier that is specified on the
|
||
|
OPNQRYF command.</div>
|
||
|
</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><a href="rbal3copysel.htm" title="You can use the RCDFMT parameter to select records of a certain record format to copy. Note that you can use this parameter on the CPYF command only.">Selecting records using a specified record format name (RCDFMT parameter)</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|