ibm-information-center/dist/eclipse/plugins/i5OS.ic.dm_5.4.0.1/rbal3howalloc.htm

75 lines
5.2 KiB
HTML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?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="How the server allocates resources" />
<meta name="abstract" content="When it allocates resources, the server waits for a predefined time if the resources are not immediately available. If the resources do not become available within the time limit, the server generates an error." />
<meta name="description" content="When it allocates resources, the server waits for a predefined time if the resources are not immediately available. If the resources do not become available within the time limit, the server generates an error." />
<meta name="DC.subject" content="operation, starting program on remote server, allocating resources, WAITFILE parameter, number-of-seconds value (WAITFILE), parameter, WAITFILE" />
<meta name="keywords" content="operation, starting program on remote server, allocating resources, WAITFILE parameter, number-of-seconds value (WAITFILE), parameter, WAITFILE" />
<meta name="DC.Relation" scheme="URI" content="rbal3waitf.htm" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rbal3howalloc" />
<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>How the server allocates resources</title>
</head>
<body id="rbal3howalloc"><a name="rbal3howalloc"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">How the server allocates resources</h1>
<div><p>When it allocates resources, the server waits for a predefined
time if the resources are not immediately available. If the resources do not
become available within the time limit, the server generates an error.</p>
<p>If you are using the <a href="../cl/alcobj.htm">ALCOBJ command</a>, the command fails. If your program is
performing a file operation, that operation fails, and the server sends an
error message to the program message queue. You can use the error-handling
functions of your high-level language to try the operation again. For example,
if an open operation fails because another job is using the device associated
with the file, you can try the open operation a specified number of times
again, in the hope that the other job would finish with the device and your
program would then be able to use it.</p>
<p>The length of time that the server waits when allocating resources is specified
on the <a href="../cl/alcobj.htm">ALCOBJ</a> command
and on the WAITFILE parameter of the CL command used to create the file. If
the ALCOBJ command is used before running a program, then the value of the
WAITFILE parameter does not matter, because the resources will be available.</p>
<p>If your application has error handling procedures for handling device errors
occurring on device files, you should specify a value of something other than
*IMMED to allow the server to recover from the error. The allocation of resources
requested by your program on an open or acquire operation that allows your
program to recover from the error will not be successful until the server
recovery procedures have been completed for the device.</p>
<p>The following list describes the values that are allowed for
the WAITFILE parameter:</p>
<dl><dt class="dlterm">*IMMED</dt>
<dd>This value specifies that no wait time is allowed. An immediate allocation
of the file resources is required.</dd>
<dt class="dlterm">*CLS</dt>
<dd>The job default wait time is used as the wait time for the file resources
to be allocated.</dd>
<dt class="dlterm">number-of-seconds</dt>
<dd>Specify the maximum number of seconds that the program is to wait for
the file resources to be allocated. Valid values are 1 through 32767 (32 767
seconds).</dd>
</dl>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal3waitf.htm" title="Resources are those parts of the server that are required by a job or task, including main storage, devices, the processing unit, programs, files, libraries, and folders. When you write a high-level language program, you should be aware of what resources the server has allocated for each file type.">Allocate file resources</a></div>
</div>
</div>
</body>
</html>