Spooler Plus Utilities Reference Manual Abstract This manual describes the Spooler Plus utilities (Peruse, Spoolcom, Font, and RPSetup) and presents the complete syntax for these utilities. It also presents a general introduction to the Spooler Plus subsystem. This manual is intended for all interactive users of the Spooler Plus subsystem. Product Version Spooler Plus D41 Spooler Plus H01 Supported Release Version Updates (RVUs) This publication supports D48.03 and all subsequent D-series RVUs, G06.
Document History Part Number Product Version Published 140946 Spooler Plus D41 May 1998 422944-001 Spooler Plus D41 September 1999 425736-001 Spooler Plus D41 February 2000 522294-001 Spooler Plus D41 May 2002 522294-002 Spooler Plus D41 July 2005 Spooler Plus H01
Spooler Plus Utilities Reference Manual Index Figures What’s New in This Manual ix Manual Information ix New and Changed Information Tables ix About This Manual xi Who Should Use This Manual xi Related Manuals xi How This Manual Is Organized xii Notation Conventions xiii 1.
1. Introduction to the Spooler Plus Subsystem (continued) Contents 1.
2. Peruse (continued) Contents 2. Peruse (continued) LINK Command 2-27 LIST Command 2-28 LOC Command 2-32 NUMCOL Command 2-33 OPEN Command 2-34 OWNER Command 2-35 PAGE Command 2-36 PRI Command 2-37 PURGE Command 2-38 REPORT Command 2-39 SHOWGROUP Command 2-40 SJFILES Command 2-42 STARTCOL Command 2-43 STATUS Command 2-44 UNLINK Command 2-45 VOLUME Command 2-46 3.
3. Spoolcom (continued) Contents 3. Spoolcom (continued) JOB Command 3-52 LIST Command 3-62 LOC Command 3-66 NEXT Command 3-70 NUMCOL Command 3-71 OPEN Command 3-72 PAGE Command 3-73 POLL Command 3-74 PRINT Command 3-75 PURGE Command 3-80 PUT Command 3-81 PUTC Command 3-81 SJFILES Command 3-82 SPOOLER Command 3-83 STARTCOL Command 3-89 VOLUME Command 3-90 4.
5. RPSetup Utility Contents 5. RPSetup Utility How the RPSetup Utility Works 5-1 Interspooler Threads 5-3 Running RPSetup 5-6 Requirements for Running RPSetup 5-7 Example 5-8 Configuring Entities in the Local Spooler 5-8 Default Configuration 5-8 ASSIGN and PARAM Commands 5-10 A. SPOOL Program Running the SPOOL Program EMS Collector DEFINE A-4 A-1 B. Peruse Messages C. Spoolcom Messages D. Font Utility Messages E. RPSetup Utility Messages F.
G. Spooler Limits Contents G. Spooler Limits Extended Memory G-1 H.
Tables (continued) Contents Tables (continued) Table 3-6. Table 3-7. Table 3-8. Table 3-9. Table 3-10. Table 3-11. Table 3-12. Table 3-13. Table 3-14. Table 3-15. Table 3-16. Table 3-17. Table 3-18. Table 3-19. Table 5-1. Table 5-2. Table F-1. Table G-1. Table H-1. Table H-2. Table H-3. Table H-4.
Tables (continued) Contents Spooler Plus Utilities Reference Manual—522294-002 viii
What’s New in This Manual Manual Information Spooler Plus Utilities Reference Manual Abstract This manual describes the Spooler Plus utilities (Peruse, Spoolcom, Font, and RPSetup) and presents the complete syntax for these utilities. It also presents a general introduction to the Spooler Plus subsystem. This manual is intended for all interactive users of the Spooler Plus subsystem. Product Version Spooler Plus D41 Spooler Plus H01 Supported Release Version Updates (RVUs) This publication supports D48.
What’s New in This Manual • New and Changed Information In Section 2, Peruse, updated the example of a Peruse program banner (page 2-4).
About This Manual The Spooler Plus Utilities Reference Manual presents a general introduction to the Spooler Plus subsystem. The manual describes the Spooler Plus utilities— Peruse,Spoolcom, Font, and RPSetup—and presents the complete command syntax anddescriptions of the messages for these utilities. This manual also describes the FASTP configuration process and gives the programmatic limits of Spooler Plus components.
How This Manual Is Organized About This Manual How This Manual Is Organized Table i. Contents Section or Appendix Title Contents 1 Introduction to the Spooler Plus Subsystem Provides a general introduction to the Spooler Plus product for the interactive user. 2 Peruse Provides the syntax of all Peruse commands. 3 Spoolcom Provides the syntax of all Spoolcom commands.
Notation Conventions About This Manual Table i. Contents Section or Appendix Title Contents F Using FASTP Describes how to configure and use the FASTP print process. G Spooler Limits Lists programmatic limits of spooler components. H Spooler and Spooler Plus Comparison Describes the major differences between the Spooler and Spooler Plus subsystems. Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text.
General Syntax Notation About This Manual [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num ] [ text ] K [ X | D ] address { } Braces.
Notation for Messages About This Manual Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In the following example, there are no spaces permitted between the period and any other items: $process-name.#su-name Line Spacing.
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input entered at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned.
Notation for Management Programming Interfaces About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number.
Change Bar Notation About This Manual Spooler Plus Utilities Reference Manual—522294-002 xviii
1 Introduction to the Spooler Plus Subsystem The HP Spooler Plus subsystem is a set of utilities that form an interface between you (and your application programs) and the print devices of a system. The Spooler Plus subsystem receives output from an application and stores it on disk. This output can be a report in the format of an EDIT file (file code 101), a listing from a compiled program, or other data. When the designated print device becomes available, the output is printed.
Introduction to the Spooler Plus Subsystem Spooler and Spooler Plus Comparison Spooler and Spooler Plus Comparison Spooler Plus is an optional product containing Spoolcom and Peruse modules that can be used to replace the Spoolcom and Peruse modules provided by the D41 or later releases of the Spooler subsystem. You can use the Spooler Plus Spoolcom and Peruse utilities to configure and manage expanded configurations of the Spooler subsystem.
Introduction to the Spooler Plus Subsystem Spooler Components Spooler Components The spooler consists of the components: • • • • • • • The spooler supervisor monitors and communicates with the other programs and determines when and where to print jobs. There is only one supervisor in each spooler subsystem; however, many spooler subsystems can operate at one time. Collector processes accept output from applications and store it on disk.
Spooler Components Introduction to the Spooler Plus Subsystem Figure 1-1. Components of the Spooler \SYS Spooler Subsystem Spoolcom* Application Spooler Control Files Peruse* Supervisor Collector Collector Data Font and RPSetup* Print Process** Printers Input/Output Process Legend * Applications can perform all the functions of Peruse, Spoolcom, Font, and RPSetup; therefore, these programs can be considered applications. ** A print process can be FASTP or user written. VST019.
Collectors Introduction to the Spooler Plus Subsystem Collectors The spooler includes one or more collectors, each of which is a continuously running copy of the program in $SYSTEM.SYSTEM.CSPOOL. An application can direct output from an application program to a collector by treating the collector as its OUT file; that is, an application can open a file to any collector and begin writing its output using the Guardian file-system WRITE[X] procedure.
Introduction to the Spooler Plus Subsystem Collectors Index blocks are used to keep track of the units of space allocated to a job. The current index block for a job is kept in memory during collection so that there is no overhead as entries are being made. The collector chooses the addresses of the first allocated unit in the collection file for a job in such a way as to minimize the contention for the same units by different jobs. It also attempts to keep the units for a job as contiguous as possible.
Introduction to the Spooler Plus Subsystem Spooling in a Network Unit Size The Spoolcom COLLECT UNIT command is used to specify a unit size for the collector. The unit size specifies the number of 512-word blocks the collector allocates from its data file each time it needs more space for a job. A collector can manage as many units as a physical file will hold. The larger the unit size, the less often the collector must allocate a new unit.
Peruse and Spoolcom Comparison Introduction to the Spooler Plus Subsystem Figure 1-2. Linked Spoolers in a Network \PRNT \APPL Application Spooler Subsystem Collector Spooler Subsystem Collector Spooler Control Files Collector Data Supervisor FASTP Print Process Collector Data Spooler Control Files Print Process Supervisor Printers Legend Data flow Control flow VST012.vsd Peruse and Spoolcom Comparison Peruse is intended for everyday users for monitoring and changing jobs.
Introduction to the Spooler Plus Subsystem Spooler Jobs and Job Attributes Spooler Jobs and Job Attributes When you request the spooler to print information, the request is called a spooler job. The spooler assigns to each job a job number in the range 1 through 65534. (The system operator can set the maximum job number to a lower value with the SPOOL program. See Appendix A, SPOOL Program.
Job Location Introduction to the Spooler Plus Subsystem For example, if an application program produces a job that fills out W-2 forms, the job must be printed on a device loaded with special W-2 form paper. If the job has a form name of W2, it will print only on a device that has the same form name. The form name W2 is assigned to the device when the special paper is loaded. Job Location The job location can be associated with a physical print device on the system or with a dummy holding location.
Introduction to the Spooler Plus Subsystem Devices and Device Attributes A job in the READY state is ready to print but is not yet printing. The job enters the READY state when the application closes the collector process. The job waits in the device queue until it is ready to print. A job in the PRINT state is being printed. The PRINT state is normally the last state before the job is deleted from the spooler.
Introduction to the Spooler Plus Subsystem Device State each device. When the header message is turned on, it prints on the first page of the job; the report name and location are printed in large banner-sized letters. If the header message is turned off, jobs print consecutively with only a form feed (new page) to indicate the beginning of the next job. If you specify a batch header, the job information prints on two of the three trailer pages as well as on the first two pages of each job.
Routing Structure Introduction to the Spooler Plus Subsystem Routing Structure The routing structure directs jobs to print devices. It consists of a set of locations and print devices. Figure 1-4 shows the association of locations with print devices. Figure 1-4. The Spooler Routing Structure Groups: #X, #Y, #Z Locations: #X.A, #X.B, #X.C, #Y.D, #Y.E, #Z.F Devices: LP1, LP2, LP3, LP4 Group #X A LP1 B LP2 C LP3 Group #Y D E LP4 (Broadcast) Group #Z F VST008.
Introduction to the Spooler Plus Subsystem Broadcast and Nonbroadcast Groups Location names have two parts: a group name and a destination name. The group name is always preceded by the # character; for example, #LP and #HT. Examples of full location names are: #LP.LPEAST #LP.LPWEST #LP is a group name, and LPWEST and LPEAST are destination names. Broadcast and Nonbroadcast Groups If you specify only the group name as the location, the spooler supplies the destination.
Introduction to the Spooler Plus Subsystem Implicit Route Creation Implicit Route Creation When jobs are routed to a dummy location, the spooler implicitly creates a route. (A dummy location is a nonexistent location.) For example: • • When a job is routed to location #X.1, where either the group or the destination does not exist, the spooler creates the location #X.1. When a job routed to group #X, where group #X does not exist, the location #X.DEFAULT and the group #X are created.
Introduction to the Spooler Plus Subsystem Sending Process Output to a SPOOL DEFINE 3> TFORM /IN MYFILE, OUT $S/ In this case, the job is sent to #DEFAULT and is printed on one of the devices associated with the #DEFAULT group name. Sending Process Output to a SPOOL DEFINE You can also use a SPOOL DEFINE to specify the attributes of a spooler job before you create it.
Introduction to the Spooler Plus Subsystem The Spooler and Batch Jobs When a batch job is printed, each member job is delivered to the device in the sequence in which it is linked in the batch. Optional batch headers can be applied to identify the beginning and end of the batch output. A batch job can be created in the spooler only when a job is opened that originates from a process that has a JOBID attribute. The JOBID attribute may be established using a DEFINE or a RUN parameter.
How to Change the Attribute Values of Batch Jobs Introduction to the Spooler Plus Subsystem Figure 1-5. How the Spooler Determines Which Jobs Are to Be Batched FUP /OUT $S.output-device, NOWAIT /COPY filename Spooler Collector OPEN request to $S NO Job is a normal job Is there a JOBID? First job for the assigned spooler batch job YES Is there an open spooler batch job with the same key attributes? NO Create a new spooler batch job YES Link this job to the first spooler batch job VST004.
Introduction to the Spooler Plus Subsystem Linking and Unlinking Jobs You can use Peruse or Spoolcom to change the following attributes for all jobs in a batch job: • • • • • • • COPIES FORM HOLD HOLDAFTER OWNER PRI REPORT Peruse commands are described in Section 2, Peruse and Spoolcom commands are described in Section 3, Spoolcom.
Introduction to the Spooler Plus Subsystem Spooler Security Dummy locations represent the same null device key attribute value. In other words, jobs whose output is directed to dummy locations, regardless of their value and preciseness of their locations, will be grouped together in the same batch job if all other key attributes match.
2 Peruse Peruse is an interactive program that allows you to examine and change the attributes of your job while it is in the spooler subsystem. Topics described in this section include the following: • • • Peruse Features on page 2-2 Running Peruse on page 2-3 Peruse Commands on page 2-9 Note. The command displays shown in this section are applicable to D41 and later versions of the spooler supervisor.
Peruse Features Peruse Peruse Features With Peruse you can • • • • • • • • Examine a job (such as a lengthy compiler listing) before printing or deleting it. Display a job while it is being spooled. Monitor changes in the status of a job. Alter job attributes, such as location, number of copies, and report name. Print out specific pages or the entire spooled job. Copy a job from the spooler queue to an EDIT file or a spooler job file. (Spooler job files are described in this section.
Running Peruse Peruse Running Peruse You can run Peruse by entering the following command at the TACL prompt: [ \system.] Peruse [ / run-options / ] [ supervisor ] [ ; command ] ... \system specifies the name of a remote system (node) where Peruse is to execute. The default system is your home system. run-options are any run options for the command-interpreter RUN command, separated from each other by commas and set off in the command line by slashes (/).
Running Peruse Interactively Peruse Running Peruse Interactively To run Peruse interactively, do not specify Peruse commands in the command line when starting Peruse. Peruse displays its program banner, copyright message, and prompt, an underscore ( _ ). An example follows: \DRPSOC.$OS.DRPUSER 1> PERUSE PERUSE - T9101H01 - (01OCT2004) SYSTEM \DRPSOC (C)1978 Tandem (C)2004 Hewlett-Packard Development Company, L.P. T9101H01 is the product version of Peruse.
Initial Job Status Display Peruse Initial Job Status Display If you have jobs in the spooler queue when you start Peruse, they are listed below the program banner as shown in the following example: PERUSE - T9101D41 - (05MAY97) SYSTEM \EAST Copyright Tandem Computers Incorporated 1978, 1982, 1983, 1984, 1985, 1986, 1987, 1988, 1989, 1991 JOB 1167 1289 1298 1322 BATCH 555 555 555 STATE READY READY READY OPEN PAGES 1 430 3 COPIES 1 1 1 3 PRI HOLD LOCATION 4 #BATCH 4 #BATCH 4 #NOT BATCH 4 #NEW DOCUMNT
Entering Peruse Commands Peruse HOLD Shows the hold status of the job: A The hold-after-printing flag is on. The job remains in the queue after it is printed. B The hold flag is on but the job cannot be placed in the HOLD state (the job is in the OPEN state). The job will be placed in the HOLD state when it has been collected. X For some reason the job is in error (for example, an application abended while spooling the job). LOCATION Shows the location of the job.
Declaring the Current Job Peruse Declaring the Current Job Most Peruse commands affect only the current job. At the beginning of a Peruse session, however, there is no current job. To declare the current job, use one of the following methods: • • Set the current job explicitly by entering a JOB command with the job number. (You can also set the current job by entering only the job number.) Set the current job implicitly by entering a Peruse command or by pressing the RETURN key or a function key.
Using Spooler Job Files Peruse Using Spooler Job Files You can also use Peruse with spooler job files. A spooler job file is an unstructured disk file with file code 129. This type of file contains a spooler job, including print data records and formatting control information (CONTROLs, CONTROLBUFs, and SETMODEs). A spooler job file does not appear in the job display list unless you declare it as the current job by using the JOB command with the file name.
Peruse Commands Peruse Peruse Commands Table 2-2 contains a summary of all Peruse commands. Refer to the Guardian User's Guide for more information on how Peruse can help you examine your spooled jobs. Table 2-2. Summary of Peruse Commands (page 1 of 2) Command Function BATCH Causes the specified batch job to be current. COPIES Alters the number of copies for the current job. DEL Deletes the current job. DEV Displays the status of a device. EXIT Terminates the Peruse session.
BATCH Command Peruse Table 2-2. Summary of Peruse Commands (page 2 of 2) Command Function STATUS Monitors and displays the status of jobs in the system. UNLINK Dissociates the specified spooler job from the current batch job. VOLUME Sets the current default volume and subvolume used by Peruse. BATCH Command The BATCH command causes the specified batch job to become current. BATCH batch-number batch-number is the number of a batch job that you own.
COPIES Command Peruse To see the status of the current job, enter a JOB command: _JOB Peruse then displays the following: JOB BATCH STATE PAGES B 1167 555 PRINT 1 1200 READY 3 B 1289 555 READY 430 _ COPIES 1 1 1 PRI HOLD LOCATION 4 #LP2X 4 #ANOTHERFILE 4 #LP2X REPORT STEVEW STEVEW STEVEW After you set the current batch, Peruse identifies jobs in this batch in subsequent displays with a B to the left of the job numbers. In the example above, jobs 1167 and 1289 are in the current batch (555).
DEL Command Peruse Example The following example illustrates how you can obtain two printed copies of a spooled job.
DEL Command Peruse Examples 1. In this example, the current job is job 52. You can use DEL to delete it from the spooler: _JOB JOB BATCH STATE J 52 HOLD 133 READY PAGES COPIES PRI HOLD LOCATION REPORT 2 1 4 #LPRMT3 ACCT SUE 5 1 4 #LP ACCT SUE _DEL _ Another JOB command verifies that job 52 has been deleted: _JOB JOB BATCH STATE 133 READY PAGES COPIES PRI HOLD LOCATION REPORT 5 1 4 #LP ACCT SUE _ 2.
DEV Command Peruse 3. Before you can delete a job, you must make it the current job. When using Peruse noninteractively, you can use the JOB * command to make the most recently spooled job current so you can delete it: 9> PERUSE; JOB *;DEL DEV Command The DEV command displays the status of a specified device and lists the job queue for that device. DEV $device $device is the name of a device on the spooler subsystem. Considerations Most of the status information is self-explanatory.
EXIT Command Peruse EXIT Command The EXIT command ends the Peruse session. E[XIT] Consideration Pressing Ctrl-Y also ends the Peruse session. Example When you exit Peruse, you receive a command-interpreter prompt: _EXIT 4> FC Command FC (Fix Command) lets you modify and resubmit the last command line entered. The FC subcommands are similar to those used for the command-interpreter FC command, described in the TACL Reference Manual.
FILES Command Peruse Example In this example, the user tried to use the DEV command with #LP instead of $LP, and received the message ENTRY NOT FOUND. The user can fix the command by replacing # with $ and reexecuting it: _DEV #LP ENTRY NOT FOUND _FC _DEV #LP . $(press Return) _DEV $LP .(press Return) DEV STATE: PRINTING JOB 1435 OWNER 009,013 PAGES 377 FORM: WAIT 00:05:55 FORM _ FILES Command The FILES command displays the names of all files on a subvolume.
FIND Command Peruse 2. In this example, the user provides the volume name, and the system and subvolume names are the current default names: _FILES $BIGVOL \SYSII.$BIGVOL.SUBVOL NAMES .SAVE _ PLANS PROFILE SOURCE 3. In this example, the user provides the system and subvolume names, and the volume name is the current default name: _FILES \NEWSYS.MYSVOL \NEWSYS.$DISK.MYSVOL .LDATA ERRORS _ .RECORDS .
FIND Command Peruse start-position is the page number from which to begin the search. start-position can be specified as [ F | L | * | number ] [ offset ] F is the first page of the job. L is the last page of the job. * is the current page of the job. number is a page number. offset is specified as [ + number | - number ] If an offset is specified, it is added to or subtracted from the base (F, L, or *) to define the page.
FORM Command Peruse **** ERROR 27 **** Illegal syntax 2. The example below shows how Peruse can find a phrase regardless of whether the characters are uppercase or lowercase: _F B 'NONSTOP' NonStop system software. _ 3. In this example, Peruse begins searching on page 95 of the job for the specified string: _F B /debug/ 95 with the DEBUG subcommand. _ FORM Command The FORM command alters the form name of the current job.
FORM Command Peruse Example In this example, you want your job to print out on a printer loaded with blank paychecks. You send the job to the spooler, specifying the location where your form paper is loaded, as the DEV command confirms: JOBV J 1221 BATCH STATE READY PAGES 1 COPIES PRI HOLD LOCATION REPORT 1458 4 #CHKWRTR BKKPG JEN _DEV $CHKWRTR DEV STATE: WAITING FORM: PAYCHECK _ Then you specify the same form for your job.
HELP Command Peruse HELP Command The HELP command describes the syntax and semantics of Peruse commands. HELP [ / OUT list-file / ] [ command-name | ALL ] OUT list-file is the file, process, or device that receives the help message. If you do not specify OUT list-file, output is directed to the OUT file specified when Peruse was started by default (the home terminal). If OUT list-file is specified, Peruse writes the data to the file, process, or device in a manner suitable for it.
HOLD Command Peruse HOLD Command The HOLD command sets the hold-before-printing flag on or off for the current job. If there is no current job, then the job most recently spooled becomes the current job. HOLD [ ON | OFF ] ON sets the hold flag on for the current job. When no argument is specified, ON is assumed. OFF sets the hold flag off for the current job. Considerations • • • The HOLD command is not supported if the current job is a spooler job file.
HOLDAFTER Command Peruse The following command, removes the hold and the job once again begins printing from page 1: _HOLD OFF;J JOB BATCH STATE PAGES COPIES PRI HOLD LOCATION REPORT J 75 PRINT 15 1 4 #LP ADMIN BILL 1001 READY 33 1 4 #DEFAULT ADMIN BILL _ HOLDAFTER Command The HOLDAFTER command sets the hold-after-printing flag on or off for the current job. If there is no current job, then the job most recently spooled becomes the current job.
JOB Command Peruse When the job finishes printing, it enters the hold state and the hold-after-printing flag is still on: JOB J 722 BATCH STATE PAGES COPIES PRI HOLD LOCATION REPORT HOLD 3 1 4 A #HT1 INVENT PAT At a later time, you can print another copy of this job without repeating the compiling and spooling time.
JOB Command Peruse * specifies the job most recently added to the spooler subsystem. Entering an asterisk causes the most recently added job to become the current job. S[TATUS] returns an expanded display of the status of the current job. See the description of #location-name. #location-name is the name of a spooler location in the form #group.destination. It specifies the job most recently sent to that location. For more information on spooler locations, refer to the Guardian User's Guide.
JOB Command Peruse • • The second part has three entries that are displayed only if the job is in one or more device queues. Their meanings are as follows: JOB is the job number of the current job. FORM is the form name of the current job. CLOSE TIME is the date and time the collector finished collecting data from the application. A job still spooling has OPEN as its closing timestamp.
LINK Command Peruse JOB FORM 1234 CLOSE TIME 14 JUL 97, 10:19:13 JOB LOCATION 1234 #HT10.DEFAULT 1234 #HT10.HT10 DEVICE $HT10.#HT10 $HT10.#HT10 SEQ 2 3 COPY 1 1 PAGE 15 15 _ If you specify the name of a spooler job file, that file becomes the current job and appears in the job display list: _J $DSK.JVOL.LISTING; J The following information is displayed: JOB BATCH STATE PAGES J FILE READY 60 1113 READY 100 1234 READY 15 _ COPIES 1 1 1 PRI HOLD LOCATION REPORT 4 $DSK.JVOL.
LIST Command Peruse To add job 1200 to batch 555, you must first enter the command to make batch 555 current. Then you enter a LINK command to link job 1200 to the current batch job. Enter a JOB command to verify that job 1200 is linked to batch 555. _BATCH 555 _LINK 1200 _JOB JOB BATCH B 1167 555 B 1200 555 B 1289 555 _ STATE READY READY READY PAGES 1 3 430 COPIES 1 1 1 PRI HOLD LOCATION 4 #BATCH 4 #ANOTHERFILE 4 #CHECK.TACL REPORT STEVEW STEVEW STEVEW Note.
LIST Command Peruse in the spooler job file. If you specify C[OMPRESS] and list-file is a process, the command is accepted but ASCII compression is not performed. OUT list-file identifies the file, process, or device to receive the output. If you specify E[DIT], S[POOL], or C[OMPRESS], then list-file is subject to the conditions described above. If you did not specify E[DIT], S[POOL], or C[OMPRESS], then the following apply: • • If list-file does not exist, Peruse creates a spooler job file.
LIST Command Peruse information is suppressed, except when listing to a spooler job file or spooler collector. For details about formatting control, refer to the Guardian Programmer's Guide. N if list-file is a spooler job file or a spooler collector, prevents formatting-control information (CONTROLs, CONTROLBUFs, and SETMODEs) embedded in the job from being written to list-file along with the print data. Normally, this information is included when listing to a spooler job file or a spooler collector.
LIST Command Peruse Examples These examples do not show the pages listed because it would require too much space. However, the effect of each example is discussed in detail. 1. This command lists absolute page 23 in text format and absolute page 30 in octal display format: _LIST 23, 30 O 2. This command lists pages 15 through 35, inclusive: _L 15/35 3. This command lists the last page of the job: _L 4. This command lists the second page from the end of the job: _LIST L-2 5.
LOC Command Peruse TFORM file, you must specify the C parameter to retain the formatting-control information. _FIND "**ERROR" _LIST /OUT $S.#LP/ 16/19 C 10. You can use Peruse to compress data for more efficient archiving. The command below stores the contents of a spooler job (file code 129) into a spooler job file. It compresses ASCII characters into 5 bits instead of 8. The A specifies all pages and the C causes these pages to retain formatting-control information.
NUMCOL Command Peruse Example In this example, you have specified #HOLD as list-file in order to examine the job before printing: _JOB JOB J 777 _ BATCH STATE PAGES COPIES PRI HOLD LOCATION READY 22 1 4 #HOLD REPORT ACCOUNT ED Once you finish inspection, use the LOC command to redirect the output to the specified printer for a hard copy: _LOC #LP3;J JOB J 777 _ BATCH STATE PAGES COPIES PRI HOLD LOCATION REPORT READY 22 1 4 #LP3 ACCOUNT ED NUMCOL Command The NUMCOL command alters the number of column
OPEN Command Peruse Example In the example below, you display lines of your spooled file on your page-mode terminal by pressing the F2 function key, which displays four lines: _(Press the F2 function key) 54. 55. 56. 57. _ 000000 000000 000000 000000 0 0 0 0 0 0 1 1 STRUCT buffer ; BEGIN INT status, reserved; Using the NUMCOL command, you can stop the display of all columns to the right of the eighteenth column.
OWNER Command Peruse Considerations • • • To open the local supervisor, the supervisor name can be omitted if it is $SPLS. To open a remote supervisor, the system name can be specified without the process name if the process is $SPLS. After you execute an OPEN command, Peruse displays the new spooler supervisor name and then lists the jobs that you have in that spooler queue.
PAGE Command Peruse Examples 1. An example of the OWNER command using the group-name.user-name form is _OWNER ADMIN.BILL 2. An example of the OWNER command using the group-#, user-# form is _OWNER 7, 10 3. You have a hold on job 454 and want to transfer its ownership to user 7,10. You can do this with the OWNER command.
PRI Command Peruse Considerations • • The current line can also be changed using a FIND command or by listing lines. The pages of a spooled job include not only the pages of your spooled file but also any error pages generated by your application. You can use this fact to find your TFORM errors. Refer to information on using Peruse with TFORM in the Guardian User's Guide. Examples 1.
PURGE Command Peruse • If a batch job is current, the PRI command operates on all jobs that are part of the current batch job. • The PRI command is not supported if the current job is a spooler job file. For a more complete description of the spooler queuing algorithm, see the Guardian System Operations Guide. Example In this example, your current job has the default priority of 4.
REPORT Command Peruse REPORT Command The REPORT command alters the report name of the current job. If there is no current job, then the job most recently spooled becomes the current job. The report name is usually printed in the header in large banner-sized letters at the beginning of the job. REPORT [ report-name ] report-name is the new report name for the current job. report-name is composed of as many as 16 letters, digits, and blanks, and must begin with a letter.
SHOWGROUP Command Peruse SHOWGROUP Command The SHOWGROUP command enables or disables the display to a group manager (user ID n,255) of all jobs that belong to group members. This command affects the displays produced by the JOB and STATUS commands. { SHOWGROUP | SG } [ ON | OFF ] ON enables display to a group manager of all the jobs that belong to the manager’s group members. This is the default value and is equivalent to entering SHOWGROUP.
SHOWGROUP Command Peruse Examples 1. The following example shows the initial JOB command display for a group manager invoking Peruse when manager access is enabled for the spooler. Only job 3080 (report name AD MGR) actually belongs to the manager.
SJFILES Command Peruse 4. The following example shows the Spoolcom SPOOLER STATUS command you can use to determine whether manager access is enabled. The display shows whether MGRACCESS is ON or OFF. 5> FontRPSetup;SPOOLER,STATUS DETAIL SPOOL SUPERVISOR: $SPLS STATE: ACTIVE MGRACCESS: ON LOG FILE: $0 LAST ERROR: NONE SJFILES Command The SJFILES command displays the names of all spooler job files on a subvolume. The names of spooler job files are preceded by a period (.).
STARTCOL Command Peruse 3. In this example, the system and subvolume names are provided while the volume name is the current default name: _SJFILES \NEWSYS.MYSVOL \NEWSYS.$DISK.MYSVOL .LDATA .RECORDS _ .OLDLIST STARTCOL Command The STARTCOL command alters the starting column number used when a job is listed. The first column is 1. STARTCOL starting-column starting-column is a number greater than 0 and less than or equal to the rightmost column in the current job. The default column number is 1.
STATUS Command Peruse Then you use the PAGE * command to reposition yourself to the first line of the page and execute a STARTCOL command to suppress the first 18 columns of the program.
UNLINK Command Peruse Example After sending job 639 to the spooler location $S.#HOLD, using the NOWAIT option, you enter Peruse. When you execute the STATUS command, a status display appears, after which the Peruse prompt does not return; Peruse is waiting for the status of a job to change. _STATUS JOB BATCH STATE PAGES COPIES PRI HOLD LOCATION REPORT 633 READY 7 1 4 #LP PAYROLL J 639 OPEN 1 4 #HOLD PAYROLL The status of a job has changed: job 639 has completed spooling and now has a page count.
VOLUME Command Peruse Example The following Peruse display shows three jobs (1167, 1200, and 1289) in batch 555: PERUSE - T9101D41 - (05MAY97) SYSTEM \NS Copyright Tandem Computers Incorporated 1978, 1982, 1983, 1984, 1985, 1986, 1987, 1988, 1989, 1991 JOB 1167 1200 1289 BATCH 555 555 555 STATE READY READY READY PAGES 1 3 430 COPIES 1 1 1 PRI HOLD LOCATION 4 #BATCH 4 #ANOTHERFILE 4 #CHECK TACL REPORT STEVEW STEVEW STEVEW To unlink job 1200 from batch 555, first enter the BATCH command to make batch
VOLUME Command Peruse Considerations • • Entering VOLUME with no volume or subvolume name restores the default names that were in effect when you started Peruse. Peruse and the command interpreters have separate default names for system, volume, and subvolume. When you return to the command-interpreter prompt from Peruse, the default names are reset to the values that were in effect before you started Peruse. Examples 1.
VOLUME Command Peruse Spooler Plus Utilities Reference Manual—522294-002 2- 48
3 Spoolcom Spoolcom is an interactive program that gives you control of the spooler. This section contains complete syntax, considerations, and examples of Spoolcom commands for authorized users and others. Topics described in this section include the following: • • • • Spoolcom Features on page 3-2 Spoolcom Security on page 3-2 Running Spoolcom on page 3-3 Spoolcom Commands on page 3-6 Information on how to use Spoolcom interactively and noninteractively is described in the Guardian User’s Guide.
Spoolcom Features Spoolcom Spoolcom Features With Spoolcom, you can • • • • • Display the status of collectors, devices, jobs, print processes, routing structures, and the spooler itself Change the location, state, or any attribute of your job Delete your job from the spooler subsystem Restart a device that has gone offline with a device error Perform the perusal functions of Peruse Other operations performed using Spoolcom can effect the entire spooler subsystem.
Running Spoolcom Spoolcom Running Spoolcom You can run Spoolcom by entering the following command at the TACL prompt: SPOOLCOM [ / run-options / ] [ supervisor ] [ ; command ] ... run-options are any run options for the command-interpreter RUN command, separated from each other by commas. See the description of the command-interpreter RUN command in the TACL Reference Manual for a complete set of the run options.
Running Spoolcom Interactively Spoolcom Running Spoolcom Interactively To run Spoolcom interactively, do not specify Spoolcom commands in the command line when starting Spoolcom. Spoolcom displays its program banner, copyright message, and the Spoolcom prompt, which is the close parenthesis character, “)”.: SPOOLCOM - T9101D41 - (05MAY97) SYSTEM \EAST Copyright Tandem Computers Incorporated 1997 ) T9101D41 is the version of Spoolcom. (05MAY97) is the release date for this version of Spoolcom.
Declaring the Current Job Spoolcom Spoolcom puts the component in the drain state but does not wait for the drain to finish. You can eliminate the need to repeat the job number in each command by first setting the job as the current job. Using this technique, you would enter the three commands shown above as follows: )JOB )JOB )JOB )JOB 1635, 1635, 1635, 1635, CURRENT HOLD REPORT TAL COMPILE START Declaring the Current Job Some Spoolcom commands affect only the current job.
Spoolcom Commands Spoolcom Spoolcom Commands A Spoolcom command summary describing the features available to all users is given in Table 3-2. Table 3-2. Spoolcom Command Summary for All Users (page 1 of 2) Command Function BATCH Alters attributes and changes the state of your batch jobs. This command also obtains the status of any batch job in the spooler subsystem. COLLECT Obtains the status of spooler collectors. COMMENT Designates a comment to be ignored by Spoolcom.
Spoolcom Commands Spoolcom Table 3-2. Spoolcom Command Summary for All Users (page 2 of 2) Command Function PUTC Creates the edit-file-name and loads it with the current job. Carriagecontrol information is saved in the first character position of each line. Topof-form is an l, over-print is a t. SJFILES Displays only the spooler job files in the specified or default subvolume. SPOOLER Obtains the status of the spooler. STARTCOL Alters the starting column number used by the LIST commands.
BATCH Command Spoolcom BATCH Command Authorized users can use the BATCH command to specify attributes, obtain the status, and change the status of any batch job. Refer to the Guardian User's Guide for a description of batch job states and default attributes. All users can perform these operations on their own batch jobs. BATCH [ batch-number ] [ , subcommand ] ... batch-number is the number of the batch job. subcommand is one of the subcommands described below.
BATCH Command Spoolcom HOLD places the batch job in the HOLD state. A batch job must be in the HOLD state before most other attributes can be modified. To remove a batch job from the HOLD state, use the START subcommand. HOLDAFTER [ OFF | ON ] sets the hold-after-printing flag on or off. HOLDAFTER or HOLDAFTER ON places the batch job in the hold state after it is printed. HOLDAFTER OFF (the default) allows the batch job to be deleted after printing.
BATCH Command Spoolcom OUT file-name indicates where Spoolcom is to write the batch job status. If not specified, the status is written to the Spoolcom OUT file (usually the home terminal). If OUT filename is specified, Spoolcom writes the data to it in a manner suitable for the file type, process, or device. file-name must be specified; if the file does not exist, Spoolcom creates an EDIT file (file type 101).
BATCH Command Spoolcom Considerations • • To change the attribute values of all jobs belonging to a batch job, you must use the BATCH command. You can still use the JOB command to change the attributes of a single job even if that job is part of a batch job; however, you cannot change any of its key attributes (form, owner, or location). Examples 1. This three-step example requires authorized access.
BATCH Command Spoolcom JOB: 10000 STATE: READY LOCATION: #LP8 FORM: REPORT: ADMN SUE HOLD BEFORE PRINT: NO HOLD AFTER PRINT: NO ABNORMAL: NO SELECTION PRIORITY: 7 PAGE SIZE: 60 CREATOR ACCESS ID: 1,32 COPIES: 2 PAGES: 28 TOTAL LINES: 1652 OPEN TIME: 16 OCT 88, 13:58:10 CLOSE TIME: 16 OCT 88, 14:23:33 DATA FILE: $SP.SPLR.SDATA COLLECTED BY: $S UNITS ALLOCATED: 15 BATCH ID: 233 BATCH NAME: MAXIMUM LINES: MAXIMUM PAGES: JOB: 10001 STATE: READY . . . .
COLLECT Command Spoolcom COLLECT Command If you are an authorized user, you can use the COLLECT command to specify attributes, obtain the status, and change the state of the spooler collectors. Refer to the Guardian System Operations Guide for a description of collector states and default attributes. Any user can obtain the status of spooler collectors. COLLECT [ $process-name ] [ , subcommand ] ... $process-name is the name of the collector to which the subcommands refer.
COLLECT Command Spoolcom DRAIN causes the collector to stop accepting new jobs. The collector becomes dormant when all open jobs finish spooling. The collector must be in the dormant state in order to have its attributes changed. FILE program-file-name specifies the file name of the program to run the collection process. Usually this is $SYSTEM.SYSTEM.CSPOOL.
COLLECT Command Spoolcom If OUT file-name is specified, Spoolcom writes the data to it in a manner suitable for the file type, process, or device. file-name must be specified; if the file does not exist, Spoolcom creates an EDIT file (file type 101). The file can be an EDIT file, an unstructured file, a relative file, an entry-sequenced file, a spooler job file, a process, or a device. DETAIL requests a complete list of all collector attributes.
COLLECT Command Spoolcom • • • • The data-file-name parameter should exist before the DATA subcommand is specified. The DATA data-file-name subcommand should be specified only before the collector is first started. See the information on creating data files in the File Utility Program (FUP) Reference Manual. File space usage efficiency is affected by the UNIT size setting if it is significantly larger than the average job size.
COLLECT Command Spoolcom COLLECT STATUS Display The STATUS subcommand can be issued at any time. It produces a display with the following headings: COLLECT STATE FLAGS CPU PRI UNIT DATA FILE %FULL Table 3-5 describes the COLLECT STATUS display entries. Table 3-5. COLLECT STATUS Display Entries Entry Description COLLECT Is the collector name. STATE Is the state of the collector. STATE can be one the following: ACTIVE The collector process is running.
COLLECT Command Spoolcom Table 3-6. COLLECT STATUS DETAIL Display Entries Entry Description STATE See the explanation of STATE in Table 3-5. LAST ERROR Is the octal number of the last error printed to the error log. This value can be %1000, %2000, %3000, %4000, or %5000 plus a file-system error number, or %100000 plus a NEWPROCESS error number. The octal error number is a 16-bit value where bits 8 through 15 contain the file-system error number.
COLLECT Command Spoolcom 2. To show the status of only one collector, enter )COLLECT $C, STATUS The following information is displayed: COLLECT STATE FLAGS CPU PRI UNIT DATA FILE %FULL $C ACTIVE 3 ,10 146 16 $ACC.SPOOLER.DATA 0 ) 3. To find more information about that one collector, specify STATUS DETAIL: )COLLECT $C, STATUS DETAIL The following information is displayed: COLLECTOR: $C STATE: ACTIVE LAST ERROR: NONE PROGRAM FILE: $SYSTEM.SYSTEM.CSPOOL CPU: 3 BACKUP: 10 PRIORITY: 146 DATA FILE: $ACC.
COMMENT Command Spoolcom Examples for Authorized Users 1. The following command specifies that CPU 3 is the primary location (and CPU 0 is the backup) from which collector $S is to run a copy of the program located in $SYSTEM.SYSTEM.CSPOOL. This collector stores jobs on the file SPLDATA: )COLLECT $S, FILE CSPOOL, DATA SPLDATA, CPU 3, BACKUP 0 2.
DEV Command Spoolcom DEV Command The DEV command controls and obtains the status of devices in the spooler subsystem. Authorized users can use the DEV command to delete a device from the spooler or to add to the spooler a new device that was configured at system generation but was not included in the spooler coldstart. Refer to the Guardian System Operations Guide for a description of these tasks as well as information on device states and default attributes.
DEV Command Spoolcom NONE specifies that no multibyte character-set translation is required. This is the default value if the CHARMAP subcommand is not used or is used without a parameter. IBMKANJIKANA specifies the IBM Kanji character set. JEFKANJIKANA specifies the Fujitsu Kanji character set. JISKANJIKANA specifies the JIS C-6234 or C-6220 character set. CLEAR [ DEL ] stops printing the current job.
DEV Command Spoolcom DEVTYPE LU1 and DEVTYPE LU3 control the configuration of a print device attached to a controller located in an IBM domain. FASTP must be the spooler print process. DEV PARM form-feed options take precedence over all DEVTYPE LU1 and LU3 subcommands. If either FASTP is not the current spooler print process, Spoolcom accepts the DEVTYPE LU1 or LU3 subcommand but the print process ignores it. DEVTYPE LU1 configures the print device for SNA character string (SCS) mode.
DEV Command Spoolcom ENDFF or ENDFF ON specifies that the print process will issue a form feed or other command to the printer to advance to a new page at the end of each job. The command varies depending on the printer type. For printers that can recognize the conditional operation, this advance is conditional so that extra blank pages do not occur if the printer is already at top-of-form when the job ends.
DEV Command Spoolcom HEADER [ ON | OFF | BATCH ] specifies whether a standard or batch header page should precede each job. The ON, OFF, and BATCH options are supported by the FASTP print processes. HEADER or HEADER ON (the default specification) specifies that a header page should print at the beginning of every job. HEADER OFF specifies that header pages are not to be printed at the beginning of jobs.
DEV Command Spoolcom If CRLF is specified, the default EOL sequence is carriage return and line feed as follows: CR (%15) and LF (%12). If new line (NL) is specified, the end-of-line sequence is NL (%205, IAW 32876-2). LUEOLWHEN [ LT132 | LTWIDTH | ALWAYS | NEVER ] indicates when the FASTP print process is to place an EOL sequence at the end of a print record for LU1 and LU3 type printers (other printer types are not affected). This subcommand applies only to the FASTP print process.
DEV Command Spoolcom • The FASTP print process uses parameter as follows: <0:8> Reserved. Set to 0. <9> =0 Print headers in the normal orientation, which is portrait. For 5577 printers, you should disable offset of jobs on output. <9> =1 For jobs sent to 5573, 5574, and 5577 printers, set 10point, 12-cpi landscape text for header and trailer pages. For 5577 printers, issue a PCL job-separation command before printing the job (which causes each job to be offset in the output bin).
DEV Command Spoolcom <14> =0 Set paper length to 66 lines (the default). <14> =1 Set paper length to 72 lines rather than the default 66 lines. This information applies for printing trailer pages (HEADER BATCH). <15> =0 Print any header and trailer outside the scope of any font job. <15> =1 Print any header and trailer pages within the scope of any font job.
DEV Command Spoolcom RETRY interval specifies the number of seconds a print process waits before retrying an I/O operation that has failed because of a retryable I/O error. The valid range for interval is 1 through 32767. The default value is 5 seconds. Table 3-7. Retryable Error Numbers Retryable Error Number Description 12 file in use 100 device not ready 102 paper out 140 modem error 218 interrupt timeout Use RESTART to specify the action to be taken for a nonretryable I/O error.
DEV Command Spoolcom START causes an offline device to become online. All users can restart devices that have gone offline due to a device error (for example, running out of paper). This subcommand causes a suspended device to resume printing. Devices taken offline can be restarted only by an authorized user. STARTFF [ ON | OFF [ ! ] ] specifies whether the spooler print process FASTP issues a form feed at the beginning of each job.
DEV Command Spoolcom DETAIL requests a complete list of all of the device attributes. If $device is not specified, then the status of all devices in the spooler subsystem is returned. SUMMARY displays a summary of the state of devices, such as the number of devices waiting, busy, suspended, in deverror, offline, in procerror, and the total number of devices. Can be used only when the $device parameter is missing. SUSPEND causes the device to suspend printing of the job currently printing.
DEV Command Spoolcom The following FASTCNG keywords and keyword attributes are required when you specify the TIMEOUT attribute: DEVICE $spooler-device-name CONTYPE = NONE Examples of FASTCNFG file entries: /* timeout = 120 seconds. */ DEVICE $DEV1 CONTYPE = NONE TIMEOUT = 120 /* timeout = 0 seconds. */ DEVICE $Dev2 CONTYPE = None TIMEOUT = 0 /* timeout = 0 seconds. */ DEVICE $dev3 CONTYPE = none TRUNC [ ON | OFF ] specifies whether lines longer than the device width are to be truncated or wrapped around.
DEV Command Spoolcom If OUT filename is specified, Spoolcom writes the data to it in a manner suitable for the file type, process, or device. The filename parameter must be specified; if the file does not exist, Spoolcom creates an EDIT file (file type 101). The file can be an EDIT file, an unstructured file, a relative file, an entrysequenced file, a spooler job file, a process, or a device. Table 3-8 shows the device states for which each DEV subcommand is valid. Table 3-8.
DEV Command Spoolcom Table 3-8. Device States During Which DEV Subcommands Can Be Used (page 2 of 2) DEV Subcommand Offline (O) SUSPEND Busy (B) Waiting (W) B TIMEOUT O TRUNC O WIDTH O XREF O B W Suspended (S) Deverror (D) S D S D Procerror (P) P Considerations • • • • • • • • • If neither $device nor subcommand is specified, Spoolcom displays the status of all devices. Any user can obtain the status of a device.
DEV Command Spoolcom • The STARTFF subcommand suppresses inserting a blank page between jobs unless HEADER ON or HEADER BATCH is configured. Other subcommands affect inserting a blank page.
DEV Command Spoolcom DEV STATUS Display The STATUS subcommand produces a display with the following headings: DEVICE STATE FLAGS PROC FORM Table 3-9 describes the DEV STATUS display entries: Table 3-9. DEV STATUS Display Entries (page 1 of 2) Entry Description DEVICE Is the name of the device whose status is being displayed. STATE Is the state of the device. STATE can be one of the following: FLAGS BUSY The device is currently printing a job. WAITING The device is idle, waiting to print.
DEV Command Spoolcom Table 3-9. DEV STATUS Display Entries (page 2 of 2) Entry Description D Draining T Truncate on ! Exclusive off PROC is the name of the device print process. FORM is the device form name. Examples for All Users 1. You can obtain the status of one device on the system by entering )DEV $DEV1 The following information is returned: DEVICE $DEV1 STATE JOB 2482 JOB LOCATION PAGE 2482 #LOC1.DEFAULT PROC FORM $SPLA DEVICE SEQ COPY $DEV1 1 1 3 $DEV1 2 1 3 2486 #LOC1.
DEV Command Spoolcom STATE: OFF LINE LAST ERROR: %004016 EXCLUSIVE: OFF FIFO: OFF HEADER: ON TRUNCATION: OFF DRAINING: NO PRINTING JOB: NONE PARM: 0 PROCESS: $PR10 RETRY: 5 TIMEOUT: 360 SPEED: 100 WIDTH: 132 FORM: RESTART: OFF DEVRESET: OFF DEVTYPE: STARTFF: OFF ENDFF: OFF CHARMAP: NONE PREXLATE: OFF LUTOFVALUE: CRFFCR LUEOLVALUE: CRLF LUEOLWHEN: LT132 ) LAST ERROR is the octal number of the last error printed on the error log file. The %004016 error shown here is translated by reading bits 8 through 15.
DEV Command Spoolcom Examples for Authorized Users 1. In the example below, the print process that is to control device $LP3 is specified and causes all jobs printed on that device to have a header page: )DEV $LP3, PROCESS $XP, HEADER ON 2. The START subcommand is used to bring back online a device that has been taken offline for any reason: )DEV $LP3, START 3.
DEV Command Spoolcom Table 3-10. Typical Configuration for Laser Printer Type 5577 Device Attribute Default? Description EXCLUSIVE: OFF Yes Close the device when no jobs are waiting. FIFO: OFF Yes Use the queuing algorithm that considers the relative job length and the time jobs have been queued. HEADER: ON Yes Print the banner at the beginning of every job. TRUNCATION: OFF Yes Print wrapped text on the next line. PARM: 64 (%100) No Use landscape headers.
ENV Command Spoolcom ENV Command The ENV command displays information about current settings. ENV Example The following is an a sample ENV command display: CURRENT JOB NUMBER: 3000 CURRENT BATCH NUMBER: 2 STARTCOL PARAMETER: 1 NUMCOL PARAMETER: 2 EXIT Command The EXIT command terminates an interactive Spoolcom session. It is also used to exit from the current job or current batch mode. EXIT Examples 1.
FC Command Spoolcom FC Command FC, or Fix Command, allows you to modify and resubmit the last command line entered. The FC edit subcommands are similar to those used for the TACL FC command, described in the TACL Reference Manual. FC Consideration • The FC command executed in Spoolcom can modify only the last line, unlike an FC command executed at a TACL prompt, which can identify and modify other lines.
FIND Command Spoolcom If you omit subvolume, Spoolcom uses the current default subvolume name. Omit the final period (.) if you specify \system or $volume without subvolume. Examples 1. This command lists the names of files on the current default subvolume. Note that LISTING is a spooler job file. This is shown by the period (.) that precedes the name. )FILES \SYSII.$DISK.SUBVOL OBJECT FILE1 ) LETTER .LISTING SAVEOBJ 2.
FIND Command Spoolcom string is a set of printable ASCII characters set off by two identical separators. You can use quotation marks ("), apostrophes ('), or slashes(/) as separators, but actually any ASCII character can act as the boundary for string. Spoolcom scans the current job, starting at the beginning of the file, for an occurrence of the specified string.
FIND Command Spoolcom Examples 1. In this example, you want to find errors in your TAL compilation. Once you key in the beginning sequence of the error message, you can reexecute the FIND command without repeating the string, and it continues to show you the next occurrence of that string: )FIND /**** ERROR/ **** ERROR 49 **** Undeclared Identifier )F **** ERROR 27 **** Illegal syntax 2.
FONT Command Spoolcom FONT Command The FONT command causes the spooler to recognize a job as a font job and to associate that job with a specified font name. A font job contains commands that can be sent to a programmable printer to control such features as character sets, vertical forms-control specifications, or compressed printing. Once a font job is defined, you can use the LOC FONT subcommand to associate it with a spooler location.
FONT Command Spoolcom (qualifiers) specify the conditions that a job must meet in order to be associated with the font name. The qualifiers parameter is any number or combination of the following qualifiers, separated by commas and all enclosed in parentheses. If more than one job meets the specified qualifications, then only the first to do so is used. Each qualifier can be specified only once. COLLECT $process-name selects all jobs collected by this collector.
FONT Command Spoolcom PAGES { > | < } pages selects all jobs whose length in number of pages falls within the range specified. The PAGES subcommand allows two special cases. If PAGES > 0 is specified, all jobs are qualified. If PAGES < 0 is specified, jobs with zero pages are qualified. This makes PAGES < 0 equivalent to PAGES < 1. REPORT name selects all jobs with a matching report name. The report name is the name assigned to a job in the spooler, usually the group and user name of the job owner.
FONT Command Spoolcom • The FONT STATUS command without the DETAIL option lists all font jobs under the following headings: FONT • JOB The FONT STATUS command with the DETAIL option lists each font job in the following format: FONT: font-name JOB: job-number • Multiple jobs sent for printing to a location configured with a font job have the font printed before each print job. For example, assume a printer configured as follows: Printer Location DEV $P1, EXCLUSIVE OFF LOC #A.
FONT Command Spoolcom • • • • Only authorized users can delete a special control job (font-name) with the FONT DELETE command. A font can be deleted even if it is associated with a location. When this occurs, the location ignores the font. Do not configure a device with DEV EXCLUSIVE OFF! if it is associated with locations that are configured with font jobs to affect the printing of a subsequent print job.
HELP Command Spoolcom HELP Command The HELP command displays the syntax of the Spoolcom commands. HELP [ / OUT filename / ] [ command | ALL ] OUT filename specifies the file to which the syntax is written. If omitted, the syntax description is written to the home terminal. If OUT filename is specified, Spoolcom writes the data to it in a manner suitable for the file type, process, or device.
JOB Command Spoolcom JOB Command If you are an authorized user, you can use the JOB command to alter attributes and change the status of any job. Refer to the Guardian System Operations Guide for a description of job states and default attributes. All users can perform these operations on their own jobs. JOB [ job-number | ( qualifiers ) ] [ , subcommand ] ... job-number is the job number of the job. qualifiers specify the conditions that a job must meet.
JOB Command Spoolcom The DATE FROM time THRU time form can be used to bracket a range: DATE FROM 16 DEC 1990, 0:0 THRU 29 DEC 1990 FORM form-name selects all jobs that have this form name specified. LOC #group[.destination] selects all jobs that have this location. OWNER [ group-name.user-name | group-number,user-number ] selects all jobs created by the user with the specified user ID. If OWNER is specified without a user ID, it defaults to the creator accessor ID of the user.
JOB Command Spoolcom the current data file. If the transfer fails, the job remains on the current data file and/or collector. COPIES number-of-copies specifies the number of copies to be printed. A job must be in the hold state before its copies attribute can be changed. The range for number-ofcopies is 1 through 32767. The default is 1. CURRENT makes a job or batch the current job or batch for subsequent subcommands. The prompt returned for current job is JOB followed by the job number.
JOB Command Spoolcom LOC [ #location ] specifies a new location for the job. The job must be in the hold state before its location attribute can be changed. If the #location parameter is omitted, then #DEFAULT is the new location. OWNER { group-name.user-name | group-number,user-number } designates a new owner of a job. You can use the local form of either the group and user name or the group and user number. The range for groupnumber and user-number is 1 through 255.
JOB Command Spoolcom If job-number is not specified, then the status of all jobs in the spooler subsystem is returned. SUMMARY displays a summary of the state of the jobs, such as jobs printing, ready, open, and on hold, and the total number of jobs for the current user. The SUMMARY subcommand can be used only when the job-number parameter is missing. Table 3-11 below shows the job states for which each JOB subcommand is valid. Job states are further described in the Guardian System Operations Guide.
JOB Command Spoolcom Table 3-12. JOB STATUS Display Entries Entry Description JOB Is the job number. BATCH Is the batch number. If the job is not part of a batch job, this field is blank. ST Is the state of the job: FLAGS RD Spooler has finished collecting; job is queued and waiting to print. HL The hold-before-printing flag is on or the hold-afterprinting flag is on and the job has printed. OP Job is still being collected by the spooler. PR Job is currently printing.
JOB Command Spoolcom Table 3-13. JOB STATUS Display Entries—Non-Detailed Single Job Status Entry Description JOB Is the job number. LOCATION Is the complete location (#group and destination) for the job. DEVICE Is the name of the device that will print or is printing the job. SEQ Is the job sequence number in the device queue. PRINT is displayed if the job is printing. COPY Is the number of copies to be printed. PAGE Is the number of pages in the job.
JOB Command Spoolcom Table 3-14. JOB STATUS Display Entries—Detailed Single Job Status (page 2 of 2) Entry Description DATA FILE Is the name of the collector data file. COLLECTED BY Is the name of the collector. UNITS ALLOCATED Is the amount of disk memory used. BATCH ID Is the number of the spooler batch job. BATCH NAME Is the name for the batch job report. MAXIMUM LINES Is the maximum number of lines in effect for the report. The default value is no maximum.
JOB Command Spoolcom 4. To get job summary information, use the following command: )JOB, SUMMARY 5.
JOB Command Spoolcom 7. Placing a job in the hold state truncates the display, as shown above. You must specify the STATUS subcommand after removing the hold in order to see the twoline display: JOB BATCH ST 36 RD FLAGS OWNER TIME COPY PAGE REPORT LOCATION 4 A 4,19 10:18 1 1 PB REPT #UNTIL JOB LOCATION 36 #UNTIL.DEFAULT DEVICE SEQ 1 COPY 1 PAGE 1 8. The * pattern-matching symbol used in the following REPORT subcommand selects these jobs.
LIST Command Spoolcom LIST Command The LIST command displays on your terminal, prints, or writes to a disk file or process all or part of the current job. If there is no current job, then the most recently spooled job becomes the current job. (To make a job current explicitly, use the JOB, CURRENT command). L[IST] [ [ type ] / OUT list-file [ ! ] / ] [ page-range [ C ] [ N ] [ O ] , ] ... type specifies the type of file to be created if list-file does not already exist.
LIST Command Spoolcom If you do not specify OUT list-file, output is directed to the OUT file-name specified when Spoolcom was started (the home terminal by default). If you specify EDIT, SPOOL, or COMPRESS without specifying OUT list-file, these keywords have no effect. ! specifies that list-file is to be purged, if it exists, and a new list-file is to be created before listing begins.
LIST Command Spoolcom Considerations • • • • • • If no current job is defined, the LIST command causes the most recently spooled job to become the current job. To explicitly make a job current, use the JOB, CURRENT command. If you create a file for receiving output from the LIST command, take care that it is large enough. If it is not, the LIST command terminates with file-system error 45 (file is full).
LIST Command Spoolcom 6. You can use /OUT $S.#device/ to print all or only a few pages of an already spooled file. The following example prints page 1 and pages 16 through 20 of the job. Because the destination is a spooler collector, formatting-control information is included by default, so the C parameter is unnecessary. (You would use the N parameter to omit formatting-control information.) )LIST /OUT $S.#LP/ 1, 16/20 7. The following command lists the entire job to the disk file $DISK.SVOL.
LOC Command Spoolcom LOC Command The LOC command defines and modifies the spooler routing structure. Refer to Routing Structure on page 1-13 for a description of default location attributes and a description of the spooler routing structure. All users can display the status of the spooler routing structure (with the STATUS subcommand) or produce a cross-reference list of locations, devices, and print processes (with the XREF subcommand).
LOC Command Spoolcom If only dest is present, then the command refers to all existing locations with a group that has that destination in it. If device-name is present, the command establishes a connection; if device-name is absent, any existing connection with a device is broken. Only authorized users can use the DEV subcommand. FONT [ font-name ] connects a location to or disconnects a location from a font. Only authorized users can use the LOC FONT subcommand. If #group.
LOC Command Spoolcom XREF [ / OUT file-name / ] produces a cross-reference list of locations, devices, and print processes ordered by location. If a location is not specified, a complete cross-reference of all locations is produced. If a location is specified, it can be entered as: #group | #group.dest If #group is specified, all locations within that group are listed. If #group.dest is specified, a cross-reference for that location is produced.
LOC Command Spoolcom Table 3-15 describes the LOC STATUS display entries. Table 3-15. LOC STATUS Display Entries Entry Description LOCATION Is the #group.dest whose status is being displayed. FLAGS Displays a B if broadcast is on. DEVICE Is the device associated with the location, if any. FONT Defines a special control job in the spooler. The special control job might consist of downloadable vertical forms control (VFC) command or possibly a special header page.
NEXT Command Spoolcom NEXT Command The NEXT command selects the next job after the current job and makes it current. NEXT Considerations If no job has been made current, the NEXT command selects the last job collected and makes it current.
NUMCOL Command Spoolcom NUMCOL Command The NUMCOL command alters the number of columns displayed when a job is listed. NUMCOL number-of-columns number-of-columns is the number of columns, counting from the left margin, that are to be displayed or printed. Considerations • • • When Spoolcom is first run, the value for NUMCOL is 0, and the width of the printing device determines the number of columns to be printed. If NUMCOL is set to a value other than 0, the value specified is used as the output width.
OPEN Command Spoolcom OPEN Command The OPEN command specifies the spooler supervisor with which Spoolcom communicates. OPEN [ \system.$supervisor ] [ $supervisor ] [ \system ] \system is the name of a system (node) where the spooler supervisor process resides. The default \system is the current system. $supervisor is the process name of a supervisor in remote or local form. The default process name for $supervisor is $SPLS.
PAGE Command Spoolcom PAGE Command The PAGE command displays or changes the page and line-number position of the current job. If there is no current job, then the job most recently spooled becomes the current job. Page numbers begin with 1 and do not include the header page, if any. Spoolcom assumes 60 lines to a page. P[AGE] [ number | F | L | * ] number is the page number of the new page position for the current job. F indicates that the new page position for the current job is the first page.
POLL Command Spoolcom POLL Command The POLL command prints the status of all available jobs (up to the first 64) each time the state of any of the jobs changes. The letter C in front of a status line means that the state of that job has changed since the last status printout. POLL [ delay ] delay is the number of seconds between checks of the job status. The default is 10 seconds.
PRINT Command Spoolcom PRINT Command If you are an authorized user, you can use the PRINT command to specify attributes and obtain the status, and change the status of the spooler print processes. See PRINT STATUS Display on page 3-78 for a description of the print-process states. All users can obtain the status of any spooler print processes. PRINT [ $process-name ] [ , subcommand ] ... $process-name is the name of the print process to which the subcommands refer.
PRINT Command Spoolcom DELETE removes the print process from the spooler subsystem. The print process must be in the dormant state before you can delete it. See Considerations on page 3-77 for more information on putting a print process in a state so that you can delete it. Also, all devices associated with this process must be disconnected from this print process before you can delete it. FILE program-filename specifies the program file for this print process. The print process provided by HP is $SYSTEM.
PRINT Command Spoolcom (file type 101). The file can be an EDIT file, unstructured file, relative file, entry-sequenced file, spooler job file, process, or device. DETAIL requests a complete list of all the print-process attributes. SUMMARY displays a summary of the state of the print processes such as print process in active, dormant, error, and drain state, and the total number of print processes. Can be used only when $process-name is missing.
PRINT Command Spoolcom become dormant approximately two minutes after the process prints its last job. If the print process does not become dormant at this time, issue a STOP command from a TACL prompt to stop the process. • When a print process is in debug mode, it is not timed out by the spooler. This means that the spooler waits indefinitely for a response. For this reason, print processes should never be debugged on a production spooler.
PRINT Command Spoolcom When DETAIL is specified, the information in Table 3-17 is shown: Table 3-17. PRINT STATUS Display Entries (With DETAIL Option) Entry Description PRINT PROCESS Is the name of the print process whose status is being given. STATE Is the same as that shown in Table 3-16 except when an error has occurred. Then only the word ERROR is displayed and the error number is displayed in LAST ERROR. LAST ERROR Is the octal number of the last error printed on the error log file.
PURGE Command Spoolcom The following information is displayed: PRINT PROCESS: $SPLA STATE: ACTIVE LAST ERROR: NONE DEBUG: OFF INDEPENDENT: NO PROGRAM FILE: $SYSTEM.SYSTEM.FASTP CPU: 5 BACKUP: 9 PRIORITY: 145 PARM: 0 Examples for Authorized Users You can use the PRINT command to define the print process $XP to be a copy of the program file $SYSTEM.SYSTEM.
PUT Command Spoolcom PUT Command The PUT command creates the edit-filename and loads it with the current job. The ! parameter purges the existing file prior to creation and load. If there is no current job, then the most recently spooled job becomes the current job. PUT [!] edit-filename edit filename is the name of the disk filename to be created and loaded. Example )PUT TEST PUTC Command The PUTC command creates the edit-file-name and loads it with the current job.
SJFILES Command Spoolcom SJFILES Command The SJFILES command displays the names of all spooler job files on a subvolume. The names of spooler job files are preceded by a period (.). SJFILES [ subvol ] subvol is the subvolume whose file names are to be listed. The subvol parameter has the form: [\system.][$volume.][subvolume] If you omit \system, Spoolcom uses the current default system name. If you omit $volume, Spoolcom uses the current default volume name.
SPOOLER Command Spoolcom SPOOLER Command If you are an authorized user, you can use the SPOOLER command to start, stop, and obtain the status of the spooler subsystem. Refer to the Guardian System Operations Guide for a description of spooler states. All users can obtain the status of the spooler subsystem with this command. SPOOLER [ , subcommand ] ... subcommand is one of the subcommands described below. If subcommand is not specified, then STATUS is assumed.
SPOOLER Command Spoolcom STATISTICS displays additional statistics maintained with the spooler for the purpose of better understanding how the spooler is currently being used. See SPOOLER STATISTICS Display on page 3-85. STATUS [ / OUT filename / ] [ DETAIL ] displays the status of the spooler subsystem. See SPOOLER STATUS Display on page 3-87. OUT filename indicates where Spoolcom is to write the status information.
SPOOLER Command Spoolcom SPOOLER STATISTICS Display You can use the STATISTICS subcommand to access additional spooler statistics.
SPOOLER Command Spoolcom Table 3-18. SPOOLER STATISTICS Display Entries (page 2 of 3) Entry Description DEVICE QUEUE NODES Represents the number of jobs queued for all devices. All jobs in the spooler take one or more device queue nodes, except jobs that are in the OPEN, WAIT, and HOLD states. If a group location or broadcast location is the destination of a job, the number of device queue nodes used by the job is the number of devices configured for the location. Jobs that are directed to group.
SPOOLER Command Spoolcom Table 3-18. SPOOLER STATISTICS Display Entries (page 3 of 3) Entry Description COLLECTORS Is the number of collectors known to the spooler supervisor. This count can be as large as the configured maximum number of collectors (20 in the example). PRINTERS Is the number of print processes known to the spooler supervisor. This count can as large as the configured maximum number of print processes (20 in the example).
SPOOLER Command Spoolcom Table 3-19. SPOOLER STATUS Display Entries Entry Description COLD This state indicates the starting of a new spooler. LOGGING FILE Is the spooler error log file. LAST ERROR Is the octal number of the last error sent to the error log file. Bits 8 through 15 contain the octal file-system error number. All of the file-system errors are described in the Guardian Procedure Errors and Messages Manual. Example for All Users 1.
STARTCOL Command Spoolcom STARTCOL Command The STARTCOL command alters the starting column number used when a job is listed. The first column is 1. STARTCOL starting-column starting-column is a number greater than 0 and less than or equal to the rightmost column in the current job. The default column number is 1. Considerations • • • • When Spoolcom is first run, the value for STARTCOL is 1. STARTCOL can be used with NUMCOL to list only a few columns of a job.
VOLUME Command Spoolcom VOLUME Command The VOLUME command changes the current default volume or subvolume names, or both, used with Spoolcom. The initial default names are the subvolume and volume names that were the current default names when you started Spoolcom. VOLUME [ [\system.]$volume.subvol ] [ $volume ] [ subvol ] \system sets the current default system name for Spoolcom. You can set the default system name only in a named system, such as one in a network.
4 Font Utility The Font utility program helps you create font jobs within the HP spooling system. A font job contains commands that can be sent to a printer to control such features as character sets, vertical forms-control specifications, or compressed printing. Font jobs, therefore, frequently contain both printable and nonprintable text, such as PCL escape sequences. With the Font utility, however, you enter all font descriptions in plain text; no nonprintable characters are used.
How the Font Utility Works Font Utility How the Font Utility Works To use the Font utility, you enter font job descriptions and locations in plain text in an EDIT file, called a script file, which the Font utility reads to create the font jobs and to associate them with spooler locations. Preparing the script file and running the Font utility is illustrated in Figure 4-1. Figure 4-1.
Running the Font Utility Font Utility Running the Font Utility You can run the Font utility by entering the following command at the TACL prompt: FONT / IN script-file [ , run-options ] ... / [ supervisor ] IN script-file designates an EDIT file containing details of the font jobs to add and locations to set up. See Script File Syntax on page 4-5 for the requirements of the file. The IN script-file parameter is actually a run option.
Running the Font Utility Font Utility Considerations • • • The collector process used by the Font utility is the first collector process in the active state that is configured in the spooler. Error messages are described in Appendix D, Font Utility Messages. After loading a font job into the spooler, you can check its contents by using the Peruse LIST command. If you specify the octal and control modifiers, you can see the nonprintable characters and any embedded procedure calls.
Script File Syntax Font Utility Script File Syntax A script file has two sections: the font description is a required section that describes font jobs; the location is an optional section that associates spooler locations with a particular font job. The contents of the script file are first described by a skeleton, which shows required and optional directives. Following the skeleton are general rules for directives, directive descriptions, and examples.
General Syntax Rules for Script File Directives Font Utility General Syntax Rules for Script File Directives The following rules apply to directives in the script file: • • • • A directive is a line that has a question mark (?) as the first nonblank character. At least one space must separate directive parameters from the directive name and from other parameters. Directive names are not case-sensitive.
FONT Directive Font Utility FONT Directive The FONT directive designates a font name and begins the description of a particular font job. A font job contains commands that can be sent to a printer to control such features as character sets, vertical forms-control specifications, and compressed printing. ?FONT font-name font-name identifies the specific font name. The font-name parameter is 1 through 16 alphanumeric characters; the first character must be a letter.
Normal Font Data Font Utility %byte-value Hbyte-value To enter actual text, delimit the text with quotation marks ("). To specify the value of a byte, precede byte-value with the symbol for the numeric base as follows: # Decimal % Octal H Hexadecim al Considerations • • • • A single comma must separate data elements that appear on a single line. The Font utility inserts each line of data into the spooler font job with one input/output (I/O) operation.
CONTROL Directive Font Utility CONTROL Directive The CONTROL directive embeds a CONTROL procedure call in the font job. This directive controls operations on devices. ?CONTROL operation param operation is a number in the range 0 through 32767. This parameter corresponds directly to the operation parameter of the CONTROL procedure. See the CONTROL procedure in the Guardian Procedure Calls Reference Manual for operation values. param is a number in the range 0 through 32767.
CONTROLBUF Directive Font Utility ; is a semicolon required to terminate CONTROLBUF data if any normal-text data follows. Otherwise, CONTROLBUF data can be terminated by a FONT, an ENDFONT, or another font description directive. Considerations • • • • CONTROLBUF parameter values are usually described in the documentation provided with your printer. CONTROLBUF data must conform to the same rules as normal font data. CONTROLBUF data is assembled in a buffer.
CONTROLBUF Directive Font Utility translation changes nonprintable characters that can produce incorrect output. The CONTROLBUF operation must be 101. CONTROLBUF data contains the characters to be translated. Each translation is given as a pair of bytes. The first byte in each pair is translated into the second byte. There is no need to include characters that do not need translation.
CONTROLBUF Directive Font Utility %33,"*c1a2338b30g2P" ! Draw Line 1 dot x 2338 dots x 30% %33,"&a68r0c0L"; ! Posn to row 68 col 0 ! left margin 0 ?CONTROLBUF 103 ! Top-of-form substitute %33,"&a0r134c134L"; ! Posn to row 0 col 134 ! left margin 134 ?CONTROLBUF 103 ! Top-of-form substitute %33,"&a68r134c134L"; ! Posn to row 68 col 134 ! left margin 134 ?CONTROLBUF 103 ! Top-of-form substitute %33,"&a0L",%14,%15; ! Left margin 0, FF CR ?END-FONT ?START-LOCATIONS #LISTING.DEFAULT LPX8D $LP2 ! ...
SETMODE Directive Font Utility ?END-FONT ?START-LOCATIONS ! Location #LASER.BLUE #LASER.PINK #LASER.RED ?END-LOCATIONS Font COLORGROUP1 COLORGROUP1 COLORGROUP1 Device $LASER.#A $LASER.#A $LASER.#A Note. In the CONTROLBUF 113 call, location names must be blank-filled to 16 characters in length. The destination need not be specified to match location groups. The location name is not case-sensitive. The data for the CONTROLBUF call is delimited by a semicolon (;).
SOURCE Directive Font Utility SOURCE Directive The SOURCE directive identifies a file containing data to be included in the font job. The Font utility copies the entire contents of the file except beginning or trailing bytes, as specified by SOURCE directive options. ?SOURCE source-file [ beginning-count [ trailing-count ] ] source-file identifies the file whose contents are copied as part of the data for the font job.
START-LOCATIONS and END-LOCATIONS Directives Font Utility Example ?SOURCE INVOICE 22 3 ! Copy data from the file INVOICE and ! trim the first 22 and last 3 bytes. START-LOCATIONS and END-LOCATIONS Directives The START-LOCATIONS directive indicates the start of the script file locations section, which describes locations to which the font should be attached and the devices to which the locations should be linked. Location entries identify the locations, fonts, and devices.
Comments in the Script File Font Utility Comments in the Script File Comments can appear anywhere in the script file and are ignored by the Font utility.
Script File Example Font Utility 18. ?END-LOCATIONS 19. Comments comments comments 20. Comments comments comments Script File Example The following is an example of a script file. This file is input to the Font utility, which loads font jobs in the spooling system. These font jobs are used by locations with Laser-LX and other similar PCL devices attached. The script file also supplies information to enable the configuration of these locations. Initial text is comments.
Script File Example Font Utility Spooler Plus Utilities Reference Manual—522294-002 4- 18
5 RPSetup Utility The RPSetup utility establishes cross-spooler connections between spoolers in a network. These connections give users access to printers on remote nodes in a network. You use RPSetup to create and maintain a spooler configuration for a node with a limited number of printers, so that print jobs from local applications can be sent to a remote spooler and queued for printing on remote printers.
How the RPSetup Utility Works RPSetup Utility Figure 5-1. Configuration Functions of the RPSetup Utility \REMOTE Print Process Printer Remote Supervisor Spooler Control Files IN \LOCAL RPSETUP Utility OUT Local Supervisor Spooler Control Files Added PRINT, DEV, and LOC entries to match locations in the remote spooler VST014.
Interspooler Threads RPSetup Utility Interspooler Threads In creating cross-spooler connections, RPSetup creates interspooler threads to provide spooler-to-spooler transfers for print jobs. An interspooler thread is a spooler device that is configured as a collector for a different spooler. An interspooler thread is a path from one spooler to another. The number of threads equals the number of print jobs that can be simultaneously transferred to the other spooler.
Interspooler Threads RPSetup Utility Figure 5-2. Interspooler Threads \APPL Application Spooler Subsystem Collector Collector Data Spooler Control Files 6 FASTP Print Process 1 2 Supervisor PRINT $SPLX DEV \PRNT.$S.#XFER.THREAD01, PROCESS $SPLX DEV \PRNT.$S.#XFER.THREAD02, PROCESS $SPLX LOC #DEFAULT.PRT, DEV \PRNT.$S.#XFER.THREAD01 LOC #OFFICE.P1, DEV \PRNT.$S.#XFER.THREAD02 LOC #OFFICE.P2, DEV \PRNT.$S.#XFER.
Interspooler Threads RPSetup Utility The numbers in Figure 5-2 mark the following elements: 1,2 Mark the definition of the interspooler threads. Each is a device configured as a collector (\PRNT.$S ...) and uses print process $SPLX (which is a process name for the FASTP program) to control the interspooler thread. 3,4,5 Mark the definition of particular locations with cross-connections to remote node \PRNT.
Running RPSetup RPSetup Utility Running RPSetup To run RPSetup, enter the following command at the TACL prompt: RPSETUP / IN remote-spooler , OUT local-spooler / remote-spooler is the supervisor process name of a remote spooler configured with printers to which remote connections are to be established. To specify remote-spooler, use the network form of the supervisor process name (for example, \FAR.$SPLS).
Requirements for Running RPSetup RPSetup Utility • • • If you use a print process other than FASTP, you must ensure that the default values of the configuration parameters are appropriate for the print process you use. Because the default configuration parameters are set for the FASTP print process, you might need to specify PARAM commands to set configuration parameters specifically for the print process you use. For some default operations performed by FASTP, see PARAM DEVPARM on page 5-12.
Example RPSetup Utility Example Assume that the \PRNT.$SPLS spooler has the following locations: COLLECT $S LOC #DEFAULT.PRT,DEV $LP LOC #OFFICE.P1,DEV $LASER.#A LOC #OFFICE.P2,DEV $LASER.#B The following command to run RPSetup sets up the spooler on \APPN so that all printing locations on \PRNT are also available on the \APPN spooler. RUN RPSETUP /IN \PRNT.$SPLS, OUT \APPN.$SPLS / RPSetup installs the devices and locations listed below in \APPN.
Default Configuration RPSetup Utility Table 5-1.
ASSIGN and PARAM Commands RPSetup Utility Table 5-1.
ASSIGN and PARAM Commands RPSetup Utility PARAM DEVEXCLUSIVE The PARAM DEVEXCLUSIVE command specifies the ownership mode of the device. This configuration parameter applies individually to all interspooler threads. The command is equivalent to the SPOOLCOM command DEV EXCLUSIVE. PARAM DEVEXCLUSIVE { ON | OFF [ ! ] } ON specifies that the print process should not close the device when the printer is not printing a job.
ASSIGN and PARAM Commands RPSetup Utility At the target node, the print process can choose to add these header or trailer pages according to settings configured for the real device. The PARAM DEVHEADER command is equivalent to the SPOOLCOM command DEV HEADER. PARAM DEVHEADER { ON | OFF | BATCH } ON specifies that a header page should print at the beginning of every job. OFF Specifies that header pages are not to be printed at the beginning of jobs. The default value is OFF.
ASSIGN and PARAM Commands RPSetup Utility Table 5-2. Default Attributes Set by FASTP on Interspooler Transferred Print Jobs Bit Value Attribute of Transferred Print Jobs FASTP’s Default Operation < 10 > 0 Retains the same job ownership at the target spooler as at the source spooler 1 Sets job ownership (PROCESSACCESSID) at target node to the print process performing the transfer Equals 0. For example, if user ADMIN.OPERATOR submitted a job at the source node, FASTP sets ADMIN.
ASSIGN and PARAM Commands RPSetup Utility individually to all interspooler threads. The command is equivalent to the SPOOLCOM command DEV TRUNC. PARAM DEVTRUNC { ON | OFF } ON causes the print process to discard the ends of spooled lines that are longer than the device width. OFF causes the print process to print on the next sequential line the ends of any spooled lines that are longer than the device width. The default value is OFF.
ASSIGN and PARAM Commands RPSetup Utility PARAM PRICPU The PARAM PRICPU command sets the processor in which the print process that controls the interspooler threads executes. This command is equivalent to the SPOOLCOM command PRINT CPU. PARAM PRICPU cpu cpu is a number in the range 0 through 15 specifying the processor where the print process executes. The default processor is the processor in which the local spooler supervisor executes.
ASSIGN and PARAM Commands RPSetup Utility PARAM PRIORITY The PARAM PRIORITY command sets the priority of the print process that controls the interspooler threads. This command is equivalent to the SPOOLCOM command PRINT PRI. PARAM PRIORITY execution-priority execution-priority is the execution priority. The value can be in the range 1 through 199. The default value is the priority of the local spooler supervisor minus 10.
A SPOOL Program The SPOOL program is used to run the spooler supervisor as part of coldstarting and warmstarting the spooler. This appendix describes the following topics: • • Running the SPOOL Program on page A-1 EMS Collector DEFINE on page A-4 Running the SPOOL Program You can run the SPOOL program by entering the following command at the TACL prompt: SPOOL /IN control-filename[.
Running the SPOOL Program SPOOL Program The default priority is 1 less than the priority of the command interpreter from which the supervisor is run. CPU primary-cpu is the processor number of the processor module (0 through 15) in which the supervisor’s primary process runs. The default processor module is the same processor module that the command interpreter is located in. backup-cpu is the processor number of the processor module (0 through 15) in which the supervisor’s backup process is to run.
Running the SPOOL Program SPOOL Program num-of-print-processes is the maximum number of print processes that will ever be declared for this spooler. The range is 1 through 255. There is no default. num-of-fonts is the maximum number of font jobs that will ever be declared for this spooler. The range is 1 through 2047. The default is 16. num-of-batch-jobs is the maximum number of batch jobs that will ever be declared for this spooler. The range is 1 through 32765. The default is 256.
EMS Collector DEFINE SPOOL Program • • The REBUILD option causes the supervisor to rebuild the spooler control files. One symptom of a corrupted control file is a corrupted job map. This can be seen if you warmstart a spooler and find a listing for a job 0 when you execute the JOB command (indicating that the new spooler has a corrupted job map).
B Peruse Messages This appendix describes the Peruse error messages that are displayed on your terminal. For additional information on Peruse, see Section 2, Peruse. ACCESS TO SPOOL DATA FILE FAILED, FILE ERROR number Cause. A file-system error occurred during input/output (I/O) to a spooler data file. Effect. Peruse cannot access the data file for this job. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error number.
Peruse Messages CAN'T PURGE 'OUT' FILE: number Cause. An exclamation point (!) was specified with the OUT file of a LIST command and the file could not be purged. number specifies the file-system error number. Effect. The operation terminates. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for the file-system error number. CAN'T SPOOLSTART 'OUT' FILE: number Cause. SPOOLSTART failed for the OUT file of a LIST command.
Peruse Messages DATA FILE OPEN FAILED, ERROR: number Cause. The Guardian OPEN procedure returned file-system error number when you attempted to open a data file for the current job. Effect. Peruse does not open the data file. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for the file-system error number. EDITREAD ERROR: number Cause.
Peruse Messages ENTRY NOT FOUND Cause. The DEV command specified a device that is not defined to the spooler. Effect. The spooler does not execute the command. Recovery. Verify the correct device name (you can use the Spoolcom DEV command to list all devices on the system), and then reexecute your command. FILE DOES NOT EXIST Cause. You attempted to declare a nonexistent file as the current job. Effect. The command is not executed. Recovery. Declare an existing spooler job file as the current job.
Peruse Messages ILLEGAL PAGE NUMBER Cause. A PAGE command was entered with an illegal page-number parameter. Effect. The spooler does not execute this command. Recovery. Check your syntax, then reenter this command with the correct page number. ILLEGAL PARAMETER Cause. A command with an illegal parameter value was entered. Effect. The spooler does not execute your command. Recovery. Check your syntax, and then reenter this command with the correct parameter value. ILLEGAL SUPERVISOR PROCESS NAME Cause.
Peruse Messages JOB ALREADY IS PART OF A BATCH JOB Cause. You attempted to link a job to a batch job to which it already belongs. Effect. The operation is ignored. Recovery. None is required. JOB DOES NOT BELONG TO CURRENT USER Cause. The job number in the JOB command does not belong to the user, or the user is not authorized to access the job. Effect. The command is ignored. Recovery. Check your job number, and then reenter your command. JOB IS NOT PART OF A BATCH JOB Cause.
Peruse Messages NO CURRENT JOB Cause. A DELETE command was given, but no current job was defined. Effect. Peruse ignores your command. Recovery. Peruse requires that you specify the current job before deleting it. Use the JOB command to specify the current job, and then use the DELETE command to delete it. NO JOBS AVAILABLE Cause. A command that refers to the default job was entered, but no job was found in the spooler. Effect. The spooler ignores the command. Recovery.
Peruse Messages NOT ALLOWED ON PART OF A BATCH JOB Cause. You attempted an operation on a job that is part of a batch job. Effect. The operation is ignored. Recovery. Either retry the operation on the batch job, or unlink the job from the batch job and then retry the operation. OPEN OF SPOOL SUPERVISOR FAILED, FILE ERROR: number Cause. A Guardian OPEN procedure encountered a file-system error. Effect.
Peruse Messages PROGRAM AND SPOOL LIBRARY VERSIONS DIFFER Cause. The current version of Peruse does not match the version of the spooler library procedures. Effect. Peruse abends. Recovery. Ask your system operator to match the versions. A new system-generation procedure might be required. PURGE ERROR: number Cause. The file-system error number occurred during the execution of a PURGE command. Effect. The operation terminates. Recovery.
Peruse Messages THE JOB IS CURRENTLY BEING PRINTED Cause. The command you entered would change the attributes of a current job, but your job is already in the print state. Effect. The spooler ignores your command. Recovery. To execute your command, put the job on hold. (This action deletes the job from the print queue.) Reissue your command, and then remove the hold; the job will enter the device queue again and print completely. USERNAME NOT FOUND Cause. The OWNER command has an incorrect group-name.
C Spoolcom Messages This appendix describes the error messages that Spoolcom writes to your terminal or to its OUT file. For additional information on Spoolcom, see Section 3, Spoolcom. CAN'T OPEN OUT FILE: number Cause. Spoolcom could not open the OUT file. Effect. Spoolcom reports a file-system error and uses the home terminal for the OUT file. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error number. DUPLICATE QUALIFIER FOUND Cause.
Spoolcom Messages ENTRY IN USE Cause. The spooler rejected an attempt to delete a spooler component because the component was already in use. Before deleting a location, first delete all jobs associated with this location. Before deleting a device, first delete all locations using this device. Before deleting a print process, first delete all processes associated with this print process. Effect. Spoolcom ignores the command. Recovery. Execute another command. ENTRY NOT FOUND Cause.
Spoolcom Messages INPUT FILE ERROR: number Cause. A file-system error occurred in the Spoolcom command file. Effect. Spoolcom abends. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error number. INVALID COMMAND Cause. A command contained incorrect syntax. Effect. Spoolcom ignores the command. Recovery. Reexecute the command with the correct syntax. INVALID COMMAND PARAMETER Cause.
Spoolcom Messages INVALID PROCESS NAME Cause. A process name was specified that has incorrect syntax. Effect. Spoolcom ignores the command. Recovery. Correct the syntax, and then reexecute the command. INVALID SUBCOMMAND Cause. A Spoolcom command has an illegal subcommand after the comma. Effect. Spoolcom executes the command but not the subcommand portion. Recovery. Either use the correct subcommand for this command, or enter a command that uses the subcommand you want.
Spoolcom Messages JOB number INVALID OPERATION IN CURRENT STATE Cause. A JOB command was entered that cannot be executed while your job is in its present state. Effect. Spoolcom ignores the command. Recovery. Refer to Section 3, Spoolcom for a list of the valid job states for the JOB command. Determine the correct state required for the requested operation. Then put the job into the correct state and reexecute the command. JOB IS NOT PART OF A BATCH JOB Cause.
Spoolcom Messages KEY ATTRIBUTES OF JOB DON'T MATCH THOSE OF BATCH JOB Cause. You tried to link a job to a batch job, but the job attributes (owner, form, device, and/or jobid) do not match those of the batch job. Effect. The operation is ignored. Recovery. Change the key attributes of the job to match those of the batch job. LINE TOO LONG, TRUNCATED Cause. A Spoolcom command line was longer than 132 characters. Effect.
Spoolcom Messages SECURITY COMMAND Cause. You entered a Spoolcom command that is restricted to authorized users such as system operators (user ID 255,n) and group managers (user ID n,255). Effect. Spoolcom ignores the command. Recovery. Informational message only; no corrective action is needed. Spoolcom ATTACHED TO UNKNOWN TYPE PROCESS Cause. The last OPEN command specified a process other than a spool supervisor. Effect. Spoolcom ignores the command. Recovery. Correct the supervisor name.
Spoolcom Messages SPOOLER OPEN ERROR number Cause. A Guardian file-system error occurred when the application attempted to open a file to the supervisor. Effect. The spooler has no supervisor at this time. Spoolcom ignores the command to open a file, and the file to a previous supervisor (if any) is closed. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error number. Remove the error condition before you try to open a file to the supervisor again.
D Font Utility Messages This appendix describes the error messages that the Font utility displays to the OUT file of the command used to run Font (the default is the home terminal). ^ ** ERROR Decimal Number too big or invalid Cause. The number specified after the # character is invalid. It is greater than 255, less than 0, or does not consist of the digits 0 through 9. It must be a decimal number in the range 0 through 255. Effect. The Font utility aborts.
Font Utility Messages ^ ** ERROR FONT name greater than 16 chars Cause. The Font-name parameter specified in the FONT directive or after a location in the locations section was more than 16 characters long. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Shorten the Font name so that it does not exceed 16 characters.
Font Utility Messages ** ERROR : %nnnnnn from SPOOLCONTROL Cause. An internal Font utility error occurred. Error nnnnnn was returned from a SPOOLCONTROL procedure call. The Font utility was attempting to place a CONTROL in the Font job that it was currently spooling. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Contact your service representative.
Font Utility Messages ** ERROR : %nnnnnn from SPOOLEND Cause. An internal Font utility error occurred. Error nnnnnn was returned from a SPOOLEND procedure call. The Font utility was attempting to close the Font job that it was currently spooling. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Contact your service representative.
Font Utility Messages ** ERROR : %nnnnnn from SPOOLSETMODE Cause. An internal Font utility error occurred. Error nnnnnn was returned from a SPOOLSETMODE procedure call. The Font utility was attempting to place a SETMODE in the Font job that it was currently spooling. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Contact your service representative.
Font Utility Messages ** ERROR : %nnnnnn from SPOOLWRITE Cause. An internal Font utility error occurred. Error nnnnnn was returned from a SPOOLWRITE procedure call. The Font utility was attempting to send Font job data to the collector that was receiving a new Font job. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Contact your service representative.
Font Utility Messages ^ ** ERROR Invalid beginning-count Cause. The value of beginning-count specified in the SOURCE directive is invalid. beginning-count must be a number in the range 0 through 32767. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Correct the value for beginning-count in the SOURCE directive.
Font Utility Messages ^ ** ERROR Invalid CONTROL parameter Cause. The param value specified in the CONTROL directive is invalid. param must be a positive decimal number in the range 0 through 32767. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Correct the param value in the CONTROL directive.
Font Utility Messages ^ ** ERROR Invalid directive Cause. A directive other than a Font or END-FONT directive followed a FONT directive. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Correct any misspelled directives or add a Font or END-FONT directive after the FONT directive. In most cases, you can fix the script file and rerun the Font utility without undoing any configuration changes that the Font utility made in the spooler.
Font Utility Messages ^ ** ERROR Invalid SETMODE Operation Cause. The function value specified in the SETMODE directive is invalid. The value must be a number in the range 0 through 32767. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Correct the function value in the SETMODE directive.
Font Utility Messages ^ ** ERROR Invalid SOURCE Filename Cause. The source-file filename specified in the SOURCE directive is an invalid file name. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Correct source-file in the SOURCE directive. In most cases, you can fix the script file and rerun the Font utility without undoing any configuration changes that the Font utility made in the spooler.
Font Utility Messages ^ ** ERROR Missing CONTROL Operation Cause. The operation value was not found in a CONTROL directive in a Font description. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Specify an operation value in the CONTROL directive. In most cases, you can fix the script file and rerun the Font utility without undoing any configuration changes that the Font utility made in the spooler.
Font Utility Messages ^ ** ERROR Missing CONTROLBUF Operation Cause. The operation value was not found in a CONTROLBUF directive in a Font description. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Specify an operation value in the CONTROLBUF directive. In most cases, you can fix the script file and rerun the Font utility without undoing any configuration changes that the Font utility made in the spooler.
Font Utility Messages deleted. You can find jobs that the Font utility created with the following Spoolcom command: SPOOLCOM ; JOB (REPORT LASER FONT JOB) If the job has an X in the FLAGS column and the TIME field corresponds to the time that you ran the Font utility, delete this job. ^ ** ERROR Missing SETMODE Operation Cause. The function value was not found in a SETMODE directive in a Font description. Effect. The Font utility aborts.
Font Utility Messages ^ ** ERROR Missing SOURCE Filename Cause. The source-file filename was not found in a SOURCE directive in a Font description. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Specify a filename for source-file. In most cases, you can fix the script file and rerun the Font utility without undoing any configuration changes that the Font utility made in the spooler.
Font Utility Messages ^ ** ERROR nnnn on file-name Cause. The Font utility received the file-system error nnnn when trying to access the source file (file-name) specified in the SOURCE directive. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error nnnn.
Font Utility Messages ^ ** ERROR ( OPEN^FILE ) nnnn on file-name Cause. The Font utility could not open the source file (file-name) specified in the SOURCE directive. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Refer to the Guardian Procedure Errors and Messages Manual for corrective action for file-system error nnnn.
Font Utility Messages *** ERROR Unable to find ?START-FONT directive in file-name Cause. The Font utility did not find a START-FONT directive anywhere in the script file. The Font utility ignores all text up to the START-FONT directive. Effect. The Font utility aborts. Any Font jobs created and configuration changes made to this point remain. Recovery. Put a START-FONT directive as the first directive in your script file.
Font Utility Messages **SPOOLERCOMMAND Error :%14010 ( Cannot Add this to Tables ) **Cmd: ccc ( "command-name" ) Subcmd: sss ("subcommand-name" ) Cause. The Font utility received an error from the SPOOLERCOMMAND procedure. The value of ccc is the command number issued. The value of command-name is a text description of the command. The value of sss is the subcommand number issued. subcommand-name is a text description of the subcommand.
Font Utility Messages **SPOOLERCOMMAND Error :%14013 ( Presently in use ) **Cmd: ccc ( "command-name" ) Subcmd: sss ("subcommand-name" ) Cause. The Font utility received an error from the SPOOLERCOMMAND procedure. The value of ccc is the command number issued. The value of command-name is a text description of the command. The value of sss is the subcommand number issued. subcommand-name is a text description of the subcommand.
Font Utility Messages Effect. The Font utility aborts. Recovery. Specify an existing supervisor process. **SPOOLERSTATUS Error :%14006 ( End of Spoolerstatus hits ) **Cmd: ( "command-name" , "subcommand-name") Scan: sss Cause. The Font utility received an error from the SPOOLERSTATUS procedure. command-name is a text description of the command. subcommand-name is a text description of the subcommand. sss is the SCAN^TYPE value passed to SPOOLERSTATUS.
Font Utility Messages Spooler Plus Utilities Reference Manual—522294-002 D -22
E RPSetup Utility Messages The appendix describes the error messages that the RPSetup utility displays to the home terminal of the command used to run RPSetup. FILE OPEN ERROR - supervisor - nonexistent device (14) Cause. The specified remote or local spooler does not exist. Effect. The FONT utility aborts. Recovery. Specify the name of an existing supervisor process. **SPOOLERCOMMAND Error :%14010 (Cannot Add this to Tables) **Cmd: ccc ( "command-name" ) Subcmd: sss ( "subcommand-name" ) Cause.
RPSetup Utility Messages Recovery. Change the device state of the indicated device to offline by issuing the following command: SPOOLCOM; DEV device-name, DRAIN Then rerun RPSetup. In most cases, you can rerun the RPSetup utility without undoing any configuration changes that RPSetup previously made in a spooler. **SPOOLERCOMMAND Error :%14013 (Presently in use) **Cmd: ccc ( "command-name" ) Subcmd: sss ( "subcommand-name" ) Cause. The RPSetup utility received an error from the SPOOLERCOMMAND procedure.
RPSetup Utility Messages **SPOOLERSTATUS Error :%003002 ( error-description ) **Cmd: ( "command-name" , "subcommand-name" ) Scan: sss Cause. The RPSetup utility received an error from the SPOOLERSTATUS procedure. error-description is a text description of the error. command-name is a text description of the command. subcommand-name is a text description of the subcommand. sss is the SCAN^TYPE value passed to SPOOLERSTATUS.
RPSetup Utility Messages Spooler Plus Utilities Reference Manual—522294-002 E- 4
F Using FASTP FASTP is the print process released with the spooler. Print processes retrieve the output stored on disk by a collector and print it on a device. Each print device in the spooler subsystem has a print process associated with it.
Tracing FASTP Using FASTP The FASTP print process supports CONTROLBUF 101, 103, and 113 calls in font jobs as described with the CONTROLBUF directive described in Section 4, Font Utility. Note. A CONTROLBUF 113 must be part of a font job to be processed by the FASTP print process. Tracing FASTP Tracing is performed by a FASTP print process for a device. The FASTP print process writes trace data to a trace file.
Specifying Trace Files for a Device Using FASTP REC 4000 specifies a record size of 4000 bytes. EXT (n,n) specifies the primary and secondary file extent sizes and depends on the amount of file space required. An extent consists of 2048 bytes. Specifying Trace Files for a Device One or more trace files for a device are specified with the SHADOW attribute, which is included as part of the device entry in the FASTCNFG file: DEVICE $device-name CONTYPE = connection-type SHADOW = $volume.subvolume.
Reading Trace Output Using FASTP If tracing is enabled for a device and either no SHADOW file has been specified or a problem is encountered when writing to a SHADOW file, tracing for that device is disabled. Reading Trace Output Each trace event causes two or more records to be written to a trace file.
Extended Configuration With FASTCNFG Using FASTP Table F-1. Types of Trace File Events and Data (page 2 of 2) Event Identifier From First Record for Trace Event Contents of Second Record for Trace Event Setmode Out SETMODE operation and two parameters sent to the device. Supervisor - Batch Status In Response received from supervisor process containing status for a batch. Supervisor - Batch Status Out Request sent to supervisor process to solicit status of a batch.
Creation Using FASTP Creation The default location for the file is $SYSTEM.SYSTEM.FASTCNFG. If a product-specific version of the FASTP print process is looking for a FASTCNFG file, it expects the file name to be $SYSTEM.SYSTEM.FASTCNFG unless the file name is explicitly defined with the following DEFINE statements: SET DEFMODE ON ADD DEFINE = FASTCNFG,FILE $volume.subvolume.file-ID A spooler subsystem uses the information in a DEFINE statement only after the subsystem is started.
Alteration Using FASTP One of the SPOOLCOM device attributes is EXCLUSIVE [ON|OFF]. The default value is EXCLUSIVE OFF. If EXCLUSIVE OFF is specified, a device is opened only if a job is queued for the device and FASTP does not already have the device open. The print process opens the device and sends the job to it. If a job is queued for the device and the print process already has the device open, the print process sends the job to the device without first opening it.
Syntax Using FASTP Syntax The syntax for a FASTCNFG file is informally structured and consists of a keyword and keyword value followed by one or more pairs of attributes and attribute values: keyword keyword-value attribute = attribute-value [ attribute = attribute-value ]...
Syntax Using FASTP Separator Characters Keywords and keyword values must be separated with one or more blank spaces. Attributes and attribute values must be separated with an equal (=) sign. One or more blank spaces can be inserted before or after the = sign. Keyword and keyword value pairs and attribute and attribute value pairs must be separated with one or more blank spaces.
FASTCNFG File Redirection Using FASTP Attributes All attributes, except for the FASTCNFG attribute, are device attributes. Some device attributes (and their attribute values) can be used with any product-specific version of a FASTP print process. Other device attributes (and their attribute values) are used only with one product-specific version of a FASTP print process. Device attributes are described in the product-specific sections of this manual.
FASTCNFG File Redirection Using FASTP The syntax for specifying a subordinate FASTCNFG file in a spooler subsystem is as follows: SPOOLER [\node.]$supervisor-name FASTCNFG = [\node.][$volume.][subvolume.]file-ID The syntax for specifying a subordinate FASTCNFG file for one print process is as follows: PROCESS [\node.]$process-name FASTCNFG = [\node.][$volume.][subvolume.
EOLWRITE Using FASTP Level-3 FASTCNFG File Syntax In a level-3 FASTCNFG file you can only specify device attributes: DEVICE [\node.]$device-name[.#qualifier] attribute = attribute-value [,attribute = attribute-value]... EOLWRITE FASTP normally attempts to buffer output, except in some cases involving parallel printers. EOLWRITE = YES | NO YES forces normally buffered output to be written to the device a line at a time. The default value is NO.
G Spooler Limits This appendix describes the programmatic limits of the Spooler and Spooler Plus subsystem components. Table G-1.
Extended Memory Spooler Limits Per Supervisor:---------- Maximum configurations ------------- 297 * JOBS SPOOLER SPLR PLUS SPOOLER SPLR PLUS Max # Max # Bytes Bytes ------- --------- ------- --------- 8191 85534 + 174 * DEVICES 4095 4095 + 268 * COLLECTORS 16 31 4288 8308 + 129 * PRINT PROCS 45 255 5805 32895 + 40 255 2047 10200 81880 32767 597870 4783982 (4.
H Spooler and Spooler Plus Comparison Spooler Plus is an optional product containing Spoolcom and Peruse modules that can be used to replace the Spoolcom and Peruse modules provided by the D41 and later releases of the Spooler subsystem. You can use the Spooler Plus Spoolcom and Peruse utilities to configure and manage expanded configurations of the Spooler subsystem. You must use these utilities if the maximum jobs has been configured above 8191.
Extended Component Limits Spooler and Spooler Plus Comparison Extended Component Limits Table H-1 compares Spooler and Spooler Plus component limits. Table H-1.
Spooler and Spooler Plus Comparison Peruse Functions Added to Spoolcom Peruse Functions Added to Spoolcom All Peruse functions are included in the Spooler Plus Spoolcom utility. Peruse functions have been added to Spoolcom as additional subcommands or commands. Table H-2 lists some of the Peruse command functions that have been included in the Spooler Plus Spoolcom utility, Table H-2.
Spooler and Spooler Plus Comparison Enhanced SPOOLER STATISTICS Subcommand Table H-4 lists subcommands that have been added to the Spooler Plus Spoolcom utility but that are not part of the Spooler Spoolcom utility. Table H-4. Spooler Plus Spoolcom Subcommands Subcommand Description NEXT Used with the JOB command. This subcommand makes the next higher number job the current job. If there is no current job, the lowest job number in the list of jobs becomes the current job.
Spooler and Spooler Plus Comparison Changes to Library Procedures Changes to Library Procedures The library procedures in the Spooler system have been enhanced to support the application of Spooler Plus utilities and the new commands and subcommands. Application Migration Issues Applications that use the Spooler library procedures may need to be changed if they use procedures that are sensitive to limits extensions.
Spooler and Spooler Plus Comparison Spooler Plus Utilities Reference Manual—522294-002 H- 6 Unsupported Procedures
Index Numbers 129 files See Spooler job files 5537 or 5577 printer 4-8 A Active state (collector), explained 3-17 Active state (spooler), explained 3-78 ALIGN subcommand, SPOOLCOM DEV command 3-21 ALL option PERUSE HELP command 2-21 PERUSE LIST command 2-29 SPOOLCOM LIST command 3-63 Archiving example 2-32, 3-65 ASCII compression example 2-32, 3-65 ASSIGN PRINTFILE command (RPSETUP) 5-10 Authorization FONT utility 4-4 B Backup CPU, for interspooler threads 5-10 BACKUP subcommand SPOOLCOM COLLECT command 3
D Index Configuration for device timeout attribute 3-31 Configuration parameters (RPSETUP) 5-8 CONTROL directive (FONT utility) 4-9 Control file name SPOOL program A-1 CONTROLBUF directive (FONT utility) 4-9/4-12 COPIES command (PERUSE) 2-11 COPIES subcommand SPOOLCOM BATCH command 3-8 SPOOLCOM JOB command 3-54 CPU subcommand SPOOLCOM COLLECT command 3-13 SPOOLCOM PRINT command 3-75 CPU subcommand, SPOOLCOM COLLECT 1-5 Cross-connected spoolers 5-1 CURRENT subcommand SPOOLCOM BATCH command 3-8 SPOOLCOM JOB
E Index Dormant state (spooler), explained 3-78 Drain state (collector), explained 3-17 DRAIN subcommand SPOOLCOM COLLECT command 3-14 SPOOLCOM DEV command 3-23 SPOOLCOM SPOOLER command 3-83 DUMP subcommand SPOOLCOM SPOOLER command 3-83 D-series system and the SPOOLCOM command 3-3 E ENDFF subcommand, SPOOLCOM DEV command 3-23 END-FONT directive 4-6 END-LOCATIONS directive 4-15 Error log file name SPOOL program A-1 Error messages FONT utility D-1/D-21 PERUSE B-1/B-10 RPSETUP utility E-1/E-3 SPOOLCOM C-1/C
G Index FONT utility 4-1/4-17 CONTROL directive 4-9 CONTROLBUF directive 4-9/4-12 END-FONT directive 4-6 END-LOCATIONS directive 4-15 error messages D-1/D-21 FONT directive 4-7 normal data 4-7/4-8 SETMODE directive 4-13 SOURCE directive 4-14 START-FONT directive 4-6 START-LOCATIONS directive 4-15 FORM command (PERUSE) 2-19/2-20 Form name device 1-11 job 1-9/1-10 FORM subcommand SPOOLCOM BATCH command 3-8 SPOOLCOM DEV command 3-24 SPOOLCOM FONT command 3-47 SPOOLCOM JOB command 3-53, 3-54 Function keys, di
K Index Job (continued) altering number of columns (SPOOLCOM) 3-71 altering number of copies (PERUSE) 2-11 altering owner of PERUSE 2-35 SPOOLCOM 3-55 altering queue priority PERUSE 2-37 SPOOLCOM 3-55 altering report name PERUSE 2-39 SPOOLCOM 3-55 altering status of (SPOOLCOM) 3-52/3-61 attributes 1-9/1-10 batch number 1-9 copies 1-9 deleting from spooler PERUSE 2-12 SPOOLCOM 3-54 described 1-9/1-10 displaying a line of (PERUSE) 2-17 displaying a line of (SPOOLCOM) 3-43 displaying pages of (PERUSE) 2-7, 2
M Index LOC command (continued) SPOOLCOM 3-66/3-69 LOC subcommand SPOOLCOM BATCH command 3-9 SPOOLCOM FONT command 3-47 SPOOLCOM JOB command 3-53, 3-55 Local spooler, RPSETUP 5-6 Location 1-10, 1-13/1-15 altering PERUSE 2-32 SPOOLCOM 3-55 sending process output to 1-15 Locations section 4-15 Locations, number of A-2 Log file name SPOOL program A-1 LUEOLVALUE subcommand, SPOOLCOM DEV command 3-25 LUEOLWHEN subcommand, SPOOLCOM DEV command 3-26 LUTOFVALUE subcommand, SPOOLCOM DEV command 3-26 NUMCOL comman
P Index PARAM DEVHEADER command (RPSETUP) 5-11 PARAM DEVPARM command (RPSETUP) 5-12 PARAM DEVRESTART command (RPSETUP) 5-13 PARAM DEVTRUNC command (RPSETUP) 5-13 PARAM DEVWIDTH command (RPSETUP) 5-14 PARAM NUMTHREADS command (RPSETUP) 5-14 PARAM PRICPU command (RPSETUP) 5-15 PARAM PRINTNAME command (RPSETUP) 5-15 PARAM PRINTPARM command (RPSETUP) 5-15 PARAM PRIORITY command (RPSETUP) 5-16 PARAM THREADNAME command (RPSETUP) 5-16 Parameters, configuring with RPSETUP 5-8/5-16 PARM subcommand SPOOLCOM DEV com
Q Index Print Process, interspooler threads assigning primary CPU 5-15 Print process, interspooler threads assigning backup CPU 5-10 assigning priority 5-16 assigning process name 5-15 assigning program file 5-10 assigning startup message 5-15 default operations 5-12 Print process, spooler changing attributes of (SPOOLCOM) 3-77 changing status of (SPOOLCOM) 3-75/3-80 independent 3-76 obtaining status of (SPOOLCOM) 3-75/3-80 specifying attributes of (SPOOLCOM) 3-75/3-80 specifying the program 3-76 states 3
S Index S Script file comments 4-16 example 4-17 syntax 4-5/4-17 Security FONT utility 4-4 RPSETUP utility 5-7 spooler 1-20 SELPRI subcommand SPOOLCOM BATCH command 3-9 SPOOLCOM JOB command 3-55 SETMODE directive (FONT utility) 4-13 SHOWGROUP command (PERUSE) 2-40/2-42 SJFILES command (PERUSE) 2-42 SJFILES command (SPOOLCOM) 3-82 SKIP subcommand, SPOOLCOM DEV command 3-29 SKIPTO subcommand, SPOOLCOM DEV command 3-29 SNA character string (SCS) mode 3-23 SOURCE directive (FONT utility) 4-14 SPEED subcommand
T Index Spooler states, explained 3-78 Spooler supervisor remote opening with PERUSE 2-34 opening with SPOOLCOM 3-72 running PERUSE 2-3 SPOOLCOM 3-3 Spoolers, linked 1-7, 5-1 START subcommand SPOOLCOM BATCH command 3-9 SPOOLCOM COLLECT command 3-14 SPOOLCOM DEV command 3-30 SPOOLCOM JOB command 3-55 SPOOLCOM PRINT command 3-76 SPOOLCOM SPOOLER command 3-83 STARTCOL command (PERUSE) 2-43 affects line displayed FIND command 2-18 LIST command 2-30 STARTCOL command (SPOOLCOM) 3-89 affects line displayed FIND
U Index Truncation option, for interspooler threads 5-13 U Unit size 1-7 UNIT subcommand SPOOLCOM COLLECT command 3-15 UNIT subcommand, SPOOLCOM COLLECT 1-5 UNLINK command (PERUSE) 2-45 UNLINK subcommand SPOOLCOM BATCH command 3-10 V Virtual font jobs 4-12 VOLUME command (PERUSE) 2-46 VOLUME command (SPOOLCOM) 3-90 W Waiting state (device), explained 3-36 Warmstarting the spooler SPOOL program A-3 WIDTH subcommand SPOOLCOM DEV command 3-32 X XREF subcommand SPOOLCOM DEV command 3-32 SPOOLCOM PRINT com
Special Characters Index Spooler Plus Utilities Reference Manual—522294-002 Index -12
