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

89 lines
6.8 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="File error detection and handling by the server" />
<meta name="abstract" content="The server can detect errors when a file is opened, when a program device is acquired or released, during I/O operations to a file, and when the file is closed. When appropriate, the server will automatically try to run a failing operation again, up to a try again limit. When a try again is successful, neither operator nor program action is required." />
<meta name="description" content="The server can detect errors when a file is opened, when a program device is acquired or released, during I/O operations to a file, and when the file is closed. When appropriate, the server will automatically try to run a failing operation again, up to a try again limit. When a try again is successful, neither operator nor program action is required." />
<meta name="DC.subject" content="error recovery, handling, handling application program error, application program, error handling, error, message, file status code, code, file status, major/minor return code, server error log, alert message, alert, permanent errors, job, log error messages, error message" />
<meta name="keywords" content="error recovery, handling, handling application program error, application program, error handling, error, message, file status code, code, file status, major/minor return code, server error log, alert message, alert, permanent errors, job, log error messages, error message" />
<meta name="DC.Relation" scheme="URI" content="rbal3ts.htm" />
<meta name="DC.Relation" scheme="URI" content="../rbam6/rbam6clmain.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzal2/rzal2kickoff.htm" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rbal3eh" />
<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>File error detection and handling by the server</title>
</head>
<body id="rbal3eh"><a name="rbal3eh"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">File error detection and handling by the server</h1>
<div><p>The server can detect errors when a file is opened, when a program
device is acquired or released, during I/O operations to a file, and when
the file is closed. When appropriate, the server will automatically try to
run a failing operation again, up to a try again limit. When a try again
is successful, neither operator nor program action is required.</p>
<div class="section"><h4 class="sectiontitle">How the server reports errors</h4><div class="p">The
server reports errors that can affect the processing of the program in any
or all of the following ways: <ul><li>A notify, status, diagnostic, or escape message might be sent to the program
message queue of the program using the file. These messages might also appear
in the job log, depending on the message logging level that is set for the
job. See <a href="rbal3mmm.htm#rbal3mmm">Messages and message monitors in files by the server</a> for more information.</li>
<li>The high-level language might return a file status code.</li>
<li>A major and minor return code is returned in the I/O feedback area for
intersystem communications function (ICF), display, and printer files. See <a href="rbal3majminrcs.htm#rbal3majminrcs">Major and minor return codes in files by the server</a> for more information.</li>
<li>A notify, status, diagnostic, or escape message might be sent to the operator
message queue (QSYSOPR) or the history message queue (QHST).</li>
<li>Information regarding the error might be saved in the server error log for
use by the problem analysis and resolution programs.</li>
<li>An alert message might be sent to an operator at another server in the network.</li>
<li>The normal program flow might be interrupted and control might be transferred
to an error-handling subroutine, or other language operations might occur. For
additional information about how to handle run-time errors, see the appropriate
book for the high-level language.</li>
</ul>
</div>
<p>Only some of these are significant to a program that is attempting
error recovery.</p>
</div>
<div class="section"><h4 class="sectiontitle">Actions to take when you receive an error</h4><p>See <a href="rbal3recoveryerr.htm#rbal3recoveryerr">Recover from file server errors</a> for information about
the actions you should take when you receive an error.</p>
</div>
<div class="section"><h4 class="sectiontitle">Unrecoverable errors</h4><p>Not all file errors allow programmed
error recovery. Some errors are permanent; that is, the file, device, or
program cannot work until you take some corrective action. This might involve
resetting the device by varying it off and on again, or correcting an error
in the device configuration or the application program. Some messages and
return codes inform the user or the application program of conditions that
are information rather than errors, such as change in the status of a communications
line, or server action taken for an unexpected condition. In many cases,
it is possible for the application program to test for an error condition
and take some preplanned recovery action which allows the program to continue
without intervention from the operator.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal3ts.htm" title="iSeries provides server reports and error messages when errors occur. You can take corresponding actions according to the errors.">Troubleshoot database file management</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../rbam6/rbam6clmain.htm">Control language (CL)</a></div>
<div><a href="../rzal2/rzal2kickoff.htm">Basic system operations</a></div>
</div>
</div>
</body>
</html>