60 lines
3.9 KiB
HTML
60 lines
3.9 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="Open considerations for inline data files" />
|
||
|
|
<meta name="abstract" content="The following considerations apply to opening inline data files:" />
|
||
|
|
<meta name="description" content="The following considerations apply to opening inline data files:" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakssubmitbatchjob.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="rzaksidfoc" />
|
||
|
|
<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>Open considerations for inline data files</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksidfoc"><a name="rzaksidfoc"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Open considerations for inline data files</h1>
|
||
|
|
<div><p>The following considerations apply to opening inline data files: </p>
|
||
|
|
<ul><li>Record length specifies the length of the input records. (Record length
|
||
|
|
is optional.) When the record length exceeds the length of the data, a message
|
||
|
|
is sent to your program. The data is padded with blanks. When the record length
|
||
|
|
is less than the data length, the records are truncated. </li>
|
||
|
|
<li>When a file is specified in a program, the server searches for the file
|
||
|
|
as a named inline data file before it searches for the file in a library.
|
||
|
|
Therefore, if a named inline data file has the same name as a file that is
|
||
|
|
not an inline data file, the inline data file is always used, even if the
|
||
|
|
file name is qualified by a library name. </li>
|
||
|
|
<li>Named inline data files can be shared between programs in the same job
|
||
|
|
by specifying SHARE(*YES) on a create file or override file command. For example,
|
||
|
|
if an override file command specifying a file named INPUT and SHARE(*YES)
|
||
|
|
is in a batch job with an inline data file named INPUT, any programs running
|
||
|
|
in the job that specify the file name INPUT will share the same named inline
|
||
|
|
data file. Unnamed inline data files cannot be shared between programs in
|
||
|
|
the same job.</li>
|
||
|
|
<li>When you use inline data files, you should make sure the correct file
|
||
|
|
type is specified on the //DATA command. For example, if the file is to be
|
||
|
|
used as a source file, the file type on the //DATA command must be source. </li>
|
||
|
|
<li>Inline data files must be opened for input only.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakssubmitbatchjob.htm" title="Since batch jobs are typically low priority jobs that require a special system environment in which to run (such as running at night) they are placed in batch job queues. In the job queue the batch job receives a run time schedule and a priority. To submit a job to a batch job queue, you use the character-based interface and one of two commands.">Submit a batch job</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|