80 lines
4.9 KiB
HTML
80 lines
4.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="reference" />
|
|
<meta name="DC.Title" content="PL/I input/output requests" />
|
|
<meta name="abstract" content="This topic discusses the types of PL/I input/output requests and their restrictions." />
|
|
<meta name="description" content="This topic discusses the types of PL/I input/output requests and their restrictions." />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5xplcon.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5plop.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="rbae5pliio" />
|
|
<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>PL/I input/output requests</title>
|
|
</head>
|
|
<body id="rbae5pliio"><a name="rbae5pliio"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">PL/I input/output requests</h1>
|
|
<div><p>This topic discusses the types of PL/I input/output
|
|
requests and their restrictions.</p>
|
|
<div class="section"><h4 class="sectiontitle">Read requests</h4><ul><li>A KEYSEARCH parameter value of BEFORE or EQLBFR is not supported by CICS/DDM
|
|
when accessing a VSAM path. However, these parameter values are supported
|
|
when accessing a VSAM KSDS.</li>
|
|
<li>A POSITION parameter value of PREVIOUS and LAST is not supported when
|
|
accessing a VSAM path. However, these parameter values are supported when
|
|
accessing a VSAM KSDS.</li>
|
|
<li>Because the DIRECT or SEQUENTIAL KEYED attributes cannot be used to open
|
|
a VSAM ESDS, it is not possible to access records by relative record number
|
|
or to have the relative record number returned by using the KEY and KEYTO parameters. </li>
|
|
<li>Because VSAM KSDS and VSAM alternate indexes are always defined as a single
|
|
key field, the NBRKEYFLDS parameter should not be used.</li>
|
|
</ul>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Write requests</h4><ul><li>The KEYFROM parameter does not work when writing a record to a VSAM RRDS.</li>
|
|
<li>The WRITE request does not work when writing a record to VSAM KSDS that
|
|
already contains a record with the same key value.</li>
|
|
<li>Because the OUTPUT or UPDATE file attribute cannot be used to open a VSAM
|
|
path, it is not possible to write records to a VSAM path. Instead, the application
|
|
program must write the record by using the base data set of the VSAM path.</li>
|
|
</ul>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Rewrite requests</h4><ul><li>The REWRITE does not work if rewriting a record of a VSAM KSDS when the
|
|
key value of the record is changed.</li>
|
|
<li>Because the UPDATE file attribute cannot be used to open a VSAM path,
|
|
it is not possible to rewrite records in a VSAM path. Instead, the application
|
|
program must rewrite the record by using the base data set of the VSAM path.</li>
|
|
</ul>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Delete requests</h4><ul><li>The DELETE does not work when deleting the record of a VSAM ESDS.</li>
|
|
<li>Because the UPDATE file attribute cannot be used to open a VSAM path,
|
|
it is not possible to delete records in a VSAM path. Instead, the application
|
|
program must delete the records by using the base data set of the VSAM path.
|
|
However, if the base data set of the VSAM path is a VSAM ESDS, the DELETE
|
|
does not work.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5xplcon.htm" title="These topics summarize the limitations that exist when using PL/I to access remote VSAM data sets from an iSeries server. These limitations should be considered in addition to those already stated in this topic collection.">PL/I considerations</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rbae5plop.htm" title="The i5/OS DDM user can access remote CICS files with PL/I programs.">PL/I open file requests</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |