Document revision date: 30 March 2001

You can display the print share information, including the permissions on the share. Use the SHOW SHARES /FULL command. For example, to display the permissions for the print share WESTWITCH, enter the following command:

LANDOFOZ\\TINMAN> SHOW SHARES WESTWITCH/FULL Shared resources on server "TINMAN": Name Type Description ----------- --------- --------------------------------------- WESTWITCH Printer Shared Print Queue in the Land of Oz Path: TOTO Connections: Current: 0, Maximum: No limit Share Permissions: Everyone Full Control LION Print TINY Manage Documents Total of 1 share LANDOFOZ\\TINMAN>

5.3.2.11 Stopping a Print Share, Using ADMINISTER Commands

You may need to stop sharing a print share for several reasons:

• To reorganize shared print queues
• To remove a printer, if this printer is the only printer servicing the queue
• To remove a shared print queue that is no longer needed

To stop sharing a print share, use the REMOVE SHARE command. The queue still exists and can be displayed using the SHOW PRINT QUEUE command, but it is unavailable to network users. Jobs in the print queue complete as usual. For example:

LANDOFOZ\\TINMAN> REMOVE SHARE TOTO Do you really want to remove share "TOTO" [YES or NO] (YES) : YES %PWRK-S-SHAREREM, share "TOTO" removed from server "TINMAN" LANDOFOZ\\TINMAN>

5.3.2.12 Managing Print Jobs, Using ADMINISTER Commands

The Advanced Server lets you display and control print jobs in Advanced Server print queues.

This section provides information on the following topics:

• Displaying print jobs
• Holding a print job
• Releasing a print job
• Restarting a print job
• Moving a print job in a print queue
• Deleting a print job

To manage print jobs, you must be logged on to a user account that is a member of one of the following groups:

• Administrators
• Server Operators
• Print Operators

There are no special requirements for displaying print job information.

5.3.2.12.1 Displaying Print Jobs, Using ADMINISTER Commands

To display print jobs, use the SHOW PRINT JOBS command. For example:

LANDOFOZ\\TINMAN> SHOW PRINT JOBS Routing Queue TOTO : ACTIVE Job User Name Size Status ---- --------------- ----------- ---------- 5 system 512 QUEUED 6 system 512 QUEUED 7 system 512 PAUSED LANDOFOZ\\TINMAN>

5.3.2.12.2 Holding a Print Job, Using ADMINISTER Commands

If you have FULL or MANAGE_DOCUMENTS permission on the share, you can hold any print job that the queue has not yet sent to the printer. The held job stays in the queue until you release it; other jobs in the queue are printed. Other users can hold and release their own print jobs.

To hold a print job, use the SET PRINT JOB /HOLD command. For example:

LANDOFOZ\\TINMAN> SET PRINT JOB 3330/HOLD %PWRK-S-JOBSET, print job 3330 held on server "TINMAN" LANDOFOZ\\TINMAN> SHOW PRINT JOB Routing Queue TOTO : PENDING Job User Name Size Status ---- ---------------- ------------ --------------- 3330 system 512 PAUSED LANDOFOZ\\TINMAN>

This example pauses or holds print job number 3330.

5.3.2.12.3 Releasing a Print Job, Using ADMINISTER Commands

You can release a print job that has been held, as described below. The job prints when it reaches the top of the queue.

To release a print job, use the SET PRINT JOB /RELEASE command. For example:

LANDOFOZ\\TINMAN> SET PRINT JOB 3330/RELEASE %PWRK-S-JOBSET, print job 3330 released on server "TINMAN" LANDOFOZ\\TINMAN>

This example releases the specified print job that was on hold. The job then proceeds to print.

5.3.2.12.4 Restarting a Print Job, Using ADMINISTER Commands

You can restart a print job, printing it again from the beginning. This can be useful if a job is interrupted by an error or printer problem.

To restart a print job, use the SET PRINT QUEUE /RESTART command. For example:

LANDOFOZ\\TINMAN> SET PRINT QUEUE TOTO/RESTART %PWRK-S-JOBACTION, print job 1 at server "TINMAN" has been restarted LANDOFOZ\\TINMAN>

5.3.2.12.5 Moving a Print Job in a Print Queue, Using ADMINISTER Commands

You can use the SET PRINT JOB command to move a print job to the beginning or end of the queue.

