 
 PRI [[queuename:][jobname][/jobsw]=]file[/filesw] . . .
 
 The PRINT command submits one or more files for printing. The files are
 grouped together into a single QMG print job and will all be printed
 together.
 
 The optional queuename allows you to submit your job to a queue other than
 the default PRINT. The optional jobname allows you to give your print job
 a name. If you do not specify jobname, the name of the first file in the
 job is used as the job name.
 
 The following job switches are available:
 
 /AF:hh:mm:dd-mmm-yy		/[NO]HO			/PA:pagecount
 /CO:jobcopies			/[NO]JO			/PRIO:priority
 /[NO]FL			/LE:pagelength		/[NO]RES
 /FO:formnumber			/[NO]LO			/[NO]TR
  
 If you specify a job switch, the equals ( = ) is required in the PRI command.

 The following file switches are available:
 
 /CO:filecopies			/[NO]DE			/[NO]TR
2 NOTR
#TR
2 TR

 The /NOTR switch inhibits copying of the file to be printed to LB:.  
 The default is /TR.  /NOTR can be a job switch or a file switch.
2 AFTER
 
 PRI /AF:hh:mm:dd-mmm-yy=files
 
 The /AF switch allows you to specify that the printing of your job should
 be delayed until after a specified date and time. The job will not print
 immediately at that time, but will become eligible to be printed, and will
 compete with other jobs at that time.
 
 You may specify either the date, or the time, or both. If you do not
 specify a date, the current date is assumed.  To specify the date
 without the time, omit the hh and mm values, but still include the
 colons.
 
 TOMORROW is a valid date specification.
 
 Examples:
 
 PRI /AF:18:00=LONGFILE.TXT		! print the file after 6 pm
 
 PRI /AF:::1-APR-82=JOKE.TXT		! print the file on April 1, 1982
 
 PRI /AF:0:0:TOMORROW=NEW.DAY		! print the file after midnight
 PRI /AF:::TOMORROW=NEW.DAY
2 COPIES
 
 PRI /CO:n=files
 PRI files/CO:n
 
 The /CO switch specifies the number of copies of a job or file that
 are to be printed. The switch may be used as either a job switch or
 a file switch. 
 
 As a job switch, /CO specifies how many copies of the complete job are
 to be printed. In the first example below, two copies of the job are
 printed. Each one consists of one copy of FILE1.TXT followed by one
 copy of FILE2.TXT.
 
 As a file switch, /CO specifies how many copies of the file on which
 the switch was used, and of all succeeding files, will be printed.
 Only one copy of the job is printed, but it contains two copies of
 FILE1.TXT followed by two copies of FILE2.TXT.
 
 Examples:
 
 PRI CO:2=FILE1.TXT,FILE2.TXT
 
 PRI FILE1.TXT/CO:2,FILE2.TXT
2 DELETE
 
 PRI files/[NO]DE
 
 The /DE switch specifies that the specified file, and all succeding files,
 are to be deleted after printing. The default is /NODE.
 
 Examples:
 
 PRI FILE1.TXT/DE,FILE2.TXT,FILE3.TXT		!Delete all files
 PRI FILE1.TXT,FILE2.TXT/DE,FILE3.TXT/NODE	!Delete FILE2.TXT only
 PRI FILE1.TXT,FILE2.TXT/NODE,FILE3.TXT/DE	!Delete FILE1.TXT and FILE3.TXT
2 FLAG
 
 PRI /[NO]FL=files
 
 The /FL switch specifies whether or not files in a job should be preceeded
 by file flag pages. The file flag pages separate files and show the
 file name and extenion in block letters. The default is /NOFL.
2 FORM
 
 PRI /FO:n=files
 
 The /FO switch specifies that your job is to be printed on a special paper
 form. Your installation may have different forms for different tasks, such
 as normal computer paper, narrow white paper for letters, check forms, etc.
 
 The default form number is /FO:0.
 
 See your system manager to find out what other forms are available at your
 installation
2 HOLD
 
 PRI /[NO]HO=files
  
 The /HO switch specifies that your job is to be held (made ineligible for
 printing). You must then release the job to allow it to be printed.
 
 See HELP QUE /REL.
2 JOBPAGES
 
 PRI /[NO]JO=files
 
 The /JO switch specifies whether or not your job should be preceeded by job
 flag pages. The default is /JO.
 
 If you specify /NOJO, your job will still start on a new page, but job flag
 pages will not be printed. You might do this if you were printing on a special
 form, particularly a short one.
2 LENGTH
 
 PRI /LE:n=files
 
 /LE specifies how many lines should be printed on a physical printer
 page. If, within 'n' lines, a formfeed has not been printed, the despooler 
 will insert one. In this way, you can limit the amount of text on a page.
  
 This is particularly useful if you are going to place the output in a listing
 binder. By using the /LE switch, you can prevent the despooler from printing
 over a perforation, which will be difficult to read when bound.  For instance,
 /LE:60 works well on a 66-line line printer.
 
 The default, /LE:0, specifies that no implied form feeds should be inserted.
2 LOWERCASE
 
 PRINT /[NO]LO=files
 
 The /LO switch specifies whether or not your job must be printed on a printer
 with lower case characters.
 
 If you specify /LO, your job will only be printed on a printer that has been
 initialized as having lower case characters.
 
 If you specify /NOLO, the default, your job may be printed on any printer that
 matches other job criteria.
 
 Notice that /LO does not affect a lower to upper translation. It is just a
 selection criteria used to select a printer.
2 PAGECOUNT
 
 PRI /PA:n=files
 
 The /PA switch allows you to specify a limit on the number of pages of output
 your job will produce. If the specified number of pages is exceeded, an error
 message is output and the job is deleted.
 
 The default is /PA:0, which specifies no page limit.
2 PRIORITY
 
 PRI /PRIO:n=files
 
 The /PRIO switch allows you to specify a priority for your print job. This
 priority has no effect on how quickly the job is printed once it is started,
 but is simply used to determine position in the queue.
 
 Privileged users may specify any priority between 1 and 250. Non-privileged
 users may only spcify priorities between 1 and 150.
 
 The default is /PRIO:50. /PRIO:0 is the same as /PRIO:50.
2 RESTART
 
 PRI /[NO]RES=files
 
 The /RES switch specifies whether or not your job is to be restarted from the
 beginning if it is interrupted.
 
 If you specify /RES, if your job is stopped for some reason, and then started,
 it will start over again from the beginning.
 
 If you specify /NORES, the default, if your job is stopped for some reason, and
 then started, it will continue from where it left off.

