81 lines
4.9 KiB
HTML
81 lines
4.9 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
||
|
|
<meta name="dc.date" scheme="iso8601" content="2005-10-17" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<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))' />
|
||
|
|
<title>Basic troubleshooting procedure</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
|
||
|
|
<a name="troubleshootingproc"></a>
|
||
|
|
<h2 id="troubleshootingproc">Basic troubleshooting procedure</h2>
|
||
|
|
<p>If you encounter problems when using OptiConnect, follow this procedure
|
||
|
|
to find out why you are having difficulties. In general, it may be helpful
|
||
|
|
to try the same DDM transaction over a communication link (LAN, for example).
|
||
|
|
If no error occurs, follow the steps below to determine where OptiConnect
|
||
|
|
is failing. If the error still occurs, the problem is not likely to be OptiConnect.</p>
|
||
|
|
<p>If all OptiConnect DDM accesses are failing, check the following: </p>
|
||
|
|
<ol type="1">
|
||
|
|
<li>Check to ensure that the system-to-system connections are operational
|
||
|
|
by using the Work with Hardware Resources (WRKHDWRSC) command. Enter:
|
||
|
|
<pre class="xmp">WRKHDWRSC TYPE(*CSA)</pre> For more information on this command, see <a href="rzau3whrsc.htm#whrsc">Work with hardware resources (WRKHDWRSC)</a>.</li>
|
||
|
|
<li>Check to ensure the cables are operational using:
|
||
|
|
<pre class="xmp">DSPOPCLNK</pre></li>
|
||
|
|
<li>Verify that QSOC subsystem is running on both the application systems
|
||
|
|
and the database system by entering the following command on both:
|
||
|
|
<pre class="xmp">WRKACTJOB SBS(QSOC)</pre></li>
|
||
|
|
<li>Verify that the SOCMGR job is running in the QSOC subsystem. If the QSOC
|
||
|
|
subsystem is not running, start it. If the subsystem is running, but there
|
||
|
|
is no SOCMGR job, either the SOCMGR job has been ended, or a software failure
|
||
|
|
has occurred. Locate the job log that is associated with the SOCMGR job by
|
||
|
|
entering:
|
||
|
|
<pre class="xmp">WRKJOB QSOC</pre> Display the log to determine why the SOCMGR
|
||
|
|
job ended. Report software failures by contacting your service provider.</li>
|
||
|
|
<li>Verify that the OptiConnect Connection Manager has established communications
|
||
|
|
between the source and target systems. Each time a connection is opened or
|
||
|
|
closed, a message is sent to the system operator message queue. Connections
|
||
|
|
are closed when the QSOC subsystem has ended, the SOCMGR job has ended, a
|
||
|
|
system is powered off, or a failure occurs. To display the system operator
|
||
|
|
messages, enter:
|
||
|
|
<pre class="xmp">DSPMSG MSGQ(*SYSOPR)</pre> Otherwise, use the following
|
||
|
|
command to select a particular time period:
|
||
|
|
<pre class="xmp">DSPLOG LOG(QHST)</pre>
|
||
|
|
<a name="wq58"></a>
|
||
|
|
<div class="notetitle" id="wq58">Note:</div>
|
||
|
|
<div class="notebody">To see only QSOC messages, use <tt class="xph">DSPMSG QSOC</tt>.</div></li>
|
||
|
|
<li>Check to ensure that the QSOC job queue is not held. Enter:
|
||
|
|
<pre class="xmp">WRKJOBQ JOBQ(QSOC/QSOC)</pre></li>
|
||
|
|
<li>Verify that the correct remote location name, device, and mode are defined
|
||
|
|
in the DDM file used for OptiConnect. See <a href="rzau3configure.htm#configure">Configure OptiConnect</a>.</li></ol>
|
||
|
|
<p>Follow these steps if you suspect a problem with a particular application: </p>
|
||
|
|
<ol type="1">
|
||
|
|
<li>Locate the failing job or job log on the source system.</li>
|
||
|
|
<li>Display the job log information and find this message:
|
||
|
|
<pre class="xmp">DDM JOB STARTED ON REMOTE SYSTEM</pre></li>
|
||
|
|
<li>Use F1 to display the detailed message text. The detailed message text
|
||
|
|
shows the OptiConnect agent job name.</li>
|
||
|
|
<li>Locate the agent job on the target system.</li>
|
||
|
|
<li>Inspect the job log information for both the application and agent jobs
|
||
|
|
to locate any unexpected errors.</li>
|
||
|
|
<li>If MSGCPF9167 is encountered, see <a href="rzau3msgs.htm#msgs">OptiConnect error messages</a> for more information
|
||
|
|
on communications messages.</li></ol>
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|