To move a print job to the first position in its queue, use the SET PRINT JOB/FIRST command. For example:

LANDOFOZ\\TINMAN> SET PRINT JOB 3330/FIRST %PWRK-S-JOBSET, job 3330 set to first position on server "TINMAN" LANDOFOZ\\TINMAN>

This example moves job number 3330 in the print queue to the first position in the queue. It prints as soon as any currently printing job is done.

To move a print job to the last position in a queue, use the SET PRINT JOB /LAST command. For example:

LANDOFOZ\\TINMAN> SET PRINT JOB 3330/LAST %PWRK-S-JOBSET, job 3330 set to last position on server "TINMAN" LANDOFOZ\\TINMAN>

This example moves print job number 3330 to the last position in the print queue. The print job prints after all other print jobs currently in the queue are done.

5.3.2.12.6 Deleting a Print Job, Using ADMINISTER Commands

If you have FULL or MANAGE_DOCUMENTS permission on the share, you can delete any job that is waiting in a print queue. Other users can delete their own print jobs. Use the SET PRINT JOB /DELETE command to delete a print job. To abort a print job that is currently printing, use the SET PRINT JOB /ABORT command.

To delete a print job, use the SET PRINT JOB/DELETE command, as in the following example:

LANDOFOZ\\TINMAN> SET PRINT JOB 3330/DELETE %PWRK-S-JOBSET, print job 3330 deleted on server "TINMAN" LANDOFOZ\\TINMAN>

This example deletes job number 3330 from the print queue.

To cancel a print job that is currently printing, use the SET PRINT QUEUE/ABORT command.

When you need to shut down a printer immediately, you may need to cancel a print job that is printing. Or you may need to cancel a print job that is printing incorrectly, such as a PostScript file that is printing as an ASCII or text file. For example:

LANDOFOZ\\TINMAN> SET PRINT JOB 3330/ABORT %PWRK-S-JOBSET, print job 3330 aborted on server "TINMAN" LANDOFOZ\\TINMAN>

This example cancels print job number 3330 while it is printing. To restart a deleted job, you must resubmit the print job.

5.3.3 Managing Advanced Server Printers Using Windows NT

The Advanced Server for OpenVMS can be configured to manage printers and print queues remotely from a Windows NT Server or workstation. Any administrators, print operators, or server operators on the Windows NT system can manage these printers. These users can manage and conceptualize printers in Windows NT-familiar terms: they manage printers, printer ports, print queues, and the associated parameters defined in each printer's OpenVMS Registry entry. Notice that all users can add a printer and manage their own print jobs from their Windows NT computer.

By default, Advanced Server shared printers are managed locally by means of the ADMINISTER command interface. To change the default on the Advanced Server for OpenVMS so that you can manage Advanced Server shared printers using Windows NT print services, you must reconfigure the server using PWRK$CONFIG and enable Windows NT printer management. For more information about enabling Windows NT printer management, refer to the Compaq Advanced Server for OpenVMS Server Installation and Configuration Guide.

The printers defined on the Advanced Server and managed by Windows NT are often referred to as the Advanced Server's Windows NT-compatible printers.

Each Advanced Server printer created and managed from Windows NT has:

• A registry entry that defines printer parameters such as the name of the printer, location, and printing information, including the share name, printer queue (execution queue), and so forth.
• A print share that is used primarily by client browsers to display printers. The print share name does not have to be the same as the printer name. In addition, the Advanced Server for OpenVMS creates a PRINT$ share during server installation (the share is located at PWRK$LMROOT:[LANMAN.SHARES.PRINTDRIVERS]). Printer drivers are placed in the PRINT$ share when a printer is created using the Windows NT Add Printer Wizard.
• A routing queue (an OpenVMS generic queue) that is created automatically by the Advanced Server if printer pooling is selected. The routing queue name is the same as the printer name.
• A printer queue (an OpenVMS execution queue), which is identical to a Windows NT port to which a printer is connected physically.
• Support for Windows NT Application Programming Interfaces (APIs) to be used by the Windows NT print services.

With Windows NT printer management enabled on your Advanced Server, you can use the same tools on Windows NT to manage printers defined on the Advanced Server that you would use to manage other Windows NT printers. For example, to add a Windows NT-compatible printer, double-click on the icon for the Advanced Server in the Network Neighborhood, then select the Printers folder. Now, double-click on the Add Printer icon in the Printers folder for the Advanced Server being managed, and use the Windows NT Add Printer Wizard to guide you through the process. The wizard allows you to select:

