57 lines
3.4 KiB
HTML
57 lines
3.4 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Use the history log" />
|
||
|
|
<meta name="abstract" content="How to use the history log, why it is important, and step-by-step instructions for setting it up." />
|
||
|
|
<meta name="description" content="How to use the history log, why it is important, and step-by-step instructions for setting it up." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvmonitorsec.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="usehistlog" />
|
||
|
|
<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>Use the history log</title>
|
||
|
|
</head>
|
||
|
|
<body id="usehistlog"><a name="usehistlog"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Use the history log</h1>
|
||
|
|
<div><p>How to use the history log, why it is important, and step-by-step
|
||
|
|
instructions for setting it up.</p>
|
||
|
|
<p>Some security-related events, such as exceeding the incorrect signon attempts
|
||
|
|
specified in the QMAXSIGN system value, cause a message to be sent to the
|
||
|
|
QHST (history) log. Security messages are in the range 2200 to 22FF. They
|
||
|
|
have the prefixes CPI, CPF, CPC, CPD, and CPA. </p>
|
||
|
|
<p>Some authority failure and integrity violation messages are no longer sent
|
||
|
|
to the QHST (history) log. All information that was available in the QHST
|
||
|
|
log can be obtained from the security audit journal. Logging information to
|
||
|
|
the audit journal provides better system performance and more complete information
|
||
|
|
about these security-related events than the QHST log. The QHST log should
|
||
|
|
not be considered a complete source of security violations. Use the security
|
||
|
|
audit functions instead. </p>
|
||
|
|
<div class="p">These messages are no longer written to the QHST log: <ul><li><samp class="codeph">CPF2218</samp>. These events can be captured in the audit journal
|
||
|
|
by specifying *AUTFAIL for the QAUDLVL system value.</li>
|
||
|
|
<li><samp class="codeph">CPF2240</samp>. These events can be captured in the audit journal
|
||
|
|
by specifying *AUTFAIL for the QAUDLVL system value.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamvmonitorsec.htm" title="This set of topics discuss various techniques for monitoring and auditing security on your system.">Monitor security</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|