| Previous | Contents | Index |
You can purge a shared print queue; that is, you can delete all jobs in the queue except the one currently printing.
Use the SET PRINT QUEUE /PURGE command. For example:
LANDOFOZ\\TINMAN> SET PRINT QUEUE TOTO/PURGE %PWRK-S-QUESET, queue "TOTO" purged on server "TINMAN" LANDOFOZ\\TINMAN> |
To remove a PATHWORKS Advanced Server print queue from network access, use the REMOVE PRINT QUEUE command. Removing the queue removes that queue's record, including its settings and related permissions.
The following rules and restrictions apply to deleting print queues:
Use the REMOVE PRINT QUEUE command. For example:
LANDOFOZ\\TINMAN> REMOVE PRINT QUEUE TOTO Do you really want to remove print queue "TOTO" [YES or NO] (YES) : YES %PWRK-S-QUEREM, queue "TOTO" removed from server "TINMAN" LANDOFOZ\\TINMAN> |
This command removes the print queue called TOTO from the list of print
queues known to the server called TINMAN. All jobs in the queue
complete before the queue is removed.
5.6 Managing Print Jobs
The PATHWORKS Advanced Server lets you display and control print jobs in PATHWORKS Advanced Server print queues.
This section provides information on the following topics:
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>
|
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.
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.6.3 Releasing a Print Job
You can release a print job that has been held, as described below. The job prints when it reaches the top of the queue.
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.6.4 Restarting a Print Job
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.
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> |
You can 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.6.6 Deleting a Print Job
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. For 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 while it is 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 text file. For example:
LANDOFOZ\\TINMAN> SET PRINT JOB 3330/DELETE %PWRK-S-JOBSET, print job 3330 deleted 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.
PATHWORKS 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, including:
PATHWORKS 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.2.1 ADMINISTER Commands
PATHWORKS 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 The Problem Analysis Process, for information
about ADMINISTER commands you can use to help solve server problems.
6.2.2 Automatic Alerts
PATHWORKS Advanced Server includes an Alerter service that sends automatic alert messages to specified clients and users when:
The Alerter service can also tell you when certain events occur, as specified in the LANMAN.INI file. You control when the Alerter service sends messages for these events by modifying the value for the appropriate keyword in the server's LANMAN.INI file. The following table lists Alerter keywords that can reside in the SERVER section of the LANMAN.INI file on your server.
| To specify these events... | Use this keyword | Default value |
|---|---|---|
| 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= n | 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= n | 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= n | 5 |
The Alerter service runs automatically when the server starts, if the Alerter service is included in the list of values for the SRVSERVICES keyword in the SERVER section of the LANMAN.INI file. The Alerter service is included in the initial configuration. To disable the Alerter service, remove the Alerter service from the list of values for the SRVSERVICES keyword. See Managing Domains and Servers, for more information about services.
You can specify that PATHWORKS Advanced Server users and clients are to receive alert messages. Include the names of these users and clients in the list of values for the ALERTNAMES keyword in the SERVER section of the LANMAN.INI file. See The LANMAN.INI File in this guide, for more information about its values and structure.
Client workstations must be running the Messenger service to receive alert messages. The Messenger service does not run on the OpenVMS system; therefore, users logged on from OpenVMS processes will not receive alert messages. |
6.2.3 Event Logging
In the PATHWORKS 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
PATHWORKS Advanced Server adds data to an event log file. This event
logging service starts automatically every time you start the PATHWORKS
Advanced Server.
Event logs can provide valuable information about server activities. In addition to system operation event logging, you can:
You may select from several event types and, for each, whether successful or unsuccessful attempts at specific operations are to generate event messages.
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 the following table.
| Event Type | Event Log File Name | Description |
|---|---|---|
| Application events | APPEVENT.EVT | Application event messages are generated by applications. |
| Security events | SECEVENT.EVT | Event messages are generated based on the audit policy specified for the server, including files or directories. (See Enabling Auditing.) |
| System events | SYSEVENT.EVT | System event messages are generated by server components. |
The following table lists the information shown in each line in an event file.
| Item | Meaning |
|---|---|
| Source | The server component that logged the message. |
| 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. |
You can display events recorded in the event log file, using the SHOW EVENTS command. Use the /TYPE qualifier to specify one of the types of events, as follows: SYSTEM (default), SECURITY, or APPLICATION. For example, to display System events, enter the following command:
LANDOFOZ\\TINMAN> SHOW EVENTS T Date Time Source Category Event User Computer - -------- ----------- ------- ----------- ----- ---- ----------- I 08/26/97 11:49:56 AM SYSTEM None 528 N/A TINMAN W 08/27/97 12:07:01 PM Eventlog None 603 N/A TINMAN I 08/27/97 12:15:31 PM Print None 604 N/A TINMAN W 08/27/97 12:46:31 PM BROWSER None 605 N/A TINMAN Total of 4 events LANDOFOZ\\TINMAN> |
If the PATHWORKS Advanced Server is not running, you can view event log files using the ELFREAD utility. The ELFREAD utility allows you to display records in the event file in the following ways:
You can view records in brief (default) or detail format.
The ELFREAD command is defined as part of the PATHWORKS Advanced Server command set in the SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM command procedure.
The syntax for the ELFREAD command is:
ELFREAD [-o] [-d] event-type
| Where | Displays |
|---|---|
| -o | Records in chronological order |
| -d | Detail records |
| event-type | The event log file specified, one of the following: |
| SYSTEM | |
| SECURITY | |
| APPLICATION |
You can display the event logs and, when necessary, clear the event
log. The Alerter service sends you a message advising you when the
event log becomes 80% or more full. When the event file is full, no
additional event logging will take place until the event file is clear.
Before clearing the event file, you should save it to a backup file for
future reference. The maximum size of an event file is specified in the
LANMAN.INI file. The LANMAN.INI keywords controlling the event log file
sizes are MAXAUDITLOG, MAXAPPLOG, and MAXERRLOG. (See Appendix A, The LANMAN.INI File in
this guide for more information.)
When an event log becomes full, you can save and clear the event log.
The default location of the event log is PWRK$LMROOT:[LANMAN.LOGS].
Use the SAVE EVENTS command. The current event log is stored using the file name and location that you specify in the command line. For example, to save the Security event log to the file SEVENTS.BKP, enter the following command:
LANDOFOZ\\TINMAN> SAVE EVENTS SEVENTS.BKP/TYPE=SECURITY %PWRK-S-ELFSAVE, Security Event Log from server "TINMAN" saved LANDOFOZ\\TINMAN> |
If you do not specify a path as part of the file name, the event file is created in the PWRK$LMLOGS: directory.
Enter the CLEAR EVENTS command. The current Security event log messages are deleted. For example:
LANDOFOZ\\TINMAN> CLEAR EVENTS/TYPE=SECURITY Clear the Security Event Log [YES or NO] (YES) : YES %PWRK-S-ELFCLEARED, Security Event Log on server "TINMAN" cleared |
If you do not specify the event log type, the default is to save and
clear the SYSTEM event log.
6.2.3.3 Enabling Auditing
By default, auditing is not enabled. You must enable auditing in order for the server to record security events.
To enable auditing on the server:
Use the SET AUDIT POLICY command with the /AUDIT qualifier. For example:
$ ADMINISTER SET AUDIT POLICY/AUDIT |
Use the SET AUDIT POLICY command with the /NOAUDIT qualifier.
Enter the SHOW AUDIT POLICY command. This displays the audit policy currently established for the server. For example:
$ ADMINISTER LANDOFOZ\\TINMAN> SHOW AUDIT POLICY Audit Policy for domain "LANDOFOZ": Auditing is currently Enabled. Audit Event states: Audit Event Success Failure ------------------ -------- -------- ACCESS Disabled Disabled ACCOUNT_MANAGEMENT Disabled Disabled LOGONOFF Disabled Enabled POLICY_CHANGE Disabled Disabled PROCESS Disabled Disabled SYSTEM Disabled Disabled USER_RIGHTS Disabled Disabled LANDOFOZ\\TINMAN> |
The audit policy defines the types of events to be included in the Security event log. You can change the audit policy for the server using the SET AUDIT POLICY command.
The SET AUDIT POLICY command lets you specify event results for which auditing is enabled, including both successful and failed attempts to perform certain functions. The following table lists the SET AUDIT POLICY event results.
| Qualifier | Meaning |
|---|---|
| /SUCCESS=( event,...) | Record successful events. |
| /FAILURE=( event,...) | Record unsuccessful events |
The following table lists the events you can specify. A [NO] prefix clears auditing of the specified parameter.
| Event | Meaning |
|---|---|
| ALL | All events. |
| NONE | None of the events. |
| [NO]ACCESS | Attempts to access a directory or file set for auditing or to send a print job to a print queue set for auditing. |
| [NO]ACCOUNT_MANAGEMENT | Attempts to create, change, and delete user accounts and groups. Attempts to rename, disable, and enable a user account. Attempts to set or change a password. |
| [NO]LOGONOFF | Attempts to log on to the network, log off the network, and make network connections. |
| [NO]POLICY_CHANGE | Attempts to change user rights policies, auditing policies, or trust relationships. |
| [NO]PROCESS | Attempts to invoke a program, handle duplication, indirect accesses, and process exits. |
| [NO]SYSTEM | Attempts to restart or shut down the system, and events that affect system security or the security log. |
| [NO]USER_RIGHTS | Attempts to exercise a user right (except those associated with logging on and logging off). |
Use the SET AUDIT POLICY command. For example, to log all failures of logon and logoff attempts, use the SET AUDIT POLICY command with the /AUDIT/FAILURE=(LOGONOFF) qualifiers.
LANDOFOZ\\TINMAN> SET AUDIT POLICY/AUDIT/FAILURE=(LOGONOFF) %PWRK-S-AUDPOLSET, audit policy set for domain "LANDOFOZ" LANDOFOZ\\TINMAN> |
| Previous | Next | Contents | Index |