ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzake_5.4.0.1/cusg.htm

71 lines
3.7 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="Usage for ICF files (position 38)" />
<meta name="abstract" content="The valid entries for this position are listed here." />
<meta name="description" content="The valid entries for this position are listed here." />
<meta name="DC.subject" content="usage positional entry" />
<meta name="keywords" content="usage positional entry" />
<meta name="DC.Relation" scheme="URI" content="cmnfl.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2001, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2001, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="cusg" />
<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>Usage for ICF files (position 38)</title>
</head>
<body id="cusg"><a name="cusg"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Usage for ICF files (position 38)</h1>
<div><p>The valid entries for this position are listed here.</p>
<div class="section">
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><thead align="left"><tr valign="bottom"><th valign="bottom" id="d0e22">Entry</th>
<th valign="bottom" id="d0e24">Meaning</th>
</tr>
</thead>
<tbody><tr><td valign="top" headers="d0e22 ">B or blank</td>
<td valign="top" headers="d0e24 ">Both input/output field</td>
</tr>
<tr><td valign="top" headers="d0e22 ">P</td>
<td valign="top" headers="d0e24 ">Program-to-system field</td>
</tr>
</tbody>
</table>
</div>
<p>A program-to-system field is used to communicate between an application
program and the sending system (which is local to the application program).
It is not sent as part of the data record across the line to the receiving
system.</p>
<div class="p">The following rules apply to program-to-system fields: <ul><li>The field must be a named, numeric, or alphanumeric output-only field.</li>
<li>In the record format, the program-to-system fields must be defined after
all the data fields (those with a use of B or blank).</li>
<li>A field cannot be defined as both a data field and a program-to-system
field; the field names must be unique.</li>
<li>A program-to-system field can be named on an EVOKE, SECURITY, TIMER, or
VARLEN keyword.</li>
<li>The only valid keywords for a program-to-system field are ALIAS, FLTPCN,
REFFLD and TEXT.</li>
</ul>
</div>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="cmnfl.htm" title="Here are some rules and examples for filling in positions 1 through 44 of the data description specifications (DDS) form.">Define an ICF file using DDS</a></div>
</div>
</div>
</body>
</html>