88 lines
9.2 KiB
HTML
88 lines
9.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="Resource accounting data" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjaabout.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjageneralinfo.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="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="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="rzaksjaresourceactngdta" />
|
||
|
|
<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>Resource accounting data</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksjaresourceactngdta"><a name="rzaksjaresourceactngdta"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Resource accounting data</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p> Each resource accounting journal entry contains information about the
|
||
|
|
resources used while the previous accounting code was in effect. Consider
|
||
|
|
the following example:</p>
|
||
|
|
<div class="p"><div class="fignone" id="rzaksjaresourceactngdta__rzaks550g"><a name="rzaksjaresourceactngdta__rzaks550g"><!-- --></a><span class="figcap">Figure 1. Resource accounting data example</span><br /><img src="rzaks550.gif" alt="" /><br /></div>
|
||
|
|
</div>
|
||
|
|
<p>At point A, the <span class="cmdname">CHGACGCDE</span> command was issued.
|
||
|
|
The accounting code is changed and the JB journal entry is sent to the journal.
|
||
|
|
The JB journal entry contains data for the first accounting segment. When
|
||
|
|
the job ends, a second JB entry is made for the job containing data for the
|
||
|
|
second accounting segment.</p>
|
||
|
|
<p>If the job accounting code was not changed during the existence of the
|
||
|
|
job, the single JB entry summarizes the total resources used by the job. If
|
||
|
|
the job accounting code was changed during the existence of the job, then
|
||
|
|
you must add up the fields in the multiple JB entries in order to determine
|
||
|
|
the total resources used by the job. The creation of a job log does not count
|
||
|
|
toward the processing unit use for a job or its printed output in the JB accounting
|
||
|
|
entries. However, if you are using print file accounting, the job log printed
|
||
|
|
is included in the printer file journal entries.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<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="rzaksjageneralinfo.htm" title="For this overview of how job accounting works, assume three different jobs enter the system.">How job accounting works</a></div>
|
||
|
|
<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="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>
|