70 lines
4.7 KiB
HTML
70 lines
4.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="concept" />
|
|
<meta name="DC.Title" content="Input/output considerations for files shared in a job or activation group" />
|
|
<meta name="abstract" content="Listed here are the considerations for processing a database file that is shared in the same job or activation group." />
|
|
<meta name="description" content="Listed here are the considerations for processing a database file that is shared in the same job or activation group." />
|
|
<meta name="DC.subject" content="input/output, sharing files in a job, sharing files in an activation group, database file, sharing in a job, input/output considerations, sharing in an activation group" />
|
|
<meta name="keywords" content="input/output, sharing files in a job, sharing files in an activation group, database file, sharing in a job, input/output considerations, sharing in an activation group" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbafosfile.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rbafoiocon" />
|
|
<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>Input/output considerations for files shared in a job or activation
|
|
group</title>
|
|
</head>
|
|
<body id="rbafoiocon"><a name="rbafoiocon"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Input/output considerations for files shared in a job or activation
|
|
group</h1>
|
|
<div><p>Listed here are the considerations for processing a database file
|
|
that is shared in the same job or activation group.</p>
|
|
<div class="p"><ul><li>Because only one open data path is allowed for a shared file, only one
|
|
record position is maintained for all the programs in the job or activation
|
|
group that is sharing the file. If a program establishes a position for a
|
|
record using a read or a read-for-update operation, and then calls another
|
|
program that also uses the shared file, the record position might have moved
|
|
or a record lock been released when the called program returns to the calling
|
|
program. This can cause errors in the calling program because of an unexpected
|
|
record position or lock condition. When sharing files, it is your responsibility
|
|
to manage the record position and record locking considerations by re-establishing
|
|
position and locks.</li>
|
|
<li>If a shared file is first opened for update operation, this does not necessarily
|
|
cause every subsequent program that shares the file to request a record lock.
|
|
The system determines the type of record lock needed for each program using
|
|
the file. The system tries to keep lock contention to a minimum, while still
|
|
ensuring data integrity. <p>For example, PGMA is the first program in the
|
|
job or activation group to open a shared file. PGMA intends to update records
|
|
in the file; therefore, when the program reads a record for update operation,
|
|
it locks the record. PGMA then calls PGMB. PGMB also uses the shared file,
|
|
but it does not update any records in the file; PGMB just reads records. Even
|
|
though PGMA originally opened the shared file as update-capable, PGMB does
|
|
not lock the records it reads, because of the processing specifications in
|
|
PGMB. Thus, the system ensures data integrity, while minimizing record lock
|
|
contention.</p>
|
|
</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbafosfile.htm" title="By default, the database management system lets one file be read and changed by many users at the same time. However, you can share the database files in the same job or activation group through the SHARE parameter.">Share database files in the same job or activation group</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |