HP Distributed Print Service Administration Guide
Chapter 7 211
Using Notification
Notification Profile Examples by HPDPS Object Type
delivery-method=electronic-mail \
delivery-address=adgreen@poplar.xyz.com} \
event-identifiers=class-server-attention \
class-server-configuration \
object-cleaned \
object-created \
object-deleted \
object-modified \
queue-backlogged \
delivery-method=message \
delivery-address=adgreen@poplar.xyz.com} \
event-identifiers=class-server-attention \
class-server-configuration \
object-cleaned \
object-created \
object-deleted \
object-modified \
queue-backlogged \
delivery-method=message \
delivery-address=fgbrown@poplar.xyz.com} \
event-identifiers=internal-server-error \
object-cleaned \
object-deleted \
server-shutdown-complete \
delivery-method=e-mail \
delivery-address=jswhite@poplar.xyz.com}" \
Spool1
Discussion:
• This notification profile could be created in an attributes file and set
from the command line. You would create a file that contained just
the notification-profile attribute and its values. Then you would
use that file (possibly named spool1.np) from the command line by
entering the command:
pdset -c server -X spool1.np Spool1
• You would want to modify all the logical printer and queue
notification profiles so that the operators do not have the same events
identified in two notification profiles. If this is not done, the operators
might receive duplicate messages for some events because both the
spooler and the other object notification profiles are active.