• A port (an OpenVMS executive queue) to print to
• The name of the printer
• Whether to share the printer, and the name of the share
• Whether to enable printer pooling
• The type of printer

For examples and illustrations, refer to the Compaq Advanced Server for OpenVMS Concepts and Planning Guide.

The Advanced Server printer name must not exceed 12 characters in length. If printer pooling is enabled, the printer name must differ from the OpenVMS execution queue name. They can be the same if printer pooling is disabled.

When you are prompted to select a port for the printer, the list box displays the available OpenVMS execution queues found by the Advanced Server. Click on the appropriate execution queue.

When you are prompted for the type of printer and the operating systems of the clients to be using the printer, you must have the appropriate printer drivers available (supplied on a CD-ROM, for example).

When the Add Printer Wizard completes, the printer is added to the Printers folder. To see the new printer in the Printers folder, you might have to refresh the folder view.

To share this printer, see Section 5.3.3.2, Using Windows NT Print Services to Share Printers Defined on the Advanced Server.

5.3.3.2 Using Windows NT Print Services to Share Printers Defined on the Advanced Server

When you add a printer using the Windows NT Add Printer Wizard, one of the dialog boxes gives you the option of sharing the printer. If you indicate that the printer is to be shared, you can enter a name for the shared resource (which defaults to the first word of the printer name).

To share an existing printer, right-click the printer in the Printers folder, and then click Properties. Click the Sharing tab, and then click Shared and enter the share name.

5.3.3.3 Enabling Printer Pooling

To set up a printer for printer pooling (similar to setting up an OpenVMS generic queue or Advanced Server routing queue), use the Windows NT Add Printer Wizard to select several ports to point the printer to, and check the box that enables printer pooling. When the printer is created, the Advanced Server creates a routing queue with the same name as the printer name. The routing queue routes to the ports (execution queues) you selected with the Add Printer Wizard.

5.3.3.4 Using Advanced Server Windows NT-Compatible Printers

Users who want to use an Advanced Server print share can add the associated printer to their computers, in the same way as described in Section 5.3.3.1, Using Windows NT Print Services to Manage Advanced Server Printers. The Add Printer Wizard allows the user to download and install the printer drivers from the server. When that is done, an icon for the printer appears in the user's Printer folder, and the user can now print to that printer.

5.3.3.5 Windows NT Printer Management Restrictions

The following restrictions apply to the Windows NT style management of Advanced Server print shares:

• With Windows NT printer management enabled, Compaq recommends managing printers defined on the Advanced Server only from Windows NT. In specific, do not use the following ADMINISTER commands:

  ADD SHARE/PRINT
  REMOVE PRINT QUEUE
  SET PRINT QUEUE

  
  You can still use the following ADMINISTER commands, and all other ADMINISTER commands not related directly to printer management:

  ADD PRINT QUEUE
  CONTINUE PRINT QUEUE
  PAUSE PRINT QUEUE
  SHOW PRINT QUEUES

