
CONVERGENT TECHNOLOGIES

RELEASE NOTICE FOR
2.1 Generic Print System (SAA1400)

Preliminary, Revised, July 16, 1987

SECTION   TITLE	PAGE
	Introduction	3
1.0	Description of Programs	4
2.0	Changes from Prior Version	8
2.1	Problems Closed in this Release	8
2.2	Changes from Release 2.0	11
3.0	Contents of Distribution Diskettes	19
4.0	Installation Procedures	24
4.1	Installing GPS from the Installation Diskettes	27
4.1.1	StandAlone Hard Disk Systems	28
4.1.2	Master Hard Disk Systems	30
4.1.3	Cluster Workstations	30
4.2	Installing GPS on a Workstation from the Master	31
4.3	StandAlone Floppy Disk Systems	32
4.4	Installing the Font Service	32
4.5	GPS Service Installation on the SRP 	33
4.6	Configuring the Context Manager	34
5.0	Required Files	35
6.0	System Software Compatibility	38
6.1	Workstation Environment	39
6.2	Diskless Workstations	39
6.3	MegaFrame SRP	39
7.0	Hardware Information	40
7.1	Hardware Configurations Supported	40
7.2	Special Hardware Requirements	40
8.0	Resource Requirements	40
8.1	Memory Requirements	40
8.2	Disk Requirements	41
8.3	CTOS Resource Requirements	42
8.4	Tuning Font Data Memory Usage	43
9.0	Restrictions	47
10.0	Supplementary Information	52
10.1	User File Additions	52
10.2	Use With PreGPS Applications	53
10.3	Devicespecific Fonts and Features	54
10.3.1	Binary Mode Driver	55
10.3.2	Daisy Driver	55
10.3.3	Epson Device Driver	57
10.3.4	HP LaserJet Driver	57
10.3.5	Imagen Device Driver.	60
10.3.6	PostScript Driver.	62
10.3.7	Simple Device Driver.	63
10.4	Configuring PostScript printers	64
11.0	Documentation Updates	65
11.1	Standard Documentation	65
11.2	Changes to Documentation	66
12.0	Status Codes	66
13.0	Known Errors and Omissions.	66

A note regarding the format of this document
This release notice was created with Document Designer 2.0 using the 12 point Times Roman proportional font for the body text and 12 point Courier monospaced font for file names and to display the CTOS Executive commands. This document was formatted for and printed on the Imagen 8300 laser printer.  The editable form of this document is provided on the distribution diskettes and may be located after GPS installation in file <ReleaseNote>gps.relNote.
This document can be easily reformatted and printed on another supported printer (such as a Daisywheel printer) by simply reviewing (Document Designer command CODEf4)  the document with the device type field in the menu set to the correct value for your printer (such as Daisy).  If the selected printer does not have a 12 point Times Roman font, the reviewing process will cause a substitution of a font that is supported.  The file <ReleaseNote>gps.relnote.wp also represents this document, but is formatted for the 10.3 version of the Word Processor.
Introduction
The Generic Printing System (GPS) is a set of related software modules which provide a uniform printing service for application programs executing in the CTOS operating system environment on Convergent workstations and servers.  
GPS provides device independence.  Instead of building printerspecific logic into each application which requires printed output, all printerspecific logic can be built into GPS device drivers.  This enables third parties to add support for additional printers without modification to applications.
Customers who wish to add support for additional printers can obtain the PrintGen package which contains software libraries and source and instructions for developing additional device drivers.
The Generic Print System provides a programming interface, the Generic Print Access Method (GPAM), to applications which wish to utilize GPS printing capabilities.  GPAM provides a library of routines used to describe a print job in terms of page attributes, text placement and attributes, graphic polylines and polygons, etc.  The device driver translates this description into the sequence of operations performed by a particular class of printers.  
GPS provides uniform access to printing resources.  Using GPS, applications can access printers anywhere on a cluster, or within a CTNet network, simply by referencing a unique device name assigned to each printer.
GPS provides backward compatibility with prior printing systems.  The functionality of the preGPS Spooler is supported as a subset of GPS.  Older programs, such as the Word Processor, which directly wrote spool files and interacted with the spooler via the Queue Manager, operate without change.    Some programs, such as the Art Designer, internally support a number of devices for which no specific GPS driver exists, and can nevertheless output to these printers via GPS.  
Programs which have printer dependent code embedded within them must create GPS print jobs in Binary mode or Image mode, which bypass the translation features of the device driver.  Image mode (also called WP mode) jobs contain escape sequences, along with the printerspecific commands, which are used to track page changes and invoke prompts for wheel changes, for example.  These escape sequences, which were processed by the preGPS spooler, are handled by all GPS device drivers.
On the other hand, print jobs which require translation by the device driver into the language of the printer must be printed in ASCII mode (the default for most applications which allow a choice of modes).   Only simple ASCII files or GPAM files (such as those created by the Document Designer Print command), should be printed in ASCII mode.  The device driver automatically recognizes whether a file printed in ASCII mode is a GPAM file.
GPS provides font services.  The range of fonts (typefaces) available on different printers today varies dramatically.  In order to utilize these fonts, applications such as Document Designer, as well as device drivers, need access to information about these fonts, such as individual character widths.  Included in GPS is a usermodifiable Font Database, containing this information, a Font Service providing transparent access to the database for device drivers and applications, and a Font Tool for modifying the database.  The font database also contains a modifiable list of reduction rules which inform applications and device drivers of which font to substitute for those which are missing from individual printers.
1.0	Description of Programs
The Generic Printing System is a set of related software components:
The Print Manager, GpsPm.run, is the user interface to GPS.  The Print Manager is an application program which is used to:
	Configure a GPS installation.
	Submit files to be printed.
	Monitor status of print jobs and print queues.
	Pause, restart or cancel jobs currently being printed.
