Q:
Topic thread:
Printer Systems (PRINT - NA/ATS)
Printing Systems Manager (PSM)
The customer would like to gather statistics such as:
downtime per printer
page-counts
interventions
job processing time
They have found screens that contain all the information they require on
the following SMIT PPO screens:
Retained and TImed Out Job Status
Printing and Queued Job Status
Printer Status
Is there a way for them to access the data using a command line or shell
script that would yield the data in a database format (e.g. comma
delimited)?
A:
Sorry for the delay. I am in class this week, but will input your
answers at the end of the day today. Thank you.
Q:
A:
After reading your questions more closely, I will need to research your
questions more. I will update the item as soon as I get some input
from development. Thank you for your patience.
Q:
A:
Some questions have come up as to the information you are looking for.
Your question seems to imply you may be looking for "lifetime"
information, that is, lifetime downtime, lifetime page count, etc for
a printer. If this is the case, then you will need to take a different
approach. The info you see in the PPO, such as printer downtime, it is
a dynamic attribute and only shows the current downtime (on a job basis
or PSF instance basis), and does not show the downtime during the
lifetime of the printer.
As for the PPO, after you perform the task in smit, you can hit the
F6 key to see the command that was run to get the results. These
are not "private" commands but could be run in a script or a complex
command line (depending on the info you are seeking). Other events
you can get from a pdls command. For instance you want to
check how long the printer "needs attention" error condition has been
on for, you can issue the command:
pdls -c printer -rprint-need-attention-time print_name
The same can be done for page counts ON A JOB. These are only counted
on a job basis and not on a printer basis, especially for a lifetime.
For that, you would need to use the PSF accounting exits, but this
would only be applicable for PSF DSS attached printers.
Another approach to gather info on some of the events you are seeking
would be to use the file/file-add-to notification delivery method and
carefully selecting which events to deliver in this way. You could
then run a cron job to take a periodic snapshot of the event file and
update your database based on the contents. This would obviously
require some custom coding.
I hope this helps address some of your issues. If you need further
clarification, please reopen and give some more detailed information
on what you are looking to do.
Thank you for using WWQ&A.
S e a r c h - k e y w o r d s:
psm accounting pdls database notification smit ppo aix format
WWQA: ITEM: RTA000155082 ITEM: RTA000155082
Dated: 02/1999 Category: PSMAIX
This HTML file was generated 99/06/24~12:43:42
Comments or suggestions?
Contact us