The accounting, post-print accounting and audit user-exit programs

The InfoPrint Manager accounting and audit user-exit programs require the same inputs and produce the same outputs so the program descriptions are the same. The post-print accounting user-exit program requires more inputs and produces more outputs.

The source code (in the C programming language) for the sample user-exit programs listed on page What sample user-exit programs are available? are in the /usr/lpp/psf/exits directory. The sample programs store the data into a file you can access with these executable reporting utilities:

ainurpt1: Provides accounting data for the actual destinations defined, based upon the destination ID.
ainurpt2: Provides accounting data for the actual destinations defined, based upon the userid.
ainurpt3: Provides detailed accounting data for the destinations defined, based upon the particular userid supplied.
ainurpt4: Provides audit data for the actual destinations defined, based upon the destination ID.
ainurpt5: Provides audit data for the actual destinations defined, based upon the userid.
ainurpt6: Provides detailed audit data for the actual destinations defined, based upon the particular userid supplied.
ainurpt7: Provides post-print accounting data stored in jobcompletion.log, sorted by actual destination.
ainurpt8: Provides summary post-print accounting data stored in jobcompletion.log, sorted by job submitter.
ainurpt9: Provides detailed entries of times and pages printed for a specific job submitter in jobcompletion.log.

The source code for these reporting utilities is also located in the /usr/lpp/psf/exits directory.

These executable reporting utilities are located in the /usr/lpp/psf/bin directory. By specifying these executable reporting utilities at the Linux command line, you can display data by either destination ID or userid. For example, to report on print requests submitted by a specific user to a actual destination for which the accounting user-exit has been activated, you can specify ainurpt3 and then provide the userid to the program.

Note: You must activate these exits to generate the log files used by these report programs. For more information about activating these exits, see Activating the user-exit program.

The data structures for the accounting, audit, and post-print accounting user-exit programs are included with the source code in the /usr/lpp/psf/exits/ainuexit.h and /usr/lpp/psf/exits/ainurpt.h files. The code for these structures is shown in User-exit program structures.

The declarations of these exits are:

void ACCOUNTING (ACCOUNTING_EXITDATA *exitdata)
void AUDIT (AUDIT_EXITDATA *exitdata)
void JOBCOMPLETION (JOBCOMPLETION_EXITDATA *exitdata)

After you create your user-exit program, you must use the Linuxmake command to compile the code (see Compiling and installing the user-exit program).

See Common input and output fields and the ainuexit.h file for explanations of the function and structure of the various components of this user-exit.

The ACCOUNTING_EXITDATA, AUDIT_EXITDATA, and JOBCOMPLETION_EXITDATA input/output parameters contain all the input and output data needed to communicate between InfoPrint Manager and the user-exit programs.

These fields are also found in the accounting, audit, and post-print accounting user-exit programs:

Pages Printed (accounting and audit user-exit only): Shows the total number of impressions processed for this job.
Bin One Sheets Processed (accounting and audit user-exit only): Shows the total number of processed sheets that were selected from the primary bin.
Bin Two Sheets Processed (accounting and audit user-exit only): Shows the total number of processed sheets that were selected from bins other than the primary bin.
User Pages Stacked by Bin (post-print accounting user-exit only): Shows the total number of stacked pages in the user print file. It does not include system pages, such as the header page, in the count.
User Sheets Stacked by Bin (post-print accounting user-exit only): Shows the total number of stacked sheets in the user print file. It does not include system pages, such as the header page, in the count.
Pages Stacked by Bin (post-print accounting user-exit only): Shows the total number of pages stacked for this job by bin.
Sheets Stacked by Bin (post-print accounting user-exit only): Shows the total number of sheets stacked for this job by bin.
Data Object Resources: Shows the total number of Data Object Resources, which can consist of PDF pages, IOCA images, and Encapsulated PostScript (EPS) files, used in this job. Data Object Resources are also known as presentation-object containers (for more information, see the presentation-object-container attributes in the RICOH InfoPrint Manager: Reference).
Note: The counters do not include resources contained in the input file. The counters only include resources used before the accounting or audit user-exit is called. Therefore, the resources required for printing error messages and the trailer page do not appear in the resource totals.
Job Copies Requested (post-print accounting user-exit only): Shows the total number of results-profile job copies requested in the job.
Fonts used: Shows the total number of fonts used in this job.
Note: The counters do not include resources contained in the input file. The counters only include resources used before the accounting or audit user-exit is called. Therefore, the resources required for printing error messages and the trailer page do not appear in the resource totals.
Overlays used: Shows the total number of overlays used in this job.
Note: The counters do not include resources contained in the input file. The counters only include resources used before the accounting or audit user-exit is called. Therefore, the resources required for printing error messages and the trailer page are not included in the resource totals.
Segments used: Shows the total number of page segments used in this job.
Note: The counters do not include resources contained in the input file. The counters only include resources used before the accounting or audit user-exit is called. Therefore, the resources required for printing error messages and the trailer page are not included in the resource totals.
ExtStart Date: Identifies the date the job started processing.
Start Date: The date the job started processing.
Start Time: The time the job started processing.
ExtStop Date: The date the job finished processing.
Stop Date: The date the job finished processing.
Stop Time: The time the job finished processing.
Completion Date (post-print accounting user-exit only): The date all pages in the job printed and stacked.
Note: If errors or operator commands affect the job so that all pages are not sent to the printer, this field indicates the time when these pages have been printed and stacked.
Completion Time (post-print accounting user-exit only): The time all pages in the job printed and stacked.
Note: If errors or operator commands affect the job so that all pages are not sent to the printer, this field indicates the time when these pages have been printed and stacked.
DORU: The data object resources used (DORU) by the exit.
DOFU: The data object fonts used (DOFU) by the exit.

RICOH InfoPrint Manager™ for Linux

The accounting, post-print accounting and audit user-exit programs