The Routing Switch, GpsRs.run, is the programmatic interface to GPS.  The Routing Switch serves requests for printing services.  Application requests are served by the nearest Routing Switch (either local to the workstation or at the master), checked for validity, and then forwarded as required to another GPS service for processing.  A Routing Switch must be installed wherever a device driver is installed and must also be installed at the master workstation if GPS devices are to be shared across the cluster or across CTNet.
The Spooler, GpsSp.run, provides simultaneous access to shared devices.  Print jobs directed to spooled devices are forwarded to the GPS Spooler by the Routing Switch.  The GPS Spooler maintains two logical job streams for each device it supports.  The first stream(s) flows from multiple application programs to a storage area on disk, where the data resides until the device is ready to accept it.  The second stream flows from this temporary storage area to the device.  The spooler allows different users to queue their print jobs to the temporary storage area, freeing the workstation to do productive work while waiting for the printing device to become available and print the job.  The spooler also has the capability to resend the job to the printer multiple times, when the printer does not have its own multiple copy capabilities, or when a job needs to be restarted because of a paper jam or a print ribbon failure.  The Spooler is an installed system service that must be installed at the same workstation as a device driver that requires spooled printing.  One Spooler supports all spooled devices installed at that workstation.
The Font Service, FontService.run, is the central repository of font information.  The font service retrieves font data from the font database for use by device drivers and applications such as the Document Designer.  
Device Drivers translate print jobs into the language of a specific printer.  They also enable human interaction in the processing of print jobs, including the ability to monitor, pause, resume or cancel jobs.  GPS provides device drivers for the following seven device classes:
(1)The Daisy wheel printer driver, DaisyDD.run, translates print jobs into a sequence of commands recognized by several popular daisywheel printers, such the Diablo 630, the Qume Sprint 9 and Sprint 11, and the NEC 3515.  The Daisy driver has also been used to support some laser printers which emulate the Diablo 630.  The Daisy driver does not support graphics.
(2)The Imagen driver, Imagen8300DD.run, translates print jobs into the Impress page definition language used by Imagen laser printers.  The Imagen device driver has graphic capabilities and supports the typographic fonts available for Imagen printers.
{The Imagen device driver can print in either portrait or landscape page orientation, and can support manual feed of paper or envelopes through the printer's rear paper feed.  If multiple copies are specified in a print job, the Imagen is instructed to print each page the requested number of times, allowing the printer to run at full speed.}
(3)The HP LaserJet driver, HPLaserJetDD.run, translates print jobs into the PCL language required by the Hewlett Packard LaserJet and LaserJet Plus printers.  The device driver provides support for the replaceable cartridge font feature of the printer.  The LaserJet driver supports graphics and landscape printing.  The LaserJet driver also supports manual feed and paper tray selection for the LaserJet500.  If multiple copies are specified in a print job, the LaserJet is instructed to print each page the requested number of times, allowing the printer to run at full speed.
(4)The PostScript driver, PSDD.run, translates print jobs into the PostScript page description language.  PostScript is a rapidly emerging  standard language for printers, especially laser printers and typesetters.  PostScript provides a high level of graphic and font capabilities to raster printing devices.  The PostScript driver has been qualified on the QMSPS800 and the Texas Instruments 2115.  It is likely to work on other PostScript printers, although the above two are the only ones officially supported by Convergent.  
The PostScript driver supports both portrait and landscape printing of graphics and typographic fonts.  It supports manual feed and multicopy output.  It will emulate either Art Designer or Imagen driver graphic line types.  It also maps colors of solid, halftone and quartertone fill patterns to appropriate gray levels.  The PostScript device driver provides support for the replaceable font cartridges and dual paper bins on the TI 2115.
(5)The Epson FX286 device driver, EpFx286DD.run, translates print jobs into escape sequences required by the Epson FX286 printer.  Various fonts with different pitches are accessible.  This device driver has full graphic capabilities.

NOTE:  There are many different Epson printer models and many other printers that claim Epson compatibility.  Only the FX286 model has been fully tested with this device driver.  Other printers are not guaranteed to work.
(6)The Binary Mode device driver, BinaryModeDD.run. is provided to make a device driver of minimal size (27Kb) available to use with applications which have printerspecific code embedded within them.  The Binary Mode driver prints jobs, which must be created in binary mode or image mode, without translation.  All device drivers support binary or image mode, but the binary mode driver is considerably smaller than other device drivers because it only supports binary or image mode.
(7)The simple device driver, LptSimpleDD.run. is intended to support all of the ordinary monospaced, data processing class printers.  Any printer that can recognize and interpret the ASCII character set and the ASCII control codes line feed (LF), carriage return (CR), and form feed (FF), can be controlled by this driver.
Pipe Drivers also do the work of translating ASCII or GPAM files into the language of a particular printer, but with output directed to a disk file.  There is one pipe driver included corresponding to each of the standard device drivers, except for the binary mode driver, for a total of six.
The Font Tool is used to modify the font database.  The Font Tool is an interactive application program.  Use of the Font Tool is described in the Printing Guide.
{2.0	Changes from Prior Version
The most significant changes in this release of GPS are in device drivers.  However problems have been fixed in several other programs as well.}
All 2.0 Device Drivers are compatible with 2.1 GPS.  Any device driver developed using 2.0 PrintGen can be run under 2.1 GPS without modification.  
To obtain the benefits of device driver bug fixes, speed optimizations and memory reductions, independently developed device drivers should be rebuilt using 2.1 PrintGen.  A minor amount of work (source edits) will be required to rebuild a 2.0based device driver with 2.1 PrintGen.  The resulting driver should be 10Kb to 20Kb smaller than the 2.0based device driver.  Consult the 2.1 PrintGen engineering update for further information.
2.1	Problems Closed in this Release
SPRs10399, 11256:		
The daisy device driver incorrectly assumed that the printer was set to 10 pitch after a reset.  Actually pitch is determined by the printer switches andor wheel that is mounted.
SPRs11012, 11593, 11598:
Installation hung if device driver was installed using a parallel port to which no printer is attached and device driver attempted to output at initialization (in DdInitializeG).
SPR 11587:		Print Manager asked the user whether to continue printing the file list if a print request was canceled from the Print Manager print form, even if the file canceled was the last or only file in the list.
SPR11592:		(Daisy driver)  Lines exceeding maximum page width of the device (when wrapping is not in effect) caused the driver to lose track of the printer head position.  Now all text beyond the addressable region of daisy devices (or other devices) is discarded by the device driver.
SPR11594:		Characters were printed in the wrong font after an overflow of font table memory.  Now the job aborts with an error code (15333) when font data memory overflows.  Reinstall the device driver specifying a larger value for Font Data Table Size.
SPR11596:		(Imagen and HpLaserJet drivers)  Spaces were erroneously underscored using the font of the previous character, rather than the font of the space itself.  This was particularly bothersome when the underlined space followed a superscript or subscript character in a smaller font than the text of the baseline.  Incidentally, if the superscript or subscript is itself underscored, the font of the last baseline character is used for the underscorewhich is correct behavior.
SPR11599:		(All device drivers)  Superscript and subscript characters continued over multiple lines reverted to the baseline.
SPR11627:		(Routing Switch)  A protected mode fault occurred attempting to service print request for the nil device name.  [First fixed in s2.0.1].
SPR11711:		(Font Tool)  Wheel set conversion incorrectly converted upward shifts in overstrike sequences to downward shifts and vice versa.
SPR11742:		(Routing Switch)  When a master was rebooted it would show drivers installed at cluster workstations to be not installed.  [First fixed in s2.0.2].
SPR11786:		(Font Tool installation)  FontDB.sub was missing a line in the command form for running the Font Tool.  This resulted in the creation of an empty editable font database.
SPR11808:		The Binary Mode driver failed with error code 15320 if the Simple device type was not present the font database.  The Binary Mode driver no longer requires the presence of any font device type, and in fact does not require or use the font service at all.
SPRs11868, 11967:		
GPS device installation from sysinit.jcl failed when rebooting a workstation as a cluster station with local file system, after booting that workstation as a standalone workstation.  [First fixed in s2.0.3]
SPR11881:		Routing Switch crashed with erc 22 when the CTOSVM SRP master is rebooted.  [First fixed in s2.0.4].
SPR 11951:		(Imagen device driver)  First character of a line following a line that is underlined was incorrectly positioned if the character fell directly under the last character of the underlined line.
SPR12126:		(Font Tool)  The first field of the Shuffle table form (translate table name) was too short (12 rather than 24 characters) and it was not possible to get to the second field (translates to new order?) at all.
SPRs12130, 12201:
(All graphical device drivers) Job aborted with error code of 7649 (out of memory for graphics) when printing polylines and polygons with more than 500 points.  The graphical device drivers can now print polylines and polygons of up to 1000 points, the maximum that will be generated by Art Designer or Chart Designer.
SPR12138:		(Epson device driver)  Only one Epson driver could be installed on a workstation, or group of workstations booted from the master, because each driver would attempt to open and use the same scratch file.
SPR 12220:		When GPS was installed on a cluster workstation and then rebooted as a standalone workstation, the error Add GpsDevice Failure, Termination code = 33 was received. This occurred because the standalone workstation tried to use the node name that was available from the master when the workstation was in cluster mode. The node name in the Gps.Printers file now appears as Local when the printer is installed at the workstation. Previously, the home node name was used.
SPR 12223	:	GPS did not use the [scr] (scratch) volume for spool files like the old spooler.  Instead it created temporary files in the [Sys]<Gps> directory.  Now the [scr] volume is used for temporary files.  
{2.2	Changes from Release 2.0
}Pipe Drivers have been added to the release.  For each of the device drivers, except the binary mode driver, there is a corresponding program which is used to print to a disk file.  Each translates a GPAM or ASCII document into a disk file in the language of the corresponding printer.  These are called pipe drivers in reference to their simple mode of operation: they take a disk file as input and create a disk file as output.  They are run in the foreground as normal applications, not installed as system services by the Print Manager.
Each pipe driver takes an input filename and output filename as parameters (plus a number of parameters similar to those available in the Print Manager device installation form).  The output file created by the Pipe driver can later be printed by specifying binary mode from the 2.1 Print Manger or the Executive print command.  
To obtain an input file for processing by a Pipe driver, a filename can be typed in place of a GPS device name into the Document Designer Print command.  Because Document Designer cannot know in this case which printer the document will eventually be printed on, it is essential to first review the document and specify the correct font device type in the Review form.  The font device type normally used by each Pipe driver is shown in parentheses in its command form.  Unless a document contains only 12 point Courier (a 10 pitch font) acceptable results can be expected only when the font device type (and font database) is the same when the GPAM file is created and when it read by a Pipe Driver.
Pipe drivers require that the font service be installed.  No other part of GPS is required for their operation.
A Draft Output Application is implemented by the Simple Pipe driver.  It converts GPAM files into editable page images.  The New Line Map Mode option allows the user to select whether lines should be terminated by a line feed as in CTOS (the binary option) or by a carriage return, line feed pair as in MSDOS (the CRLF option).
Different drivers are provided for use on the AWS and the IWS.  The drivers whose run filenames begin with the letter m must be used on versions of CTOS prior to 9.4.  This includes CTOS 9.1 for the AWS and IWS, as well as CTOS 3.2 for the SRP.  [In GPS 2.0 these drivers were required on versions of CTOS prior to 9.1 onlyi.e., CTOS 3.2 for the SRP].  
The standard drivers now differ in two respects from the m drivers.  The first difference is unchanged from GPS 2.0, while the second difference is new in GPS 2.1.  (1) The standard drivers are linked V6, protected, as required by PMOS and CTOSVM, but not supported prior to CTOS 9.1.  (2) The standard drivers are linked without support for the old implementation of bytestreams prior to CTOS 9.4.  This reduces the installed size of the standard drivers by 3.5 Kb.  Each of the m drivers, which have this support, is 3.5 Kb larger than the corresponding standard driver.
Device driver sizes have been reduced.  A number of economies have been introduced into the portions of the device driver that are common to all or many device drivers.  These economies result in memory savings ranging from 12K to 32K for each driver.  It is also believed that many device drivers will be faster as a result.
Binary mode printing support has been clarified.  Previously a number of device dependent routines were called at the beginning and ending of binary (or image) mode print jobs.  Consequently, binary (or image) mode was not truly passing through the print job unmodified, as intended.  It turned out that several device drivers performed logic in these routines which interfered with the function of binary mode print jobs.  In fact, binary mode was qualified only using the Binary Mode driver, or (in conjunction with the Word Processor) the Daisy driver.  In 2.1 GPS, no device dependent routines are invoked by binary mode print jobs, unless the job is aborted.  Binary mode works in all device drivers.  Use of the binary mode driver is no longer required for support of Art Designer plotters, for example, although it is preferred, merely because it is considerably smaller than other drivers.  Some other driver might be appropriate, (chiefly the simple device driver for certain dot matrix printers supported by Art Designer) to enable the same device to be utilized by other applications such as Document Designer.  
Interpretation of installation page dimensions has been revised.  Previously the page dimensions specified in the device installation form was used as the maximum page dimensions.  However, it is possible to obtain pages of different dimensions from various input sources.  Many printers have multiple input trays, or allow manual feed of larger than normal pages.  It was therefore necessary to specify installation page dimensions equal to the largest paper source available.  This provided no means of specifying the normal page dimensions for the standard paper input source.  Now the installation page dimensions are used as the standard (or default) page dimensions.  Unformatted documents will be paginated according to the installation page dimensions.  That is, the driver will assume that the standard paper source should be used.  But formatted (GPAM) documents may be printed with larger or smaller dimensions, and the device driver core will assume that the devicedependent part of the driver has the capability to load larger paper.  
Note that each driver has maximum page dimensions specified when the program was built.  Characters in formatted documents outside of those dimensions are discarded when the document is printed.
The chars per line field of the installation form is no longer used.
Support for multicopy printers has been added.  Previously, the entire print job was resent to the device driver for each requested copy.  Now, certain printers (generally, laser printers) will instead be instructed to generate multiple copies of each page.  This allows printers to be driven at their rated output speed.  This works only on spooled device drivers (for normalmode jobs), since applications which support multiple copies in direct printing generate multiple copies independently.  
The pause for manual paper feed has been eliminated from laser printer drivers.  On such printers, the manual feed option (available from the Document Designer Print form) is used to instruct the printer to await paper from the manual feed slot.  Since these printers automatically pause until the paper is inserted, it is unnecessary to require the user to issue a restart command from the Print Manager or Document Designer.  This change means that the Document Designer will continue to send data to the printer, via the device driver, until the printer buffer fills.  At that point in time, if the paper has not been inserted, the printer will be reported to be offline.  The device driver has no means of knowing whether the problem is this, or caused by a paper jam, an empty paper tray or some other condition.  The user must determine by examination of the printer console and paper trays whether manual feed is required.
A PostScript Device Driver has been implemented.  Its features in common with other device drivers include graphics support, support for a wide selection of typefaces and sizes, support for national character sets, multicopy output, manual feed, and prompts for font cartridge changes.  Distinctive features include simulation of solid, half tone and quarter tone colors via gray level, and a choice of polyline styles compatible with either Art Designer or the Imagen device driver.  For the TI 2115, it allows selection of paper source either by physical bin (Document Designer bin 2 selects the bottom bin and bin 3 selects the top bin), or by paper size (whenever bin 1 is specified).
Font data for PostScript has been added to the font database.  If a user of the Screen font database needs to be able to print to a PostScript device, 2.1 Screen font database must be installed, or the user's screen font database must be updated by merging the port files provided with this release with the editable screen font database.
Graphics and landscape support have been added to the HP Laser Jet Driver.  Graphics and text are supported in landscape and in portrait mode, but care must be exercised by the user to utilize only those fonts in documents which are available in the orientation required.  This care is required because orientation is currently not recognized as an attribute for font selection by the Font Service, its database, or applications using the Font Service.  The LaserJet is the only printer supported in 2.1 Generic Print which requires this caution.
The LaserJet driver also has new support for multicopy output, manual feed and bin selection on the LaserJet500.  
Underlining and support for binary mode jobs have been improved in the Laser Jet driver.
A number of font database changes have been made for the HP LaserJet.  Therefore, LaserJet users must use the new font database.  If a user of the Screen font database needs to be able to print to a LaserJet, 2.1 Screen font database must be installed, or the user's screen font database must be updated by merging the port files provided with this release with the editable screen font database.
The Imagen Device Driver now supports multicopy output and manual feed, without pause.  Underlining has been improved.  Management of the Imagen's font maps has been optimized to minimize the likelihood that the Imagen's internal memory will overflow when printing jobs with many fonts.
Several bugs in the Epson Device Driver have been fixed.  A fault that occurred under CTOSVM has been eliminated.  Now it is possible to install multiple Epson Device drivers sharing the same system volume.  Underlining in justified text has been fixed.  A bug that occured when page length was changed from one document to the next has been corrected.
Several bugs in the Daisy Device Driver have been fixed, including a fault that occurred under CTOSVM.  Several bugs related to the use of sheet feeders have been fixed.  This driver has been tremendously simplified as it now relies on new facilities in the device driver core to perform many of the jobs which it previously needed to do itself (e.g., ordering the text and underscores for output in the required order, sensitive to wheel changes and printhead logicseeking).  Users who obtain PrintGen will find it much easier to take the source for this driver and modify it for unusual devices which are largely (but not completely) compatible with Diablos.  For example, there are a number of laser printers which emulate Diablos with the added abilities to automatically change fonts and do primitive graphics.
The Simple Device Driver has been made more simple, and it now uses the same generic font change routine which is used by the LaserJet and Daisy device drivers.  This font change routine parses the font alias from the font database to recognize either or both of (1) an escape sequence to send to the printer and (2) a wheel or cartridge name to prompt the user to mount.  The latter is displayed in Document Designer's and Print Manager's printer status displays until a user restarts (resumes) the print job.  This allows the Simple device driver to be used to select a monospaced font or fixed character pitch on printers which only require a simple escape sequence or user prompt to accomplish this job.
{The Binary Mode Device Driver has been greatly reduced in size (from 61Kb to 27Kb) mostly by elimination of all code that was relevant only to the printing of GPAM or ASCII jobs.  It can now run without the presence of the Font Service.}
{Font Service character width table values are now rounded when converted to required units.  This will cause many fonts to be displayed in parentheses in Document Designer, until the document is Reviewed or Printed with the new font service.  (Also, due to a bug in 2.0 WYSIWYG Document Designer, codeV characters such as the paragraph mark overlap text until the document is reviewed).  2.1 Device Drivers perform the same rounding.  It is therefore important that all the font services on a cluster be updated when the GPS device drivers are updated.}
Two littleused forms (Shuffle and Propagate) in the Font Tool were corrected to show correct field sizes.  Also a bug in the wheel set conversion of vertical shifts was corrected.
The Printing Mode field of the print form of the Print Manager has been implemented. This field was previously ignored by the Print Manager and always defaulted to ASCII.  The Print Manager will now print documents in Image (WP) mode and Binary Mode as well.  Output of the Pipe Drivers can be printed from Print Manager by selecting Binary Mode.
The Print Manager has a new field in the device installation form: Board ID. This permits the system administrator to specify that a device driver be installed on a specified board on an SRP, e.g., CP01, TP02.  This information is then stored in the Gps.Printers file.  The purpose of this change is to permit MegaFrame machines to run device drivers on multiple boards. This field is currently not used.  It will become operational in a future release of CTOSSRP.
The Print Manager status display now shows the error code, if a job aborted due to an error detected by the device driver, for the last five jobs processed.  This feature depends also upon a change to the device driver core.  Thus the error code will not be displayed for device drivers built from 2.0 PrintGen.
When the GPS Installer runs on MegaFrame machines, it checks the Gps.Printers file for each device to see what board the device driver should be installed on. The GPS Installer must be run on every board that is to have GPS drivers installed on it.  This will be supported in a future release of CTOSSRP.
A bug in the Installer which caused it to write into a random word in memory in certain conditions has been fixed.
{In previous versions of GPS, there was no way to prevent the Installer from installing the Font Service locally once it was installed locally.  If the Font Service was ever installed locally,} GPS would note this in the Gps.printers file, and forever after it would try to install the Font Service locally each time that GPS was installed.  It may be desirable to use the Font Service at the master rather than always have GPS install it locally.  To turn off the automatic installation of the Font Service, use the Deinstall Font Service command to deinstall the Font Service, then remove GPS using the Print Manager.  The gps.printers file will be updated when the Print Manager removes GPS.
The GPS Spooler will permit more that one device driver to access the same queue.  This allows multiple printers to be retrieve jobs from a common queue.  For example, two different Imagen device drivers could be installed, and each could use the queue called Imagen. The queue name is specified in the device driver installation form.
When the GPS Spooler is installed from the Print Manager, it accepts [Maximum Number of Devices] as a parameter. This parameter specifies the maximum number of spooled devices that can be handled by the Spooler. Previously, this parameter was ignored, and the number was set to 3. This change was made to permit the Spooler to handle more than 3 spooled devices. Each spooled device adds 1K of memory and one process to the Spooler system service.
When the GPS Routing Switch is installed from the Print Manager, it accepts [Maximum Number of Devices] as a parameter. This parameter specifies the maximum number of local devices that can be handled by the Routing Switch. Previously, this parameter was ignored, and the number was set to 4. This change was made to permit the Routing Switch to handle more than 4 local devices. The maximum number of local devices that can be handled is 10. The variable number of devices specified for the Spooler and the Routing Switch will be more important for a future release of CTOSSRP that will permit device drivers to run on multiple boards.
The Routing Switch also contains bug fixes.  A bug in GetGPSNetList caused it to list the same device twice under certain conditions.  The priority of the uplink process was changed from C0 to 54 to be higher priority than the device driver.  Previously busy devices could be dropped from the list of devices available on that node.
3.0	Contents of Distribution Diskettes
The Generic Print System Distribution Diskettes are your master copies, and have been shipped writeprotected.  They should not be writeenabled, nor should they be used as working copies.
The following Generic Print System components are contained in this distribution set:
	GPS Print Manager
	GPS system services
		Routing Switch
		Spooler
		Device drivers
	Pipe Drivers
	Font Service
	Font Tool
	Font database source files
	GPAM object library, example program source files and 	cluster installation files
{Parameters entered by the user at installation time control which of the above printing components will be installed, and whether the installation is intended for a master system or an LFS cluster workstation.}
The Generic Printing System is designed to operate over the full range of Convergent workstations and CTOS versions currently supported.  As such, the distribution diskettes contain versions of runfiles and loadable request files which are suitable only for certain hardwaresoftware configurations.  All possible configurations are shipped on the distribution diskettes, but only those components needed on a particular configuration are actually copied from the installation diskettes to the hard disk of the target system.  In addition, a second installation procedure, LfsInstall.sub, is included in the GPS distribution which may be used to install GPS on cluster workstations with local file systems from their master.
GPS is distributed in archival form, a file format created by the Selective Backup command and read by the Restore command.  The archival format does not create distinct files on the distribution diskettes, but instead combines the files into a single archive file, which span 6 diskettes.  On each diskette is an extent of this file, named .01, .02, .03, .04, .05, and .06, respectively.  The installation procedure determines the type of hardware and software in use and loads the correct subset of files to the target system.  There are additional files in the <Sys> directories of diskettes 1 of 6 and 6 of 6, that are used for control of the installation sequence.  Of these files, only those that are also used in the LfsInstall.sub cluster installation sequence are copied to the <Gps> directory on the target system.  The complete list of files is listed below.
Archive file:

GPAM Development, in directory GPS:
Gpam.lib	Gpam.pas
GpamProcs.edf	GpamTypes.edf
GpsBs.pas	GpsProcs.edf
GpsTypes.edf	Graphics.c
LinkGpam.sub	LinkGpsBs.sub
LinkGraphics.sub

Font Tool, in directory FontDB:
FontCharacterSet.port	FontDB.sub	
FontDevice.port	FontFamily.port	
FontKey.port	FontPseudoFamily.port
FontRaster.port	FontReduction.port
FontTranslate.port	FontWidth.port	
Script	TextSet.Font
VM003TextSet.Font

Font Tool, in directory Sys:
FontForms.lib	FontIsam.config
FontTool.run

Pipe Drivers, in directory GPS:
DaisyPipe.run	EpFx286Pipe.run
HPLaserJetPipe.run	Imagen8300Pipe.run
LptSimplePipe.run	PSPipe.run

System Services, linked V4, in directory GPS:
mBinaryModeDD.run	mDaisyDD.run
mEpFx286DD.run	mGpsInstall.run
mGpsRs.run	mGpsSp.run
mHPLaserJetDD.run	mImagen8300DD.run
mLptSimpleDD.run	mPSDD.run

For installation on workstation from master,
in directory GPS:
CmdFontServer.sub	CmdFontServerV4.sub
CmdFontServerV6.sub	CmdFontTool.sub
CmdNoFontServer.sub	CmdNoFontTool.sub
CmdNoPrinters.sub	CmdPipeDrivers.sub
CmdNoPipeDrivers.sub	cmdPrinters.sub
CmdPrintersV4.sub	CmdPrintersV6.sub
GpsHdInstall.run	IFontDB.fls
IGpsGpam.fls	IGpsNoGpam.fls
IGpsFontServer.fls	IGpsNoFontServer.fls
IGpsNoPrintersV4.fls	IGpsNoPrintersV6.fls
IGpsPrintersV4.fls	IGpsPrintersV6.fls
IGpsWSmin.fls	ISysFontServerV4.fls
ISysFontServerV6.fls	ISysnoFontServerV4.fls
ISysnoFontServerV6.fls	ISysFontTool.fls
ISysWSmin.fls	Lfs.sub
LfsEditFontData.sub	LfsInstall.sub
LfsInstallFontTool.sub	LfsInstallNoFontTool.sub
mgRqIFontTool.sub	mgRqIIFontTool.sub
mgRqIInoFontTool.sub	mgRqInoFontTool.sub
PMCmInstall.sub

Standard (V6) Device Drivers, in directory GPS:
BinaryModeDD.run	DaisyDD.run
EpFx286DD.run	HPLaserJetDD.run
Imagen8300DD.run	LptSimpleDD.run
PSDD.run

System services, in directory GPS:
GpsSp.run	GpsInstall.run
GpsRs.run	Font.dbs

System services, in directory SYS:
DeinstallFS.run	mFontService.run
FontService.run

Print Manager, in directory GPS:
gpsforms.lib	GpsPm.Msg
GpsPm.run

In directory SYS:
Gps.User

for SRP, in directory GPS:
SRPInitCPxx.jcl	SRPInitFPxx.jcl

for SRP in directory SYS:
mRequest.9.sys
Diskette 1 of 6 files:
GpsHdInstall.run	HdInstall.sub
IGpsSysV4.fls	IGpsSysV6.fls
IGpsFontServer.fls	IGpsGpam.fls
IGpsPrintersV4.fls	IGpsPrintersV6.fls
IGpsWSmin.fls	IGpsWsSupport.fls
Install.sub	ISysFontServerV4.fls
ISysFontServerV6.fls	IFontTool.fls
ISysWSmin.fls	Restore.sub
Res1.sub	Res2.sub
Res3.sub	Res4.sub
Res5.sub	Res6.sub
SRP.fls
Diskette 6 of 6 files:
CmdFontServer.sub	CmdFontServerV4.sub
CmdFontServerV6.sub	CmdFontTool.sub
CmdNoFontServer.sub	CmdNoFontTool.sub
CmdNoPrinters.sub	CmdPipeDrivers.sub
CmdnoPipeDrivers.sub	CmdPrinters.sub
CmdPrintersV4.sub	CmdPrintersV6.sub
mgRqIFontTool.sub	mgRqIIFontTool.sub
mgRqIInoFontTool.sub	mgRqInoFontTool.sub
PMCmInstall.sub	ISAMServer.run
Request.9.sys	Request.I.sys
In directory <RelNote>:
Gps.RelNote	Gps.RelNote.wp
Gpam.lib is an object library that provides the procedures necessary for an application program to use the Generic Print Access Method and the underlying Generic Print System services.  This library name should be specified to the Linker in the [Libraries] parameter when linking the application.
FontService.run is the runfile for the Font Service.  Font.dbs is the runtime version of the font database that contains the font information that may be accessed through the Font Service.  DeinstallFS.run is a utility program, invoked by the 'Deinstall Font Service' command, which will cause the font database and Font Service to be removed from memory.  Refer to section 10.3 of this document for further information about the font database.
GpsPm.run is the runfile for the Print Manager, the user interface to GPS.  This program is used to install GPS and to monitor its functions.  The files GpsForms.lib and GpsPm.msg are needed for Print Manager operation.  GpsInstall.run is the runfile for the program that implements the 'Install Generic Print System' command that installs the Generic Print System in system memory, given the desired system configuration as recorded in the file [Sys]<Gps>GPS.Printers, built by the Print Manager.
GpsRs.run is the runfile for the Routing Switch, a system service that accepts GPS requests from application programs and routes them to the proper service, whether on the same workstation, another workstation in the cluster, or over CTNet to a remote node.
GpsSp.run is the runfile for the GPS Spooler program.
LfsInstall.sub is a submit file which allows the installation of GPS on local file system cluster workstations after the installation has been completed on the master workstation.  The files lfs*.sub and those transferred from Diskettes 1 of 6 and 6 of 6 listed above, are used by this installation process and should be kept in the master workstation's <Gps> directory until all distribution installation is complete throughout the workstation cluster.  Section 4 of this document describes the installation process.
Request.9.sys and mRequest.9.sys are the loadable request files that need to be read and loaded by the operating system at bootstrap time in order to enhance the operating system to include GPS and FontService facilities.  Request.9.Sys is the standard loadable request file.  mRequest.9.sys is the CTOSI, SRP loadablerequest file.  Request.I.sys is the loadablerequest file for the ISAM server, that is needed by the Font Tool.  The distribution installation procedures place the appropriate request information into their proper places, provided that the hardware and software description parameters are specified properly at installation time.
BinaryModeDD.run, DaisyDD.run, EpFx286DD.run, HPLaserJetDD.run, Imagen8300DD.run, PSDD.run, LptSimpleDD.run are the runfiles for the device drivers supplied with this release of the Generic Print System.  The corresponding files that begin with 'm' are required for AWS and IWS systems, as well as MegaFrame SRP systems which are not yet running the CTOSII operating system.  Further details about the device drivers are contained in section 10.3.
Gps.relNote in the <ReleaseNote> directory is the editable form of this document in Document Designer 2.0 format.  The file Gps.relNote.wp is the same document in Word Processor Format.
{4.0	Installation Procedures
The term installation has two meanings:}
{1.	The copying of new distribution files to a workstation or SRP.  That is what most of this release notice is about.  The following subsections describe copying different sets of GPS 2.1 files onto different hardware configurations.  We will call this the distribution installation in this subsection.}
{2.	The invocation of a file that then becomes a part of that processor's OS (i.e., a System Service).  Each time that a system service runfile is invoked so that it may be accessed by system users, it is said to be installed.  We will call this the system service installation in this subsection.}
{Most of the GPS 2.1 runfiles are system services, so they must be installed twice.  Their first installation is when they are copied to the system from the distribution diskettes or from the master to the cluster workstation by the LfsInstall.sub procedure.  Their second installation is each time that they are invoked for use by the system.}
{The Generic Print System should only be used on Convergent Information Processing Systems which are equipped with hard disk, or in clusters where the master is equipped with hard disk.  The Generic Print System works on AWS, IWS, CWS, NGEN, and 286i workstations.}
{The Generic Print System requires that Standard Software at revision level 11.0 or later exists on the workstation.  If you have not yet installed Standard Software at such a revision level, do so before installing the Generic Print System.}
{Use the installation procedures described below.  Characters that you must type are shown in boldface.  Special keys, such as RETURN and GO, are shown in upper case.}
{Warning: make sure that GPS is not currently running on the workstation where you intend to install this release.  Otherwise, the installation procedure may not be able to copy the new software to the hard disk.  If necessary, use the administrator REMOVE command of the Print Manager to deinstall GPS before starting the installation procedure.  Use the Deinstall Font Service command to remove that service if it is installed:
Command   Deinstall Font Service  GO}
{Use the Deinstall Queue Manager command to remove that service from the master workstation
Command   Deinstall Queue Manager  GO}
{Warning:  Versions of the Queue Manager prior to 11.0 created queue files incompatible in some respects with later versions.  It is recommended that all spooler queues be deleted before installing GPS:
Command   delete			RETURN
Delete
  File list			[sys]<*>*.queue
  [Confirm each?]			GO
GPS Device Driver installation will create any queues needed.}
{Warning:  The CTOSII1.0 version of the Restore program terminates improperly if there is inadequate disk space to restore all specified files.  In some cases the workstation may crash with an Erc91.  If the workstation crashes while installing this software; reboot the system, delete enough files to insure adequate file space, and repeat the installation procedure.}
{Warning:  If you have not previously installed GPS 2.0, remove the GPS directory and all files in it prior to installing GPS 2.1.  The device configuration files used by GPS 1.x are incompatible with GPS 2.1, and the GPS 2.1 installation requires and creates a larger GPS directory than that created by GPS 1.x.}
Command   remove directory 			 RETURN
Remove Directory
  Old Directory name(s)             			[sys]gps
  [Volume or directory password]
  [Delete all files in directory?]  Yes
  [Confirm each while deleting?]    GO
{Note:   This installation uses Restore to install selective lists of files on your system.  Restore reports two numbers: the number of files processed (present in the backup archive) and the number of files successfully restored.  These numbers will differ, depending on the installation parameters that have been specified.  If Restore fails to install any of the files that were required, a third number will be reported: the number of files which could not be restored.}
The Font Service and the Font Tool are included in the GPS 2.1 (distribution) installation.  The Font Service is required by the Document Designer and all the device drivers except the binary mode driver.  If the  Font Service is installed, a standard runtime font database, [sys]<GPS>Font.dbs), is installed along with it.  The Font Tool is the set of programs enabling the user to create a customized font database.  If the Font Tool is installed, an editable font database is installed along with it, containing the data from which the standard runtime font database is generated.  Typically, the user will not want to install the Font Tool.
The Font Service need not be installed on a cluster workstation, if it will be installed at the master workstation.  Device drivers and Document Designer may run faster if the Font Service is installed at each workstation where these products will run.  However, disk space and memory is conserved by installing the Font Service only on the master workstation.
GPS can be installed in two ways. GPS is usually installed from a set of 6 installation diskettes. When GPS has been installed on a master from the installation diskettes, it can then be installed on a cluster workstation by using a submit file that causes files to be copied from the master to the local file system of the workstation. In either case, the installation procedure displays a set of forms that allows the user to select installation options. 
{4.1	Installing GPS from the Installation Diskettes
Place the Generic Print System installation Diskette 1 of 6 in drive [f0] and enter the Install command as follows:
Command   Install  GO
Install}
{or, if you do not have the Install command:
Command   Submit   RETURN
Submit
  File List	        [f0]<Sys>HdInstall.sub
  [Parameters]	     [f0]  GO}
The installation begins by displaying a form to permit the user to select options. The first form displayed will be different depending on the system where the installation is being done. 
{4.1.1	StandAlone Hard Disk Systems
A.	When the options form is displayed, follow the instructions in choosing the options you want:
Printers	Select this option if you want device drivers installed at this workstation.
Pipe Drivers	Pipe Drivers are used to create print image files.
Font Service	This option copies the files necessary to install the Font Service at your workstation.
Font Tool	This option copies the files necessary to install the Font Tool at your workstation. You only need the Font Tool if you wish to modify the font database.
GPAM Development 	Select this option to copy the GPAM library, .edf files and GPAM programming examples to your workstation.
When you have selected the options you want, press GO to continue.}
{B.	If you selected the Printers option, the Printers form will be displayed. Select the printers that you want and press GO to continue.}
{Imagen 	Impress (Imagen) printers
Daisy 	Diablocompatible printers
Epson 	Epson printers
HP LaserJet	PCL (Hewlett Packard) printers
LPT Simple	Generic  for draft printing
PostScript	PostScript printers
Binary	Binary mode (plotters)}
{C.	If you selected the Pipe Drivers option, the Pipe Drivers form will be displayed. This form looks just like the Printers form except that there is no Binary pipe driver. Select the pipe drivers that you want and press GO to continue.}
{D.	During the installation, you will be prompted to mount the appropriate volume .02, .03, .04, .05 or .06.}
E.	Reboot the workstation when the installation is complete.  
{F.	If FontTool was selected as one of the installationoption parameters, execute the following command:
Command   Submit   RETURN
Submit
  File list        [Sys]<FontDB>FontDB.sub  GO}
{G.	See the Printing Guide for instructions on (system service) installation of the Font Service and the device drivers you need.}
{4.1.2	Master Hard Disk Systems
A.	When the master options form is displayed, follow the instructions in choosing the options you want:}
{GPS Workstation Support
This option provides submit files so that workstations can install GPS from the master.}
{Support for Workstations using CTOS 9.3 or less
This option will appear if your master is a CTOS II or CTOSVM master. Selecting this option causes old style device driver run files to be copied to the master so that they may be accessed by workstations that are running CTOS 9.3 or less.}
{Support for CTOS II or CTOSVM Workstations
This option will appear if your master is running CTOS 9.4 or greater. Selecting this option causes new style device driver  run files to be copied to the master so that they may be accessed by workstations that are running CTOS II or CTOSVM.}
When you have selected the options you want, press GO to continue.
B.	Continue as in 4.1.1 above to select the rest of the installation options.
{4.1.3	Cluster Workstations
A.	When the installation diskettes are installed at a cluster workstation, the user has the option of installing GPS at the workstation or at the master. The form displayed will permit the user to select one of three options: }
{Workstation 	Select this option to install GPS at the workstation. Then continue as in 4.1.1 above when the options menu is displayed.}
{Master 	Select this option to install GPS at an NGEN master. Another form will appear so that the user can specify the version of CTOS that is running at the master. Select CTOS II or VM or CTOS 9.x and press GO. Then continue as in 4.1.2 above when the master options menu is displayed.}
{SRP Master 	Select this option to install GPS at an SRP master. Another form will appear so that the user can specify the version of CTOS that is running at the master. Select CTOS II or VM or CTOS 3.x and press GO. Then continue as in 4.1.2 above when the master options menu is displayed. See Section 9.1 of this document for information about installing the GPS system services on the MegaFrame SRP.}
{4.2	Installing GPS on a Workstation from the Master
Cluster workstations with local file systems can have GPS installed on them after successful GPS installation with the GPS Workstation Support option on the Master workstation of their cluster.}  
The following command sequence performs the distribution installation by copying specified files from the master workstation to the cluster workstation's local file system.
{A.	Execute the command:
	Command   Submit  RETURN
Submit
  File list       [sys]<Gps>LfsInstall.sub GO
  [Parameters]
  [Force Expansion?]
  [Show Expansion?]}
{B.	When the options form is displayed, follow the instructions in choosing the options you want as in 4.1.1 above.}
{4.3	StandAlone Floppy Disk Systems
The Generic Print System is not supported on standalone floppy disk systems.}
{4.4	Installing the Font Service
If you require the use of the Times and Helvetica screen fonts in various sizes at a cluster workstation (e.g., you have a VM003 bitmap video display and will be using Document Designer 2.0 or later), you will need to install the Screen Font Database product (STA2200) after completing the GPS (distribution) installation.  You will use the database. ScreenFont.dbs, included in that distribution, instead of the database, Font.dbs, included in this distribution when you install the Font Service.
The Font Service must be installed as a service before Generic Print System device drivers, which require its presence.  It may be installed at the master workstation of a cluster, or at local workstations where devices are installed.  If the Font Service is not already installed, the Install Generic Print System command will install it (with default parameters) prior to installing a device driver.}
Better performance can be obtained by installing the font service on each workstation in a cluster which requires font services, but only if the runtime font database can be located on local file storage.  The Font Service may be installed both on the master and on as many cluster workstations as desired.  Those cluster workstations which do not have a local font service will access the Font Service from the master.
Only one Font Service can be accessed from any workstation:  either the one installed locally, or if there is none, the one installed at the master.
{Initially, the Font Service should be installed from the Admin form of the Print Manager if it is to be installed locally.  This will change the [Sys]<Gps>GPS.Printers file, allowing the Font Service to automatically be installed in the future with the Install Generic Print System command.  If you wish, you may install the Font Service by entering the following Executive command:}
{  Command   Install Font Service  GO
  Install Font Service
    [Font Database]
    [Bytes of Buffer Space]}
The default font database is [Sys]<Gps>Font.dbs, while the default size of the buffer is 8192 bytes.  The maximum that can be specified is 65535 bytes.  Performance may be improved by increasing the buffer size to 11264 bytes.  The performance improvements are slight with sizes larger than 11K.  
{Note: The device drivers and Document Designer require access to the font database, that is, they must have a Font Service installed.  The Font Service may be installed at the master workstation and shared by all users in the cluster, or it may be installed at individual workstations for better performance.}
{4.5	GPS Service Installation on the SRP 
}The contents of the file [sys]<Gps>GPS.Printers determines which GPS system services are to be installed on the SRP.  This file is built during an interactive session of the Print Manager by the system administrator, selecting the Master function key from the Admin form.  While in this mode, all installation commands are recorded in this file but the installations themselves are deferred until the SRP itself in rebooted.
The recommended SRP installation sequence is to install the Queue Manager and the Font Service on the Master File Processor, since these system services make frequent disk accesses and operate more efficiently when executing directly upon a file processor.  The rest of GPS; Routing Switch, Spooler, and Device Drivers, should be installed on either a CP or a TP, to which are attached whatever printers are supported by the SRP.  The sample files <Gps>SRPInitFPxx.jcl and <Gps>SRPInitCPxx.jcl provide an example of such an installation sequence.  The contents of these files should be combined with the existing SRP initialization batch files to install GPS.  Please note the use of the sync program in the example files.  Sync is used to ensure that both the Queue Manager and the Font Service complete their respective system service installations before GpsInstall.run is invoked to  install the rest of the GPS system services.
See the Printing Guide and the CTOS System Administrator's Guide for more information on SRP installation.
{4.6	Configuring the Context Manager
}The GPS installation procedures, both from distribution diskettes and LfsInstall.sub, provide an option to add the Print Manager to the Context Manager configuration file.  Alternatively, it can be added  by the procedure outlined below.  It is important that the correct command case be specified, as in the following example:
{	Command  CM Add Application  RETURN
	CM Add Application
		[CM Config File]	
		Application	        'Print Manager'
		Run file	        [Sys]<Gps>GpsPm.Run
		Memory required	        170
		[Abbreviation]	        ' P M'
		[Function key]
		[Command case]	        PM  GO}
{5.0	Required Files
The installation procedure creates the directory <Gps> on the system volume.  It copies the files required for correct GPS operation into this directory.}
The installation procedure also copies files into the <Sys>, <FontDB>, and <ReleaseNote> directories.  See Section 3 for a list of the files which will be added to each directory.
{If the Print Manager is to be executed from the workstation, the following files are required in the <Gps> directory:
GpsForms.lib	GpsPm.msg
GpsPm.run}
{If a device driver is to be installed at workstation, the following files are required in the <GPS> directory:
<Gps>GpsInstall.run	<Gps>GpsRs.run
<Gps>GpsSp.run	}
{One or more of the following device drivers will also be required in the <Gps> directory, if you are installing device driver on a system running CTOS level 9.4 and up, or CTOSVM.
BinaryModeDD.run	binary mode only (plotters)
DaisyDD.run	Diablocompatible printers
EpFx286DD.run	Epson printers
HPLaserJetDD.run	PCL (Hewlett Packard) printers
Imagen8300DD.run	Impress (Imagen) printers
LptSimpleDD.run	generic  for draft printing
PSDD.run	for PostScript printers}
{One or more of the following device drivers will be required in the <Gps> directory, if you are installing device driver on a system running CTOS below level 9.4: e.g., AWS or IWS workstations or CTOS 3.2 for the SRP.
mBinaryModeDD.run	binary mode only (plotters)
mDaisyDD.run	Diablocompatible printers
mEpFx286DD.run	Epson printers
mHPLaserJetDD.run	PCL (Hewlett Packard) printers
mImagen8300DD.run	Impress (Imagen) printers
mLptSimpleDD.run	generic  for draft printing
mPSDD.run	for PostScript printers}
{The following pipe drivers are required, in the GPS directory, only if you need to obtain device driver output in a disk file.  
DaisyPipe.run	Diablo file
EpFx286Pipe.run	Epson file
HPLaserJetPipe.run	PCL file
Imagen8300Pipe.run	Impress file
LptSimplePipe.run	draft image file
PSPipe.run	PostScript file}
{The following files are required to run the font service:
<GPS>Font.dbs	<Sys>FontService.run
<Sys>DeinstallFS.run}
{The following files are only needed in the <Gps> directory while you are completing installation with LfsInstall.sub on all of the workstations in your cluster:
lfs.sub	lfsEditFontData.sub
LfsInstall.Sub	IFontDB.fls
IGpsWSmin.fls	ISysWSmin.fls
IGpsPrinters.fls	IGpsNoPrinters.fls
IGpsFontServer.fls	ISysFontServer.fls
IGpsnoFontServer.fls	ISysnoFontServer.fls
ISysFontTool.fls	ISysnoFontTool.fls
CmdFontServer.sub	CmdFontTool.sub
CmdPrinters.sub	CmdNoFontServer.sub
CmdNoFontTool.sub	CmdNoPrinters.sub
PMCmInstall.sub	mgRqIFontTool.sub
mgRqInoFontTool.sub	mgRqIIFontTool.sub
mgRqIInoFontTool.sub	Request.I.sys
Request.9.sys} 
The run files beginning with 'm', other than device drivers, (e.g. mGpsRs.run, mGpsSp.run) are only required on MegaFrame SRP systems running versions of CTOS prior to CTOSII.
{The following files are required for the Font Tool in the [Sys]<Sys> directory:
FontTool.run	IsamServer.run
Request.I.sys	FontForms.lib
FontIsam.config}
{The following files are intialially required for the Font Tool in the [Sys]<FontDB> directory (these files could actually be in any directory, but they are placed into [Sys]<FontDB> by the GPS installation procedure):
<FontDB>FontCharacterSet.port
<FontDB>FontDB.sub
<FontDB>FontDevice.port	
<FontDB>FontFamily.port
<FontDB>FontKey.port
<FontDB>FontPseudoFamily.port
<FontDB>FontRaster.port
<FontDB>FontReduction.port
<FontDB>FontTranslate.port
<FontDB>FontWidth.port
<FontDB>Script
<FontDB>TextSet.Font
<FontDB>VM003TextSet.Font}
After FontDB.sub is processed, it and the .port files are no longer needed.  The data is permanently stored in corresponding files with suffixes of .dat, .isam and .ind.
{6.0	System Software Compatibility
The Generic Print System is backward compatible with previous Convergent printing products.  That is, it supports the Spooler and Queue Manager operations previously used in applications and therefore can support spooled printing in the former fashion.  Version 11.0 or later of the Queue Manager should be used with this release of GPS.  It is important that both QueueMgr.run and InstallQMgr.run be 11.0 or later.}
Direct printing through GPS from previous applications is not supported.  However, a directprint application and a directprint GPS device driver may share a device if they do not attempt to print to that device at the same time.
2.0 GPS device drivers are compatible with 2.1 GPS.  However, it is advisable to rebuild independently developed device drivers with 2.1 PrintGen.  Device drivers based on versions of PrintGen prior to 2.0 are not compatible with 2.1 GPS.  
{6.1	Workstation Environment
The Generic Print System and Font Service depend upon loadable requests that are read from the [Sys]<Sys> directory at bootstrap time.  Due to this need, the loadable request facility provided by 9.1 and later versions of CTOS is required.}
{6.2	Diskless Workstations
}The Generic Print System builds a set of unique configuration files for each workstation in a cluster which has installed GPS services.  These files are located in the GPS working directory, [Sys]<Gps>, at each workstation.  Diskless workstations share the GPS directory at the master workstation, and thus require some method of distinguishing these files as unique to a particular workstation.  GPS uses an alphanumeric prefix, specified in the user file, to uniquely distinguish these files.  See section 10.0 for instructions.
{6.3	MegaFrame SRP
}The Generic Print System and Font Service depend upon loadable requests that are read for the [Sys]<Sys> directory at bootstrap time.  Due to this need, the loadable request facility provided by version 3.2 of MegaFrameCTOS or CTOSSRP 1.0 or laster is required.

MegaFrameCTOS version 3.2 or CTOSSRP 1.0 or later MUST be used with GPS
{7.0	Hardware Information
7.1	Hardware Configurations Supported
The Generic Print System can run on AWS, CWS, IWS, NGEN, and 286i workstations (including NGENs with the XC002 port expander) with hard disk or hard disk at the Master.  The Print Manager can be executed on an AWS 210 workstation, but no device drivers can be installed, due to the lack of serial and parallel IO ports.}
{7.2	Special Hardware Requirements
The Generic Print System can run on the full range of Convergent workstation products provided they are equipped with at least 512K memory, and that they have access to 5Mb of disk either locally or elsewhere on their cluster.}
{8.0	Resource Requirements
8.1	Memory Requirements
}The installable services require a fixed amount of system memory to be allocated to them exclusively.  The Print Manager executes as an application program and will work under the Context Manager version 2.0 or later.
The memory requirements (in KBytes) of the GPS components are summarized in the table below.  The memory required by device drivers is substantially less than in 2.0 GPS.  For sake of comparison, 2.0 GPS sizes are shown for products which were included in that release.
{Component	2.1 GPS	2.0 GPS
Routing Switch	31	27
Spooler	31	31
Font Service	20	20
Imagen Driver	61	84
PostScript Driver	61	
Epson Driver	93	127
Daisy Driver	56	74
HP LaserJet Driver	73	67*
BinaryMode Driver	27	61
LptSimple Driver	50	62
Installer	60	60
Print Manager	170	170}
*The size of the 2.0 LaserJet driver is not directly comparable as it did not support graphics.
Installed driver sizes are shown for the standard drivers.  Add 3 to 4 Kb for the m drivers used on versions of CTOS prior to 9.4 (AWS and IWS workstations; CTOSSRP 3.2).
The Routing Switch must be installed at each workstation which has a printer attached to it as well as at the master workstation. The size of the Routing Switch has increased in order to support up to 10 local device drivers.
The GPS Spooler must be installed at each workstation which has a spooled printer attached.
A device driver must be installed at the workstation to which the printer is attached.}
{8.2	Disk Requirements
The directory <Gps>, created on the [Sys] volume by the installation procedure, is the working directory for GPS.  A similar directory is required for each workstation which has installed GPS components.}
The directory <FontDB>, created on the [Sys] volume by the installation procedure, is where the editable font database is placed.  If the Font Tool not requested as one of the installation options, then this directory is not created.
The directory <ReleaseNote>, created on the [Sys] volume by the installation procedure, is where the editable form of the document you are currently reading is placed.
Installation of all GPS components on a master workstation, when selecting the option Support for 9.x Workstations or the option Support for CTOS II or CTOSVM Workstations, will consume less than 6,000 sectors of disk space.  Otherwise (e.g., on a cluster workstation) less than 5,000 sectors of disk space are required.  The difference of 1,000 sectors is saved when the installation need not include both standard (linked V6) and m (linked V4) versions of each system service.
If pipe drivers are not installed, 1,000 sectors less than the amounts shown above will be required.  Additional space can be saved by installing only those device drivers which will be needed.
If the font tool is not installed, 1,700 sectors less than the amounts shown above will be required.  If the font service is not installed, 400 sectors can be conserved.
A typical installation on a cluster workstation, including font service, one device driver, routing switch, spooler and print manager will require approximately 1100 sectors.
{8.3	CTOS Resource Requirements
}GPS installed services request operating system resources as needed for their execution.  Since these resources are allocated from a fixed pool whose size is determined when the operating system image is built, it may sometimes be necessary to build a new system image with more resources in order to install GPS when there are a significant number of other system services installed at the same workstation.  The table below lists the fixed resources consumed by each GPS installed service or application program.
{Service	PCB	exch
Routing Switch	6	11	*
Spooler	2	4	**
Device Driver	2	4
Font Service	1	2}
{Application	PCB	exch
Print Manager	2	5
Installer	1	2}
{PCB = Process Control Block
exch = exchange}
*	A Routing Switch installed at the master workstation consumes 1 additional exchange for each device installed at a cluster workstation.
**	The values in the table are for a spooler installed to support 1 device driver.  Add 1 PCB and 2 exchanges for each additional device driver supported.
If it is necessary to generate a new system image, consult the release notice for the version of CTOS in use for instructions.
8.4	Tuning Font Data Memory Usage
Probably the greatest single variable factor which influences the efficiency of GPS device drivers is access to font data.  There are three decisions which the system administrator makes which controls this factor.
1.	Should the font service be installed at the cluster workstation, or only at the master, when the device driver is installed on a cluster workstation?
2.	How much buffer space should be allocated to the Font Service when installing it?  The default is 8K, which is a miminal allocation.  A larger amount can be specified, in bytes, as the second parameter to the program.
3.	How much font table space should be allocated to the Device Driver when installing it?  The default is 4K, which is a minimal allocation for most device drivers.  A larger amount can be specified, in Kbytes, at the bottom of the Print Manager's device installation form.
With respect to decision (1), it is not advisable to install the font service on a cluster workstation unless the font database file also resides on the cluster workstation, or a very large (e.g., 32K) buffer can be allocated to the font service.  Otherwise, the cost of disk reads over the cluster channel will probably exceed the cost of font service accesses over the cluster channel.
Decisions (1) and (2) will influence all font service clients (GPS device drivers and Document Designer) on the workstation.  If several font clients exist on a workstation, installing the font service locally with a larger amount of buffer space will benefit all clients, and may be the most effective use of resources.  However, decision (3) has a larger influence on the performance of an individual device driver.  Giving more font table space to the device driver will surely have greater benefit than installing the font service locally, when the device driver is the only font client on the workstation.
A test was performed to dermine the impact of increasing Font Service buffer space andor increasing font table space in a device driver.  The test was performed using the Imagen Pipe driver on a 286 cluster workstation.  Output was directed to the [nul] device to eliminate output device speed as a variable.  The input GPAM file resided on a local disk, and the font service was installed locally, accessing the font database on the same disk.  The test document contained roughly 25,000 words and 1200 font changes.  The text made use of five fonts in total, which we consider to represent a typical mixture of fonts.  The time to translate the document to Impress varied from 3 minutes and 43 seconds when the standard memory allocations were used to 2 minutes and 14 seconds when large amounts of memory were dedicated in both the font service and in the device driver.  The following table shows the results of this test.  The percentage increase over the the best time (2:14) is shown, in order to better interpret the data.  Each row shows a device driver memory allocation, and each column show a font service memory allocation.
		Font Service Memory Allocations
