Create a physical printer named X4517PS_rm3520.pp from the existing printer X4517PS.pp on the supervisor named

big-super.

pdcreate -c printer -x

copy-from=big_super:X4517PS.pp X4517PS_rm3520.pp

5. pddelete

Name

pddelete - delete a print object.

Synopsis

pddelete [-c class_name] [-m message_text] [-x extended_attribute_string ... ]

[-X attribute_filename ... ]object_instance ...

Use this command to display help about pddelete.

pddelete -h

Description

Use the pddelete command to delete a logical printer, physical printer, job, queue, initial-value-job, initial-value-document, or server.

The following items should be considered when using this command:

• When multiple objects are specified, they must all be the same class.

• Spoolers, supervisors, queues, logical and physical printers must be disabled before they can be deleted.

• The deleted object is removed from the object database.

• NameSpace database considerations when deleting spoolers, supervisors,queues, logical and physical printers:

— In the Windows NT environment:

— For PrintXchange Name Service, the object entry is automatically removed from the Name Service.

— In the UNIX environment:

— For Local File and NIS, you must propagate the change throughout the network.

— In the NIS environment, the network administrator must remove the object from the NIS NameSpace database (printers.conf.byname) and propagate the information throughout the NIS servers operating in that domain.

PDDELETE

• Deletion of spoolers, supervisors, queues, logical and physical printers performs immediate updates on the server that controls the object to be deleted. Updates to associated objects that are controlled by a different server occur immediately if the

associated server is running; otherwise, the updates occur when the server is started.

• When the object to be deleted is a logical printer:

— The printer-associated-printers attributes for the associated physical printers are updated.

— The logical-printers-supported attributes for the associated server and queue are updated.

• When the object to be deleted is a physical printer,

— The spooler associated with the physical printer must be running.

— All currently active jobs must be deleted or you must wait for them to complete.

— An unregister-printer event is sent to the associated spooler, which updates all affected queues and logical printers.

— The physical-printers-supported attributes for the supervisor, spooler, and queue are updated.

— The printers-ready and printer-associated-printers attributes for the associated logical printers are updated.

— If the specified printer is the only physical printer associated with a queue, the spooler stops scheduling jobs in that queue until it is associated with another physical printer.

— Jobs in the spooler specifying the deleted printer via the physical-printers-requested attribute will remain in a pending state. These jobs must have the physical-printers-requested attribute modified before they can be rescheduled for a different printer.

• When the object to be deleted is a spooler:

— All jobs currently on the spooler must be deleted (i.e., disable and then clean the spooler).

— All associated spooler objects (queues, logical printers, initial-value-jobs, initial-value-documents, and the spooler itself) are deleted.

PDDELETE

• When the object to be deleted is a supervisor:

— All jobs currently in the supervisor must be deleted.

— An unregister-printer event is sent to the associated spooler for each affected physical printer. The spooler removes the printers from all mapping attributes, updating the affected queues and logical printers.

— All physical printers are deleted.

— All dynamic data files that are created and maintained by the supervisor, such as the temporary job data file and object data files, are deleted.

• When the object to be deleted is a job:

— The specified job (and all documents contained in the job) is deleted, regardless of its state.

— The specified job is canceled if it was already delivered to the supervisor and the job stops printing as soon as possible.

— The value of the job-retention-period attribute is set to zero, overriding its previous value, if any. The value of default-job-completion-period is ignored. (This differs from the pdrm command which honors the value of these attributes.)

— The job is removed from the system.

• When the object to be deleted is a queue:

— All jobs must be removed from the queue (i.e.,disable and then clean the queue) or wait until the queue empties.

— The queue is disassociated from its logical and physical printers (the logical and physical printer attributes associated-queue, printer-associated-printers, and printers-ready are set to empty).

— All associated printers are disabled.

— The queue is disassociated with its spooler. (The spooler removes the queue from its queues-supported attribute.)

• When the object to be deleted is an initial-value-job:

— The object is not removed from the printer-initial-value-job attribute on the logical printers. To manually remove the logical printer associations:

— Issue a pdls command for all logical printers on the same spooler to determine the associated logical printers.

— For each associated logical printer, issue a pdset command to associate the logical printer with an existing initial-value-job (set the logical printer’s printer-initial-value-job attribute).

PDDELETE

• When the object to be deleted is an initial-value-document:

— The object is not removed from the printer-initial-value-document attribute on the logical printers. To manually remove the logical printer associations:

— Issue a pdls command for all logical printers on the same spooler to determine the associated logical printers.

— For each associated logical printer, issue a pdset command to associate the logical printer with an existing initial-value-document (set the logical printer’s printer-initial-value-document attribute).

access level Administrator

Options

The following options are supported for pddelete.

-c class_name

Specifies the class, or type, of object you are deleting.

arguments The values allowed for class_name are the following:

• printer (This is the default.)

• job

• queue

• initial-value-document

• initial-value-job

• server

Note: The Operands section describes the specific object_instance associated with each class.

If you use the -x string option or the -X file option, the comparable

PDDELETE

-m message_text

Use this option to include a message about the object that you are deleting. For example, when a printer is to be deleted the message attached to the printer might be:

-m "Printer1 no longer available"

If you use the -x extended_attribute_string option or the -X

attribute_filename option in the pddelete command, the comparable client attribute type and value is the following:

For printers, queues, servers, initial value jobs and initial value documents:

message=message_text For jobs:

job-message-from-administrator=message_text The option will look like this:

-x "message='Printer1 no longer available' "

To retrieve a message of this type, use the pdls command, specify the object, and include the following option:

-r message

-x extended_attribute_string

Use this option to specify a series of attribute=value pairs on the command line that will be processed by the pddelete command.

attributes Object attributes cannot be used in the -x option.

The following client attributes can be used:

• attributes

• class

• message (The message will be deleted along with the object.)

syntax Follow the syntax rules for attribute value strings, listed in the Overview chapter of the PrintXchange Command Line Interface Reference Guide.

Note: You can produce the same result by including the

extended_attribute_string in an attribute file and identifying that file as the attribute_filename in the -X option.

PDDELETE

-X attribute_filename

The -X option identifies an attribute file to be read by the command.

When the pddelete command executes, the attribute data included in the file is processed at the current point in the command line as though it had been specified with the -x option.

attributes Object attributes cannot be used in the -X option. Refer to the -x section for a list of the client attributes that may be used.

Note: Refer to the Overview chapter of the PrintXchange Command Line Interface Reference Guide for information on developing an attribute file.

Operands

The value of the object_instance in the operand is based on the value of the -c class_name option or the class=class_name attribute.

Note: Before you delete the object, run a report on every object that is associated with it so that you can document all of the setup and initialization requirements. You can use this information if you need to create the object again.

printer_name ... When class equals printer, the value of printer_name is the name of the printer to be deleted. The printer to be deleted can be a logical or physical printer.

server_name ... When class equals server, the value of server_name is the name of the server to be deleted. The server to be deleted can be a supervisor or spooler.

[spooler_name:]job_id ... When class equals job, the value of job_id is the unique identifier that points to the job to be deleted.

queue_name ... When class equals queue, the value of queue_name is the name of the specific queue to be deleted.

[spooler_name:]ivjob_name ... When class equals initial-value-job, the value of ivjob_name is the name of the initial-value-job object to be deleted.

PDDELETE

Examples

1. Delete the printer named sams-printer. Notice the -c class_name option is not needed since the default class is printer.

pddisable sams-printer pddelete sams-printer