• The length of the name of a Windows NT manageable printer must not exceed 12 characters.
• If printer pooling is enabled, the name of the printer must not be the same as the name of the OpenVMS execution queue selected from the list of printer ports during printer creation.
• Advanced Server print shares cannot be renamed from Windows NT. If you use Windows NT to try to rename a shared printer that is defined on the Advanced Server, the printer name will revert to the original name. No error messages are displayed. Likewise, the Advanced Server ADMINISTER command-line interface as well as OpenVMS do not allow renaming of printers, print shares, or print queues.
• To view changes to print jobs, you must select the Refresh item from the View menu for the print queue.
• You cannot adjust the scheduling properties of Advanced Server printers (this property is normally accessed from the Windows NT printer's Properties window, under the Scheduling tab).
• You cannot set the Take Ownership security property.
• Upgraded printers (that is, printers or print shares that were already defined on an Advanced Server when Windows NT printer management was enabled) cannot be managed with all the management functionality available for printers that were added to the server by Windows NT print services. Note, for example, that you cannot use Windows NT to add an upgraded server printer to another workstation.
  To gain full Windows NT printer management functionality for these print queues and shares, delete them using the command procedure provided with your kit, and add them again using Windows NT print services.

Advanced Server provides several ways for you to determine the specific cause of a server problem and to implement a solution.

This chapter describes the procedures you can use to monitor events and troubleshoot problems:

• Section 6.1, Monitoring Server Events, describes commands and utilities that allow you to monitor current server activity and display information about server events in log files, including:
  • ADMINISTER commands
  • Alert messages
  • Event logs
  • Advanced Server log files
• Section 6.2, Troubleshooting Server Problems, describes how to troubleshoot Advanced Server problems.

Advanced Server lets you monitor server events as they happen and capture events in log files. The following sections describe the tools you can use to monitor and evaluate server events.

6.1.1 ADMINISTER Commands

Advanced Server ADMINISTER commands let you display information about current server activity and status, as well as recorded events and error messages. In addition, you can use ADMINISTER commands to modify items in the server database to correct certain types of problems.

For example, the SHOW SESSIONS command displays current client sessions. To remove a session that is no longer being used, enter the CLOSE SESSION command.

Refer to the procedures described in Section 6.2.2, The Problem Analysis Process, for information about ADMINISTER commands you can use to help solve certain types of server problems.

6.1.2 Automatic Alerts

Advanced Server includes an Alerter service that sends automatic alert messages to specified clients and users when:

• The number of failed logon attempts exceeded the set alert level.
• Errors are encountered during server startup.
• Any event log file is 80% or more full.
• A printer is malfunctioning.
• A print request has been deleted.

The Alerter service can also tell you when certain events occur, as specified by the data associated with the Alerter server configuration parameters in the OpenVMS Registry. You control when the Alerter service sends messages for these events by modifying the data for the appropriate value in the OpenVMS Registry, as described in Section 7.2, Managing Server Configuration Parameters Stored in the OpenVMS Registry.

Table 6-1, Alerter Configuration Parameters, lists the server configuration parameters you can modify to control the way the Alerter service works.

Table 6-1 Alerter Configuration Parameters

To specify...	Use this Value	Default Data
The total number of errors that can occur before the server sends an alert message. You can set the value for this keyword to any positive integer.	ErrorAlert	5
The total number of incorrect password attempts that can occur before the server sends an alert message. You can set the value for this keyword to any positive integer.	LogonAlert	5
The total number of resource access violations that can occur before the server sends an alert message. You can set the value for this keyword to any positive integer.	AccessAlert	5

The Alerter service runs automatically when the server starts, if the Alerter service is included in the data associated with the ServerServices server parameter in the OpenVMS Registry. The Alerter service is included in the initial configuration by default. To disable the Alerter service, remove the Alerter name from the list of data for the ServerServices value. See Section 2.3.4, Managing Services, for more information about services.

You can specify that Advanced Server users and clients are to receive alert messages. Include the names of these users and clients in the data field for the AlertNames value in OpenVMS Registry. See Appendix A, Server Configuration Parameters, for more information about OpenVMS Registry values and data.

In the Advanced Server, an event is any significant occurrence in the system or in an application that requires user notification. For events that do not require immediate attention, the Advanced Server adds data to an event log file. This event logging service starts automatically every time you start the Advanced Server.

Event logs can provide valuable information about server activities.

Event messages are stored in event files in PWRK$LMROOT:[LANMAN.LOGS]. Each event type is maintained in a separate event log file, as shown in Table 6-2, Event Log Files.

Table 6-2 Event Log Files

Event Type	Event Log File Name	Description
Application events	APPEVENT.EVT	Application event messages are generated by applications. For example, user-written applications may store messages in the application event log.
Security events	SECEVENT.EVT	Event messages are generated based on the audit policy specified for the server, including files or directories. (For more information, see Section 6.1.3.3, Auditing Security Events Domain-Wide.)
System events	SYSEVENT.EVT	System event messages are generated by server components.

Table 6-3, Information in Event Files, lists the information shown in each line in an event file.

Table 6-3 Information in Event Files

Item	Meaning
Source	The server component that logged the message.
Class	The event class, either information, warning, error, success audit, or failure audit.
Time	The date and time of the event.
Category	Classification of the message.
Message ID	Unique number for the message.
User	The user account name for the user who was logged on and working when the message was logged. N/A indicates that the entry does not specify a user.
Computer	The name of the computer where the message was generated.

	privacy and legal statement
6543PRO_016.HTML