Spooler Utilities Reference Manual Abstract This manual describes the Spooler utilities—Peruse, Spoolcom, Font, and RPSetup— and presents the complete syntax for these utilities. It also presents a general introduction to the Spooler subsystem. This manual is intended for all interactive and operational users of the Spooler subsystem. Product Version Spooler D48, H01 and H02 Supported Releases This manual supports D48.03, G06.16 and H06.
Document History Part Number Product Version Published 135721 Spooler D41 August 1997 140947 Spooler D41 May 1998 422816-001 Spooler D46 June 1999 425735-001 Spooler D46 February 2000 522295-001 Spooler D48 November 2001 522295-002 Spooler D48 May 2002 522295-003 Spooler D48, H01 and H02 July 2012
Legal Notices © Copyright 2012 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Spooler Utilities Reference Manual Index Examples Figures Tables Legal Notices What’s New in This Manual ix Manual Information ix New and Changed Information ix About This Manual xi Who Should Use This Manual xi How This Manual Is Organized xi Related Manuals xii Your Comments Invited xiii Notation Conventions xiii 1.
Contents 2. Introduction to the Spooler Subsystem (continued) Spooling in a Network 2-7 Peruse and Spoolcom Comparison 2-9 2.
Contents 3. Peruse (continued) Displaying a Job 3-8 Using Spooler Job Files 3-8 3.
Contents 4. Spoolcom 4. Spoolcom Spoolcom Features 4-2 Spoolcom Security 4-2 Running Spoolcom 4-2 Running Spoolcom Noninteractively 4-3 Running Spoolcom Interactively 4-3 Entering Spoolcom Commands 4-4 Spoolcom Commands 4-5 BATCH Command 4-7 COLLECT Command 4-12 COMMENT Command 4-19 DEV Command 4-20 EXIT Command 4-40 FC Command 4-41 FONT Command 4-42 HELP Command 4-47 JOB Command 4-48 LOC Command 4-58 OPEN Command 4-62 PRINT Command 4-63 SPOOLER Command 4-70 5.
Contents 6. RPSetup Utility 6. RPSetup Utility How the RPSetup Utility Works 6-2 Interspooler Threads 6-3 Running RPSetup 6-6 Requirements for Running RPSetup 6-7 Example 6-8 Configuring Entities in the Local Spooler 6-8 Default Configuration 6-8 ASSIGN and PARAM Commands 6-11 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.
Contents G. Spooler Limits G. Spooler Limits H.
Contents Examples Examples Example 1-1. Example 1-2. Example 1-3. Example 1-4. Example 1-5. Example 1-6. Example 1-7. Example 1-8. Example 1-9. Example H-1. Example H-2. Example H-3. Example H-4.
Contents Tables (continued) Tables (continued) Table 4-8. Table 4-9. Table 4-10. Table 4-11. Table 4-12. Table 4-13. Table 4-14. Table 4-15. Table 4-16. Table 4-17. Table 6-1. Table 6-2. Table F-1. Table G-1. Table H-1. Table H-2.
What’s New in This Manual Manual Information Spooler Utilities Reference Manual Abstract This manual describes the Spooler utilities—Peruse, Spoolcom, Font, and RPSetup— and presents the complete syntax for these utilities. It also presents a general introduction to the Spooler subsystem. This manual is intended for all interactive and operational users of the Spooler subsystem. Product Version Spooler D48, H01 and H02 Supported Releases This manual supports D48.03, G06.16 and H06.
What’s New in This Manual New and Changed Information Added a description about the limitation of the device name usage under the Considerations on page 4-33. Added a Peruse error message on page B-8. Changes in the May 2002 manual: The following changes have been made to this manual: In Section 3, Peruse, a new feature has been added to the LIST command. In previous releases of spooler, a job that contained more than 99,999 lines listed to an EDIT file would become truncated.
About This Manual Purpose of This Manual This manual describes: The Spooler utilities—Peruse, Spoolcom, Font, and RPSetup—and provides the command syntax and message descriptions for these utilities. The FASTP configuration process and gives the programmatic limits of Spooler components. Who Should Use This Manual This manual is intended for any users of the Spooler subsystem who wants complete command syntax information for the Spooler utilities.
About This Manual Related Manuals Section or Appendix Title Contents C Spoolcom Messages Explains error and warning messages issued by Spoolcom and recommends ways to recover from errors. D Font Utility Messages Explains error and warning messages issued by the Font utility and recommends ways to recover from errors. E RPSetup Utility Messages Explains error and warning messages issued by the RPSetup utility and recommends ways to recover from errors.
About This Manual Notation Conventions Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
About This Manual General Syntax Notation … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation.
About This Manual !i:i. Notation for Messages In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes. For example: error := FILENAME_COMPARE_ ( filename1:length , filename2:length ) ; !i:i !i:i !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes.
About This Manual Hypertext Links | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK | Failed } % 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.
About This Manual Change Bar Notation Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
About This Manual HP Encourages Your Comments HP Encourages Your Comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs. Send any errors found, suggestions for improvement, or compliments to: docsfeedback@hp.com Include the document title, part number, and any comment, error found, or suggestion for improvement that you have concerning this document.
1 Spooler Quick Start This section is a concise set of instructions for starting and draining, or stopping, the spooler. Depending on the release from which you are upgrading, some configuration of spooler might be required. The best method for assuring that any previous version (T9101) of spooler can be used is to always back up the control files and the collector files for that version, prior to warm starting the new version of spooler.
Spooler Quick Start Spooler Configuration File Spooler Configuration File Example 1-1 is a sample spooler configuration file: Example 1-1. Spooler Configuration File COMMENT******************************************* COMMENT \ACCT $SPLS Spooler config file COMMENT COMMENT Author; John Scott COMMENT Date; 12/23/99 COMMENT Function; To configure $SPLS supervisor COMMENT COMMENT******************************************* COLLECT COLLECT COLLECT $S, FILE $SYSTEM.SYSTEM.CSPOOL $S, DATA $OPER.SPLS.
Spooler Quick Start Spooler Start Macro Example 1-2. Spooler Start Macro (page 1 of 2) ?TACL MACRO #set #informat tacl ==************************************************** == \ACCT $SPLS SPOOLER START MACRO == == AUTHOR; John L. Scott == DATE; 2/24/97 == FUNCTION; To start spooler $SPLS and collector $S. == FILE; $system.startup.strtspls == == To Cold Start; RUN $SYSTEM.STARTUP.STRTSPLS COLD == (Spooler isn't configured,to create new Spooler environment) == == To Warm Start; RUN $SYSTEM.STARTUP.
Spooler Quick Start Starting the Spooler Example 1-2. Spooler Start Macro (page 2 of 2) | ELSE | == It's a WARMSTART FUP GIVE ($SYSTEM.SYSTEM.CSPOOL,$SYSTEM.SYSTEM.PSPOOL, $SYSTEM.SYSTEM.SPOOL),30,1 FUP SECURE ($SYSTEM.SYSTEM.CSPOOL,$SYSTEM.SYSTEM.PSPOOL, $SYSTEM.SYSTEM.SPOOL),"NUNU",PROGID & & SPOOL /IN $OPER.SPLS.SPL,TERM $YMIOP.
Spooler Quick Start Cold Starting a Spooler Example 1-3. Spooler Warm Start File comment -- This is $SYSTEM.STARTUP.SPLWARM comment -- This file warm starts the spooler, leaving all jobs intact. SPOOL / IN $SYSTEM.SPL.SPL, OUT $ZHOME, NAME $SPLS, NOWAIT, PRI 149, CPU 1& / 0 SPOOLCOM; SPOOLER, START comment -- check to see that the spooler started successfully SPOOLCOM; SPOOLER, STATUS Note that $ZHOME is specified as the home terminal in Example 1-3.
Spooler Quick Start Cold Starting a Spooler Example 1-4. Spooler Cold Start File (COLDFILE) COMMENT -- THIS IS $SYSTEM.SPLUTIL.COLDFILE COMMENT -- THIS COMMAND FILE CREATES A SPOOLER SYSTEM COMMENT -- Purge any existing collector data files having the COMMENT same name as the data file you intend to use. PURGE $MKT.SPL.DATAFILE COMMENT -- Purge spooler supervisor control files having COMMENT names you intend to use: PURGE $MKT.SPL.SPL0 PURGE $MKT.SPL.SPL1 PURGE $MKT.SPL.SPL2 PURGE $MKT.SPL.
Spooler Quick Start Cold Starting a Spooler Example 1-5. Spooler Configuration File Named SPLCONF COMMENT -- THIS IS $SYSTEM.SPLUTIL.SPLCONF COMMENT -- THIS CONTROL FILE USES SPOOLCOM TO CONFIGURE THE COMMENT SYSTEM TO BE COLD STARTED AND PASSES THIS COMMENT INFORMATION TO THE SUPERVISOR. COMMENT ***** YOUR SYSTEM COMMENT ***** SPOOLER CONFIGURATION COMMENT ***** 28 AUG 1993 COMMENT -- To configure one collector named "$S": COLLECT $S, FILE $SYSTEM.SYSTEM.CSPOOL COLLECT $S, DATA $MKT.SPL.
Spooler Quick Start Cold Starting a Drained Spooler Cold Starting a Drained Spooler This subsection explains how to cold start your spooler subsystem after it has been drained. See Draining the Spooler on page 1-9. Starting a new spooler is known as “cold starting” the spooler. Coldstarting a spooler erases existing print jobs and previously configured settings. (When you cold start a spooler, you create new control files in which the supervisor stores all the configuration information.
Spooler Quick Start Draining the Spooler 7. Specify the names and attributes of the print processes: ) PRINT $ print-process 8. Specify the names and attributes of the devices: ) DEV $ device , PROCESS $ print-process 9. Specify locations and connect locations to devices: ) LOC [ # group]. dest , DEV [ $device ] 10. Start the spooler: ) SPOOLER, START Draining the Spooler Draining brings the spooler to an orderly halt after all jobs have currently printed or spooling has finished.
Spooler Quick Start Draining the Spooler Step 2: Drain the Spooler Properly To drain the spooler, log on as a super group user (255,n), access SPOOLCOM, and enter the following command: SPOOLCOM> SPOOLER, DRAIN This command causes the spooler to move from the active to the dormant state. Caution. Do not use the TACL STOP command to bring down the spooler. Also, never use the TACL STOP command after you have issued the SPOOLCOM DRAIN command.
Spooler Quick Start Draining the Spooler You also must know the name of the Supervisor process that has the control file open. To identify the Supervisor process, you need to: 3. Find the PID of the Supervisor process. Issue the following FUP command: 35> FUP LISTOPENS $SYSTEM.SPOOLER.CTRL3 Example 1-7 shows the outcome of this command: Example 1-7. PID of the Supervisor Process $SYSTEM.SPOOLER.
Spooler Quick Start Recovery for the Spooler Recovery for the Spooler Use this subsection to help recover from a spooler problem. Recovery for an Improperly Drained Spooler If a spooler was improperly drained or suffered an abnormal shutdown, follow these steps to recover from this situation: 1. Warm start the spooler. 2. Enter the SPOOLCOM JOB command: ) JOB 3. If you find a Job 0 listed as a result of the SPOOLCOM JOB command, the spooler has a corrupted job map.
Spooler Quick Start Connecting Spoolers in a Network Using RPSetup 4. Enter SPOOLCOM and start the spooler: > SPOOLCOM SPOOLER, START This example shows how to rebuild control files. > SPOOLCOM SPOOLER, DRAIN > SPOOL /IN $MKT.SPL.SPL, NAME $SPLS/ R,995,995,150,10,10 > SPOOLCOM SPOOLER, START The parameters used in this example are as follows: $MKT.SPL.SPL is the control file. $SPLS is the name of the supervisor. R stands for REBUILD.
Spooler Quick Start Connecting Spoolers in a Network Using RPSetup Spooler Utilities Reference Manual—522295-003 1-14
2 Introduction to the Spooler Subsystem The Spooler 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 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 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 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. There can be up to 15 collectors associated with a given spooler.
Introduction to the Spooler Subsystem Spooler Components The spooler components are shown in Figure 2-1 Figure 2-1.
Introduction to the Spooler Subsystem Collectors 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 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 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.
Introduction to the Spooler Subsystem Spooling in a Network Figure 2-2. Linked Spoolers in a Network \APPL \PRNT Application Application 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 CDT 012.
Introduction to the Spooler Subsystem Peruse and Spoolcom Comparison Peruse and Spoolcom Comparison Many commands in Peruse and Spoolcom are nearly equivalent. For example, the Peruse DEV and Spoolcom DEV commands both display the status of devices, and many Peruse commands are also subcommands of the Spoolcom JOB command (COPIES, DEL, FORM, HOLDAFTER, OWNER, and PRI).
Introduction to the Spooler Subsystem Job Priority Job Priority Job priority determines when a job will print in relation to other jobs queued for the same device. The spooler maintains a device queue for all print devices, and higherpriority jobs are placed ahead of lower-priority jobs in the queue. For more information, see Selection Algorithm on page 2-15. Job Copies The job copies attribute specifies the number of copies to print.
Introduction to the Spooler Subsystem Job State Figure 2-3. Life Cycle of a Spooler Job Job is created OPEN READY PRINT Job is deleted HOLD CDT 003.CDD You create a job when your application opens a collector process and writes to it; for example: TFORM / IN filename, OUT $S.device / A job in the OPEN state is being added to the spooler. For example, if you send the output from a TFORM process to the spooler, the job is in the OPEN state until the TFORM output is complete.
Introduction to the Spooler Subsystem Devices and Device Attributes Devices and Device Attributes A device produces a hard-copy listing of your job. Every device is controlled by a print process. Devices (and print processes) have four attributes that can affect your spooler jobs: Form name Device header message Device state Selection algorithm Device Form Name The form name of a device is an optional attribute that allows you to control the type of job that can be printed on the device.
Introduction to the Spooler Subsystem Device Header Message Figure 2-4.
Introduction to the Spooler Subsystem Device State Device State The device state describes the status of the device. There are six possible device states: PRINTING The device is currently printing a job. WAITING The device is idle and is waiting for a job to print. OFFLINE The device is not available for printing. SUSPENDED The device is in the process of printing a job but has been suspended by the operator (to change ribbons, for example).
Introduction to the Spooler Subsystem Routing Structure Routing Structure The routing structure directs jobs to print devices. It consists of a set of locations and print devices. Figure 2-5 shows the association of locations with print devices. Figure 2-5. 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 CDT 003.
Introduction to the Spooler 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 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 Subsystem Sending Process Output to a SPOOL DEFINE 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. Specifying all the spooler job attributes in a SPOOL DEFINE is faster than using Peruse to change the job attributes after the job is in the spooler.
Introduction to the Spooler 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.
Introduction to the Spooler Subsystem The Spooler and Batch Jobs Figure 2-6. 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 CDT 004.
Introduction to the Spooler Subsystem How to Change the Attribute Values of Batch Jobs How to Change the Attribute Values of Batch Jobs With the exception of key attributes, you can change any attribute of a single job that belongs to a batch job. Use Peruse or Spoolcom to change these attributes in the same way you would if the job did not belong to a batch job. Note. When a job is part of a batch job, you cannot alter the key attributes.
Introduction to the Spooler 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.
3 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 3-2 Running Peruse on page 3-3 Peruse Commands on page 3-9 Note. The command displays shown in this section are applicable to D41 and later versions of the spooler supervisor.
Peruse Peruse Features 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.
Peruse Running 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 (/).
Peruse Running Peruse Interactively 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: 1> PERUSE PERUSE - T9101D48 - (30MAR2001) SYSTEM \EAST Copyright Tandem Computers Incorporated 1978, 1982, 1983, 1984, 1985, 1986, 1987, 1988, 1989, 1991 _ T9101D48 is the product version of Peruse.
Peruse Initial Job Status Display 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 - T9101D48 - (30MAR2001) SYSTEM \NS 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
Peruse HOLD Entering Peruse Commands 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.
Peruse Declaring the Current Job 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.
Peruse Displaying a Job Displaying a Job There are three ways to display the current spooler job using Peruse: Use the LIST Command, which is described later in this section. Press the Return key to display one line. Press and hold down the Return key to scroll the job until you release the key. If you have a page-mode terminal, use the function keys to list lines from the current job. Table 3-1 shows the number of lines listed by each function key. Table 3-1.
Peruse Peruse Commands If you attempt to execute one of these commands for a spooler job file, Peruse displays the following message: COMMAND NOT SUPPORTED FOR SPOOLER JOB FILES You can run Peruse and access spooler job files even if the spooler supervisor process is not running.
Peruse Peruse Commands Table 3-2. Summary of Peruse Commands (page 2 of 2) Command Function PURGE Purges one or more disk files. REPORT Changes the report name of the current job. SHOWGROUP Enables display to a group manager of all jobs that belong to the group. SJFILES Displays the names of all spooler job files in a specified or default subvolume. Spooler job file names are preceded by a period (.). STARTCOL Sets the first column to be displayed by the LIST command.
Peruse BATCH Command 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. Unless you log on as the super ID (255,255), you are not permitted to affect another user’s batch job. The batch job specified by batch-number becomes current. Considerations Once a batch job is current, most subsequent commands are applied to all the jobs in the batch job.
Peruse COPIES Command 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). COPIES Command The COPIES command alters the number of copies for the current job. If there is no current job, then the job most recently spooled job becomes the current job. COPIES number-of-copies number-of-copies is the number of copies of the current job to be printed.
Peruse DEL Command DEL Command The DEL command deletes the current job from the spooler subsystem. DEL Considerations Before you can delete a spooler job, you must make it the current job. Refer to Declaring the Current Job on page 3-7. A job that is printing when the DEL command is issued will stop printing and be deleted. If the job to be deleted is linked to a batch job, Peruse unlinks the job from the batch job and then deletes it.
Peruse DEL Command 2.
Peruse DEV Command 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. FORM is the form name, if any, denoting a special print device or paper associated with that printer. The jobs in the device queue are listed in the order that they will print.
Peruse EXIT Command EXIT Command The EXIT command ends the Peruse session. E[XIT] Consideration Pressing Ctrl-Y also ends the Peruse session.
Peruse FC Command 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. FC Consideration The FC command executed in Peruse can modify only the last line, unlike an FC command executed at a TACL prompt, where the FC command can also identify and modify other lines.
Peruse FILES Command FILES Command The FILES command displays the names of all files on a subvolume. The names of spooler job files are preceded by a period (.). FILES [ subvol ] subvol is the subvolume whose file names are to be listed. subvol has the form [\system.][$volume.][subvolume] If you omit \system, PERUSE uses the current default system name. If you omit $volume, PERUSE uses the current default volume name. If you omit subvolume, PERUSE uses the current default subvolume name.
Peruse FIND Command FIND Command The FIND command locates an occurrence of a specified string in the current job and prints the line containing the string. If there is no current job, then the job most recently spooled becomes the current job. F[IND] [ B[OTH] ] [ / string / ] [ start-position ] B[OTH] specifies that the FIND command should find and display both uppercase and lowercase occurrences of string. string is a set of printable ASCII characters set off by two identical separators.
Peruse FIND Command Considerations The NUMCOL and STARTCOL commands affect the line displayed by FIND. FIND will find string even if string is located in an area excluded by a NUMCOL or STARTCOL command, but FIND displays only that area permitted by NUMCOL and STARTCOL. If no line is displayed after a FIND command is executed, then there are no occurrences of string in the remainder of the job.
Peruse FORM Command FORM Command The FORM command alters the form name of the current job. If there is no current job, then the job most recently spooled becomes the current job. The form name of a job denotes the requirement for a special print device or paper associated with that printer. FORM [ form-name ] form-name is a string of as many as 16 letters, digits, and spaces. If you omit form-name, Peruse assigns a form name containing all blanks.
Peruse FORM Command Then you specify the same form for your job. The JOB STATUS command confirms this: _FORM PAYCHECK _J S JOB BATCH STATE J 1221 READY PAGES COPIES PRI HOLD LOCATION REPORT 1 1458 4 #CHKWRTR BKKPG JEN JOB FORM 1221 PAYCHECK CLOSE TIME 11 DEC 91, 09:50:40 JOB LOCATION 1221 #CHKWRTR.DEFAULT DEVICE $CHKWRTR SEQ 1 COPY 1 PAGE 1458 _ If you send a job to a destination device whose form name does not agree with the job, your job does not print.
Peruse HELP Command 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.
Peruse HOLD Command 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.
Peruse HOLD Command 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 _ Spooler Utilities Reference Manual—522295-003 3-25
Peruse HOLDAFTER Command 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. When the hold-after-printing flag of a job is on and the job has finished printing, the spooler places that job in the HOLD state rather than deleting it from the spooler subsystem.
Peruse HOLDAFTER Command At a later time, you can print another copy of this job without repeating the compiling and spooling time. Remove the hold, and your job enters the print queue: _HOLD OFF; J JOB J 722 BATCH STATE PAGES COPIES PRI HOLD LOCATION REPORT PRINT 3 1 4 A #HT1 INVENT PAT When the job finishes printing, it again enters the HOLD state. You can do this any number of times.
Peruse JOB Command JOB Command The JOB command sets the status of the current job or displays the status of all jobs that you own. Most of the Peruse commands affect only the current job. The meaning of each entry in the job display is given earlier in this section under Running Peruse. J[OB] [ option ] option is one of the following: job-number file-name * S[TATUS] #location-name job-number is the number of a job that you own.
Peruse JOB Command Considerations If you are a group manager (user ID n,255), the JOB command displays the status of all jobs that belong to your group members if manager access is enabled for the spooler (through the Spoolcom SPOOLER, MGRACCESS command). Assuming manager access is enabled for the spooler, you can enable and disable the display of your group’s jobs by using the SHOWGROUP command as described later in this section.
Peruse JOB Command SEQ is the job sequence number in the device queue. If the job is printing, its SEQ is PRINT. The next job to print on the device has a sequence number of 1. COPY is the number of copies of the job that are to be printed. PAGE is the number of pages in the job. Examples 1.
Peruse JOB Command 4. You can declare the current job by entering only the job number.
Peruse LINK Command LINK Command The LINK command links the specified job to the current batch job. The key attributes of the specified job must match those of the current batch job. LINK job-number job-number specifies the job to be linked to the current batch job. Example The following Peruse display shows that batch 555 contains two jobs, 1167 and 1289. Note that job 1200 is not currently part of batch 555.
Peruse LIST Command 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. 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.
Peruse LIST Command If you do not specify OUT list-file, output is directed to the OUT file-name specified when Peruse was started (the home terminal by default). If you specify E[DIT], S[POOL], or C[OMPRESS] 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.
Peruse LIST Command 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. For details about formatting control, refer to the Guardian Programmer's Guide. O causes the data to be displayed in octal representation rather than in ASCII. Considerations If no current job is defined, the LIST command causes the most recently spooled job to become the current job.
Peruse LIST Command 5. The LIST command below shows the first page, the second page, and the next-tolast page in the job. Page 5 is not listed because the current page changes during the LIST command. Also see the PAGE Command on page 3-42. _P 5 _L F, *, L-1 6. You can use /OUT $S.#device/ to print all or only a few pages of an already spooled file. The example below prints page 1 and pages 16 through 20 of the job.
Peruse LIST Command To print the archived spooler job file, use the Peruse JOB command to specify the file name. Then use the Peruse LIST command to list the file to a printer. You must specify the pages you want to print, as shown below. If you do not specify the pages you want, only the last page is printed (see Example 3). _JOB SVOL.ARCH01 _LIST /OUT $S.
Peruse LOC Command LOC Command The LOC command alters the location of the current job. If there is no current job, then the job most recently spooled becomes the current job. LOC [ #location-name ] #location-name is the name of the new location for the current job. If #location-name is not specified, then the current job is given #DEFAULT (your default printer) as its new location. Considerations The LOC command is not supported for a single job that is part of a batch job.
Peruse NUMCOL Command 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 Peruse 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.
Peruse OPEN Command OPEN Command The OPEN command allows you to specify a new spooler supervisor without exiting Peruse. OPEN [ supervisor-name ] supervisor-name is the name of the new spooler supervisor that Peruse is to communicate with. The process name of the supervisor can be in local or network form. The local form is $process-name, which identifies the spooler process (see Considerations). The network form is \system.$process-name, where system identifies a remote node.
Peruse OWNER Command OWNER Command The OWNER command changes the owner of the current job. If there is no current job, then the job most recently spooled becomes the current job. After this command is issued, the current job becomes the property of the specified owner and can no longer be accessed by the previous owner. OWNER { group-name.user-name | group-# , user-# } group-name.user-name is the name of the new owner, entered without spaces on either side of the period.
Peruse PAGE Command 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. Peruse 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.
Peruse PAGE Command Examples 1. In the following example, the PAGE command tells you the line and page number of where you are located in the spooled job: _PAGE PAGE: 7 _ LINE: 15 2.
Peruse PRI Command PRI Command The PRI command alters the priority of the current job. If there is no current job, then the job most recently spooled becomes the current job. The higher the priority, the sooner a job will print. PRI priority priority is a number in the range 0 through 7. Zero is the lowest priority. The default priority is 4. Considerations When a job is added to the spooler, it is given a priority of 4.
Peruse PURGE Command PURGE Command The PURGE command deletes one or more disk files. This command applies only to Enscribe files. PURGE file-name [ , file-name ] ... file-name is the name of a disk file to be deleted. Peruse expands a partial file name by adding the current default names for system, volume, and subvolume. Multiple file-name parameters can be specified, separated by commas.
Peruse REPORT Command 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.
Peruse SHOWGROUP Command 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.
Peruse SHOWGROUP Command 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.
Peruse SJFILES Command 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. subvol has the form: [\system.][$volume.][subvolume] If you omit \system, Peruse uses the current default system name. If you omit $volume, Peruse uses the current default volume name.
Peruse STARTCOL Command 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 Peruse is first run, the value for STARTCOL is 1. STARTCOL can be used with NUMCOL to list only a few columns of a job.
Peruse STATUS Command STATUS Command The STATUS command displays the status of all available jobs each time the state of any of the jobs changes. A C in front of a status line means that the state of that job has changed since the last status display. S[TATUS] [ delay ] delay is the number of seconds to wait between each status check. The range of values permitted for this argument is 2 through 32767. When no delay is specified, Peruse waits 10 seconds between status checks.
Peruse STATUS Command The status of a job has changed: job 639 has completed spooling and now has a page count. The terminal beeps and Peruse displays the status information. The C indicates that this job has changed status since the last display. JOB 633 JC639 BATCH STATE PAGES COPIES PRI HOLD LOCATION REPORT READY 7 1 4 #LP PAYROLL READY 5 1 4 #HOLD PAYROLL Job 633 is ahead of job 639 in the printer queue and job 633 now begins printing.
Peruse UNLINK Command UNLINK Command The UNLINK command unlinks the specified job from the current batch job. UNLINK job-number job-number specifies the job to be unlinked from the current batch job.
Peruse VOLUME Command VOLUME Command The VOLUME command changes the current default volume or subvolume names, or both, used with Peruse. The initial default names are the subvolume and volume names that were the current default names when you started Peruse. VOLUME [ [\system.]$volume.subvol ] [ $volume ] [ subvol ] \system sets the current default system name for Peruse. You can set the default system name only in a named system, such as one in a network.
4 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 4-2 Spoolcom Security on page 4-2 Running Spoolcom on page 4-2 Spoolcom Commands on page 4-5 Information on how to use Spoolcom interactively and noninteractively is described in the Guardian User’s Guide.
Spoolcom Spoolcom Features 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 Other operations performed using Spoolcom can effect the entire spooler subsystem.
Spoolcom Running Spoolcom Noninteractively The file can be an EDIT file, unstructured file, a relative file, an entry-sequenced file, a spooler job file, a process, or a device. supervisor is the name of the spooler supervisor with which Spoolcom communicates. If supervisor is omitted, then Spoolcom assumes $SPLS is the supervisor. If you want to communicate with a remote supervisor, you should use the network form of the supervisor process name (for example, \FAR.
Spoolcom Entering Spoolcom Commands Entering Spoolcom Commands A Spoolcom command consists of a command word sometimes accompanied by a parameter; it can be followed by one or more subcommands. The command and its parameter are separated from the subcommands by commas. Subcommands are also separated from each other by commas.
Spoolcom Spoolcom Commands Spoolcom Commands A Spoolcom command summary describing the features available to all users is given in Table 4-1. Table 4-1. Spoolcom Command Summary for All Users 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 Spoolcom Commands Table 4-2 is a Spoolcom command summary describing the features available only to authorized users. Note the differing functions of these commands, depending on the authorization of the user. Table 4-2. Spoolcom Command Summary for Authorized Users Command Function BATCH Specifies attributes, obtains status, and changes the state of any batch job in the spooler subsystem. COLLECT Specifies attributes, obtains status, and changes the state of collectors.
Spoolcom BATCH Command 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.
Spoolcom BATCH Command 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. LINK job-number causes the job specified by job-number to become linked to the current batch job if the key attributes of the specified job match those of the batch job. LOC [ #location ] specifies a new location for the batch job.
Spoolcom BATCH Command 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). 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 batch job attributes.
Spoolcom BATCH Command Examples 1. This three-step example requires authorized access. It shows two jobs associated with batch 233: job 7 is the log file, and job 9 has been linked to the log file by the same batch number. )JOB JOB 1 6 7 9 ) BATCH STA RDY RDY 233 RDY 233 RDY FLAGS 4 4 4 4 OWNER 1,28 1,44 1,32 1,32 TIME 11/22 11/16 11/16 11/16 COPY 1 1 1 1 PAGE 7 1 28 100 REPORT DEV JAN MNL BOB ADMN SUE ADMN SUE LOCATION #S.PRTR #SAUR #LOG #LOG 2.
Spoolcom BATCH Command JOB: 7 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: 9 STATE: READY . . . .
Spoolcom COLLECT Command 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 User’s 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.
Spoolcom COLLECT Command 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.
Spoolcom COLLECT Command OUT file-name indicates where Spoolcom is to write the collector status. If not specified, the status is written to the Spoolcom OUT file (usually the home terminal). 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).
Spoolcom COLLECT Command File space usage efficiency is affected by the UNIT size setting if it is significantly larger than the average job size. Since the collector file is not limited by the number of units and UNIT allocation is very efficient, it is recommended that UNIT be set to 4 unless jobs average much less than 4K. The collector uses both the collection file buffer size and its UNIT size to establish the size of the buffers it uses in job collection for each opener.
Spoolcom COLLECT Command 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 4-4 describes the COLLECT STATUS display entries. Table 4-4. 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.
Spoolcom COLLECT Command 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.
Spoolcom COLLECT Command 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.
Spoolcom COMMENT Command COMMENT Command The COMMENT command is used to insert explanatory material, which is ignored by Spoolcom, into a Spoolcom command file. It is often used in command files (sometimes called OBEY files) to explain the purpose of the file and what the commands in it do. Command files are often used as an easy-to-execute and uniform procedure for starting the spooler. COMMENT [ any-text ] any-text is text that is ignored by Spoolcom.
Spoolcom DEV Command 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 User’s Guide for a description of these tasks as well as information on device states and default attributes.
Spoolcom DEV Command 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.
Spoolcom DEV Command 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.
Spoolcom DEV Command 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.
Spoolcom DEV Command 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. HEADER BATCH specifies that two header pages and three trailer pages (also containing job information) print for every job. This enables jobs printed on accordion-fold paper to have a header page appearing on top regardless of whether the job begins on an odd or even page.
Spoolcom DEV Command 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. If no option is specified or if LT132 is specified, FASTP places the EOL sequence at the end of the print record if the byte length is less than 132. This is the default placement.
Spoolcom DEV Command 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).
Spoolcom DEV Command <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.
Spoolcom DEV Command 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 4-5. 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.
Spoolcom DEV Command 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. If STARTFF or STARTFF ON is specified, FASTP issues a form feed at the beginning of each job. This form feed is suppressed if the paper is at top-ofform or if the job started with a form feed, thereby preventing extra blank pages.
Spoolcom DEV Command SUSPEND causes the device to suspend printing of the job currently printing. The same job resumes printing when the device is restarted with the START subcommand. TIMEOUT number-of-retries specifies the number of times a print process retries a retryable I/O operation that has failed. The value for number-of-retries can be either in the range 1 through 32767, or equal to -1 (-1 means the print process retries a retryable operation indefinitely). The default value is 360.
Spoolcom DEV Command 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. TRUNC or TRUNC ON causes the print process to discard the ends of spooled lines that are longer than the device width. TRUNC OFF (the default) causes the print process to print on the next sequential line the ends of any spooled lines that are longer than the device width.
Spoolcom DEV Command Table 4-6.
Spoolcom DEV Command Considerations The device name uses an internal filename format. The device name can only be up to 32 bytes. Therefore, any device with an eight character remote volume name cannot be configured for use with DEV command. If neither $device nor subcommand is specified, Spoolcom displays the status of all devices. Any user can obtain the status of a device. The SKIP and SKIPTO subcommands can be executed by the owner of the job currently printing on the device.
Spoolcom DEV Command Do not configure a printer 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. The EXCLUSIVE OFF! attribute causes the device to be closed and opened between printing the font job and printing the subsequent print job, thereby terminating the effects of the font job. Configure a device in this situation with either EXCLUSIVE ON or EXCLUSIVE OFF.
Spoolcom DEV Command DEV STATUS Display The STATUS subcommand produces a display with the following headings: DEVICE STATE FLAGS PROC FORM Table 4-7 describes the DEV STATUS display entries. Table 4-7. 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.
Spoolcom DEV Command Table 4-7. 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 FLAGS H PROC $SPLA FORM JOB LOCATION 2482 #LOC1.DEFAULT DEVICE $DEV1 SEQ 1 COPY 1 PAGE 3 2486 #LOC1.
Spoolcom DEV Command 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.
Spoolcom DEV Command 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.
Spoolcom DEV Command Table 4-8. 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.
Spoolcom EXIT Command EXIT Command The EXIT command terminates an interactive Spoolcom session. EXIT Example 1.
Spoolcom FC Command 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.
Spoolcom FONT Command 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.
Spoolcom FONT Command (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.
Spoolcom FONT Command 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.
Spoolcom FONT Command 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.
Spoolcom FONT Command Considerations for Authorized Users Only authorized users can define a special control job (font-name) in the spooler. The special control job might consist of downloadable VFC commands or possibly a special header page. 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.
Spoolcom HELP Command 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.
Spoolcom JOB Command 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 User’s 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.
Spoolcom JOB Command 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.
Spoolcom JOB Command 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. DELETE [ ! ] deletes a job from the spooler.
Spoolcom JOB Command 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. REPORT [ report-name ] changes the report name for the job. A job must be in the hold state before its report name can be changed. A report-name is composed of as many as 16 letters, numbers, and blanks, and it must begin with a letter.
Spoolcom JOB Command Table 4-9. Job States During Which JOB Subcommands Can Be Used Job State JOB Subcommand HOLD (H) PRINT (P) READY (R) COPIES H DELETE H FORM H HOLD OPEN (O) P R H P R HOLDAFTER H P R O LOC H OWNER H REPORT H SELPRI H START H STATUS H P R O Considerations If job-number, qualifiers, or subcommand is not specified, then Spoolcom displays the status of all jobs.
Spoolcom JOB Command Table 4-10. JOB STATUS Display Entries (page 2 of 2) Entry Description FLAGS is any or all of the following: 0-7 Job selection priority. A Hold after on. B Hold on (but job is still open). X Job is bad (examples: TGAL abended while spooling the job, or the job was spooled at level 3, but the collector process was closed before calling SPOOLEND). OWNER Is the job owner in the form group-number,user-number.
Spoolcom JOB Command Detailed Status of a Single Job Table 4-12 describes the JOB STATUS display entries when the detailed status for a single job is requested. Table 4-12. JOB STATUS Display Entries—Detailed Single Job Status Entry Description JOB Is the job number. STATE Is the state of the job. LOCATION Is the location assigned to the job. FORM Is the form name, if any. REPORT Is the report name, if any. HOLD BEFORE PRINT Is yes or no. HOLD AFTER PRINT Is yes or no.
Spoolcom JOB Command Examples for All Users 1. You can enter Peruse to find the job number of your spooled job, or you can use this Spoolcom equivalent: )JOB (DATE FROM 10:00 THRU 11:00, OWNER) The following information is displayed: JOB BATCH STA FLAGS OWNER TIME COPY PAGE REPORT LOCATION 3000 RDY 4 4,19 10:18 1 3 COMMSW RJ #LOC1 2.
Spoolcom JOB Command The following information is displayed: JOB: 3000 STATE: READY LOCATION: #LOC1 FORM: REPORT: COMMSW RJ HOLD BEFORE PRINT: NO HOLD AFTER PRINT: NO ABNORMAL: NO SELECTION PRIORITY: 4 PAGE SIZE: 60 CREATOR ACCESS ID: 4, 19 COPIES: 1 PAGES: 3 TOTAL LINES: 169 OPEN TIME: 28 MAY 96, 10:23:00 CLOSE TIME: 28 MAY 96, 10:23:18 DATA FILE: $KIRK.TESTLIM.CD1 COLLECTED BY: $COL1 UNITS ALLOCATED: 2 BATCH ID: BATCH NAME: MAXIMUM LINES: MAXIMUM PAGES: 4.
Spoolcom JOB Command 6. The * pattern-matching symbol used in the following REPORT subcommand selects these jobs.
Spoolcom LOC Command LOC Command The LOC command defines and modifies the spooler routing structure. Refer to Section 2 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).
Spoolcom LOC Command 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.
Spoolcom LOC Command 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.
Spoolcom LOC Command Table 4-13 describes the LOC STATUS display entries. Table 4-13. 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.
Spoolcom OPEN Command 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.
Spoolcom PRINT Command 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 4-67 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.
Spoolcom PRINT Command 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 4-65 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.
Spoolcom PRINT Command (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. XREF [ / OUT filename / ] produces a cross-reference listing of print processes, devices, and locations, ordered by print process. If a print process is not specified, a complete crossreference is produced. (This more time than any other XREF command.
Spoolcom PRINT Command 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.
Spoolcom PRINT Command PRINT STATUS Display The STATUS subcommand produces a display with the following headings: PRINT STATE FLAGS CPU PRI Table 4-14 describes the PRINT STATUS display entries. Table 4-14. PRINT STATUS Display Entries (Without DETAIL Option) Entry Description PRINT Is the name of the print process whose status is being given. STATE Is the state of the print process. STATE can be one the following: FLAGS ACTIVE The print process is running.
Spoolcom PRINT Command Table 4-15. 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 4-14 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.
Spoolcom PRINT Command 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.
Spoolcom SPOOLER Command 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.
Spoolcom SPOOLER Command 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 4-72. STATUS [ / OUT filename / ] [ DETAIL ] displays the status of the spooler subsystem. See SPOOLER STATUS Display on page 4-74. OUT filename indicates where Spoolcom is to write the status information.
Spoolcom SPOOLER Command SPOOLER STATISTICS Display You can use the STATISTICS subcommand to access additional spooler statistics. Much of the data is assembled after the report is requested. Because preparation of the report takes precedence over other spooler requests, using it often can affect spooler performance.
Spoolcom SPOOLER Command Table 4-16. SPOOLER STATISTICS Display Entries (page 2 of 2) 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 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.
Spoolcom SPOOLER Command SPOOLER STATUS Display The STATUS subcommand produces a display with the following headings: SPOOLER STATE LOGGING FILE LAST ERROR Table 4-17 describes the SPOOLER STATUS display entries. Table 4-17. SPOOLER STATUS Display Entries Entry Description SPOOLER Is the process name of the spooler. STATE Is the state of the spooler (active, drain, warm, or cold). Spoolcom cannot communicate with a dormant spooler.
Spoolcom SPOOLER Command 2.
Spoolcom SPOOLER Command Spooler Utilities Reference Manual—522295-003 4-76
5 Font Utility The Font utility program helps you create font jobs within the Tandem 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.
Font Utility How the Font Utility Works 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 5-1. Figure 5-1.
Font Utility Running the 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 5-5 for the requirements of the file. The IN script-file parameter is actually a run option.
Font Utility Running the 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. 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.
Font Utility Script File Syntax 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.
Font Utility General Syntax Rules for Script File Directives 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 Utility FONT Directive 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.
Font Utility Normal Font Data %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.
Font Utility CONTROL Directive 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.
Font Utility CONTROLBUF Directive ; 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.
Font Utility CONTROLBUF Directive Example of User-Character Translation (CONTROLBUF 101) The following example provides a translation table through a CONTROLBUF 101 directive to instruct FASTP to replace some nonprintable characters with spaces. This 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.
Font Utility CONTROLBUF Directive ! Draw page dividers %33,"&a67r0C" ! Posn to row 67 col 0 %33,"*c3389a1b25g2P" ! Draw line 3389 dots x 1 dot ! x 25% %33,"*p0Y",%33,"&a133C" ! Posn to dot 0 col 133 %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 m
Font Utility SETMODE Directive "This "This "This "This is is is is font font font font "#LASER RED job data for pink job data for pink job data for pink job data for pink "; and and and and red red red red jobs" jobs" jobs" jobs" ?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.
Font Utility SOURCE Directive 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.
Font Utility START-LOCATIONS and END-LOCATIONS Directives 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.
Font Utility Comments in the Script File Comments in the Script File Comments can appear anywhere in the script file and are ignored by the Font utility.
Font Utility Script File Example 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.
Font Utility Script File Example Spooler Utilities Reference Manual—522295-003 5-18
6 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.
RPSetup Utility How the RPSetup Utility Works How the RPSetup Utility Works When RPSetup runs, it reads configuration information from the remote spooler supervisor, analyses the information, and writes new configuration information to the local spooler supervisor. RPSetup sets up connections to all valid locations on the remote node. To create these connections, RPSetup creates locations on the local spooler with the same names as locations on the remote node.
RPSetup Utility Interspooler Threads 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.
RPSetup Utility Interspooler Threads Figure 6-2. Interspooler Threads \APPL Application Application Application Spooler Subsystem Collector Collector Data 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.
RPSetup Utility Interspooler Threads The numbers in Figure 6-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.
RPSetup Utility Running RPSetup 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).
RPSetup Utility Requirements for Running RPSetup 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 6-13.
RPSetup Utility Example 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.
RPSetup Utility Default Configuration Table 6-1.
RPSetup Utility Default Configuration Table 6-1.
RPSetup Utility ASSIGN and PARAM Commands ASSIGN and PARAM Commands The syntax for the commands listed in Table 6-1 is described in the following subsections. ASSIGN PRINTFILE The ASSIGN PRINTFILE command specifies the Guardian file name of the program file for the print process controlling the interspooler thread. This configuration parameter applies individually to all interspooler threads.
RPSetup Utility ASSIGN and PARAM Commands OFF! specifies that the device is to be closed between jobs. PARAM DEVFIFO The PARAM DEVFIFO command specifies the algorithm by which jobs are selected for printing on this device. This configuration parameter applies individually to all interspooler threads. The command is equivalent to the SPOOLCOM command DEV FIFO. PARAM DEVFIFO { ON | OFF } ON specifies first-in, first-out (FIFO) queuing.
RPSetup Utility ASSIGN and PARAM Commands an odd or even page. Printing over the page folds on the trailer pages enables jobs to be easily separated from each other. PARAM DEVPARM The PARAM DEVPARM command specifies a device parameter that is passed to the print process controlling this device whenever the supervisor communicates with the print process. This configuration parameter applies individually to all interspooler threads. The command is equivalent to the SPOOLCOM command DEV PARM.
RPSetup Utility ASSIGN and PARAM Commands Table 6-2. Default Attributes Set by FASTP on Interspooler Transferred Print Jobs (page 2 of 2) Bit Value Attribute of Transferred Print Jobs FASTP’s Default Operation < 12 > 0 Omits any HOLDAFTER flag for a job transferred to target spooler Same as < 11 >.
RPSetup Utility ASSIGN and PARAM Commands PARAM DEVWIDTH The PARAM DEVWIDTH command configures the maximum line length for the device. This configuration parameter applies individually to all interspooler threads. The command is equivalent to the SPOOLCOM command DEV WIDTH. PARAM DEVWIDTH device-width device-width specifies the maximum line length for the device. The range of values is 0 through 32676; -1 is also valid.
RPSetup Utility ASSIGN and PARAM Commands PARAM PRINTNAME The PARAM PRINTNAME command sets the process name of the print process that controls the interspooler thread. This configuration parameter applies individually to all interspooler threads. This command is equivalent to the SPOOLCOM command PRINT $process-name. PARAM PRINTNAME $process-name $process-name is the process name (in local form) of the print process.
RPSetup Utility ASSIGN and PARAM Commands PARAM THREADNAME The PARAM THREADNAME command sets the generic portion of the device name for an interspooler thread. This configuration parameter applies individually to all interspooler threads. You can use the command to override the entire DEV name, specified through the Spoolcom DEV command, including the remote collector name. You can also use this parameter to override the #qualifier.name portion only. PARAM THREADNAME name name is a device name.
RPSetup Utility ASSIGN and PARAM Commands Spooler Utilities Reference Manual—522295-003 6-18
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[.
SPOOL Program Running the 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.
SPOOL Program Running the SPOOL Program num-of-print-processes is the maximum number of print processes that will be declared for this spooler. The range is 1 through 45. 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 255. 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 4095. The default is 256.
SPOOL Program EMS Collector DEFINE If a recovery from control-file corruption is to be done during a SPOOL REBUILD operation, the coldstart parameters specified in the command string must be the same as those values that were specified when the spooler was coldstarted. Examples 1.
B Peruse Messages This appendix describes the Peruse error messages that are displayed on your terminal. For additional information on Peruse, see Section 3, 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. For corrective action of the file-system error number, see the Guardian Procedure Errors and Messages Manual.
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. For corrective action of the file-system error number, see the Guardian Procedure Errors and Messages Manual. CAN'T SPOOLSTART 'OUT' FILE: number Cause. SPOOLSTART failed for the OUT file of a LIST command. number specifies the spooler error number.
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. For corrective action of the file-system error number, see the Guardian Procedure Errors and Messages Manual. 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 'OUT' FILE MUST BE PROCESS OR SPOOLER JOB FILE Cause. SPOOL or COMPRESS was specified in a LIST command, and the OUT file was not a process or a spooler job file. Effect. The command is not executed. Recovery. Specify a process or a spooler job file as the OUT file, and then retry the command. 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.
Peruse Messages Effect. Peruse ignores this command. Recovery. Reenter the command, specifying a report-name that contains only letters, digits, and spaces.
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.
Peruse Messages Spooler Utilities Reference Manual—522295-003 B-12
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 4, 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 4, 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 NOT OPEN Cause. A command was issued before the spooler was opened. Effect. Spoolcom ignores the command. Recovery. Open the spooler before issuing another Spoolcom command. 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.
Spoolcom Messages WARNING: USERID NOT DEFINED Cause. Either the user ID was not recognized on the system or network or $SYSTEM.SYSTEM.USERID cannot be accessed. Effect. Spoolcom executes the command. Recovery. Specify a valid user ID.
Spoolcom Messages Spooler Utilities Reference Manual—522295-003 C-10
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 Utilities Reference Manual—522295-003 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 Effect. The RPSetup utility aborts. Any configuration changes made up to this point remain. 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.
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 Utilities Reference Manual—522295-003 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.
Using FASTP Tracing FASTP The FASTP print process supports CONTROLBUF 101, 103, and 113 calls in font jobs as described with the CONTROLBUF directive described in Section 5, 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.
Using FASTP Specifying Trace Files for a Device 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.
Using FASTP Reading Trace Output 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.
Using FASTP Extended Configuration With FASTCNFG 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.
Using FASTP Creation 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.
Using FASTP Alteration 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.
Using FASTP Syntax 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 ]...
Using FASTP Syntax 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. For example: !This is legal DELAY=999 !This is legal DELAY = 999 Starting Position Relative to the Beginning of a Line Keywords and attributes can begin in any position on a line. For example: !This is legal DELAY=999 Keywords There are three keywords: SPOOLER PROCESS DEVICE SPOOLER [\node.
Using FASTP FASTCNFG File Redirection with one product-specific version of a FASTP print process. Device attributes are described in the product-specific sections of this manual. The next example shows a device keyword and keyword value (DEVICE $PRT) followed by two pairs of attributes and attribute values (CONTYPE = NONE). DEVICE $PRT CONTYPE = NONE The LAN print queue has already been configured with SPOOLCOM and has been assigned the name $PRT.
Using FASTP FASTCNFG File Redirection The syntax for specifying a subordinate FASTCNFG file for one print process is as follows: PROCESS [\node.]$process-name FASTCNFG = [\node.][$volume.][subvolume.]file-ID Level-1 FASTCNFG File Syntax In a level-1 FASTCNFG file you can: Redirect FASTP in a spooler subsystem to a subordinate FASTCNFG file (this FASTCNFG file would be a level-2 file): SPOOLER [\node.]$supervisor-name FASTCNFG = [\node.][$volume.][subvolume.
Using FASTP EOLWRITE 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. ERRORRECOVERY FASTP normally recovers from nonfatal errors during printing by restarting the entire job output. ERRORRECOVERY = YES | NO YES forces FASTP to recover from non-fatal errors by simply reissuing the last input/output (I/O) request.
G Spooler Limits This appendix describes the programmatic limits of the Spooler and Spooler Plus subsystem components. Table G-1.
Spooler Limits Spooler Utilities Reference Manual—522295-003 G-2
H Migration Considerations for Pre-D41 Spooler Versions The D41, D46, and D48 releases of the Spooler subsystem present many enhancements and new features to support improved operational management. This appendix describes D-series system interoperability considerations and explains the major enhancements and changes in the D41, D46, and D48 release of the Spooler subsystem. For information on new enhancements for D46 and D48, see Extended Memory Changes for D46 and D48 Versions of the Spooler on page H-12.
Migration Considerations for Pre-D41 Spooler Versions New Control File New Control File A new format SPL3 file is introduced in the D46 and later D41 (ADI, ADM, and later) product versions of Spooler. The current Spooler product versions no longer use the SPL4 control file. In the SPL3 file, all information for jobs, batches, names, and attributes of other Spooler objects are integrated and retained in data structures.
Migration Considerations for Pre-D41 Spooler Versions Migrating Files From a Pre-D41 Product Version of Spooler 7. Start the spooler: )SPOOLER,START 8. Use PERUSE and SPOOLCOM to manage jobs still residing in the pre-D41 collector files as well as the jobs being added to the new collector files. D41 spooler Peruse commands have remained the same and can be run against jobs resident in old or new format collector files.
D41,D46, D48 Common Enhancements and Changes Migration Considerations for Pre-D41 Spooler Versions D41,D46, D48 Common Enhancements and Changes Compared to older product versions of the Spooler subsystem, the D41 release of the Spooler subsystem includes the following enhancements and changes; these enhancements and changes are included in the D46 and D48 versions of the Spooler: Increased object and resource limits New collector file requirements New collector data file re
Migration Considerations for Pre-D41 Spooler Versions New Collector Data File Capacity Requirements Although older versions of spooler collection files are used to access jobs present at the time of the warmstart, new jobs cannot be collected onto these files. New Collector Data File Capacity Requirements The number of units in a new collection file is no longer constrained by the spooler. Instead, it is limited solely by the amount of space allocated on the disk.
Migration Considerations for Pre-D41 Spooler Versions D48 New Product Version of Spooler the DP2 BUFFERSIZE to 4096 or to the minimum value that can contain the average size job collected. A collector configuration is valid only if the unit size is a whole multiple of BUFFERSIZE. BUFFERSIZE must be at least 2 K bytes or a multiple of 2 K bytes.This is illustrated in Table H-2. Table H-2.
Migration Considerations for Pre-D41 Spooler Versions More Collector Openers for Each Collector When all jobs in an older-version collector file have been deleted or moved, the file is no longer needed by the spooler. Older-version collector files used in this way are not altered in any way by the D41 spooler. JOB DELETE and MOVE operations are processed by deleting or altering the job information retained by the supervisor.
Migration Considerations for Pre-D41 Spooler Versions Changes to Spoolcom Commands COLLECT STATUS Command Display The PERCENT FULL and %FULL values reported by the COLLECT STATUS command are now accurate to within plus or minus one percent. Previously, the values retained in the supervisor for reporting were updated only at times when the collector completed a job or started a new job. Now, any time a value changes by 0.
Changes to Spoolcom Commands Migration Considerations for Pre-D41 Spooler Versions Example H-1.
Migration Considerations for Pre-D41 Spooler Versions Changes to Spooler Library Procedures and Structures All job parameters are retained and the job is rapidly recollected into the new collector data file. For the COLLECT subcommand to function on a job, the job must be in the HOLD state. If the job has a current, active collector, it is deleted from the current collector after the transfer has completed successfully.
Migration Considerations for Pre-D41 Spooler Versions Unsupported Procedures The following three system library spooling procedures are no longer applicable for access to jobs that reside in the D41 product version of Spooler (first available in the D44 and G03 system releases): PRINTCOMPLETE PRINTSTART SPOOLEREQUEST These three procedures can continue to be used, however, if the application accesses jobs only in the form of filecode 129 job files.
Migration Considerations for Pre-D41 Spooler Versions Increased Extended Memory Increased Extended Memory The spooler supervisor process now uses approximately 30 megabytes (Mbytes) of flat extended segment space. Each spooler collector process now uses from 2 to 5 Mbytes of flat extended segment space depending on the buffer size used. The collector attempts to match the DP2 BUFFERSIZE.
Migration Considerations for Pre-D41 Spooler Versions Reduced Support for PSPOOL and PSPOOLB Print Processes Reduced Support for PSPOOL and PSPOOLB Print Processes FASTP and the available value-added products for specific network printing (TCP/IP LAN Print and LAN Print for Netware, for example) are now the only print processes documented and fully supported. However, D41 versions of PSPOOL and PSPOOLB are provided to minimize migration impact.
Extended Memory Changes for D46 and D48 Versions of the Spooler Migration Considerations for Pre-D41 Spooler Versions D46 and D48 Spooler memory usage for internal tables: Spooler Supervisor Memory usage for its major tables = STRUCT JOB^STRUCT + STRUCT DEV^STRUCT 297 bytes 112 bytes * MAX number of jobs * MAX number of devices + STRUCT CDEV^STRUCT 62 bytes * MAX number of devices + STRUCT COL^STRUCT 132 bytes * MAX number of collectors + STRUCT CCOL^STRUCT 136 bytes * MAX number of collectors
Extended Memory Changes for D46 and D48 Versions of the Spooler Migration Considerations for Pre-D41 Spooler Versions Spooler Maximum: 32K queue nodes, 1 collector: 2 Supervisors 5435526 (5.4 Mb) 2 Collectors 4194304 (4.2 Mb) -------9629830 (10 Mb) Spooler Maximum: default queue nodes, 3 collectors: 2 Supervisors 10351426 (10 Mb) 6 Collectors 31457280 (31 Mb) --------42160132 (42.2 Mb) Spooler Plus Maximum: default queue nodes, 3 collectors: 2 Supervisors 10351426 (10.
Migration Considerations for Pre-D41 Spooler Versions Extended Memory Changes for D46 and D48 Versions of the Spooler Spooler Utilities Reference Manual—522295-003 H-16
Index Numbers BREAK key, while PERUSE is listing a job 3-35 BROADCAST subcommand SPOOLCOM LOC command 4-58 Busy state (device), explained 4-35 129 files See Spooler job files A Active state (collector), explained 4-16 Active state (spooler), explained 4-67 ALIGN subcommand, SPOOLCOM DEV command 4-20 ALL option PERUSE HELP command 3-23 PERUSE LIST command 3-34 Archiving example 3-36 ASCII compression example 3-37 ASSIGN PRINTFILE command (RPSETUP) 6-11 Authorization FONT utility 5-4 B Backing up all file
Index D CONTROL directive (FONT utility) 5-9 Control file name SPOOL program A-1 Control file, new for D41 and D46 H-2 CONTROLBUF directive (FONT utility) 5-9/5-12 COPIES command (PERUSE) 3-12 COPIES subcommand SPOOLCOM BATCH command 4-7 SPOOLCOM JOB command 4-50 CPU subcommand SPOOLCOM COLLECT command 4-12 SPOOLCOM PRINT command 4-63 CPU subcommand, SPOOLCOM COLLECT 2-5 Cross-connected spoolers 6-1 D Data file, collector 4-12, 4-14 Data stream compatibility (DSC) mode 4-22 DATA subcommand SPOOLCOM COLLE
Index E Drain state (collector), explained 4-16 DRAIN subcommand 1-10 SPOOLCOM COLLECT command 4-13 SPOOLCOM DEV command 4-22 SPOOLCOM SPOOLER command 4-70 Draining the spooler 1-9 DUMP subcommand SPOOLCOM SPOOLER command 4-70 D-series system and the SPOOLCOM command 4-3 E ENDFF subcommand, SPOOLCOM DEV command 4-22 END-FONT directive 5-6 END-LOCATIONS directive 5-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-9 Error s
Index G FONT utility 5-1/5-17 CONTROL directive 5-9 CONTROLBUF directive 5-9/5-12 END-FONT directive 5-6 END-LOCATIONS directive 5-15 error messages D-1/D-21 FONT directive 5-7 normal data 5-7/5-8 SETMODE directive 5-13 SOURCE directive 5-14 START-FONT directive 5-6 START-LOCATIONS directive 5-15 FORM command (PERUSE) 3-21/3-22 Form name device 2-12 job 2-10 FORM subcommand SPOOLCOM BATCH command 4-7 SPOOLCOM DEV command 4-23 SPOOLCOM FONT command 4-43 SPOOLCOM JOB command 4-49, 4-50 Function keys, displa
Index K Job (continued) altering number of columns (PERUSE) 3-39 altering number of copies (PERUSE) 3-12 altering owner of PERUSE 3-41 SPOOLCOM 4-51 altering queue priority PERUSE 3-44 SPOOLCOM 4-51 altering report name PERUSE 3-46 SPOOLCOM 4-51 altering status of (SPOOLCOM) 4-48/4-57 attributes 2-9/2-10 batch number 2-9 copies 2-10 deleting from spooler PERUSE 3-13 SPOOLCOM 4-50 described 2-9/2-10 displaying a line of (PERUSE) 3-19 displaying pages of (PERUSE) 3-8, 3-33 displaying status of PERUSE 3-28,
Index M LOC subcommand SPOOLCOM BATCH command 4-8 SPOOLCOM FONT command 4-43 SPOOLCOM JOB command 4-49, 4-50 Local spooler, RPSETUP 6-6 Location 2-10, 2-15/2-17 altering PERUSE 3-38 SPOOLCOM 4-50 sending process output to 2-17 Locations section 5-15 Locations, number of A-2 Log file name SPOOL program A-1 LUEOLVALUE subcommand, SPOOLCOM DEV command 4-24 LUEOLWHEN subcommand, SPOOLCOM DEV command 4-25 LUTOFVALUE subcommand, SPOOLCOM DEV command 4-25 M Manager access See Group manager access MBCS 4-20 Memo
Index P PARAM DEVRESTART command (RPSETUP) 6-14 PARAM DEVTRUNC command (RPSETUP) 6-14 PARAM DEVWIDTH command (RPSETUP) 6-15 PARAM NUMTHREADS command (RPSETUP) 6-15 PARAM PRICPU command (RPSETUP) 6-15 PARAM PRINTNAME command (RPSETUP) 6-16 PARAM PRINTPARM command (RPSETUP) 6-16 PARAM PRIORITY command (RPSETUP) 6-16 PARAM THREADNAME command (RPSETUP) 6-17 Parameters, configuring with RPSETUP 6-8/6-17 PARM subcommand SPOOLCOM DEV command 4-25/4-27 SPOOLCOM PRINT command 4-64 Pattern matching, SPOOLCOM REPORT
Index Q Print process, interspooler threads assigning backup CPU 6-11 assigning priority 6-16 assigning process name 6-16 assigning program file 6-11 assigning startup message 6-16 default operations 6-13 Print process, spooler changing attributes of (SPOOLCOM) 4-65 changing status of (SPOOLCOM) 4-63/4-69 independent 4-64 obtaining status of (SPOOLCOM) 4-63/4-69 specifying attributes of (SPOOLCOM) 4-63/4-69 specifying the program 4-64 states 4-67 user-written 4-64 Printer device types 4-21/4-22 Printer, l
Index S S Script file comments 5-16 example 5-17 syntax 5-5/5-17 Security FONT utility 5-4 RPSETUP utility 6-7 spooler and individual users 2-22 SELPRI subcommand SPOOLCOM BATCH command 4-8 SPOOLCOM JOB command 4-51 SETMODE directive (FONT utility) 5-13 SHOWGROUP command (PERUSE) 3-47/3-48 SJFILES command (PERUSE) 3-49 SKIP subcommand, SPOOLCOM DEV command 4-28 SKIPTO subcommand, SPOOLCOM DEV command 4-28 SNA character string (SCS) mode 4-22 SOURCE directive (FONT utility) 5-14 SPEED subcommand, SPOOLCOM
Index T START subcommand (continued) SPOOLCOM DEV command 4-28 SPOOLCOM JOB command 4-51 SPOOLCOM PRINT command 4-64 SPOOLCOM SPOOLER command 4-70 STARTCOL command (PERUSE) 3-50 affects line displayed FIND command 3-20 LIST command 3-35 STARTFF subcommand, SPOOLCOM DEV command 4-29 Starting the spooler SPOOL program A-1 START-FONT directive 5-6 START-LOCATIONS directive 5-15 STATE subcommand SPOOLCOM FONT command 4-44 SPOOLCOM JOB command 4-49 States of spooler components collector 4-16 device 4-31 job 4-
Index W W Waiting state (device), explained 4-35 Warmstarting the spooler SPOOL program A-3 Warmstart, definition of 1-8 WIDTH subcommand SPOOLCOM DEV command 4-31 X XREF subcommand SPOOLCOM DEV command 4-31 SPOOLCOM PRINT command 4-65 Special Characters $SPLS (default spooler supervisor) 3-3, 3-40, 4-2, 4-62, 5-3, A-1 $SYSTEM.SYSTEM.CSPOOL 2-5, 4-13, 4-18 $SYSTEM.SYSTEM.