Device Driver	8K	10K	12K	14K	64K
4K	66	49	36	31	18
5K	25	19	16	12	4
6K	12	11	8	7	3
7K	8	7	5	5	1
8K	7	7	5	4	1
30K	2	1	2	1	BEST
This test clearly shows that a small increase in font table space in the device driver generally has a greater impact than a larger increase in the font service buffer space.  This is expected because (1) the device driver is able to buffer exactly the data that it may need to reuse and (2) the overhead of communicating with the Font Service is eliminated when the device driver buffers its own data.
This test, performed with a pipe driver, does not indicate that this document will print 66 slower than the optimum when the minimal memory allocations are used in a GPS device driver installation.  Other factors, including line speed, printer speed and GPS routing speed influence the time to print.  This test does suggest that the installed GPS device driver would consume about 66 more CPU when the minimal memory allocations are used.  Depending upon saturation of the system, this could have have a large effect or a negligible effect on throughput.
The amount of font table space needed for efficient performance varies depending on the device driver used as well as on the document printed.  
Part of the font table space is used for buffering character translation tables.  Typically, translation tables use 0.75Kb.  Some drivers need two (1st level and 2nd level) translation tables to be present most of the time.  Some drivers use different translation tables, depending on the font used.  
Much of the font table space is used for buffering character width tables.  Each uses 0.5Kb and all drivers require two (1st and 2nd level) to be present most of the time, unless the font is monospaced.  The PostScript driver uses the same width table for all sizes of a font, while other drivers use separate width tables for each size.
Part of the font table space is used for storing information about the fonts in use in the current document.  This varies approximately from 15 to 30 bytes per font.  This space cannot be reclaimed until the end of the document.  If a document contains a great number of fonts, the space for this information will be stolen from the space used for holding width and translation tables.  This will slow down the device driver until the job aborts with error code 15333, because no room at all is left for the minimal requirement of width and translation tables.
Based on tests which have been performed, we generally recommend the following uses of memory resources, in order:
(1)	If a device driver will typically print jobs with multiple proportional fonts, install the device driver with a 6K or 7K font table space, if this amount can be spared.
(2)	If a device supports many fonts of different families, types or sizes (e.g., PostScript) and documents utilizing a large number of fonts will be printed, give the device driver an additional 1K of font table space.
(3)	If more than one font client exists on a workstation, or the workstation has memory and disk to spare, install the Font Service at that workstation.  For example, if printers are attached to a workstation, consider installing the font service at that workstation.
(4)	When the font service is installed on a workstation, install it with at least an 11K or 12K buffer space, if the memory can be spared.  
(5)	On 286 and 386 systems with large amounts of unused or underutilized memory, larger allocations of memory can be considered for the font service andor device drivers.
{9.0	Restrictions
It is not possible to perform a remote installation to a master workstation running CTOS II or CTOSVM when the cluster workstation is running CTOS 9.7 or earlier, since the necessary Standard Software tools needed to merge loadable request files are not available on the cluster workstation.}
WARNING: Do not Deinstall GPS when printers (either spooled or direct) are in a paused state.  Due to the multiprocess nature of the Routing Switch, Spooler and device drivers, deinstalling a paused or offline printer will create a deadlock of processes.  Occasionally, performing remote Print Manager functions while deinstalling GPS will lead to  similar deadlocks.  In general, the safest practice is to have all printers attached to a system idle before removing GPS from that system, and to remove GPS from only one system at a time in a cluster.
GPS cannot be deinstalled when running PMOS.  The multipartition deinstallation sequence of GPS is incompatible with PMOS.  The workaround for this problem is to remove the installation entries from the file [sys]<sys>SysInit.jcl and reboot the workstation.
GPS components Routing Switch, Spooler, and Device Drivers can be installed on one and only one SRP processor at a time.  This implies that all devices controlled by GPS must be physically attached to the same processor board, either a Cluster Processor (CP) or a Terminal Processor (TP).  This restriction will be removed by a future release of CTOSSRP.
GPS device drivers can use only the first four ports on the SRP TP board.  The remaining ports lack the interrupt hardware required by GPS device drivers.
The Font Service can be installed only on the Master File Processor board of a Shared Resource Processor.  See the file <Gps>SRPInitFPxx.jcl for an example installation sequence that accomplishes this.  This is due to a bug in CTOSSRP which will be fixed in a future release of CTOSSRP.  The same bug prevents the font service from being installed on diskless workstations clustered to an SRP.
No more than 5 spooled devices can be installed on a cluster, due to a limitation of the 11.0 Queue Manager.  If there are other clients of the Queue Manager besides GPS, this limitation may be lower.  This limitation will be removed in a future release of Standard Software.
Print jobs to be printed after a specified date and time will commence based on the clock of the workstation or SRP where the queue manager is installed, not the clock of the workstation that queued the print job.  These two clocks may vary if the printer is attached to a remote CTNet node.
Graphical objects that exceed page dimensions will not print correctly.  It is possible with the Document Designer to create a page of graphical objects whose dimensions exceed that of the page dimensions.  In such cases, a graphics device driver may produce unexpected results.
Some thin lines are lost in low resolution graphics printed by the Epson and HpLaserJet device drivers.
Page Dimensions specified in GPAM documents are assumed to be correct, unless they exceed the maximum dimensions predetermined for each device driver.  Because different paper bins or different forms may be utilized with various printers, the page dimensions are assumed to describe the paper source that will be used.  Page dimensions for unformatted documents are specified in the Print Manager's device installation form (page width and length) and must correctly describe the standard paper source.  Tractorfed printers (with Epson or Daisy drivers) will advance paper the distance equal to the page length specified in the document.  Daisy wheel printers with sheet feeders will not be able to locate the left edge of the paper if the page width is incorrect.  Laser printers may misalign the image on the printed page if page dimensions are incorrect.
Security mode is not fully implemented.  The password is not checked when a job is paused for security mode, since the device driver does not know what password is required.  Any restart command will cause the job to be printed.  Security mode is usefull only to prevent a job from being printed when the printer is not monitored.
Typethrough is not implemented in this release of GPS.
The 2.1 GPAM library is not reentrant.  This means that a single application cannot have more than 1 GPAM output stream open at one time.  
One of the Routing Switch installation parameters is ignored.  The maximum number of open files has been fixed at 64 in the Routing Switch.  
If a device driver installed locally is unable to access the Font Database at the master, problems will occur  if the master goes down.  Forcing the installation of a local Font Service through the Admin form of the Print Manager will prevent such problems, at the cost of less available memory.
ASCII files cannot be printed in binary mode to printers configured for Impress or PostScript.  ClusterShare, Network PC, PC's, AT's or AT compatibles submit jobs to GPS printers in binary mode, under the assumption that the logic to translate a document into printerspecific language is imbedded in the application, and the device driver should simply pass the data through.  If an ordinary ASCII file (instead of a job in printerspecific language) is queued in binary mode it will usually print, since most printers will accept ASCII.  However, printers configured for Impress (Imagen) or PostScript will only print jobs which are in the Impress or PostScript page description languages.  These printers typically have a panel setup or a physical switch which configure them other interpretation modes, such as diablo emulation, which will accept ordinary ASCII.  It will be necessary to reconfigure these printers in order for them to process ASCII files printed in binary mode.  They must be reconfigured again to print Impress or PostScript jobs generated by a device driver or other application.
Printers which use the Canon CX marking engine, such as the most commonly used models of Imagen, HP LaserJet and PostScript printers, are incapable of printing to the edges of the paper.  These drivers have default values for the size of the dead zones on the top, bottom, left and right borders of the paper.  For other marking engines, the deadzone value for any of the four edges can be entered in the appropriate Border field of the devicedriver installation form.  The default borders for these drivers result in a portraitorientation page length of 10.5 inches, or 63 lines per page at 6 lines per inch.  This should be taken into account when using applications that generate formatted output.  
New Line Map Mode in the device driver installation form is ignored by most device drivers.  Typical device drivers know how to handle new lines on that device, and they therefore drive the printer in binary mode regardless of what is specified in the installation form.  The Simple device driver is the only driver which uses this field.
Characters Per Line in the device driver installation form is ignored by device drivers.  Instead, the page width and left and right borders determine how many characters will be printed per line, based upon the pitch of the default font (usually 10 characters per inch).  This line wrapping occurs only in ordinary (nonGPAM) ASCII documents and only when Wrap: is specified in the device setup field.
Banner pages cannot be specified when installing the Binary Mode device driver.  Banner pages are ASCII jobs created by the Spooler which are not in a printerspecific language.  Therefore they cannot be printed by the Binary Mode driver.  The print job will abort with an error code 4536.
Many printers which support font cartridges have significant restrictions concerning the removal of font cartridges.  It is commonly necessary to turn the printer offline before removing the cartridge, in order to avoid damaging the font cartridge.  On some printers, removing the font cartridge will cause the current page or print job to abort.  The prompt to mount a particular wheel or font cartridge. which is issued by the device driver, is provided without regard to actual restrictions that may exist on various printers concerning font cartridge replacement.  For some printers, this prompt should be regarded as providing information only, concerning which cartridge that the job expects to be present in the printer.  For such printers, print jobs should avoid depending upon more than one font cartridge, and if the cartridge does require changing, the user should restart the print job from the beginning, or from the top of the first page that requires the font cartridge.
Device drivers track the mount of only one font cartridge at a time.  For printers which have two or more font cartridge slots, only one slot should be designated by user convention for cartridge replacement.  The other slots should be reserved for the permanent installation of designated font cartridges.  The font database should be modified so that no cartridge name prompt is issued for those fonts which are present in the permanently mounted font cartridges.
The PC Emulator on 386 systems does not give GPS device drivers enough time to run.  MSDOS contains 'busywait' loops that keep the CPU occupied even when MSDOS has no real work to do.  
Canceling PostScript print jobs sometimes causes one or more subsequent print jobs to be lost.  Also a restart operation (from a location other than the current location) will cause the job to be lost, since this kind of restart is in effect a cancelation of a print job, followed by a reprint of the job.  When a PostScript print job is canceled, an interrupt character (code 03) and endoffile character  (code 04) is sent to the printer.  PostScript printers sometimes fail to recognize the endoffile character after a job terminates abnormally, causing the next job to be processed (without printing it) before the printer returns to an idle state, ready to process additional jobs.  To be sure to avoid this problem Convergent recommends that the following steps be performed before canceling or restarting a print job:
	Pause the device driver.
	Wait a few moments for the printer to indicate that it is waiting for data.  This is indicated by a repeated double flash in the QMS LED, or by the message 'PROCESSING WAITING' in the TI LCD.
	Wait for the PostScript printer to timeout the job, or power the printer off and on.  When the printer is ready, the QMS LED will be off, or the TI LCD will display 'IDLE'.  See section 10.4 of this release notice for information on setting the length of time before PostScript jobs timeout.
	Issue the restart or cancel command.
