106 lines
7.2 KiB
HTML
106 lines
7.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="concept" />
|
|
<meta name="DC.Title" content="Messages" />
|
|
<meta name="abstract" content="Messages contain the job name, the message type, the date and time it was sent, the action that occurred, and the necessary actions needed to fix a problem. This is useful when you are trying to troubleshoot any problems that might occur on your servers. You can access job logs for server jobs through iSeries Navigator. Messages fall into two categories, alertable messages and messages logged in a job log." />
|
|
<meta name="description" content="Messages contain the job name, the message type, the date and time it was sent, the action that occurred, and the necessary actions needed to fix a problem. This is useful when you are trying to troubleshoot any problems that might occur on your servers. You can access job logs for server jobs through iSeries Navigator. Messages fall into two categories, alertable messages and messages logged in a job log." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogdispchar.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakschangeloglevel.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004-2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004-2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzaksmessages" />
|
|
<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>Messages</title>
|
|
</head>
|
|
<body id="rzaksmessages"><a name="rzaksmessages"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Messages</h1>
|
|
<div><p>Messages contain the job name, the message type, the date and time
|
|
it was sent, the action that occurred, and the necessary actions needed to
|
|
fix a problem. This is useful when you are trying to troubleshoot any problems
|
|
that might occur on your servers. You can access job logs for server jobs
|
|
through iSeries™ Navigator.
|
|
Messages fall into two categories, alertable messages and messages logged
|
|
in a job log.</p>
|
|
<p><span class="uicontrol">Alertable messages</span> - These messages are sent to
|
|
QSYSOPR because they need immediate action. The message contains the problem,
|
|
the cause, and the recovery action necessary. For example, the server fails
|
|
to start or the server ends unexpectedly. Some servers send alertable messages
|
|
to QSYSOPR. These messages have the Alert Option (ALROPT) defined in the message
|
|
description. You can use alerts to provide centralized handling of alertable
|
|
messages.</p>
|
|
<p><span class="uicontrol">Messages logged in a job log</span> - These messages are
|
|
diagnostic in nature, meaning that they are not critical but are alerting
|
|
the user of some action that was taken. These messages can be system generated
|
|
as well as user created.</p>
|
|
<div class="section"><h4 class="sectiontitle">Message logging level</h4><p>The message logging level
|
|
determines which messages and what message types should be logged for the
|
|
job. The following is an explanation of what each level represents.</p>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="void" border="1" rules="rows"><thead align="left"><tr valign="bottom"><th valign="bottom" width="NaN%" id="d0e34"> </th>
|
|
<th valign="bottom" width="NaN%" id="d0e35"> </th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" width="NaN%" headers="d0e34 ">Level 1</td>
|
|
<td valign="top" width="NaN%" headers="d0e35 ">All messages sent to the job's external message
|
|
queue with a severity greater than or equal to the message severity value.
|
|
(In iSeries Navigator,
|
|
the Message severity (0-99) value can be found on the Job Properties - Job
|
|
Log window. This is a value that you can control.)</td>
|
|
</tr>
|
|
<tr><td valign="top" width="NaN%" headers="d0e34 ">Level 2</td>
|
|
<td valign="top" width="NaN%" headers="d0e35 ">All messages that meet Level 1 qualifications
|
|
and any request messages which result in a high level message greater than
|
|
or equal to the message severity value.<div class="note"><span class="notetitle">Note:</span> A high-level message is one that
|
|
is sent to the program message queue of the program that receives the request
|
|
message. (For example, QCMD is an IBM-supplied request processing program
|
|
that receives request messages.)</div>
|
|
</td>
|
|
</tr>
|
|
<tr><td valign="top" width="NaN%" headers="d0e34 ">Level 3</td>
|
|
<td valign="top" width="NaN%" headers="d0e35 ">All messages that meet Level 1 or Level 2
|
|
qualifications and all request messages. Additionally, any commands from CL
|
|
programs are included if the <span class="uicontrol">Log commands from CL programs box</span> is
|
|
checked (Job Properties - Job Log window). <div class="note"><span class="notetitle">Note:</span> The <span class="uicontrol">Log commands
|
|
from CL programs box</span> is equivalent to the log attribute of the
|
|
CL program.</div>
|
|
</td>
|
|
</tr>
|
|
<tr><td valign="top" width="NaN%" headers="d0e34 ">Level 4</td>
|
|
<td valign="top" width="NaN%" headers="d0e35 ">All request messages and all messages with a severity
|
|
greater than or equal to the message logging severity, including trace messages.
|
|
Additionally, any commands from CL programs are included if the <span class="uicontrol">Log
|
|
commands from CL programs box</span> is checked Job Properties - Job
|
|
log window). <div class="note"><span class="notetitle">Note:</span> The <span class="uicontrol">Log commands from CL programs box</span>
|
|
is equivalent to the log attribute of the CL program.</div>
|
|
</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksjoblogdispchar.htm" title="The iSeries Navigator provides you with a user friendly, easy to read interface from which you can view job logs and the job log's messages. You can also view job logs by using the character based interface.">Job log characteristics</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzakschangeloglevel.htm" title="The log level of a job is a numeric level assigned to a specific combination of message types that are logged. You can change the log level in the job description by using the character-based interface. However, if you want to change the log level of a specific job, use the Job Properties - Job Log window in the iSeries Navigator.">Change the log level of a job</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |