109 lines
10 KiB
HTML
109 lines
10 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="How job accounting works" />
|
||
|
|
<meta name="abstract" content="For this overview of how job accounting works, assume three different jobs enter the system." />
|
||
|
|
<meta name="description" content="For this overview of how job accounting works, assume three different jobs enter the system." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjaabout.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjawhenusejobactng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjasecrtyjobactng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjajournalentries.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjaactngcode.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjaresourceacctng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjaresourceactngdta.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjbactngprestartjobs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjasystemjobactng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/xjobntfy.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjabatchproc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjainteractivejobactng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjaprinterfileactng.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjajobandrunpriority.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjajobaccountingentry.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="rzaksjageneralinfo" />
|
||
|
|
<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>How job accounting works</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksjageneralinfo"><a name="rzaksjageneralinfo"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">How job accounting works</h1>
|
||
|
|
<div><p>For this overview of how job accounting works, assume three different
|
||
|
|
jobs enter the system.</p>
|
||
|
|
<div class="p"><div class="fignone" id="rzaksjageneralinfo__rsls879g"><a name="rzaksjageneralinfo__rsls879g"><!-- --></a><span class="figcap">Figure 1. Job Accounting Overview</span><img src="RSLS879.gif" alt="" /></div>
|
||
|
|
</div>
|
||
|
|
<ol><li>When Job1 is completed, the system summarizes the resources used and writes
|
||
|
|
the JB journal entry to the QACGJRN journal. If the accounting code was changed
|
||
|
|
during the job, a JB journal entry will written for each time the accounting
|
||
|
|
code was changed and at the end of the job. Job1 does not make any printer
|
||
|
|
output, and no job log is made. Therefore, no direct print (DP) or spooled
|
||
|
|
print (SP™)
|
||
|
|
journal entries are made for Job1.</li>
|
||
|
|
<li>Job2 is printing a file directly to a printer. When the file is completed
|
||
|
|
a DP journal entry is written that summarizes the printed data. When Job2
|
||
|
|
is completed, the system summarizes the resources used and writes the JB journal
|
||
|
|
entry. Job2 does not make any spooled printer output and no job log is made.
|
||
|
|
Therefore, no SP journal
|
||
|
|
entry is made for Job2.</li>
|
||
|
|
<li>Job3 is printing to a file that is spooled. The SP journal entry is not written unless a print
|
||
|
|
writer prints the file. When Job3 is completed, the system summarizes the
|
||
|
|
resources used and writes the JB journal entry. If a job log is made at the
|
||
|
|
completion of the job, it is considered a normal spooled file and an SP journal entry
|
||
|
|
is created if the file is printed.</li>
|
||
|
|
<li>A print writer is started and it prints the files made by one or more
|
||
|
|
jobs. When the writer finishes a file, it makes an SP journal entry. The SP journal entry is not made if the file is
|
||
|
|
canceled before printing starts.</li>
|
||
|
|
<li>At the close of an accounting period, the Display Journal (<span class="cmdname">DSPJRN</span>)
|
||
|
|
command can be used to write the accumulated journal entries into the database
|
||
|
|
file.</li>
|
||
|
|
<li>User-written programs or the query utility can be used to analyze the
|
||
|
|
accounting data. Reports such as resources used will compile data by a specific
|
||
|
|
accounting code, user, or job type.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjajobandrunpriority.htm">Job Accounting operating characteristics</a></strong><br />
|
||
|
|
The iSeries™ system
|
||
|
|
attempts to allocate main storage as efficiently as possible. A job might
|
||
|
|
not use the same amount of resources each time it is run. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjajobaccountingentry.htm">Accounting Journal Processing</a></strong><br />
|
||
|
|
The accounting journal QSYS/QACGJRN is processed as any other journal. Files can also be recorded in this journal although for simplicity it is recommended that you keep it solely for accounting information.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksjaabout.htm" title="The job accounting function gathers data so that you can determine who is using your system and what system resources they are using. It also assists you in evaluating the overall use of your system. Job accounting is optional. You must take specific steps to set up job accounting. You can request the system to gather job resource accounting data, printer file accounting data, or both. You can also assign accounting codes to user profiles or specific jobs.">Job accounting</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaksjawhenusejobactng.htm" title="Should you use the job accounting function in QHST messages since message numbers CPF1124 and CPF1164 are always available in the QHST log? Or, should you use job accounting? Use the following information to help you determine which method is best for your organization.">When to use job accounting</a></div>
|
||
|
|
<div><a href="rzaksjasecrtyjobactng.htm" title="Only the security officer (or a program adopting his authority) or a user with *ALLOBJ and *SECADM authority can change the Journal accounting information (QACGLVL) system value.">Security and job accounting</a></div>
|
||
|
|
<div><a href="rzaksjajournalentries.htm" title="The system provides different journal entries for the different types of data that can be gathered:">Journal entries for job accounting</a></div>
|
||
|
|
<div><a href="rzaksjaactngcode.htm" title="The initial accounting code (up to 15 characters in length) for a job is determined by the value of the ACGCDE (accounting code) parameter in the job description and user profile for the job.">About the accounting code</a></div>
|
||
|
|
<div><a href="rzaksjaresourceacctng.htm" title="Job resource accounting data is summarized in the job (JB) journal entry at the completion of a job. In addition, the system creates a JB journal entry summarizing the resources used each time a Change Accounting Code (CHGACGCDE) command occurs. The JB journal entry includes:">Resource accounting</a></div>
|
||
|
|
<div><a href="rzaksjaresourceactngdta.htm" title="When analyzing the journal entries, it is important to understand how and when journal entries are written. A JB journal entry is written to the job accounting journal for a job any time the job accounting code is changed and when the job ends. Therefore, one job may have multiple journal entries.">Resource accounting data</a></div>
|
||
|
|
<div><a href="rzaksjbactngprestartjobs.htm" title="If your system uses job accounting, the prestart job program should run the Change Prestart Job (CHGPJ) command with the program start request value for the accounting code parameter (CHGPJ ACGCDE(*PGMSTRRQS)) immediately after the program start request attaches to the prestart job.">Prestart jobs and job accounting</a></div>
|
||
|
|
<div><a href="rzaksjasystemjobactng.htm" title="System jobs that you control (for example, readers and writers) are assigned an accounting code of *SYS. Other system jobs that you do not control (for example, QSYSARB, QLUS,SCPF) do not receive a journal entry.">System job processing for job accounting</a></div>
|
||
|
|
<div><a href="rzaksjabatchproc.htm" title="Any batch job that is submitted using the Submit Job (SBMJOB) command automatically uses the same accounting code as the job that submitted the batch job. When the SBMJOB command is used, the accounting codes cannot be overridden regardless of how the job description entry is coded.">Batch processing and job accounting</a></div>
|
||
|
|
<div><a href="rzaksjainteractivejobactng.htm" title="If an interactive job has a fixed set of options for a user and each option has an assigned accounting code, it might be desirable to automatically assign a new code when the user requests to work on a new function.">Interactive processing and job accounting</a></div>
|
||
|
|
<div><a href="rzaksjaprinterfileactng.htm" title="There are two types of journal entries for printer file accounting; DP for nonspooled printer files and SP for spooled printer files. These two types of journal entries share a common journal entry format although some of the information is only available in the SP entry. The DP and SP journal entries include information such as:">Printer file accounting</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../apis/xjobntfy.htm" title="The job notification exit point can be used as an alternative to job accounting. This depends on what information you are interested in.">Job Notification Exit Point</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|