Restart from a relative location (top of page, backup, or next page) will fail if the device driver was paused before the print job was ready (i.e., while the device was idle).  
Restart from a location other than current will fail when the job was created by Art Designer.  
When a restart location is not found, another restart may be attempted; however the only valid restart locations at this point are by physical or logical page number.  
Drivers that share the same queue must run on the same workstation or be booted from the same master. When drivers that share the same queue have different [SCR] volumes, then one will report erc = 203 (no such file) for the files it is supposed to print. This is because the files are spooled on the [SCR] volume of the driver whose device name was used in submitting the job.
{10.0	Supplementary Information
10.1	User File Additions
}Some users will want to run the Print Manager program in administrative mode.  This enables a user to install and remove GPS services.  The two steps needed to run in administrative mode are: First, edit the [Sys]<Sys>UserFileTemplate.sys file and add the following lines:
{:Category:Generic Print System
  :Field:GPSUserClass
    :Description:User Class (User, Admin)
    :Default:User
  :Field:GPSDefaultPrinter
    :Description:Default Printer Name
  :Field:GPSWorkstationPrefix
    :Description:Unique Id	(diskless only  
	may be any string of 
	up to 12 characters.)}
The second step is to run the User File Editor, and set the GPS UserClass to 'Admin'.  Thereafter, when the user runs Print Manager, the administrator mode functions will be available.
The user file 'GPS.user', supplied with the installation files, is an example of a user file with Admin privileges.
Warning:  The use of the :SignonUserName: option in a user file will make it impossible for GPS to find your user file, since you have, in effect, changed its name.  The effect of this is to ignore any of your GPS user file options.
{10.2	Use With PreGPS Applications
Any application released prior to GPS that uses the printer file [Sys]<Sys>Sys.printers, can access GPS facilities if the following rules are applied.  Using the following example entry,

DIABLO: [SplB]: Diablo630: : DiabloF32}
A.	Use the first field of the printer entry in Sys.printers as the device name when installing the device with the GPS Print Manager.  In the example, DIABLO.
B.	Use the second field of the printer entry in Sys.printers as the queue name when installing the device with the GPS Print Manager.  PreGPS applications can only reference GPS devices that are spooled.  In the example, [SplB].
C.	Use the third field of the printer entry to configure the Daisy Device driver if it is one of the following values: Diablo630, QumeSprint9, NEC3515 or Envision.  Enter the same value into the 'Device Setup' field of the Install Device form of the Print Manager.  If the third field is 'draft', you should install the LptSimple device driver instead, unless there is another GPS device driver which supports that printer.  In the example, Diablo630.
{D.	The fourth field of the printer entry is the graphics device type used by Art Designer and Chart Designer.  The Art Designer drives those devices which have entries specified in the sys.printers files in binary mode.  Any driver will work with Art Designer.  If the third field was draft (e.g., a dot matrix printer) you should probably use the LptSimple device driver.  If the third field was blank (e.g., a plotter), you should probably use the BinaryMode driver.  But if there is a specific GPS device driver available for that device, you should use that driver instead.  In the example, the fourth field is blank.}
	Note that Art Designer and Chart Designer support some printers (such as Imagen, PostScript, HP LaserJet and Epson FX286) only via specific GPS device drivers.  These printers should NOT be listed in sys.printers, or the graphics field should be blank.  
