96 lines
6.9 KiB
HTML
96 lines
6.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 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="Interactive job logs" />
|
||
|
|
<meta name="abstract" content="The IBM-supplied job descriptions QCTL, QINTER, and QPGMR all have a log level of LOG(4 0 *NOLIST); therefore all messages help text are written to the job log. However, the job logs are not printed if the job ends normally unless you specify *LIST on the SIGNOFF command." />
|
||
|
|
<meta name="description" content="The IBM-supplied job descriptions QCTL, QINTER, and QPGMR all have a log level of LOG(4 0 *NOLIST); therefore all messages help text are written to the job log. However, the job logs are not printed if the job ends normally unless you specify *LIST on the SIGNOFF command." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowjoblogscreated.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutjoblogpending.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogserverabout.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogdispchar.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksqhistlog.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutspoolfile.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="rzaksinteractjoblogs" />
|
||
|
|
<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>Interactive job logs</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksinteractjoblogs"><a name="rzaksinteractjoblogs"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Interactive job logs</h1>
|
||
|
|
<div><p>The IBM-supplied job descriptions QCTL, QINTER, and QPGMR all have
|
||
|
|
a log level of LOG(4 0 *NOLIST); therefore all messages help text are written
|
||
|
|
to the job log. However, the job logs are not printed if the job ends normally
|
||
|
|
unless you specify *LIST on the SIGNOFF command.</p>
|
||
|
|
<p>If a display station user uses and IBM-supplied menu or the command entry
|
||
|
|
display, all error messages are displayed. If the display station user uses
|
||
|
|
a user-written initial program, any unmonitored message causes the initial
|
||
|
|
program to end and a job log to be produced. However, if the initial program
|
||
|
|
monitors for messages, it receives control when a message is received. In
|
||
|
|
this case, it is important to ensure that the job log is produced so that
|
||
|
|
you can determine the specific error that occurred. </p>
|
||
|
|
<div class="p">For example, assume that the initial program displays a menu that includes
|
||
|
|
a signoff option, which defaults to *NOLIST. The initial program monitors
|
||
|
|
for all exceptions and includes a Change Variable (<span class="cmdname">CHGVAR</span>)
|
||
|
|
command that changes the signoff option to *LIST if an exception occurs:<blockquote><pre>PGM
|
||
|
|
DCLF MENU
|
||
|
|
DCL &SIGNOFFDPT TYPE(*CHAR) LEN(7)
|
||
|
|
VALUE(*NOLIST)
|
||
|
|
.
|
||
|
|
.
|
||
|
|
.
|
||
|
|
MONMSG MSG(CPF0000) EXEC(GOTO ERROR)
|
||
|
|
PROMPT: SNDRCVF RCDFMT(PROMPT)
|
||
|
|
CHGVAR &IN41 '0'
|
||
|
|
.
|
||
|
|
.
|
||
|
|
.
|
||
|
|
IF (&OPTION *EQ '90') SIGNOFF
|
||
|
|
LOG(&SIGNOFFOPT);
|
||
|
|
.
|
||
|
|
.
|
||
|
|
.
|
||
|
|
GOTO PROMPT
|
||
|
|
ERROR: CHGVAR&SIGNOFFOPT '*LIST'
|
||
|
|
CHGVAR &IN41 '1'
|
||
|
|
GOTO PROMPT
|
||
|
|
ENDPGM</pre>
|
||
|
|
</blockquote>
|
||
|
|
</div>
|
||
|
|
<p>If an exception occurs, the <span class="cmdname">CHGVAR</span> command changes the
|
||
|
|
option on the SIGNOFF command to *LIST and sets on an indicator. This indicator
|
||
|
|
can be used to condition a constant that displays a message explaining that
|
||
|
|
an unexpected error occurred and telling the display station user what to
|
||
|
|
do. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksjoblogs.htm" title="A job log contains information related to requests entered for a job. A job log has two forms, a pending form and a spooled form.">Job logs</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><img src="./delta.gif" alt="Start of change" /><a href="rzakshowjoblogscreated.htm" title="Release V5R4 brings job logs into the "on demand" world. The job logs are available when needed, but no work is done to produce job logs for which there is no need.">How job logs are created</a><img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<div><img src="./delta.gif" alt="Start of change" /><a href="rzaksaboutjoblogpending.htm" title="The job log pending state has been available for many years. When a job's job log attribute is *PND, no job log is produced. With the release of V5R4 enhancements have been made to both iSeries Navigator and the character-based interface so that you can now control how and under what circumstances the job log for a specific job will be produced.">Job log pending</a><img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<div><a href="rzaksjoblogserverabout.htm" title="Typically the job log server writes a job's job log to a spooled file. You can route the job log to a printer or to an outfile, (if specified to do so by using the QMHCTLJL, Control job log API), however this is not the recommended method for producing job logs.">Job log server</a></div>
|
||
|
|
<div><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><a href="rzaksqhistlog.htm" title="The history (QHST) log consists of a message queue and a physical file known as a log-version. Messages sent to the log message queue are written by the system to the current log-version physical file.">QHST History Log</a></div>
|
||
|
|
<div><a href="rzaksaboutspoolfile.htm" title="A spooled file holds output data until it can be printed. The spooled file collects data from a device until a program or device is able to process the data. A program uses a spooled file as if it were reading from or writing to an actual device. This is input and output spooling.">Spooled files</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|