What do these user-exit programs provide?

The accounting and auditing user-exit programs record statistical data on jobs processed by InfoPrint actual destinations. PSF DSS accounting, post-print, and audit user-exit programs shows the most common accounting and auditing user-exit programs, the files where they record data, and the types of data that they record.

PSF DSS accounting, post-print, and audit user-exit programs

Program Log File Records
/usr/lpp/psf/bin/ainuxaccp /var/psf/podaccount.log Job submitter, job ID, actual destination, pages per job, pages per actual destination, pages per output bin, data object resources, start date, start time, copies per job
/usr/lpp/psf/bin/ainacclog /var/psf/accounting.log Job submitter, job name, actual destination, pages per job, pages per actual destination, jobs per output bin, data object resources, start date, start time, fonts, resident fonts, overlays
/usr/lpp/psf/bin/ ainuxjobcompletion /var/psf/ jobcompletion.log Job submitter, job ID, job name, spool ID, actual destination, global ID, user pages stacked by tray, user sheets stacked by tray, actual pages stacked by tray, actual sheets stacked by tray, copies requested, fonts and resident fonts used, overlays used, hard and soft segments used, processing start and stop date/time, job completion date/time, file date/time, extended user ID, extended job ID, address, account, building, department, programmer, room, title, job ticket name
/usr/lpp/psf/bin/ainaudlog /var/psf/audit.log Job submitter, job name, actual destination, pages per job, pages per actual destination, jobs per output bin, data object resources, start date, start time, fonts, resident fonts, overlays
Note: /usr/lpp/psf/bin/ainacclog and /usr/lpp/psf/bin/ainaudlog record the same information in different files.
This information is specified in flat ASCII format, with a single line for each job that is processed. You can use this information to determine billing procedures, to assess the workload of different output devices, or to determine how resources are used at your installation.

The ainuxjobcompletion exit is called when the printer reports back to InfoPrint Manager that all of the pages for a job have printed. This includes a partial job (due to a data stream error or because the job was paused/canceled or forward-spaced) and also any extra pages produced as a result of a backspace or other recovery. For the last job that prints on a continuous forms printer, the exit is not called until an NPRO (non-process run out) is done, either by an operator or automatically by InfoPrint Manager.

Only one record is written for a job that prints, unless a job is paused. In this case, a record is written for the part of the job that was printed up to the pause point; later, if the job is resumed another record is written for the rest of the job.

Note: If InfoPrint Manager does not receive feedback from the printer that all pages have stacked, such as when the printer is shut down in the middle of a job or when an error such as a server failure occurs, no record is written.

A new procedure has been added to the InfoPrint Manager Administration GUI to show you how to activate the default PSF ainuxjobcompletion accounting logs. The ainuxjobcompletion accounting exit interface can be used for PSF-driven IPDS printers. It provides actual (versus projected) accounting data and provides additional information about completed print jobs.

Customers who migrate from an existing V4.12 InfoPrint Manager server to InfoPrint Manager V4.13 will continue to find the previous accounting exit interface intact. Accounting programs that count on the previous accounting interface, which include the InfoPrint supplied samples, will function without modification.

Customers installing an InfoPrint Manager V4.4 and higher versions for the first time will see the post-print accounting exit activated and the accounting data written to /var/psf/jobcompletion.log.

The intent is to minimize migration issues for existing customers, but to start new customers out with the preferred accounting exit. The default installation for new machines will not activate both accounting exits. However, when V4.13 is installed, both new and migrated customers can choose to have the old, preferred, or both accounting exits active.

If a migrating installation wants to activate the preferred (new) exit, the administrator must set the psf-post-print-accounting-program-name auxiliary sheet attribute in the appropriate auxiliary sheet object to provide the name of either the InfoPrintsupplied sample exit or a custom version of the preferred exit. The administrator can also choose to deactivate the old exit by resetting the value of the psf-exit-program-name auxiliary attribute in the appropriate auxiliary sheet object to <not set>.

If a new installation wants to deactivate the preferred exit and instead run the old exit, the administrator must reset the psf-post-print-accounting-program-name auxiliary sheet attribute in the appropriate auxiliary sheet object to <not set>. The administrator can also choose to activate the old exit by setting the value of the psf-post-print-accounting-program-name auxiliary sheet attribute in the appropriate sheet object to the name of either the InfoPrint supplied sample exit or a custom version of the old exit.

In both cases, the administrator can also choose to have both exits active by setting the psf-exit-program-name and the psf-post-print-accounting-program-name auxiliary sheet attributes to the names of the two accounting programs (old and preferred). The administrator can also choose to deactivate both exits by leaving both attributes unset.