89 lines
6.2 KiB
HTML
89 lines
6.2 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="task" />
|
||
|
|
<meta name="DC.Title" content="Determine problems with REXEC" />
|
||
|
|
<meta name="abstract" content="Read the following information to learn how to determine problems with REXEC." />
|
||
|
|
<meta name="description" content="Read the following information to learn how to determine problems with REXEC." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzal7overview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzal7matreq.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzal7getcopy.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzal7tracerex.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="pdrex" />
|
||
|
|
<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>Determine problems with REXEC</title>
|
||
|
|
</head>
|
||
|
|
<body id="pdrex"><a name="pdrex"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Determine problems with REXEC</h1>
|
||
|
|
<div><p>Read the following information to learn how to determine
|
||
|
|
problems with REXEC.</p>
|
||
|
|
<div class="section"> <p>If you detect a problem when using the REXEC server, you can
|
||
|
|
use the following flow chart and cause lists to identify potential problems.
|
||
|
|
However, you may be having problems with general TCP/IP connectivity. In that
|
||
|
|
case, it may be beneficial to first use the <a href="../rzaku/rzakuoverview.htm">TCP/IP troubleshooting</a> topic to identify basic TCP/IP
|
||
|
|
problems before using the REXEC flow chart for more localized problems.</p>
|
||
|
|
<div class="fignone" id="pdrex__pdrx"><a name="pdrex__pdrx"><!-- --></a><span class="figcap">Figure 1. REXEC Server Problem Analysis</span><br /><img src="rbaee555.gif" alt="REXEC Server Problem Analysis
flow chart" /><br /></div>
|
||
|
|
</div>
|
||
|
|
<ul><li><span>Cause List A</span><ol><li class="substepexpand"><span>Check to see that the REXEC server is running. If not, start
|
||
|
|
it with the STRTCPSVR SERVER(*REXEC) command.</span></li>
|
||
|
|
<li class="substepexpand"><span>If the message "Connection refused" is returned to the REXEC
|
||
|
|
client, check the exit program associated with the exit point QIBM_QTMX_SERVER_REQ. </span> This exit program has either specified that the connection should be
|
||
|
|
rejected, returned a value that is not correct for the Allow Operation parameter,
|
||
|
|
or ended abnormally. Examine the REXEC server job log for messages. Resolve
|
||
|
|
any problems with the exit program and install the corrected version.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li><span>Cause List B</span><ol><li class="substepexpand"><span>Check your user ID and password by logging on to the system.
|
||
|
|
If you are unable to do so, contact the system administrator to verify that
|
||
|
|
your user ID and password are correct.</span></li>
|
||
|
|
<li class="substepexpand"><span>Check the exit program associated with exit point QIBM_QTMX_SERVER_LOGON
|
||
|
|
(if any). </span> This exit program has either specified that the connection
|
||
|
|
should be rejected, returned a value this is not correct for the Allow Operation
|
||
|
|
parameter, or ended abnormally. Examine the REXEC server job log for messages.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li><span>Cause List C</span><ol><li class="substepexpand"><span>Check for any job log messages returned to the REXEC client.
|
||
|
|
Resolve any indicated problems and try the command again.</span></li>
|
||
|
|
<li class="substepexpand"><span>If the message "Command Rejected" is returned to the REXEC client,
|
||
|
|
check the exit program associated with the exit point QIBM_QTMX_SERVER_REQ. </span> This exit program may be specifying that the command should be rejected,
|
||
|
|
returning a value this is not correct for the Allow Operation parameter, or
|
||
|
|
ending abnormally. Examine the REXEC server job log for messages. Resolve
|
||
|
|
any problems with the exit program and install the corrected version.</li>
|
||
|
|
<li class="substepexpand"><span>Verify that the correct ASCII CCSID is configured for the REXEC
|
||
|
|
server. If not, set the correct CCSID with the CHGRXCA command.</span></li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzal7matreq.htm">Materials required for reporting REXEC problems</a></strong><br />
|
||
|
|
This information specifies materials required for reporting REXEC problems.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzal7getcopy.htm">Get a copy of a REXEC server job log</a></strong><br />
|
||
|
|
To get a copy of the REXEC server job log, you need to create it.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzal7tracerex.htm">Trace the REXEC server</a></strong><br />
|
||
|
|
The REXEC server can be traced by creating a data area. Note that running the REXEC server with trace running may cause a significant performance impact.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzal7overview.htm" title="The Remote Execution (REXEC) server is a Transmission Control Protocol/Internet Protocol (TCP/IP) application that allows a client user to submit system commands to a remote server system. The Remote Execution Protocol (REXEC) allows processing of these commands or programs on any host in the network. The local host then receives the results of the command processing.">REXEC</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|