ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddm_5.4.0.1/rbae5failures.htm

56 lines
4.1 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="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="Handle connection request failures for TCP/IP" />
<meta name="abstract" content="The main causes for failed connection requests at a server configured for TCP/IP use is that the DDM TCP/IP server is not started, an authorization error occurred, or the machine is not running." />
<meta name="description" content="The main causes for failed connection requests at a server configured for TCP/IP use is that the DDM TCP/IP server is not started, an authorization error occurred, or the machine is not running." />
<meta name="DC.Relation" scheme="URI" content="rbae5probana.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5badportid.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5connauth.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5noserver.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5nojobs.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="rbae5failures" />
<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>Handle connection request failures for TCP/IP</title>
</head>
<body id="rbae5failures"><a name="rbae5failures"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Handle connection request failures for TCP/IP</h1>
<div><p>The main causes for failed connection requests at a server configured
for TCP/IP use is that the DDM TCP/IP server is not started, an authorization
error occurred, or the machine is not running.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbae5badportid.htm">DDM server is not started or the port ID is not valid</a></strong><br />
The error message given if the DDM TCP/IP server is not started is CPE3425.</li>
<li class="ulchildlink"><strong><a href="rbae5connauth.htm">DDM connection authorization failure</a></strong><br />
The error messages given for an authorization failure is CPF9190.</li>
<li class="ulchildlink"><strong><a href="rbae5noserver.htm">DDM server not available</a></strong><br />
If a remote server is not up and running, or if you specify an incorrect IP address or remote location name in the DDM file, you will get message CPE3447.</li>
<li class="ulchildlink"><strong><a href="rbae5nojobs.htm">Not enough prestart jobs at server</a></strong><br />
If the number of prestart jobs associated with the TCP/IP server is limited by the QRWTSRVR prestart job entry of the QUSRWRK or user-defined subsystem, and all prestart jobs are being used for a connection, an attempt at a new connection will fail with these messages.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5probana.htm" title="Some functions that involve a target server may take a relatively long period of time to complete. In these situations, the target server may not appear to be functioning when it is actually waiting for a reply.">DDM problem analysis on the remote server</a></div>
</div>
</div>
</body>
</html>