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

70 lines
4.6 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="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="Permanent device or session error on I/O operation" />
<meta name="abstract" content="A major return code of 81 indicates a serious error that affects the device or session." />
<meta name="description" content="A major return code of 81 indicates a serious error that affects the device or session." />
<meta name="DC.subject" content="error, permanent, device, session, return code, description, major 81" />
<meta name="keywords" content="error, permanent, device, session, return code, description, major 81" />
<meta name="DC.Relation" scheme="URI" content="rbal3recoveryerr.htm" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rbal3permdev" />
<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>Permanent device or session error on I/O operation</title>
</head>
<body id="rbal3permdev"><a name="rbal3permdev"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Permanent device or session error on I/O operation</h1>
<div><p>A major return code of 81 indicates a serious error
that affects the device or session.</p>
<p>This includes hardware failures that affect the device, communications
line, or communications controller. It also includes errors due to a device
being disconnected or powered off unexpectedly and abnormal conditions that
were discovered by the device and reported back to the server. Both the minor
return code and the accompanying message provide more specific information
regarding the cause of the problem.</p>
<p>Depending on the file type, the program must either close the file and
open it again, release the device and acquire it again, or acquire the session
again. To reset an error condition in a shared file by closing it and opening
it again, all programs sharing the open data path must close the file. In
some cases, the message might instruct you to reset the device by varying it
off and on again. It is unlikely that the program will be able to use the
failing device until the problem causing the error is found and corrected,
but recovery within the program might be possible if an alternate device is
available.</p>
<p>Some of the minor return codes in this group are the same as those for
the 82 major return code. Device failures or line failures might occur at any
time, but an 81 major code occurs on an I/O operation. This means that your
program had already established a link with the device or session. Therefore,
the program can transfer some data, but when the program starts from the beginning
when it starts again. A possible duplication of data might result.</p>
<p>Message numbers accompanying an 81 major code might be in the range that
indicates either an I/O or a close operation. A device failure on a close
operation might be the result of a failure in sending the final block of data,
rather than action specific to closing the file. An error on a close operation
can cause a file to not close completely. Your error recovery program should
respond to close failures with a second close operation. The second close
will always complete, regardless of errors.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal3recoveryerr.htm" title="This section describes the errors you might receive and the actions you should take to recover from those errors.">Recover from file server errors</a></div>
</div>
</div>
</body>
</html>