83 lines
3.2 KiB
HTML
83 lines
3.2 KiB
HTML
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
|
||
|
|
<title>Problem Management APIs</title>
|
||
|
|
<!-- 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. -->
|
||
|
|
<!-- Change History: -->
|
||
|
|
<!-- YYMMDD USERID Change description -->
|
||
|
|
<!-- 050201 JETAYLOR repurposed for v5r4 -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<script type="text/javascript" language="Javascript" src="../rzahg/synch.js"></script>
|
||
|
|
|
||
|
|
<h2>Problem Management APIs</h2>
|
||
|
|
|
||
|
|
<p>The problem management APIs offer you the ability to write
|
||
|
|
problem management solutions, improve serviceability, and manage
|
||
|
|
your own applications. Problem management APIs deal directly with
|
||
|
|
how the iSeries<SUP>(TM)</SUP> server handles problems today. The problem log
|
||
|
|
provides most of the operations necessary for problem management in
|
||
|
|
a network environment.</p>
|
||
|
|
<p>The problem management APIs are organized into the following groups:</p>
|
||
|
|
<ul>
|
||
|
|
<li><a href="pm1a.htm">Problem Logging</a></li>
|
||
|
|
|
||
|
|
<li><a href="pm1b.htm">Service</a></li>
|
||
|
|
|
||
|
|
<li><a href="pm1c.htm">Monitoring</a></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<h3><a name="filtering">Filtering</a></h3>
|
||
|
|
|
||
|
|
<p>In the problem management APIs, a <strong>filter</strong> categorizes problem log entries into groups and
|
||
|
|
performs operations on them accordingly.
|
||
|
|
The problem log applies the currently active filter to a problem log entry
|
||
|
|
whenever a problem entry is created, changed, or deleted using system-provided
|
||
|
|
interfaces.</p>
|
||
|
|
|
||
|
|
<p>The operations supported allow you to send application notification to a
|
||
|
|
user data queue and assign the problem to a user. Your application can receive
|
||
|
|
these notifications from the data queue using existing APIs.
|
||
|
|
See also <a href="obj2.htm">Data Queue APIs</a>.</p>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
|
||
|
|
<h3><a name="workwithproblem">Working with a Problem</a></h3>
|
||
|
|
|
||
|
|
<p>Problem analysis is the process of finding the cause of a
|
||
|
|
problem and identifying why the system is not working. Often, this
|
||
|
|
process identifies equipment or data communications functions as
|
||
|
|
the source of the problem. The <a href="qpdwrkpb.htm">Work with
|
||
|
|
Problem</a> (QPDWRKPB) API allows you to perform problem analysis on local machine-detected
|
||
|
|
problems in the problem log. The Work with Problem (QPDWRKPB) API
|
||
|
|
prepares the problem in the problem log for reporting; it does not
|
||
|
|
report the problem automatically.</p>
|
||
|
|
<br>
|
||
|
|
<h3>Key Groups</h3>
|
||
|
|
<p>See <a href="pmkeygroups.htm">Key Groups for Problem Log APIs</a> for information
|
||
|
|
about keys for problem log APIs.</p>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
|
||
|
|
<hr>
|
||
|
|
<center>
|
||
|
|
<table cellpadding="2" cellspacing="2">
|
||
|
|
<tr align="center">
|
||
|
|
<td valign="middle" align="center">
|
||
|
|
<a href="#Top_Of_Page">Top</a> |
|
||
|
|
<a href="aplist.htm">APIs by category</a></td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
</center>
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|