E.	If it is present, include the fifth field of the printer entry to configure the Daisy device driver for that sheet feeder.  Enter the same value into the 'Device Setup' field of the Install Device form of the Print Manager.  Values allowed are DiabloF32, DiabloF33, Ziyad200, Ziyad300, NecSingle and NecDual.  In the example, DiabloF32.
F.	The sheet feeder and printer type names in the Device Setup field may appear in any order and must be separated by a space.  If these values are omitted, the Daisy device driver will be configured for a Diablo630 without sheet feeder.
{10.3	Devicespecific Fonts and Features
}This section discusses:
	Font information used by each device driver which is contained in the standard font database distributed by Convergent;
	How each driver makes use of the alias field of the font key in the font database;
	How to modify the font database to utilize a different set of fonts with each device driver;
	Important installation options for each device driver;
	How to utilize features which are specific to certain device drivers.
This section does not list the general features of each device driver, which would be repetitious of other sections of this release notice.
This section assumes knowledge of certain general principles of the font database which are discussed in detail in the Printing Guide.
There are three font families which are implemented on a number of devices.  Courier is the default family, and is monospaced.  Times is a serif font (with little feet on all the letters) and is proportional.  Helvetica is a sans serif (no little feet) proportional font.  Times and Helvetica are licensed names and properly apply only to the fonts available on the Imagen and PostScript printers, among the following.  On other printers, these fonts are mapped to fonts with the most similar characteristics.
{10.3.1	Binary Mode Driver
}The font database is not accessed by the binary mode device driver.  The device installation fields Font Device Type, Device Setup, Page Dimensions and Font Data Table Size are inapplicable to (ignored by) the binary mode device driver.  Print Banner Pages must be set to No.  See section 10.2 for information on use of the binary mode driver with Art Designer.
{10.3.2	Daisy Driver
}The default font devicetype for the daisy driver is daisy.  Customers who have several different types of daisy wheel printers, with different wheels available for each, should generate a database with distinct font device types (e.g., Diablo and NEC).  Each device type would have appropriate reductions for various general font descriptions and correct character translations for the actual wheels for each printer.  Then the installation for each device should specify the correct value in the Font Device Type field of the Print Manager.  This principle holds for other device drivers as well.
{This driver parses the font key alias in order to: 
1.	Determine the cartridge or printwheel to be loaded (through operator intervention), and  
2.	Find and transmit to the device any escape sequences.}  
The alias is divided into tokens, delimited by spaces.  Any token that starts with \E (or \e) is assumed to be an escape sequence.  \E represents the escape character, and it can occur several times in the escape sequence.  All other tokens are assumed to be parts of a cartridge or printwheel name.  If wheel (or cartridge) name is present in a font key alias, and if that name is different from the wheel name last requested, that name will be used to prompt the printing device operator to install the desired cartridge or printwheel.  If no such name is present, it is assumed than any printwheel or cartridge is acceptable, no prompt is issued, and the record of the last mounted print wheel or cartridge is unchanged.
The font database contains fonts for the daisy device in three font families: Courier, CourierWP, and Cubic PS 96.  12 point Courier calls for a 10 pitch Courier wheel, while 10 point Courier calls for an Elite (12 pitch) wheel.  CourierWP is similar to Courier, except that wheels with Word Processing symbols (such as the section symbol, ) are requested first, instead of standard ASCII wheels.  This family can be eliminated from the font database, if the customer wishes to adopt a set of wheels differentiated only by font and not by character set differences.  Cubic PS 96 is a proportional font family, present in the font database in only a single size and style.  CourierWP and Cubic PS 96 are not used by device drivers other than the Daisy device.  Instead they are usually reduced to Courier and Helvetica, respectively.
The pseudo family feature of the font database serves to map from the old wheelset names (distinct by size and style as well as by family) to the appropriate font descriptions, including font family and type size.  The current font database supports all the print wheels available through the pre2.0 Document Designer.  The Font Tool has a utility to add information to the font database from Word Processor wheel set files.  Consult the Printing Guide for the details of this conversion process.
{10.3.3	Epson Device Driver
}The default font device type for the Epson Fx286 driver is EpFx286.  This driver parses the font key alias for keywords in order to determine the necessary escape sequences to send to the Fx286.  Keywords include Bold, Italic, Pica or Elite, Draft or Nlq (near letter quality), Wide or Cond (condensed).  A combination of keywords may be entered, but not every combination will be recognized by the Fx286 device.  Some combinations will result in one or more keywords being ignored.  Consult the appropriate printer manual for specific information.  
The escape sequence used to set printer character width and print attributes in this driver is the Master Select sequence.  This sequence is not implemented on some older versions of Epson printers.  The Epson FX286 User's Manual gives detail information concerning the limitations of attribute selection.
The font family implemented on the Epson FX286 is Courier.  The Espon Fx286 will print various character pitches but only in one character height (12 point).  Different selected point sizes will reduce to fonts of different pitches, which are (relatively) appropriate.  Bold and Italics are available in each pitch.
To run properly, the Epson FX286 must be set up in Epson Mode.  Improper setting of dip switches can produce results that might be interpreted as font database problems, since many of the escape sequences are ignored in other modes.
10.3.4	HP LaserJet Driver
}The default font devicetype for the LaserJet driver is HPLaserJet.  The standard font database contains information allowing the immediate use of the HP font cartridges 92286A and 92286B.  Font cartridge names (numbers) are included in the alias fields of the LaserJet's font keys along with an escape sequence used to select the correct font.  The alias is parsed according to the same rules as the alias for the Daisy driver.
The alias must not include the font orientation escape sequence (10O or 11O).  Orientation in GPS is determined by the order of page dimensions, not by font.  The user must exercise care to reference only those fonts which exist in the orientation required.  If the requested font does not exist in the requested orientation, the text that will be printed will be in the correct orientation but in the wrong font.  The spacing of the text will likely be unacceptable since a different set of character widths will have been used by the printer, than that which the application (e.g., Document Designer) expected.
The editable font database also contains width tables for the 92286F font cartridge.  That cartridge contains the same fonts as the 92286B cartridge, but the character widths are different.  If the F widths are desired, the name of the width table in each corresponding font key should be changed.
Generally there is a lot of overlap between which fonts are available on which cartridge, and it doesn't make much sense to change cartridges often.  For this reason, the standard font database is configured to map the familiar font families (Times, Helvetica and Courier) to the closest matching fonts on the most common cartridges.  However, in environments using several font cartridges, it would be more sensible to name font families according to cartridge (e.g., TaxFonts for the 92886T cartridge) in order to make it easy to ensure that each document selects from a set of related fonts on a single cartridge.
The standard font database contains important changes from the GPS 2.0 font database with respect to the HP LaserJet driver.  The (portrait) orientation escape was previously included in the font keys, although landscape orientation was not a supported feature of the 2.0 LaserJet driver.  The widths for the Tims and Helv fonts were correct for the F cartridge, not the B cartridge, even though the B cartridge was called for in the mount messages.
For sheet feeder support, specify SheetFeeder:Hp500 or SheetFeeder:Ziyad in the device setup field of the Print Manager device installation form.  These setups support, respectively, the HP 500 (sheet feeder built in) and the Ziyad sheet feeder.  SheetFeeder: can be abbreviated to Feed:.
Bin number can be specified in Document Designer from the Page Attributes menu.  Bin 1 selects the top or internal bin, Bin 2 selects the bottom or first external bin and Bin 3 selects envelope feed.  The Ziyad sheet feeder has an automatic envelop feeder which will be used when Bin 3 is selected; on other printers the manual feed slot is used for envelopes.  When the Printer is ready to accept an envelope it will flash PE on the display.  Insert an envelope and it will automatically be accepted.  
Page length is sent to the HP LaserJet so that it can check for the presence of the correct paper tray.  For example, the HP LaserJet will display UC and LL and wait for the legal tray to be installed (assuming it isn't already installed) if a 14 inch page is printed.  Dimensions of individual pages can be specified in Document Designer.  Dimensions specified in the device installation form will be applied to all ordinary ASCII (nonGPAM) documents.
If manual feed is requested in a print job (e.g., in the Paper Feed field of the Document Designer Print command form), the device driver does not pause.  Instead the printer displays L and PF on the display.  Simply place paper in the manaul feed slot.  If the user presses the the continue key on the printer, it will take paper from the current bin.
Depending upon the amount of memory in a LaserJet printer and the complexity of a page, graphics can cause the LaserJet to overflow its memory.  The image will print on 2 separate sheets of paper and the printer will show status 20 on its display.  This is avoided by printing the graphics at a lower resolution.  The LaserJet driver will by default generate graphics at 75 dots per inch, which will avoid this problem.  If a printer has additional memory or typical print jobs contain fairly simple graphics, the driver can be configured to generate higher resolutions (100, 150 or 300 dots per inch).  Enter Resolution:100 (or Res:100), Resolution:150 or Resolution:300 in the Device Setup field of the device installation form.  Recommended resolutions for various HP LaserJet models are shown below.
Model	guaranteed to work	may work
LaserJet	75 dpi	100 dpi
LaserJet+	150 dpi	300 dpi
Series II	150 dpi	300 dpi
Series II with extended memory	300 dpi	
A lower resolution may be chosen to reduce the time spent printing graphics.  A full page takes about 30 sec at 100 dpi and more than 4 minutes at 300 dpi.
{10.3.5	Imagen Device Driver.
}The default font devicetype for the Imagen driver is Imagen.  The standard font database is built assuming that the optional Times and Helvetica font ROM is installed in the Imagen IP3.  This provides Times and Helvetica in three styles (Roman, Bold, Italic) in a range of point sizes from 6 to 36 points.  Courier is available in a range of point sizes from 7 to 14 points.  Courier Bold is available in 10 and 12 point.
The editable database also includes font descriptions for font sizes which were not included in this font ROM, and for Lucida and Lucida Sans fonts.  If a user has a different font ROM installed, or has assembled a font diskette for use with the IP2, the reduction table in the font database should be modified to map all font descriptions to those actually available.  If these families are available, Gen? should be changed to Yes for Lucida and Lucida Sans font families.  If differently configured Imagens are available in the same environment, more than one device type for Imagen should be created.
The bold attribute is used by the Imagen driver for font selection only.  If a bold font is not available, a nonbold font is substituted.  This version of the Imagen driver no longer attempts to overprint to simulate bold.
The font key alias for Imagen fonts contains the name of the font as it is known to the Imagen.  This name usually consists of an abbreviation for the family name, followed by a letter indicating the style (r=roman, b=bold and i=italic), followed by the size, strung together without spaces, as in helvi18.
It is possible to specify more fonts than the Imagen printer can print in a single document.  This usually results in the text for the overflowed fonts appearing as white areas on the page.  If the Imagen job header is enabled, Status messages will be listed on a trailer page concerning the fonts that could not be defined and the glyphs (characters) that could not be printed.  If this happens, the user should either (1) reduce the number of fonts used in the document or (2) break the document into a number of smaller documents.
The Imagen driver is designed to support either the IP2 or IP3 printer products.  Because the resolution (pixel size) of these two models are different, IP2 should be entered into the Device Setup field of the installation form when installing for the IP2.  Otherwise graphics are generated for the IP3 resolution.
When cancelling a job on the Imagen printer, it is sometimes possible to cause a paper jam in the printer.  This is caused by a timing inconsistency between the Imagen image processor and the marking engine.  If this happens, open the marking engine by lifting the green lever on the right side of the marking engine and clearing any paper in the paper path.
{ImagenDriver Status Codes
Code	Meaning                                
}15300	The document specifies more distinct fonts than can be output in one document by this device driver.  Reduce the number of fonts in the document.  Note that this error indicates an overflow in the device driver's internal table.  The printer usually overflows its own font table long before the device driver does.  The device driver makes no attempt to predict when the printer will overflow, and no error message is reported by GPS when the printer overflows its memory.
15301	An erroneous 2ndleveltranslation value has been encountered in the Font Database's fonttranslation data for the Imagen printer.  Verify that the Imagen device driver was installed with a valid Font Device Type string (leaving this field blank will cause the correct font data to be used if the Convergentsupplied Font Database is being used).  Use the Font Tool to correct the Imagen's translation data in the Font Database.
15303	The document requires more Imagenprinter Families than can be used at one time.  Reduce the number of fonts in the document.
15304	The document requires more Imagenprinter Maps than can be used at one time.  Reduce the number of fonts in the document.
{10.3.6	PostScript Driver.
}The default fontdevice type for the PostScript driver is PostScript.  The standard runtime font database includes font data for Times, Helvetica, and Courier.  These fonts are available in all sizes that can be specified by the application program (they are dynamically scaled by PostScript) and in all style combinations (Roman, Italic, Bold and Bold Italic).  These are the fonts that are available in all PostScript devices.  In addition, the editable font database (.port files in this release) contains font data for many other PostScript fonts which are available on some PostScript devices.  Users who have additional fonts available to their PostScript printers should generate a font database which includes the relevant font families.  It will be necessary to add reduction rules to the font database, if this is done, that define what fonts should be used in place of these families on other devices.
The first word (delimited by a space) of the font key alias is the name of the font as it is known by PostScript.  The remainder of the alias (if anything remains) is considered to be the name of a font cartridge which the user will be prompted to mount.  If there are replaceable PostScript font cartridges available, the user should modify the appropriate font keys and perform the other necessary steps to generate a font database to support these cartridges.
By default the PostScript driver emulates Art Designer line types for graphics.  If line types in the style of the Imagen device driver are desired instead, enter Lines:Imagen into the Device Setup field of the Print Manager device installation form.
Page length is used to instruct the TI2115 to search for whichever bin has a paper tray of the appropriate size.  Letter, A4 and legal sizes are recognized.  Dimensions of individual pages can be specified in Document Designer.  Dimensions specified in the device installation form will be applied to all ordinary ASCII (nonGPAM) documents.
Bin number, for the TI2115, can be specified in Document Designer from the Page Attributes menu.  Bin 2 selects the lower tray and Bin 3 selects the upper tray.  Bin 1 causes either tray to be used, according to which has the correct paper tray (see above).  The upper tray is used if there is no difference.
{10.3.7	Simple Device Driver.
}The default Font Device Type of the Simple driver is Simple.  The standard font database reduces all fonts for the Simple driver to 12 point (10 pitch) Courier.  The only printable characters output are those in the ASCII range (21 to 7E hex).
However, the simple device driver is designed to support more sophisticated character translation and font selection, providing that such information specific to an individual printer is added to the font database.  If this is done, it is advised that a distinct font device type should be used.  The simple driver parses the font key alias according to the same rules as the Daisy driver.  Printers on which different pitches can be selected by an escape sequence could utilize this feature.  Different point sizes could select different font keys, which in turn could specify the appropriate escape sequence (in the alias) to set the printer's pitch.  The pitch (character width) selected must also be entered into the font key (e.g., 7212 for 12 pitch) so that Document Designer and the simple driver understand what pitch is in effect.
This driver assumes that text is printed six lines to the inch.  Horizontal pitch is determined by information retrieved from the Font Database.  Within those parameters, this device driver will place text upon the page as near to its requested location as possible.  Truly desirable results can only be obtained by specifying character and line spacings that fit these constraints when formatting the document.
10.4	Configuring PostScript printers
PostScript printers are designed to abort a print job when data is not received after a period of time.  This will occur, for example, if a print job is paused and not restarted in a timely fashion.  When restarted, the remainder of the job will be ignored by the printer.  This feature is intended as a technique for recovering the printer when a job has been canceled by the host computer.
The standard period of time that a printer will wait for data (called waittimeout) is 30 seconds.  The printer will abort the job after 30 seconds:
	when the device driver has been paused by a user, 
	when a device driver reports the device offline and is not restarted as soon as (or before) the device is ready again,
	when the device driver is too slow to keep up with the printer.  
The last case can occur because the device driver does not have sufficient font table space to efficiently process the document, due to the number of fonts and frequency of font changes.  If this occurs, the device driver should be installed with a larger font table space.
The PostScript printers will also abort a print job if it has to wait too long for paper to be inserted into the manual feed slot, or for the paper tray to be loaded.  The default value for this parameter (called manualfeedtimeout) is 60 seconds.
The standard values for these wait times are probably too short.  Convergent recommends changing these values by sending a PostScript program to the printer.  The following program sets manualfeedtimeout to 15 minutes (900 seconds) and waittimeout to 20 minutes (1200 seconds):
serverdict begin 0 exitserver
statusdict begin
25 9600 7 setsccbatch
0 900 1200 setdefaulttimeouts
start
If you have installed the PostScript driver, the above program can be found in the GPS directory under the name Setup.ps.  The above program can be sent to the printer by printing [sys]<GPS>Setup.ps in binary mode.  If you print this file in normal (ASCII) mode, it will merely print out the program.  You must print the file in binary mode, in order for the PostScript printer to execute the program.  The printer will not print anything when executing this program.  
This program can be modified by replacing the values 900 and 1200 with values deemed appropriate in the user environment.  The value of 0 in either position completely disables the respective timeout value, so that the printer will wait indefinitely.
Notice also that the third line of the program (containing the command setsccbatch) sets certain PostScript printers to use CTSDTR handshaking, as opposed to XONOFF.  This line can be removed from the program.  It is included here since Convergent recommends use of CTSDTR with supported PostScript printers.
{11.0	Documentation Updates
11.1	Standard Documentation
The Generic Print System is documented in the Printing Guide (DA170).  The GPS Programmer's Guide documents GPS and GPAM interfaces for use by application programmers.}
{11.2	Changes to Documentation
}The first edition of the Printing Guide (part number 090096701) has several errors and omissions.  These defects are fixed  with Update Notices 1 and  2 to the Printing Guide (part numbers 7300161A and 7300161B).  
{12.0	Status Codes
}Consult Update Notice 2 to the Printing Guide (part number 7300161B) for a list of 2.1 GPS status codes.  There have been few significant changes in 2.1 GPS concerning status codes.  A number of status codes indicating internal errors have been eliminated (now denoted as reserved).
{One significant status code may be encountered in 2.1 GPS, under normal circumstances, that was previously documented as an internal error.  In 2.0 Generic Print, when font table storage in the device driver was exhausted, due to the sheer number of fonts in a document, another font was arbitrarily substituted.  This resulted in incorrect spacing and other unpredictable and undesirable results.  In 2.1 device drivers, the print job will abort with an error code of 15333 when the font table space is exhausted.  When this occurs, it is necessary to reinstall the device driver, specifying a larger value for Font Data Table Size in order to print the affected document.}
{13.0	Known Errors and Omissions.
}System service installation may hang due to insufficient CTOS resources.  Section 8.3 describes the CTOS resources needed in order for the GPS system services to install properly.  If these resources are unavailable, it is possible that the system may hang during the installation process.  Contact Technical Support for instructions on Sysgening an operating system with the appropriate resources.
System Service installation may hang due to a CTOS deadlock.  A file system timing deadlock which can occur during the installation of system services, will cause the system to hang.  This happens most frequently when several system services are rapidly installed on a system.  If this is a frequent problem on your system, remove the automatic installation of GPS from the .jcl file and install the GPS system services manually from the Print Manager.  This problem is corrected in CTOS 9.8 and in CTOSVM.
Deinstalling GPS when a print job is paused or offline will hang the Print Manager.  Drivers installed for spooled printing can be safely deinstalled while printing.  The workaround is to restart all spooled printers and to cancel all active jobs for direct printers, before attempting to deinstall GPS.
Deinstalling GPS when a driver installed for direct printing is printing, may hang the PrintManager.  The workaround is to cancel all active direct print jobs, before attempting to deinstall GPS.
{A delay is required after device installation failure.  If a device installation fails due to incorrect parameters, for example, it is necessary to wait 45 seconds before reattempting the installation with corrected parameters.  This delay is required so that the Routing Switch at the master workstation can eliminate duplicate entries in its internal tables.  Failure to wait the 45 seconds can cause an error code 4586 to be returned.}
Text and graphics may overlap on the Imagen, if textual data is placed close to a graphic object which is at the right edge of a page.  This is due to the fact that the resolution of the printer is not exactly 300 dpi and is not quite square.  Graphics are scaled to account for this discrepancy but the textual fonts, imbedded in the printer, cannot be scaled.  The workaround is to increase the border on the left side of the graphical object, allowing more space between the objects.
An application that terminates with an outstanding GetGpsStatus request can cause the system to hang. The following sequence will cause the system to hang 3 out of 10 times. From a workstation, use Document Designer to print to a printer installed at the master such that the printer will go offline. Wait until the printer alert is displayed by DD, but don't go to the print menu. Instead, service the printer and restart from a Print Manager on another workstation. Wait until the job completes. Exit DD. The OS hangs on an outstanding request to the master.
More than two drivers installed on an AWS may cause it to crash with erc 430 (no memory available to load the exit run file).