![[Compaq]](../../images/compaq.gif)
![[Go to the documentation home page]](../../images/buttons/bn_site_home.gif)
![[How to order documentation]](../../images/buttons/bn_order_docs.gif)
![[Help on this site]](../../images/buttons/bn_site_help.gif)
![[How to contact us]](../../images/buttons/bn_comments.gif)
![[OpenVMS documentation]](../../images/ovmsdoc_sec_head.gif)
| Document revision date: 19 July 1999 | |
|
|
|
|
|
|
| Previous | Contents | Index |
Controls whether form feeds are inserted into the print job when the printer reaches the bottom margin of the form in use. You can suppress this automatic form feed (without affecting any of the other carriage control functions that are in place) by using the /NOFEED qualifier. The /[NO]FEED qualifier does not affect user-formatted files and can be used to override the installation-defined defaults that have been set for the output queue you are using.
Controls whether a file flag page is printed preceding a file. The flag page contains the name of the user submitting the job, the job entry number, and other information about the file being printed. If the /FLAG qualifier is positioned between the PRINT command and the file specifications, it can take either of the following keywords:
| ALL | Prints a file flag page before each file in the job. |
| ONE | Prints a file flag page before the first file in the job. |
If you want the /FLAG qualifier to apply to individual files in a multifile job, place the qualifier directly after each file that you want to have a flag page.
Use the /[NO]FLAG qualifier to override the /DEFAULT=[NO]FLAG option that has been set for the output queue you are using. The /[NO]FLAG qualifier does not override the /SEPARATE=[NO]FLAG option set for the queue.
When you specify the /BURST qualifier for a file, the /[NO]FLAG qualifier does not add or subtract a flag page from the two flag pages that are printed preceding the file.
Forms have attributes such as print image width and length or paper stock, which the print symbiont associates with a job when the job is processed. To see which forms have been defined for your system, use the SHOW QUEUE/FORM command. To find out which form is mounted currently on a particular queue and which form is specified as that queue's default form, use the SHOW QUEUE/FULL command.
The stock of the form associated with the job must match the stock of the form mounted on the execution queue on which you want the job to be processed. If the stocks do not match, the job remains pending until one or more of the following occurs:
Controls whether a heading line is printed at the top of each page.
Specifies the number of pages to print for the specified job. You can use the /PAGES qualifier to print portions of long files. By default, all pages of the file are printed.
The lowlim specifier refers to the first page in the group of pages that you want printed for that file. If you omit the lowlim specifier, the printing starts on the first page of the file.
The uplim specifier refers to the last page of the file that you want printed. If you want to print to the end of the file, but do not know how many pages the file contains, use quotation marks (" ") as the uplim specifier. You can omit the parentheses if you are including only a specific value for the uplim specifier. For example, /PAGES=10 prints the first ten pages of the file; /PAGES=(5,10) prints pages 5 through 10; /PAGES=(5,"") starts printing at page 5 in the file and continues until the end of the file is reached.
Each parameter can take from 1 to 8 values for a total of 255 characters. If you specify only one parameter or parameter value, you can omit the parentheses. Enclose parameter values containing lowercase letters or nonalphanumeric characters (such as spaces, parentheses, or commas) in quotation marks.
You can specify the /PARAMETERS qualifier only once in each PRINT command. For example, in the command PRINT /PARAMETERS=(JJJ,KK) /PARAMETERS=(LL,MMM), the JJJ and KK are ignored because the second occurrence of the /PARAMETERS qualifier supersedes the first occurrence.
For information on parameters available for printing to PostScript printers using DECprint Supervisor software (DCPS), refer to the DCL Help topic PRINT_Parameter.
Specifies whether the symbiont bypasses all formatting and sends the output QIO to the driver with format suppressed. All qualifiers affecting formatting, as well as the /HEADER, /PAGES, and /SETUP qualifiers, are ignored.
If the /PASSALL qualifier is placed between the PRINT command and any file specifications, all files are printed in PASSALL mode. To specify the /PASSALL qualifier for only some files in the job, place the qualifier after each file that you want printed in PASSALL mode.
Specifies the job-scheduling priority of the print job. The value of the parameter n can be from 0 through 255, where 0 is the lowest priority and 255 is the highest. The default value of n is the value of the system parameter DEFQUEPRI. No privilege is needed to set the priority lower than the queue's maximum scheduling priority.
You can specify only the following qualifiers with the /REMOTE qualifier:
Note that, unlike the printing on the local node, multiple files queued by a single PRINT/REMOTE command are considered separate jobs.
Use the following options to specify job retention:
You cannot specify a /NORETAIN qualifier with the PRINT command (as system managers can with the commands INITIALIZE/QUEUE, START/QUEUE, and SET QUEUE). However, you can specify /RETAIN=DEFAULT with the PRINT command. The default option holds the job in the queue as specified by the queue's retention policy. If the system manager has not specified retention for the queue, the job is not retained. |
How Job Retention Is Determined
Although you can specify job retention options for your own jobs, the job retention option you specify may be overridden by the job retention option of the queue on which your job executed. If you submit or print a job to a generic queue, the generic queue's job retention setting may also override the job retention option you specify. This section describes how job retention is determined.
An execution queue's job retention setting takes precedence over a generic queue's job retention setting. However, if the job's completion status does not match the job retention setting (if any) on the execution queue, then the generic queue's job retention setting attempts to control job retention. If the job's completion status does not match the job retention setting (if any) on the generic queue, then the user-specified job retention setting is used. Jobs submitted directly to execution queues are not affected by job retention settings on generic queues.
If the execution queue's retention setting applies, the job is retained on the execution queue. Likewise, if the generic queue's retention setting applies, the job is retained on the generic queue. If the user-specified setting applies, the job is retained in the queue to which it was submitted.
The following example illustrates how the queue manager determines job retention:
Suppose you submit a job to a generic queue and specify /RETAIN=ALWAYS, and the job completes successfully.
First, the queue manager compares the job's completion status to the execution queue's retention setting. Suppose the queue is set with /RETAIN=ERROR (retains only jobs that complete unsuccessfully). The job is not retained in the execution queue because the error condition was not met.
The queue manager then compares the job's completion status to the generic queue's retention setting. Suppose the generic queue has no retention setting. The queue manager's comparison again fails to retain the job.
Finally, the queue manager compares the job's completion status to the retention setting you specified for the job. This comparison reveals that the job should be retained. Because the user-specified setting leads the queue manager to retain the job, the job is held in the queue to which the job was submitted---in this case, the generic queue.
For more information on types of queues, see the INITIALIZE/QUEUE command. For more information on setting retention options for queues, see the INITIALIZE/QUEUE, START/QUEUE, or SET QUEUE command.
Timed retention, which you specify using the UNTIL=time-value option, allows you to retain a job in the queue only as long as you need it. This eliminates the need to delete the job from the queue later.
For example, the following command retains the print job MYFILE in the queue until 7:31 on December 14, when the job will automatically be deleted from the queue.
$ PRINT/RETAIN=UNTIL=14-DEC-1998:07:31:0.0 MYFILE.DAT |
However, depending on the queue's job retention policy, the job might be retained indefinitely. The job retention policy set on the queue takes precedence over the user-specified job retention setting. Because system managers cannot specify timed job retention for a queue, any jobs retained as a result of a queue's setting are retained indefinitely.
If you specify the /RETAIN=UNTIL=time-value option, you must supply a time value. The time value is first interpreted as a delta time, then as a combination time, and finally as absolute time. If you specify a delta time, the delta begins when the job completes. For example, if you specify PRINT/RETAIN=UNTIL="+3:00", the job will be retained for three hours after the job completes. For information on specifying time values, refer to the OpenVMS User's Manual.
Note that the module names are not checked for validity until the time that the file is actually printed. Therefore, PRINT/SETUP is susceptible to typing errors and other mistakes. It is recommended only for experimental setups.
For production setups, see DEFINE/FORM/SETUP.
For complete information on specifying time values, refer to the OpenVMS User's Manual or the online help topic DCL_Tips (subtopic Date_Time).
Controls whether print job output is double-spaced. The default is single-spaced output.
The valid keywords for this qualifier are CONDENSED and EXPANDED. Descriptions are as follows:
| Keyword | Explanation |
|---|---|
| CONDENSED (default) | Displays the file name representation of what is generated to fit into a 255-length character string. This file name may contain a DID or FID abbreviation in the file specification. |
| EXPANDED | Displays the file name representation of what is stored on disk. This file name does not contain any DID or FID abbreviations. |
The keywords CONDENSED and EXPANDED are mutually exclusive. This qualifier specifies which file name format is displayed in the output message, along with the confirmation if requested.
File errors are displayed with the CONDENSED file specification unless the EXPANDED keyword is specified.
Refer to the OpenVMS Guide to Extended File Specifications for more information.
Controls whether a file trailer page is printed at the end of a file. The trailer page displays the job entry number as well as information about the user submitting the job and the files being printed. If the /TRAILER qualifier is positioned between the PRINT command and the file specifications, it can take either of the following keywords:
| ALL | Prints a file trailer page after each file in the job. |
| ONE | Prints a file trailer page after the last file in the job. |
If you want the /TRAILER qualifier to apply to individual files in a multifile job, place the qualifier directly after each file that you want to have a trailer page.
Use the /[NO]TRAILER qualifier to override the /DEFAULT=[NO]TRAILER option that has been set for the output queue you are using. The /[NO]TRAILER qualifier does not override the /SEPARATE=[NO]TRAILER option set for the queue.
Allows you to print a job on behalf of another user. The print job runs exactly as if that user had submitted it. The print job runs under that user's user name and user identification code (UIC), and accounting information is logged to that user's account. By default, the user identification comes from the requesting process. The user name qualifier value can be any user name that is valid on your system. The name must be 1 to 12 alphanumeric characters.
| #1 |
|---|
$ PRINT/QUEUE=LPB0/COPIES=10/AFTER=20 RESUME
Job RESUME (queue LPB0, entry 239) holding until 14-DEC-1998 20:00
|
The PRINT command in this example queues 10 copies of the file RESUME.LIS to printer LPB0, but requests that the copies not be printed until after 8:00 P.M.
| #2 |
|---|
$ PRINT THETA.TXT + BETA/FLAG + GAMMA/FLAG + *.LIS/FLAG
Job THETA (queue SYS$PRINT, entry 237) pending
|
The PRINT command in this example submits the files THETA.TXT, BETA.TXT, GAMMA.TXT, and the highest versions of all files with the file type .LIS as a single print job. Flag pages separate the individual files. Notice that the file type for BETA and GAMMA is .TXT, the file type of the first file in the list.
| #3 |
|---|
$ PRINT/LOWERCASE THETA.TXT/COPIES=2, -
_$BETA.DOC/COPIES=3
Job THETA (queue SYS$PRINT, entry 240) pending
|
The print job queued by the PRINT command in this example consists of two copies of THETA.TXT followed by three copies of BETA.DOC. This job must be printed on a printer that can print lowercase letters. If no such printer is available, the job waits in the queue.
| #4 |
|---|
$ PRINT/JOB_COUNT=3 THETA.TXT,BETA/NOIDENTIFY
|
The PRINT command in this example concatenates the files THETA.TXT and BETA.TXT into a single print job and prints three copies of the job. The /NOIDENTIFY qualifier requests that the job entry number and queue name not be displayed.
| #5 |
|---|
$ COPY REPORT.MEM NODE3::
$ PRINT/REMOTE NODE3::REPORT.MEM
|
In this example, the two commands are entered at a node other than NODE3. The COPY command copies the file REPORT.MEM from the current node to the NODE3 node. The PRINT command queues the file REPORT.MEM located on the NODE3 node for printing at the NODE3 node. The job entry number and queue name are not displayed when the /REMOTE qualifier is used.
| #6 |
|---|
$ PRINT/HOLD MASTER.DOC
Job MASTER (queue SYS$PRINT, entry 540) holding
.
.
.
$ SET ENTRY 540/RELEASE
|
The PRINT command in this example queues a copy of the file MASTER.DOC to the default printer in a hold status. Later, the SET ENTRY command releases the hold status on the file and makes it available for printing.
| #7 |
|---|
$ PRINT TEST.TXT
Job TEST.TXT (queue SYS$PRINT, entry 867) started on LPA0
$ SHOW ENTRY '$ENTRY'
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
867 TEST.TXT Gibbons 135 Printing
Submitted 10-DEC-1998 11:07 /FORM=DEFAULT /PRIORITY=100
File: $5$DUA174:[GIBBONS]TEST.TXT;3
|
The PRINT command in this system example queues a copy of the file TEST.TXT to the default printer. It also creates the local symbol $ENTRY to store the job entry number. The SHOW ENTRY command requests a display of the entry using the symbol $ENTRY to identify it.
| #8 |
|---|
$ PRINT/RETAIN=UNTIL=1 MYFILE.DAT
.
.
.
$ SHOW QUEUE DOC$LN03
Server queue DOC$LN03, stopped, on NEWTON::, mounted form DEFAULT
Entry Jobname Username Blocks Status
----- ------- -------- ------ ------
436 MYFILE HERSHEY 8 Retained until 11-DEC-1998 16:56
%JBC-F-JOBABORT, job aborted during execution
Completed 11-DEC-1998 15:56 on queue DOC$LN03
|
The SHOW QUEUE display in this system example includes the date and time at which a retained job completed and the queue on which it executed. The user set job retention to be one hour after job completion. Depending on the queue's job retention policy, the job might be deleted from the queue at 16:56.
| #9 |
|---|
PRINT /PARAMETERS=AAA=123
|
This command passes the parameter AAA=123 to the print symbiont. The interpretation of the parameter is dependent on the symbiont.
| #10 |
|---|
$ PRINT /PARAMETERS=(ddd,"e,(F=(3,4),g),h)",iii)
|
This command passes three parameters to the print symbiont: DDD, "e,(F=(3,4),g),h)", and III. The use of the quotes around the second parameter allows the use of nested parentheses, commas, and the preservation of alphabetic case. This parameter value is perfectly acceptable to the PRINT command, even though it is apt to subsequently be rejected by the print symbiont.
| #11 |
|---|
PRINT /PARAMETERS=("N,O,P,Q,R,S,T",U,V)
|
This command passes three parameters to the print symbiont: "N,O,P,Q,R,S,T", U, and V. Depending on the parsing capabilities of the symbiont and the length of the parameters (each parameter is limited to 255 characters), this may be a workaround to the limitation of eight parameters.
| Previous | Next | Contents | Index |
|
|
| privacy and legal statement | ||
| 9996PRO_040.HTML | ||