
CONVERGENT TECHNOLOGIES

RELEASE NOTICE FOR
2.3.1 Generic Print System (SAA1401)

June 15, 1989

SECTION   TITLE	PAGE
	Introduction	3
1.0	Description of Programs	4
2.0	Changes from Prior Version	7
2.1	Problems Closed in this Release	7
2.2	Changes from Release 2.2	9
3.0	Contents of Distribution Diskettes	13
4.0	Distribution Installation Procedures	21
4.1	Preparing for Installation	21
4.2	Installing GPS from the Installation Diskettes	23
4.2.1	Cluster Workstations	24
4.2.2	Master Hard Disk Systems	24
4.2.3	StandAlone Hard Disk Systems	25
4.3	Installing GPS on a Workstation from the Master	26
4.4	StandAlone Floppy Disk Systems	27
4.5	Configuring the Context Manager	27
5.0	System Service Installation Procedures	27
5.1	Installing the Font Service	28
5.2	Installing the Queue Manager	29
5.3	Installing the Print Service	29
5.4	Installing Printing devices for the First Time	30
5.5	GPS Service Installation on the SRP 	31
6.0	Required Files	32
7.0	System Software Compatibility	34
7.1	Workstation Environment	35
7.2	Diskless Workstations	35
7.3	Shared Resource Processor	35
8.0	Hardware Information	35
8.1	Hardware Configurations Supported	35
8.2	Special Hardware Requirements	36
9.0	Resource Requirements	36
9.1	Memory Requirements	36
9.2	Disk Requirements	37
9.3	CTOS Resource Requirements	38
9.4	Tuning Device Driver and Font Service Buffers	39
9.5	Device driver overlays	43
9.6	Tuning Networked Print Services	44
10.0	Restrictions	45
11.0	Supplementary Information	49
11.1	Nationalization	49
11.2	User File Additions	50
11.3	Use With PreGPS Applications	50
11.4	Devicespecific Fonts and Features	51
11.4.1	Binary Mode Driver	52
11.4.2	CT Matrix Driver	52
11.4.3	Daisy Driver	53
11.4.4	Epson Device Driver	54
11.4.5	HP LaserJet Driver	55
11.4.6	Imagen Device Driver.	58
11.4.7	PostScript Driver.	60
11.4.8	Simple Device Driver.	61
11.5	Configuring PostScript printers	61
12.0	Documentation Updates	63
12.1	Standard Documentation	63
12.2	Changes to Documentation	63
12.2.1	The Generic Print System Programmer's Guide	63
12.2.2	The Using the Font Tool Manual	68
13.0	Status Codes	68
14.0	Known Errors and Omissions.	69
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 that 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, on each node of the network.
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, GPAM files (such as those created by the Document Designer Print command) or TIFF files (such as those created by Image Designer), should be printed in ASCII mode.  The device driver automatically recognizes whether a file printed in ASCII mode is a GPAM file or a TIFF 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 not resident on 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 processed.
The Print Service, GpsPsMstr.run, GpsPsClstr.run or GpsPsStndAln.run is the program procedural interface to GPS.  The Print Service serves requests for printing services.  Application requests are served by the nearest Print Service (either local to the workstation or at the master), checked for validity, and then forwarded as required to another GPS service for processing.  A Print Service 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 Gps install program, GpsInstall.run automatically  launches the correct run file for the workstation.
The Print Service provides simultaneous access to shared devices by spooling.  Spooling allows different users to queue their print jobs to temporary disk storage, freeing the workstation to do productive work while waiting for the printing device to become available and print the job.  The Print Service 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 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 eight device classes:
(1)	The CT Matrix driver, CTMatrixDD.run, translates print jobs into the DPL24C language recognized by the 2400 series of matrix printers sold by Convergent.  This driver supports both color and monochrome graphics.  It provides Courier and Draft fonts in six sizes of four styles and a Proportional font in three sizes of four styles.  (From Document Designer, select Cubic PS or any other proportional font to get the proportional font when printing).  The larger sizes (20 and 24 point) are double the height of the standard sizes (10 and 12 point), which is accomplished with multiple passes of the print head.  It also supports underlining, strike out, and alternate ribbon.
(2)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.
(3)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.  It maps colors of solid, halftone and quartertone fill patterns to appropriate gray levels.  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.}
(4)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.  It will download fonts, as needed, if instructed by the font database.  The LaserJet driver supports graphics and landscape printing.  It maps colors of solid, halftone and quartertone fill patterns to appropriate gray levels.  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.
This device driver has been qualified with the LZ5, LZ12 and LZ18 printers sold by Convergent.  The font database contains font device types for the resident fonts which are present on each of these printers.
(5)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 following printers:  QMSPS800, Texas Instruments 2115, LaserWriter and LaserWriter Plus.  It is likely to work on other PostScript printers, although the above listed printers 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.
(6)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 supports monochrome and color graphics.

NOTE:  There are many different Epson printer models and many other printers that claim Epson compatibility.  Only the FX286 and Honeywell Bull 441 models have been fully tested with this device driver.  Other printers are not guaranteed to work.
(7)The Binary Mode device driver, BinaryModeDD.run, is provided to make a device driver of minimal size (27Kb) available for 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.
(8)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 seven.
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 Using the Font Tool Manual.
{2.0	Changes from Prior Version
All 2.0, 2.1 and 2.2 Device Drivers are compatible with 2.3.1 GPS.  Any device driver developed using 2.0, 2.1 or 2.2 PrintGen can be run under 2.3.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.3.1 PrintGen.  Little or no source changes will be required to rebuild a 2.2based device driver with 2.3.1 PrintGen.  Consult the 2.3.1 PrintGen engineering update for further information.
The SamGenGpam.obj module has been removed from Gpam.lib.
To take advantage of the size reduction in memory of the GPS services and the reduction in the time required to spool print jobs, version 2.3.1 GPS must be installed at the master and all workstations with printers in the cluster.  However versions 2.2 and 2.3.1 can be run at different workstations on the same cluster at the performance level of 2.2.
2.1	Problems Closed in this Release
11591	The Detail screen in the Print Manager would only display the job parameters of the current job printing and not that of the selected job waiting in the queue.
13098	GPS installation would overwrite Font.dbs.  If it exists, the file is now renamed to Font.dbsold.
13123	Device drivers cannot be deinstalled without deinstalling all GPS services.
13553	In the Font Tool, inserting a record into one of the lists of ISAM records would cause error code 3704 to be displayed, returning to the main menu, if the end of the list was visible.
13565	Same as 13123.
14290	GPS did not install spooled devices sharing the same queue name on different SRP boards.
14388	The request, QueueGpsFile, did not work.
14462	The HP LaserJet driver would loop on certain print jobs unless the SwapArea was made larger than the default.
14463	The cursor on the Status screen of Print Manager would remain on a blank line instead of tracking its position as the job moved up the queue.
14465	Same as 11591.
14500	Imagen Driver: The line type for a polyline which collapses on a single point might be propagated back to the prior polyline.  
14511	PrintGen 2.2 did not work with standard software 11.3, but only 11.2, because SamGenDd.asm was assembled with the 11.2 version of SamGen.mdf.
14530	Same as 14511.
14832	Printing a small scanned image (from 9 to 16 pixels wide) would cause a GPS device driver to crash or GP fault.
14842	Generating a font database including a large number of device types and families (e.g., at least 16 devices and 16 families or 8 devices and 32 families) would fail during hash bucket allocation andor cause the Font Tool to crash.
14902	Using the Update function while in Master Mode could corrupt the Board ID field, causing the device driver to be installed on the wrong board the next time the SRP master is rebooted.
14940	PostScript Driver: The fill pattern for a polygon which collapses on a single point might be propagated back to the prior polygon.  
14950	GPS installation from sysinit.jcl could fail if the user file for the user name specified in sysinit.jcl did not exist.
14960	Several blank pages, (3 or more) caused a PostScript print job to job to abort (inside the printer), with no error message.
15033	With 9.9 or 9.10 CTOS, GPS would not report a password violation when installing device drivers from volumes requiring passwords.
(none)	Occasionally the PostScript device driver failed to draw a polyline, when the previous polyline began on the same point.  For example, the curved part of the capital D in the standard font might be dropped.  
(none)	Borders of landscape pages were incorrectly computed on landscape pages when the borders were not symmetrical (as in the Imagen driver), possibly leading to truncation of text printed from applications like spreadsheets.  
(none)	When duplicate device names were used at different CTNet nodes, error 5117 was displayed as the status.
(none)	Print Manager was unable to operate when pathed to a remote CTNet node.
{2.2	Changes from Release 2.2
}The GPS Spooler and Routing Switch have been combined into a single program called the Print Service.  There are three versions of the Print Service which are designed for use on master workstations or SRP, for cluster workstations, and for standalone workstations.  The correct run file is automatically loaded by the GPS installer.  These versions of the Print Service are 20K to 35K smaller than the sum of the 2.2 Spooler and Routing Switch.  The Print Service may be externally nationalized, via the message file, GpsPsMsg.bin
Whenever possible, Print jobs are now spooled at the master workstation, rather than at the workstation where the printer is installed.  Additionally, whenever possible, the Print Manager will queue files directly instead of copying them.  These enhancements greatly reduce the time required to spool a print job from another workstation, especially when the printer resides at a diskless workstation.  Communication performance has been improved between the Print Service at a master and the Print Service located on a cluster workstation with a printer attached.
The 2.3.1 Print Service will operate in a compatible fashion with 2.1 and 2.2 Routing Switches and Spoolers, regardless of where they are installed (CTNet remote, master, cluster).  
Print Manager:  can deinstall individual device drivers without disturbing other GPS services.  Function keys on the Admin form that install individual services have been replaced by function keys labeled Install and DeInst.  These keys install or deinstall whichever service is highlighted.  The Queue Manager, Font Service or individual device drivers may be installed or deinstalled independently of one another.  Deinstalling the Print Service will cause all local device drivers to be deinstalled.  It is no longer necessary to wait 45 seconds, before reattempting a failed installation.  If the Queue Manager is deinstalled when spooled printers are in service, it will take about 30 seconds for the Print Service to reestablish spooled service automatically.  The Admin form only displays printers that are installed at the local workstation.
The Print, Queue and Status functions are now available directly from the Admin Form.  Banner pages may be selected for direct printers.  The Home form has been simplified by removing the User field.  This provides more room for the Location field entries to be read.
An Append key has been added to the DevHelp form so that the existing customized Device Help file can be appended with the Default Device Help file installed with GPS.
GPS Installer:  The GPS installer program is now externally nationalized, via the same message file, GpsPmMsg.bin, which is used by the Print Manager.
CT Matrix driver:  has been implemented, which supports the 2400 series (CT2425, CT2450 and CT2475) of dot matrix printers sold by Convergent.  This driver utilizes the DPL24C printer language, and may work with other dot matrix printers which implement that language, such as those manufactured by Fujitsu.  These printers are 24pin printers with 180 dpi resolution in both dimensions.  They have a wider variety of fonts than are available on the Epson FX286 printer, including double height, double width fonts (i.e., 20 or 24 point), and proportional fonts (select Cubic PS 96 or any other proportional font to use).  The CT Matrix driver also supports color printing on devices equipped with 4color ribbons.  It will print vector graphics from a pallete of over 150 colors, and it supports print of text in an alternate ribbon (red).
Imagen device driver:  has been overlayed, resulting in a reduction of memory consumed.  It now simulates colored fills by use of a halftone spot pattern which simulates that perceived gray level of individual colors.
HP LaserJet device driver:  The dither pattern used for colored fills has been modified to a halftone spot pattern which photocopies better than the old dither patterns and is more like the fill patterns obtained from PostScript printers.  At 150 dpi and up, the HP Laser Jet, along with the Imagen and CT Matrix drivers, uses a 4x8 spot pattern with 31 levels of gray.  At lower resolutions, the HP LaserJet driver, along with the Epson driver, uses a 2x4 spot pattern with 9 levels of gray.  The HP LaserJet driver now supports downloading of required font files on the fly.  The font files themselves are not sold by Convergent but are widely available and should be acquired from an authorized vendor.  Section 11.4.5 of this document describes how downloadable font files are specified within the font database.
Epson device driver:  has been overlayed, resulting in a reduction of memory consumed.  The 2.2 Epson driver previously microshifted the paper in order to output graphics at 240 by 216 dpi.  However, the actual dot size of the Epson printer is much too big to represent graphics at that resolution.  The resulting spot overlap caused gray areas in images to completely blacken, and caused undue wear on the print ribbon and paper.  The driver now outputs graphics at the natural resolution of the printer, 120 by 72 dpi.  This change also speeds up graphics output and reduces the memory required by the driver.  It makes possible the output of over 150 colors now supported by this driver, when used with a compatible model of printer equipped with a 4color ribbon.
Device Driver Overlays:  All graphical device drivers (CT Matrix, Epson, Imagen, LaserJet, and PostScript) have been overlayed, resulting in net reductions in size.  Previously, only the LaserJet driver was overlayed.  The overlay architecture has been improved, so that even the LaserJet driver is smaller than before.
Messages used by the device driver core are now nationalized by the message file GpsDdMsg.bin.
The Font Tool now generates all required reduction rules automatically, so that in most circumstances it is unnecessary to create or modify reduction rules.  However, if you wish to specify your own reduction rules, these will override those which the Font Tool might otherwise invent.  The Font Tool looks at the keys present in the Font database to determine which reduction rules to create.  It will supply a reduction rule to change the font family if no font key for a given familydevice combination exists.  Otherwise, it will reduce missing sizes to the nearest smaller size for which a font key (in that family) is present.  Lastly it will reduce missing style combinations to a style combination which exists at the nearest size.  The Font Tool will apply the widest possible scope to the reduction rules which it generates, in order to minimize the size of the reduction table it generates.  (E.g., if there is no Bold Italic face of any font for a given device type, a single reduction rule is generated to map Bold Italic to Italic, regardless of the family and size).  If any of these reduction rules are unnecessary because of rules which are explicitly listed in the Reduction Table, they will be omitted from the generated database.
The Auto generate key has been removed from the Font Key list, because this feature is inconsistent with the automatic generation of the Reduction table.  (Instead of deducing required font keys from explicitly listed reduction rules, the Font Tool now induces the required reduction rules from the explicitly listed font keys).
The Font Tool now supports variant databases.  Variant databases serve to isolate your changes to the font database from the underlying font data distributed by Convergent.  This makes it easier to update a customized font database when information in future releases of GPS must be merged into it, as you are able to insure that records which you have already modified are not overwritten.  It also makes it easier to create export files for specific additions you have implemented to the font database (such as support for specific device drivers or font cartridges).
The second parameter to the Font Tool is the name of a variant database to create, modify or read.  It is used as a prefix applied to variant files.  Variant files contain exceptions (changes, additions, and deletions) to the invariant (underlying) font database.  All changes made to the variant font database are recorded in the variant files.  Variations are signified by a '+' symbol next to the record in the appropriate list.  The Revert function key can be used within a variant database to discard a modification to the database (restore a record from the invariant database).  The Export Variant command will export only the variant portion of a font database.  
The new manual, Using the Font Tool, should be purchased by customers who need to use the Font Tool.  It provides more information on the new features, as well as a more comprehensive discussion of the capabilities of the product than was previously available.
Gpam.lib:  TIFF (raster) images can now be incorporated into GPAM files you create.  The procedures GPAMBeginRaster and GPAMEndRaster, which were already present in the GPAM library, but which were ignored by GPS device drivers, are now supported by GPS device drivers.  Only GPAMWriteRecord calls may be made following GPAMBeginRaster, until GPAMEndRaster is called.  The matter included in these GPAMWriteRecord calls must consist of a TIFF image.  That is to say, your application can read a TIFF file from disk and copy it into the GPAM file via a series of GPAMWriteRecord calls, delimited by the GPAMBeginRaster and GPAMEndRaster calls.  GPAMBeginRaster takes the same parameters as the GPAMGrBeginGraphics call, namely a pointer to the GPAM work area, the width and height (word values) of the image (expressed in 1440ths of an inch), and a flag, fClear, which is ignored.  GPAMEndRaster takes only a pointer to the GPAM work area.  If the width and height values are zero, the width and height of the image will be derived from the size of the image in pixels and the resolution of the printer.  TIFF files can be created using the Image Designer, or by using the CCGI+ library which will be released in the near future.
The SamGenGpam module has been removed from Gpam.lib.  GPS byte streams have been enabled in the SamGenAll, in CTOS.lib, in the last several releases of Standard Software.  The presence of this redundant module caused link conflicts, if it was not paired with the corresponding version of CTOS.lib.  See the Generic Print System Programmer's Guide for detailed information about inclusion and configuration of byte streams in GPS applications.
The call GetGpsParams has been added to allow applications to get job parameter information about jobs being spooled.  QueueGpsFile has been implemented, which allows an application to queue a file to be printed without copying it, and specify whether it should be deleted following printing.  QueueGpsFile is intended for use with only spooled  printers.  The call QueryGpsFile has been added to allow applications to determine whether a file is directly accessible to a printer, for use with the call QueueGpsFile.  The GetGpsNetList call has been enhanced to provide current information on installed devices only (i.e. those available to the requesting user).  
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 Print Service
	GPS 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 run files 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 spans 9 of the 10 release diskettes.  On each diskette is an extent of this file, named .01, through .09, 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 10 and 9 of 10, 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 editable form of this document is on the last diskette.  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	FontToolMsg.bin
System Services, linked V4, in directory GPS:
mBinaryModeDD.run	mCTMatrixDD.run
mDaisyDD.run	mEpFx286DD.run	
mGpsInstall.run	mGpsPsMstr.run
mGpsPsClstr.run	mGpsPsStndAln.run
mHPLaserJetDD.run	mImagen8300DD.run
mLptSimpleDD.run	mPSDD.run
Pipe Drivers, in directory GPS:
CTMatrixPipe.run	DaisyPipe.run	
EpFx286Pipe.run	HPLaserJetPipe.run	
Imagen8300Pipe.run	LptSimplePipe.run	
PSPipe.run	CTMatrix.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	IGpsFontServer.fls	
IGpsPrintersV4.fls	IGpsPrintersV6.fls
IGpsWSmin.fls	ISysFontServerV4.fls
ISysFontServerV6.fls	ISysFontTool.fls
ISysWSmin.fls	Lfs.sub
LfsInstall.sub	mgRqIFontTool.sub	
mgRqIIFontTool.sub	mgRqIInoFontTool.sub	
mgRqInoFontTool.sub	PMCmInstall.sub
Standard (V6) Device Drivers, in directory GPS:
BinaryModeDD.run	CTMatrixDD.run
DaisyDD.run	EpFx286DD.run	
HPLaserJetDD.run	Imagen8300DD.run	
LptSimpleDD.run	PSDD.run
GpsDdMsg.bin	GpsDdMsg.txt
System services, in directory GPS:
Font.dbs	GpsInstall.run
GpsPsMsg.bin	GpsPsMsg.txt
GpsPsMstr.run	GpsPsClstr.run	
GpsPsStndAln.run
System services, in directory SYS:
DeinstallFS.run	mFontService.run
FontService.run
Print Manager, in directory GPS:
GpsForms.lib	GpsPm.run
GpsPmMsg.txt	GpsPmMsg.bin
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 10 files:
Directory <Sys>
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
IFontDB.fls
ISysFontTool.fls
ISysWSmin.fls
Restore.sub
Res1.sub
Res2.sub
Res3.sub
Res4.sub
Res5.sub
Res6.sub
Res7.sub
Res8.sub
SRP.fls
.01
Archive file .01 contains:
<Gps>Gpam.lib
<Gps>Gpam.pas
<Gps>GpamProcs.edf
<Gps>GpamTypes.edf
<Gps>GpsBs.pas
<Gps>GpsProcs.edf
<Gps>GpsTypes.edf
<Gps>Graphics.c
<Gps>LinkGpam.sub
<Gps>LinkGpsBs.sub
<Gps>LinkGraphics.sub
<Gps>GpsPsMsg.txt
<Gps>GpsPmMsg.txt
<Gps>GpsDdMsg.txt
<Sys>FontToolMsg.txt
<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 ...
{Diskette 2 of 10 files:
Directory <Sys>	.02
Archive file .02 contains:
}<FontDB>FontWidth.port
<FontDB>Script
<FontDB>TextSet.Font
<FontDB>VM003TextSet.Font
<Sys>FontForms.lib
<Sys>FontIsam.config
<Sys>FontTool.run
<Sys>FontToolMsg.bin
<Gps>mGpsPsMstr.run
<Gps>mGpsPsStndAln.run ...
Diskette 3 of 10 files:
Directory <Sys>	.03
Archive file .03 contains:
<Gps>mGpsPsStndAln.run
<Gps>mGpsPsClstr.run
<Gps>mGpsInstall.run
<Gps>mBinaryModeDD.run
<Gps>mDaisyDD.run
<Gps>mEpFx286DD.run
<Gps>mHpLaserJetDD.run
<Gps>mImagen8300DD.run ...
Diskette 4 of 10 files:
Directory <Sys>	.04
Archive file .04 contains:
<Gps>mImagen8300DD.run
<Gps>mLptSimpleDD.run
<Gps>mPSDD.run
<Gps>mCTMatrixDD.run
<Gps>DaisyPipe.run
<Gps>EpFx286Pipe.run ...
Diskette 5 of 10 files:
Directory <Sys>	.05
Archive file .05 contains:
<Gps>EpFx286Pipe.run
<Gps>HpLaserJetPipe.run
<Gps>Imagen8300Pipe.run
<Gps>LptSimplePipe.run
<Gps>PSPipe.run ...
{Diskette 6 of 10 files:
Directory <Sys>	.06
Archive file .06 contains:
}<Gps>PSPipe.run
<Gps>CTMatrixPipe.run
<Gps>CmdFontServer.sub
<Gps>CmdFontServerV4.sub
<Gps>CmdFontServerV6.sub
<Gps>CmdFontTool.sub
<Gps>CmdNoFontServer.sub
<Gps>CmdNoFontTool.sub
<Gps>CmdNoPrinters.sub
<Gps>CmdPipeDrivers.sub
<Gps>CmdNoPipeDrivers.sub
<gps>CmdPrinters.sub	
<Gps>CmdPrintersV4.sub	
<Gps>CmdPrintersV6.sub
<Gps>GpsHdInstall.run	
<Gps>IFontDB.fls
<Gps>IGpsGpam.fls	
<Gps>IGpsPrintersV4.fls	
<Gps>IGpsPrintersV6.fls
<Gps>IGpsWSmin.fls	
<Gps>ISysFontServerV4.fls
<Gps>ISysFontServerV6.fls	
<Gps>ISysFontTool.fls
<Gps>ISysWSmin.fls	
<Gps>Lfs.sub
<Gps>LfsEditFontData.sub	
<Gps>LfsInstall.sub
<Gps>LfsInstallFontTool.sub	
<Gps>LfsInstallNoFontTool.sub
<Gps>mgRqIFontTool.sub	
<Gps>mgRqIIFontTool.sub
<Gps>mgRqIInoFontTool.sub	
<Gps>mgRqInoFontTool.sub
<Gps>PMCmInstall.sub	
<Gps>BinaryModeDD.run
<Gps>DaisyDD.run	
<Gps>EpFx286DD.run ...
Diskette 7 of 10 files:
Directory <Sys>	.07
Archive file .07 contains:
<Gps>EpFx286DD.run
<Gps>HpLaserJetDD.run	
<Gps>Imagen8300DD.run
<Gps>LptSimpleDD.run
<Gps>PSDD.run
<Gps>setup.ps
<Gps>CTMatrixDD.run ...
Diskette 8 of 10 files:
Directory <Sys>	.08
Archive file .08 contains:
<Gps>CTMatrixDD.run
<Gops>GpsDdMsg.bin
<Gps>GpsPsClstr.run
<Gps>GpsPsStndAln.run
<Sys>mRequest.Q.sys
<Gps>SRPInitCPxx.jcl	
<Gps>SRPInitFPxx.jcl
<Gps>GpsPsMstr.run
<Sys>mFontService.run
<Gps>GpsPsMsg.bin
<Gps>GpsInstall.run
<Sys>FontService.run
<Gps>Font.dbs
<Sys>DeinstallFS.run
<Gps>DefaultDevHelp ...
{Diskette 9 of 10 files:
Directory <Sys>
}.09
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.Q.sys
Request.I.sys
Archive file .09 contains:
<Gps>DefaultDevHelp
<Gps>GpsForms.lib
<Gps>GpsPmMsg.bin
<Gps>GpsPm.run
<Sys>Gps.user
Diskette 10 of 10 files:
Directory <RelNote>	Gps.RelNote

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 run file 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 5.1 of this document for further information about the font database.
GpsPm.run is the run file for the Print Manager, the user interface to GPS.  This program is used to install or deinstall GPS services and to monitor their functions.  The files GpsForms.lib and GpsPmMsg.bin are needed for Print Manager operation.  GpsInstall.run is the run file 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.  The file GpsPmMsg.bin is also used by GpsInstall.run.
GpsPsMstr.run, GpsPsClstr.run and GpsPsStndAln.run are the run files for the Print Service, 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.  The program also spools and despools files for printing.  The file GpsPsMsg.bin is needed for Print Service operation.
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 file lfs.sub and those transferred from Diskettes 1 of 10 and 9 of 10 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.Q.sys is the loadable request file that needs 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.  In GPS 2.3.1, the GPS request code information has been removed from Request.9.Sys, where it formerly resided along with the request code information for the Queue Manager.  Request.I.sys is the loadablerequest file for the ISAM server, that is needed only 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, CTMatrixDD.run are the run files 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.  The file GpsDdMsg.bin is needed for Device Driver Service operation.  Further details about the device drivers are contained in section 11.4.
Gps.RelNote in the <RelNote> directory on diskette 10 is the editable form of this document in Document Designer 2.2 format.
{4.0	Distribution Installation Procedures
4.1	Preparing for Installation
}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.3.1 files onto different hardware configurations.  We will call this the distribution installation.}
{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 run file 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.}
{Most of the GPS 2.3.1 run files 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 2.3.1 works on CWS, SRP, NGEN, 286i and 386i workstations.}
{The Generic Print System requires that Standard Software at revision level 11.3 or later exists on the workstation.  It is strongly recommended that a Queue Manager at revision level 11.3 or later be used, since several bug fixes affecting GPS have been made.  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 GPS 2.2 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:  If you have not previously installed GPS 2.0, 2.1 or 2.2, remove the GPS directory and all files in it prior to installing GPS 2.3.1.  The device configuration files used by GPS 1.x are incompatible with GPS 2.3.1, and the GPS 2.3.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.}
If GPS 2.0, 2.1 or 2.2 have been installed previously, it is not necessary to remove the device configuration files having the suffixes .Queue, .config or .state for printers currently in use.  If no jobs were in progress at the time of deinstallation, delete the .Queue and .state files.  However, deleting all other files is suggested to remove unnecessary files.
The Font Service and the Font Tool are included in the GPS 2.3.1 (distribution) installation.  The Font Service is required by all device drivers but the binary mode driver, and by the Document Designer.  If the  Font Service is installed, a standard, Convergentsupplied, 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 10 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.2	Installing GPS from the Installation Diskettes
Place the Generic Print System installation Diskette 1 of 10 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 depends on the system where the installation is being done and the operating system that it is running.
{4.2.1	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 cluster workstation.  The procedure will continue as described in Section 4.2.3.
Master 	Select this option to install GPS at an NGEN master.  The procedure will continue as described in NGEN Master below.
SRP Master 	Select this option to install GPS at an SRP master.  The procedure will continue as described in SRP Master below.}
When you have selected the option you want, press GO.
If you did not select Master, the form in section 4.2.3 will be displayed.
If you selected Master, you will be asked to describe the operating system at the master.  The following two choices will be displayed.
{CTOS VM or 
CTOS Classic > 9.8
This option will create the proper request files for NGEN masters that are running CTOS 9.9 or greater or any CTOSVM or CTOS II operating system.  Select this option for any CTOSSRP for 1.4 or greater.}
CTOS Classic 9.8 
or less
This option creates request files for use with any master running 9.8 or earlier.
After you press GO, the form in section 4.2.2 will be displayed.
{4.2.2	Master Hard Disk Systems
}A.	When the master options form is displayed, choose one, both or none of the options listed.  Selecting either or both of the two options will provide the necessary submit files for local file system cluster workstations to get a distribution installation from the master.
{GPS NGen Workstation Support
This option will provide new style device driver  run files to be copied to the master so that they may be accessed by workstations that are running CTOS 9.8 or greater or CTOSVM.}
{GPS AWS 
Workstation Support
This option will provide 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}
When you have selected the options you want, press GO, and the form in section 4.2.3 will be displayed.
{4.2.3	StandAlone Hard Disk Systems
}A.	When the options form is displayed, follow the instructions in choosing the options you want:
Font Service	This option copies the files necessary to install the Font Service at your workstation.
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 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.  These files are used only when developing new software applications that will access GPS printers.  The editable files to modify the text messages of GPS Services are available with this option.
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
Convergent's LZ5, LZ12, and LZ18 printers.
LPT Simple	Line Printers  for draft printing
PostScript	PostScript printers
CT Matrix	Convergent 2400 series 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 through .09.}
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.3	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.3 above.}
{4.4	StandAlone Floppy Disk Systems
The Generic Print System is not supported on standalone floppy disk systems.}
{4.5	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	System Service Installation Procedures
Invoking GPS system service run files so that they become installed in memory as system services is done through the Print Manager by users having the :GpsUserClass: Admin specified in their .user files.  See the Generic Print System Administrator's Guide for specific instructions.}
{5.1	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 1.3 Screen Font Database product (STA2201) 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 be installed automatically in the future with the desired parameters.  Alternatively however, 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 gradual 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.  The Binary Mode device driver does not require the Font Service.}
{5.2	Installing the Queue Manager
}Initially, the Queue Manager should be installed from the Admin form of the Print Manager at the master.  This will change the [Sys]<Gps>GPS.Printers file, allowing the Queue Manager to be installed automatically in the future with the desired parameters with the Install Generic Print System command.  Alternatively however, you may install the Queue Manager by entering the following Executive command:
{  Command   Install Queue Manager  GO
  Install QueueManager
    [Use Cache?]	yes
    [Maximum number of dynamic queues]}	20
The default number of dynamic queues is 0 when using the Install Queue Manager Command.  With GPS, the cache should be used and the number of dynamic queues should be at least equal to 2 times the maximum number of spooled printers on the cluster.
{5.3	Installing the Print Service
}Initially, the Print Service should be installed from the Admin form of the Print Manager at the master and at every cluster workstation that will have a printer install on it.  This will change the [Sys]<Gps>GPS.Printers file, allowing the Print Service to be installed automatically in the future with the desired parameters with the Install Generic Print System command.
{The installation form for the Print Service has the following four parameters:
  [Maximum number of Devices]
     Cluster: Number of local devices
     Master:  Number of spooled devices on cluster

   [Increase stack size by]

   [Increase heap size by]

   [Maximum number of jobs 
         spooling simultaneously]}
The first parameter on cluster workstations should contain the maximum number of printing devices that will be installed at that workstation.  The Print Service at the master spools jobs for all spooled printers on the cluster.  Because of this, on a master, the first parameter should contain the maximum number of printing devices that will be installed at the master plus the total number of spooled printers that will be installed at all cluster workstations.  If error 717 is reported, deinstall the Print Service and reinstall with a larger value.
A value of 0 for the second parameter should be sufficient for all configurations.  If error 4531 is reported frequently, deinstall the Print Service and reinstall with a value of 50 or 100.
A value of 0 for the third parameter should be sufficient for all configurations.  If error 4533 is reported frequently, deinstall the Print Service and reinstall with a value of 1000 or 2000.  At times of heavy cluster activity or CTNet difficulties, an occasional report of error 4533 would be normal.
The fourth parameter should contain the maximum number printing jobs that are anticipated to be submitted for processing at the workstation at any one time.  On cluster workstations a value equal to the number of printers installed locally should be sufficient.  On master systems the value typically should be somewhat larger than the value entered in the first parameter.  This number provides resources for peak printing activity and generally should be correlated to the total number of users having access to the printers on the cluster.  If users frequently have their jobs fail with error 722, deinstall the Print Service and reinstall with a larger value.  At times of very heavy use an occasional report of error 722 would be normal.
{5.4	Installing Printing devices for the First Time
}Most printers are shipped from their manufacturers with their communication line speeds, protocols and other communication parameters preset to reasonable defaults.  However, you may wish to change them.  These communication parameters are sometimes set through electromechanical switches and sometimes through software downloading.  Consult the manufacturer's documentation to determine what options are available and how they are to be invoked.
If the printer communication parameters are setup by downloading a software program, for example, see Section 11.4.7 Configuring PostScript Printers, then note that the downloaded program must be sent to the printer using its current communication speeds and protocols.  Usually such printers list their current configuration on a startup test page printed during power up.  You must first install the GPS device driver from Print Manager with the communication parameters listed on the startup test page in order to send the commands to the printer that will reset it to the desired communication parameters.  After such commands are accepted by the printer, GPS must be removed by the Print Manager and reinstalled with the new communication settings.
{5.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 master mode, all installation commands are recorded in this file but the installations themselves are deferred until the SRP itself is rebooted.
When in master mode, a message is displayed at the bottom of the Admin form indicating whether the GPS.Printers file is set to install the selected service at the next reboot of the SRP.  To change the state of the GPS.Printers file (to install or not), press the appropriate key, Install or DeInst.
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 (Print Service and device drivers) may be installed on any combination of CP and TP boards.  Only one Print Service should be installed on the SRP, generally on the board where the printers for which you expect the most activity are attached.  The files <Gps>SRPInitFPxx.jcl and <Gps>SRPInitCPxx.jcl give 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 first.  Then GpsInstall.run is invoked to install the Print Service on the desired board second, and finally GpsInstall.run is invoked on the remaining boards to install the rest of the GPS system services in any desired order.
See the Generic Print System Administrator's Guide and the CTOS System Administrator's Guide for more information on SRP installation.
{6.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>and <FontDB> directories.  The procedure does not copy the release note from the <RelNote> directory of the last distribution diskette.  This can be copied manually if desired.  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	GpsPmMsg.bin
GpsPm.run}
{If GPS is to be installed at a master workstation, the following files are required in the <Gps> directory:
GpsInstall.run	GpsPmMsg.bin
GpsPsMsg.bin	GpsPsMstr.run}
{If a device driver is to be installed at a cluster workstation, the following files are required in the <Gps> directory:
GpsInstall.run	GpsPmMsg.bin
GpsPsClstr.run	GpsPsMsg.bin
GpsDdMsg.bin}
{If a device driver is to be installed at a standalone workstation, the following files are required in the <Gps> directory:
GpsInstall.run	GpsPmMsg.bin
GpsPsStndAln.run	GpsPsMsg.bin
GpsDdMsg.bin}
{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)
CTMatrixDD.run	Convergent 2400 series printers
DaisyDD.run	Diablocompatible printers
EpFx286DD.run	Epson printers
HPLaserJetDD.run	PCL (Hewlett Packard) printers
	CT's LZ5, LZ12, and LZ18.
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 drivers on a system running CTOS below level 9.7: e.g., AWS or IWS workstations.
}mBinaryModeDD.run	binary mode only (plotters)
mCTMatrixDD.run	Convergent 2400 series printers
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
{One or more of the following pipe drivers is required, in the <Gps> directory, only if you need to create device driver output in a disk file.  
}CTMatrixPipe.run	DPL24C 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 [Sys]<Gps> directory while you are completing installation with LfsInstall.sub on all of the workstations in your cluster:
}lfs.sub	
LfsInstall.Sub	IFontDB.fls
IGpsWSmin.fls	ISysWSmin.fls
IGpsPrinters.fl	IGpsFontServer.fls	
ISysFontServer.fls	ISysFontTool.fls	
CmdFontServer.sub	CmdFontTool.sub
CmdPrinters.sub	CmdNoFontServer.sub
CmdNoFontTool.sub	CmdNoPrinters.sub
PMCmInstall.sub	mgRqIFontTool.sub
mgRqInoFontTool.sub	mgRqIIFontTool.sub
mgRqIInoFontTool.sub	
{The following files are required for the Font Tool in the [Sys]<Sys> directory:
FontForms.lib	FontIsam.config
FontTool.run	FontToolMsg.bin
IsamServer.run	Request.I.sys}
{The following files are initially 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):
}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
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.
{7.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.  Nevertheless, version 11.3 or later of the Queue Manager is recommended with this release of GPS because of several bug fixes related to GPS.
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, 2.1 and 2.2 GPS device drivers are compatible with 2.3.1 GPS.  However, it is advisable to rebuild independently developed device drivers with 2.3.1 PrintGen.  Device drivers based on versions of PrintGen prior to 2.0 are not compatible with 2.3.1 GPS.  
{7.1	Workstation Environment
GPS runs under version 9.1 or later of CTOS, including any version of CTOSVM.}
{7.2	Diskless Workstations
}The Generic Print System builds an installation file, GPS.printers, and a set of unique configuration files for each printer at a workstation where GPS is installed.  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, :GpsWorkstationPrefix: xxxx, specified in the user file, to uniquely distinguish these files.  Each diskless workstation that supports a printer should have a unique Gps Workstation prefix.  For more information on installing GPS on diskless workstations, see the Generic Print System Administrator's Guide.
For a user at a diskless workstation to have GPS Administration capabilities, a GPS workstation prefix must also be supplied.  See Section 11.1 for the syntax of the user file entries.
{7.3	Shared Resource Processor
}GPS 2.3.1 runs under version 1.4 or later of CTOSSRP.  Contact Technical Support for information about GPS and CTOSSRP 3.2 or earlier.
{8.0	Hardware Information
8.1	Hardware Configurations Supported
The Generic Print System can run on CWS, AWS, IWS, SRP, NGEN, 286i, and 386i workstations (including NGENs with the XC002 port expander) with hard disk or hard disk at the Master.}
{8.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.}
{9.0	Resource Requirements
9.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 of the GPS components are summarized in the table below.  
{Component	Size (Kb)
Print Service (Master)	61*
Print Service (Cluster)	52*
Print Service (Standalone)	51*
Font Service	20
Imagen Driver	68
PostScript Driver	69
Epson Driver	72
Daisy Driver	65
HP LaserJet Driver	70
Binary Mode Driver	34
LptSimple Driver	59
Installer	50
Print Manager	210}
*	The memory sizes above are the minimum required to support one spooled device.  Add the following to support each additional printer:
{Component	Size (Kb)
Device installed for direct printing	2.2
Device installed for spooled printing	4.2
Additional simultaneous spool jobs	2.0}
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).  The sizes shown include the default value of Font Data Table Size (4K).  The following table presents reasonable Font Data Table Size numbers for device drivers that are to print graphics from Art Designer or Image Designer.
{Device Driver	Font Data Table Size (Kb)
CT Matrix (monochrome)	18
CT Matrix (color)	50
Imagen	15	
PostScript	8	
Epson	10	
HP LaserJet (75 DPI)	8	
HP LaserJet (100 DPI)	10	
HP LaserJet (150 DPI)	15	
HP LaserJet (300 DPI)	48	}
If raster images will typically be scaled by the device driver, larger values will be required for all of the device drivers except the PostScript driver.  Scaling occurs only when a job is printed to a different resolution printer than the user selected when scanned by Image Designer, or when the image has been resized in Document Designer.  Add at least 12K to each recommended value above (except for PostScript) to handle image scaling.  If large images will be scaled down to very small, install the CT Matrix and Imagen with the maximum Font Data Table Size of 64.  See the section 9.4 of this release notice for more detailed recommendations.
The Print Service must be installed at each workstation which has a printer attached to it as well as at the master workstation. 
A device driver must be installed at the workstation to which the printer is attached.
The Font Tool requires 425K to generate the standard font database.  Larger font databases require additional memory.}
{9.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 is not requested as one of the installation options, then this directory is not created.
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, print service and print manager will require approximately 1100 sectors.
Scratch (temporary) disk files are created by 2.3.1 GPS device drivers that print raster images (from Image Designer).  Scratch disk files are also created when vector graphics (e.g., Art Designer pictures) are printed by drivers that must rasterize the image (i.e., the CT Matrix, Epson and HP LaserJet drivers).  The scratch files are created on the workstation's scratch volume ([Scr]).  The [Scr] volume is equivalent to [Sys] by default, but can be redirected to another volume.  The Print Service spools files into the directory [Scr]<$Gps>.  See the CTOS System Administrator's Guide for information about how this may be accomplished.  
{9.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
Print Service	 1	 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}
If it is necessary to generate a new system image, consult the release notice for the version of CTOS in use for instructions.
9.4	Tuning Device Driver and Font Service Buffers
Probably the most important judgmental decision that must be made when installing a device driver is how much memory to allocate to that device driver in the Font Data Table Size field of the device installation form.  The default value for this field is 4K.  Larger amounts, up to 64K, are appropriate under various circumstances.
In 2.3.1 GPS, this memory is used not only for font data, but also for processing of graphics.  On some devices, certain types of graphics must be processed in memory.  Because the entire graphic will probably not fit into this memory at one time, even if the maximum of 64K is allocated, the portion of the page which is occupied by the graphic is divided into bands.  When a larger Font Data Table Size is specified, the band is larger, and consequently the page needs to be divided into fewer bands.  In many cases, much work (such as rereading of temporary files) must be repeated for each band.  Large amounts of memory can be effectively used to increase band size and device driver speed in the following cases:
	Complex vector graphics (e.g., from Art Designer) will be printed on the HP LaserJet or Epson device.  The vector list is reread for each band as the driver converts the image to raster form.
	Raster images (e.g., from Image Designer) will be printed in landscape orientation on the HP LaserJet.  The device driver must rotate the image for the LaserJet.  The entire raster image must be reread for each band as the image is rotated.
	Raster images will be printed on the CT Matrix or Epson device.  Since text and graphics must be processed simultaneously, the image is reprocessed for each band of text and graphics.
The size of the band is affected by the width of the graphic object and the resolution of the printer.  Given the same amounts of memory, the HP LaserJet will need 16 times as many bands to rasterize a graphic when a resolution of 300 dpi is specified in the installation, as is required when a resolution of 75 dpi is specified.  When printing color images, the CT Matrix or Epson driver will require 4 times as many bands to rasterize an image, as when the driver is installed for monochrome printing.  All vector graphics on a page are rasterized as one image, so if images are present on both the left and right edges of the page, the band is the full width of the page. 
If raster images must be scaled by the device driver, memory must be allocated for both the band of the page to be filled and the corresponding band of the image which will be expanded or shrunk to fill that band of the page.  Consequently, even more memory is appropriate when raster image scaling is expected.  It may be appropriate to increase band size for reasons other than speed in the following cases:
	Images will be scaled down by a large amount by the Imagen or CT Matrix device driver.  The Imagen has a minimal band height of 32 pixels, and the CT Matrix printer has a minimal band height of 24 pixels.  If the corresponding slice of the source image does not fit into memory, the print job will fail with error code 15355.
	Quality of images scaled by the CT Matrix, Epson, HP LaserJet or Imagen devices drivers is important.  The scaling is more uniform when larger bands are used.
Little additional memory is required by PostScript driver for handling of graphics.  The PostScript interpreter in the printer handles scaling of images.  The driver requires only enough memory to pass one line of the original image at a time to the printer.  
No additional memory is required by the Imagen driver if vector graphics only will be printed.
If it is necessary to install the device driver with a large amount of memory for the sake of graphics, this memory will also be used to buffer font data when handling text.  This will result in much better performance when documents contain a variety of fonts.  The remainder of this section discusses these efficiencies.  If you have already determined that you need a large Font Data Table Size, you probably need not bother with the rest of this discussion.  But if you don't need the space for graphics, you may still need to optimize the installation for font usage.
There are three decisions which the system administrator makes which controls this efficiency of access to font data.
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 minimal 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 determine 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 best time (2:14) is shown, in order to better interpret the data.  Each row shows a device driver memory allocation, and each column shows 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 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 the Imagen Device driver will be printing raster images, or if the CT Matrix, HP LaserJet driver or Epson driver will be printing any type of graphics, give the device driver at least 10K of font data table space.  More, up to the maximum of 64K should be allocated depending on the resolution of the printer, color capability and the nature of the graphics.
(2)	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.
(3)	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.
(4)	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.
(5)	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.  
(6)	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.5	Device driver overlays
The CT Matrix, Epson, HP LaserJet, Imagen and PostScript device drivers are overlaid.  Using PrintGen, other device drivers can be designed which are overlaid.  The memory use and performance of overlaid device drivers can be modified during device installation.}
Only part of an overlaid device driver is in memory at any one time.  When a portion of the device driver code that is not in memory must be executed, that code is read into memory from disk, overwriting a portion of driver code that was already in memory.  Functions that are infrequently required, or are required for only certain documents, are read into memory only when needed.  Examples of such functions are forms alignment and raster scaling.
The area of device driver memory into which code overlays are read from disk is called the swapping area.  Overlaid device drivers are configured with a default swapping area that will normally be the optimal size.  
The size of the driver's swapping area can be specified at installation by the keyword SwapArea: in the Device Setup field of Print Manager's device driver installation form.  If the string,  SwapArea:ALL is specified, the driver's swapping area will be made large enough to contain all of the driver's code overlays in memory at once.  The size of the swapping area can be explicitly set, in kilobytes, by following SwapArea with a decimal number.  If, for example, the string SwapArea:12 was entered in the Device Setup field, a swapping area of 12,288 bytes would be allocated for that device driver.  
Generally, increasing the swapping area has less affect on device driver performance than increasing the Font Data Table Size.
{9.6	Tuning Networked Print Services
}The following is important if you are installing GPS onto a network with more than three nodes.  The most important performance tuning adjustment for networked Print Services is done with the installation parameters of CTNet.  To understand how to make this adjustment, consider how GPS manages network printing.
Each Print Service at a master CPU polls network remote printers once each minute for their status.  This polling continues if the error returned to the status request is 0, ercOK, or 4598, ercDeviceNotInstalled.  For all other error codes, the polling wait time is doubled until a maximum of one hour is reached.  Print Services at cluster workstations do not poll remote printers, but instead get the status of network remote printers and other cluster printers from the master every 3 seconds.  The design strategy is to maintain reasonably uptodate status of remote printers while holding network traffic to an acceptable level.
CTNet is is quite able to support this strategy, however the default installation parameters provide an environment that can severely restrict network performance when many nodes are using GPS for remote printing.  In particular, using the default value of 60 seconds for the Session timeout parameter (parameter 5) of the Net Agent will have this effect.  This parameter is the time that CTNet holds a connection open after a client has completed a transaction.  (A connection is a communication link pairing a Net Agent session at the source node with a Net Server session at the destination node.)  The purpose of this lag in ending the connection is to have a connection in operation in case a client issues a subsequent transaction to the same fromto connection pair, thus saving the overhead of establishing new sessions for the new transaction.  Unfortunately, no transactions to other fromto node pairs can use the connection while it is being held open.  Error codes 5110 or 8923 are returned to clients when CTNet is unable establish a connection for them.
A long Net Agent timeout period will restrict performance in a network with many nodes and bidirectional traffic between nodes.  Note that a network with  N nodes has N(N1) fromto node pairs.
A Net Agent session timeout period of 5 to 15 seconds is a far more reasonable value for networks where more than 3 nodes communicate with one another on a frequent basis as GPS does.  This allows more than adequate time for applications to issue subsequent transactions and reuse an open session.  Timeout periods as low as 3 to 5 seconds may be used successfully.
To maximize network performance, set Max  Connections, parameter 6, in the Net Transport Service to 16 and set the sum of the Net Agent and Net Server sessions to be greater than or equal to 16.  Generally, one sets the number of Net Server sessions and Net Agent sessions so their sum is the number of Net Transport connections.  If there are more senders at the node than receivers, then there should be more Net Agent sessions than Net Server sessions and vice versa.  A Printer  that is accessible from other nodes will be a receiver for each node that lists it as a remote printer.  A Print Service at a master will be a sender for each remote printer that it has listed.  (Press the Update key to see the list of printers.)  GPS generally requires a balanced mix of Net Agent and Net Server sessions.
For optimum GPS and CTNet performance, take the following steps:
A.	Review the printer lists at the master at each node and remove the remote printers that are never used.
1.	Use the delete device key to delete the obsolete remote 	printer at all workstations in the cluster that have the remote 	printer listed.  This removes the obsolete remote printer 	from the GPS.printers files.
2.	Deinstall, then reinstall the Print Service.  This removes the 	obsolete remote printer from memory at the workstation.
B.	Modify the installation parameters for CTNet.
1.	In the installation of Net Agent:
	set parameter 1, Max  sessions,  to 8 and 
	set parameter 5, Session timeout, to 10.
2.	In the installation of Net Server:
	set parameter 1, Max  sessions,  to 8.
2.	In the installation of Net Transport Server:
	set parameter 6, Max  connections,  to 16.
{10.0	Restrictions
}When the cluster workstation is running CTOS 9.7 or earlier, a distribution installation cannot be performed to a master workstation running CTOSVM.  This is because the necessary Standard Software tools needed to merge loadable request files are not available on the cluster workstation.
If a remote printer is known to be installed, yet the Print Manager shows it as Not Installed, or if it is not included in the list of available printers by applications such as Document Designer, then use the SetUp key from Print Manager to reselect (mark) the remote printer and activate the Print Service to maintain status information on the device.
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.
Overlaid device drivers cannot run under PMOS.  PMOS does not support overlaid servers.
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.
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.
Documents containing raster images which must be scaled may fail to print with error code 15355.  This error indicates that there was insufficient space to hold the unscaled portion of an image that maps to one band of the printer.  This occurs most often when scaling an image down by a significant amount.  It occurs on the Imagen and CT Matrix printers, because they have a fairly large minimum band height (32 and 24 pixels, respectively).  Reinstall the device driver with a larger Font Data Table Size.  A 300 dpi image 8 inches wide cannot be scaled to less than 1.5 inches wide on the Imagen, even with the maximum Font Data Table Size of 64K.  In that case, the image should be rescanned at the smaller size with Image Designer
{PostScript printers may fail to print documents containing images which contain a very large amount of data, and which must be scaled.  This appears to be due to a memory overflow in the printer.  In this case, a subsequent job may also be lost before the printer recovers.}
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 CT Matrix, 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.
Typethrough is not implemented in this release of GPS.
If a device driver installed locally is unable to access the Font Database at the master, problems will occur.  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.  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.  If you are printing to ordinary text files to these printers via ClusterShare, you must select ASCII print streams.  See the 1.1 ClusterShare Release Notice for more information about printing to GPS devices via CluserShare.
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 device driver 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).  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.  
The Spooler.Notice file used for appending a message to a banner page must be an unformatted ASCII file, such as created by the Editor.  A formatted Spooler.Notice file will abort the job with an error code 4573.
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, after powering off the printer and replacing 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.
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.
Time required for raster image processing:  Due to the very large amount of data contained in a raster image, printing a job that contains raster images may take significantly longer than printing one without raster images.  Images that require scaling by the device driver will require more processing time than raster images that do not require scaling.  
{11.0	Supplementary Information
11.1	Nationalization
To nationalize the Print Manager:
}Edit each of the forms in [Sys]<Gps>GpsForms.lib using Forms Editor.  Use Librarian to obtain a list of forms in the library,  to extract forms from the library, and to replace forms in the library.  Edit [Sys]<Gps>GpsPmMsg.txt and recreate [Sys]<Gps>GpsPmMsg.bin from it, using Create Message File.
To nationalize the Print Service:
Edit [Sys]<Gps>GpsPsMsg.txt and recreate [Sys]<Gps>GpsPsMsg.bin from it, using Create Message File.
To nationalize device drivers:
Edit [Sys]<Gps>GpsDdMsg.txt and recreate [Sys]<Gps>GpsDdMsg.bin from it, using Create Message File.  Most of the strings defined in this file are used in printer status displays in Print Manager and other applications, or are used to select installation options in the device setup field of the Print Manager.
To nationalize the Font Database:
Use the Font Tool to nationalize the Font Database.  Nationalization of the font database is described in detail in the manual, Using the Font Tool.
To nationalize the Font Tool:
Edit each of the forms in [Sys]<Sys>FontForms.lib using Forms Editor.  Use Librarian to obtain a list of forms in the library,  to extract forms from the library, and to replace forms in the library.  Edit [Sys]<Sys>FontToolMsg.txt and recreate [Sys]<Sys>FontToolMsg.bin from it, using Create Message File.
11.2	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.
{11.3	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 Binary Mode 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.
For more information on using GPS with preGPS applications, see the Generic Print System Administrator's Guide.
{11.4	Devicespecific Fonts and Features
}This section assumes knowledge of certain general principles of the font database which are discussed in detail in the Using the Font Tool manual.  The 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.
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.
{11.4.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.  
{11.4.2	CT Matrix Driver
}The default font devicetype for the CT Matrix driver is CT2400.  This driver parses the font key alias for keywords in order to determine the necessary escape sequences to send to the printer.  Keywords Font1, Font2, etc., select the various resident fonts in the printer (omit this keyword for font 0).  Keyword Card selects a cartridge font; in this case keyword Font1 or Font2 select an alternate cartridge font.  Keywords Bold and Italic cause the font to be bolded or slanted.  Keyword Double causes the font to be printed double height and double width.  Keyword Compressed causes the font to be squished horizontally.  Keyword Pica causes the font to be printed at 10 pitch (unless doubled or compressed) and keyword Elite causes the font to be printed at 12 pitch (unless doubled or compressed).  Keyword PS selects proportional spacing (the correct width table must be supplied).
The keyword BoldFace calls for resident font 4 (the proportional font) on the models 2450 and 2475, and for the BoldFace cartridge on the model 2425.  Any unrecognized keyword is considered to be part of a cartridge name which the user should be prompted to mount.
Conventions in the standard font database for selecting various resident resident fonts on the 2400 series printers are as follows:
Size	Courier	Draft	Cubic PS	Modifiers
24 pt	font 0	font 2	BoldFace	Pica, Double
20 pt	font 1	font 3		Elite, Double
12 pt	font 0	font 2	BoldFace	Pica
10 pt	font 1	font 3		Elite
9 pt	font 0	font 2	BoldFace	Pica, Condensed
8 pt	font 1	font 3		Elite, Condensed
The fonts selected under Courier and Draft are printed monospaced, and the BoldFace font is printed proportionally.  The BoldFace font will be used if any of the proportional fonts (such as Times) is selected from Document Designer.  The user may be prompted to mount the Scientific 12 cartridge if characters not present in the resident fonts are used, or if the Greek font family is selected.
If no family is specified, the Draft family will be used.  Therefore, a nonformatted document sent to the printer will be printed using the faster draft fonts (fonts 2 and 3).  Courier is the default family specified by Document Designer documents, so those documents will by default be printed using the higher quality fonts (fonts 0 and 1).
The device setup parameter, Model:2425, Model:2450 or Model:2475, should be entered to indicate which of the 2400 series printers is in use.  The device setup parameter, Color, is entered to obtain color output on versions of these printers equipped with a color ribbon.
{11.4.3	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 print wheel 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 print wheel 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 print wheel.  If no such name is present, it is assumed than any print wheel 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.  
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 Using the Font Tool for the details of this conversion process.
{11.4.4	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 Epson Fx286 device.  Some combinations will result in one or more keywords being ignored.  Consult the appropriate printer manual for specific information.  
The Epson 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.
Two font families, Draft and Courier, are implemented for the Epson FX286.  The Draft family is used to select lowquality fonts which print faster.  Nlq Epson fonts are used when the Courier family is selected.  If no family is specified, the Draft family will be used.  Therefore, a nonformatted document sent to the Epson will be printed using the faster draft mode.  Courier is the default family specified by DocumentDesigner documents, so those documents will by default be printed using the Epson's higher quality fonts.
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.
The Epson driver supports color printing on some Epsoncompatible printers with 4color ribbons.  Specify Color in the device setup to enable color printing.  The driver also supports certain Epson printers equipped with sheet feeders.  Specify SheetFeeder:441 in the device setup to enable this.  Bin 1 or Bin 0 selects the first bin and Bin 2 selects the second bin.  Selecting the manual feed print job option invokes semiautomatic mode, in which the printer waits until the user presses the feed button on the printer to print.  Specifying bin 3 invokes semiautomatic mode on specific individual pages of a document.  These features have been qualified only with the Honeywell Bull 441 model printer, and are not warranted to work with other printers.
{Epson Driver Status Codes
15300	Characters were sent to the Epson device driver in the wrong y order.  (I.e., a character with a lesser y coordinate was received by the driver after it had printed a character with a greater y coordinate.)  This status code indicates an error in the application sending data to the GPS system.}
{11.4.5	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, with the following additions:
	The string that follows is the name of a portrait font file to download, if the page is printed in the portrait orientation.
	The string that follows is the name of a landscape font file to download, if the page is printed in the landscape orientation.
	The string that follows is the name of a font file to download, regardless of the page orientation.
+	The string that follows is the name of a font file to download.  The character '+' will appear again in the file name.  The '+' will be replaced with the letter 'P' to access the portrait font file, and the letter 'L' to access the landscape font file.
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 several other font device types for use with the HP LaserJet device driver, in addition to 'HpLaserJet'.
HpDownLoad	Supports the AD downloadable font package from HewlettPackard (part number 33412AD).  It provides fonts similar to Times and Helvetica in various styles and sizes (6, 8, 10, 12 and 14 point in 3 styles; and 18, 24, and 30 point in bold style).  The user must purchase this font package and install it (using MSDOS Read or Cluster Share) himherself.
LZ18	Supports resident fonts on the LZ18 printer (8, 10 and 12 point Courier in 3 styles; 8, 10 and 12 point Times in 3 styles; and 14 point Helvetica Bold).
LZ12	Supports resident fonts on the LZ12 printer (8, 10 and 12 point Courier and 10 point Times).
LZ5	Supports resident fonts on the LZ5 printer (8 and 12 point Courier).
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 manual feed slot.  If the user presses 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
LZ5	150 dpi	300 dpi
LZ12	150 dpi	300 dpi
Series II	150 dpi	300 dpi
Series II with extended memory	300 dpi	
LZ18	300 dpi	}
A lower resolution may be chosen to reduce the time spent printing graphics.  A full page takes about 30 seconds at 100 dpi and more than 4 minutes at 300 dpi.
{11.4.6	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.
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.
{Imagen Driver Status Codes
}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.
{11.4.7	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.
Many PostScript printers now offer a newer and larger standard set of 35 font faces, including several styles of Palatino, ITC Avant Garde Gothic, New Century Schoolbook, Helvetica Narrow and ITC Bookman, plus ITC Zapf Chancery Italic and ITC Zapf Dingbats.  If your PostScript printer supports this larger standard set, enter LaserWriter+ into the font device type field of the device installation form.
Users who have some other set of fonts available to their PostScript printers should generate a font database which includes the relevant font families.  The editable font database (.port files) contains font data for several other Adobe (PostScript) font families besides those available in the two standard sets.
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.
{11.4.8	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.
11.5	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.
{12.0	Documentation Updates
12.1	Standard Documentation
}Use of the Print Manager for configuration of the print system is described in the Generic Print System Administrator's Guide.  Use of the Print Manager for everyday tasks, such as printing and monitoring printers, is described in the Using the Print Manager manual.  Use of the the Font Tool is described in Using the Font Tool manual.  The GPS Programmer's Guide documents GPS and GPAM interfaces for use by application programmers.
{12.2	Changes to Documentation
12.2.1	The Generic Print System Programmer's Guide
Change Table 73, FORMAT OF GPS NET LIST, (page 746) to read as follows:
}			Size
	Offset	Field	(bytes)	Contents
	0	nPrinters	2	The number of printers in this table.
	2	sRgPrinter	2	The size of the rgPrinter data structure following.  nPrinters * sRgPrinters + 12 is the total required size in bytes of this data structure.
	4	dwTimeStamp	4	System time of last GPS network topology change.  If this value changes, it may be necessary to requery device configurations.
	8	wGpsVersion	2	Current version of GPS (23).
	10	wReserved	2	Reserved for future use.
	12	rgPrinter	80*n	See Table 72 for rgPrinter format.  There are nPrinters occurrences of rgPrinter in this table.
{Add the following fields to the end of Table 74, DEVICE CONFIGURATION INFORMATION, (page 748):
			Size
	Offset	Field	(bytes)	Contents
	92	sbFontDevice	25	Font device type used to access fonts in the font database, which are available for this device.}
	117	bReserved	1	Reserved for future use.
	118	wHorizDPI	2	Device horizontalaxis resolution, in Dots Per Inch.
	120	wVertDPI	2	Device verticalaxis resolution, in Dots Per Inch.
	122	wPgWidth	2	Installed page width, in GPS units.
	124	wPgLength	2	Installed page length, in GPS units.
	126	bcOrients	1	Number of page orientations supported by this device.  Will be 1 or 2.
	127	bDevOrient	1	Device's installed page orientation.  Set to 1 for landscape.  Set to 2 for portrait.  
	128	bVersion	1	Device driver version, multiplied by 10.  (For GPS2.3.1, the value in this byte will be 22.)  This version number will not necessarily change in future versions that do not add driver capabilities.  
	129	bValidVersion	1	If the value in this byte is 5A hex, then the value in the bVersion field is valid, and all of the new, GPS2.3.1 Device Configuration Information fields are valid.  If the value in the bValidVersn byte is not 5A hex, then the version of the GPS device driver being queried predates GPS2.3.1.
	130	wLeftBorder	2	The left border specified in the driver or the driver installation form.
	132	wRightBorder	2	The right border specified in the driver or the driver installation form.
	134	wTopBorder	2	The top border specified in the driver or the driver installation form.
	136	wBottomBorder	2	The bottom border specified in the driver or the driver installation form.
For a nongraphics device, the values of wHorizDPI  wVertDPI are undefined.
The explanation of GPAMGrColorTable on pages 651 and 652 is incomplete, and the example is misleading.  By convention, color 0 is used for the background and always prints as white, regardless of how it is defined in the color table.  Any color, other than color 0, defined as either {red=0, green=0, blue=0} or {red=1000, green=1000, blue=1000} will print as black.  The latter value technically defines white; however in color palettes for applications (such as BGP) designed for screens with a dark background, this color defines the foreground color which displays as white but should print as black.  By adhering to these conventions, GPS drivers will print the background as white and the foreground as black, regardless of whether the foreground color (always color 0) is white and the background color (usually color 1) is black, or vice versa.
The description of GPAMSetVerticalOffset on page 643 is incorrect.  The amount that a subscript (intLevel < 0) character is shifted is proportional to the height (specified via GPAMSetFont) of the subscript character.  The amount that a superscript character (intLevel > 0) is shifted is proportional to the height of the last prior unsuperscipted and unsubscripted character.  The GPAMSetSLD call has no bearing on superscript or subscript shifts.  The formula for the shift amount is the applicable font height divided by four, times intLevel.  Document Designer specifies intLevel=2 (or 2), which is half the height of the applicable font.
The wWidth parameter to GPAMSetFont (pages 640 and 641) specifies the pitch at which the font should be printed, regardless of its actual size and whether it is a monospaced font.  (1440  wWidth = pitch).  Normally wHeight is used to specify the size of the font.  (WHeight  20 = point size).  If both wHeight and wWidth are nonzero, the font size is specified by wHeight but the font is printed at the pitch specfied by wWidth, even if that is inappropriate for that font.  If wWidth is zero, the appropriate pitch or proportional width table for that font determines character spacing.  If wHeight is zero, the height is implied according to the rule that point size times pitch = 120 (or wHeight = wWidth * 5  3).  However, regardless of whether the size of the font is specified directly via wHeight, or indirectly via wWidth, the actual size of the font is determined by the font keys and reduction table in the font database.
The following information should be added to the section on GPAMGrBeginGraphics, and also applies to newly implemented function GPAMBeginRaster:  The current GPAM output location defines the position of the upper left corner of the graphical object to follow.  Typically, a call to GPAMReposition will immediately precede the call to GPAMGrBeginGraphics, to define this upper left coordinate.  If this coordinate is (0, 0), the image is centered on the page (or within the imageable borders of the page).  This will occur, for example, if GPAMGrBeginGraphics immediately follows GPAMBeginPage.  If the wWidth and wHeight parameters are zero, the graphic will be sized to the page borders or, in the case of raster images, will be printed at the resolution of the image.  The fClear parameter is currently ignored.
The following GPS calls described in the GPS Programmer's Guide are unimplemented (although dummy procedures for them exist in GPAM.lib):
GPAMBeginBound
GPAMEndBound
GPAMSetTranslateTable
These three functions are unlikely ever to be implemented.  Character translation is governed by the translate tables in the Font Database, and is both devicedependent and fontdependent.  GPAMSetTranslateTable is therefore both superfluous and inappropriate.  Applications should obtain font width tables for the intended device from the Font Service to perform justification, rather than using GPAMBeginBound and GPAMEndBound.  
The GPAMPerimeterColor documented in the GPS Programmer's Guide does not exist.  Use GPAMLineColor to select the perimeter color of a polygon.
Change the description of QueueGPSFile, (page 726) to read as follows:
QueueGPSFile	(pbFileName, cbFileName, pbDeviceName, cbDeviceName, fDelete, pJobParameters, sJobParameters, mode) :
	ErcType
The added parameter, mode, is for mode control and has the identical function as the mode parameter found in the procedure, SetImageModeGPS on page 740.  Thus QueueGPSFile concatenates the following sequence of calls normally made to spool a file for printing:  OpenGPSFile, SetGPSParams, SetImageModeGPS, WriteGPSFile, CloseGPSFile.
Add the following operations to the section GPS ROUTING SWITCH REQUESTS (sic).
QueryGPSFile	(pbDeviceName, cbDeviceName, pbFileName, cbFileName, pbPassword, cbPassword, 
pfFloppy) :	ErcType
The QueryGPSFile request provides information whether a file is accessible for printing to a spooled printer.  Error codes 203, 204, 205 or 215 will be returned if the file cannot be queued.  If error code 0 is returned, then a flag is returned indicating whether the file is on a floppy disk drive.  If so, and QueueGPSFile is used to print the file, then the floppy will need to remain mounted until the job has completed printing.
The above pbcb pairs refer to the device name intended for output, the file name and its password, if any.  pfFloppy is a pointer to the flag described above.
{Request Block:	Offset		Field	Size	Contents
0	sCntInfo	1	8
1	RtCode	1	0
2	nReqPbCb	1	3
3	nRespPbCb	1	1
4	userNum	2
6	exchResp	2
8	ercRet	2
10	rqCode	2	8162h
12	reserved	8
20	pbDeviceName	4
24	cbDeviceName	2
26	pbFileName	4
30	cbFileName	2
32	pbPassword	4
36	cbPassword	2
38	pfFloppy	4
42	spfFloppy	2	1}
GetGPSParams	(jh, pJobParameters, sJobParameters, psBufferRet) :	ErcType
jh is a job handle returned from an OpenGPSFile operation.  The pbcb pair, JobParameters, should refer to a data structure as defined in 
Table 79.  psBufferRet is a pointer to the number of bytes returned.
{Request Block:	Offset		Field	Size	Contents
0	sCntInfo	1	2
1	RtCode	1	0
2	nReqPbCb	1	0
3	nRespPbCb	1	2
4	userNum	2
6	exchResp	2
8	ercRet	2
10	rqCode	2	8160h
12	jh	2
14	pJobParameters	4
18	JobParameters	2
20	psBufferRet	4
24	spsBufferRet	2	2}
A complete device specification that includes a CTNet node name may be used for the parameter DeviceName in all GPS operations.  This provides a more efficient routing path and allows applications to access and differentiate between devices having the same name on different CTNet nodes.
12.2.2	The Using the Font Tool Manual
On page B4, in the section about HP LaserJet downloadable fonts, replace the backslash character (\) with the slash character () as the character used to access a portrait font for pages printed in protrait orientation.
The Font Service is documented in the Office Applications Programmer's Guide.
{13.0	Status Codes
}Consult the Generic Print System Administrator's Guide for a list of GPS status codes.  The following status codes are new to 2.3.1 GPS.
{New GPS Status Codes
}4570	File to be downloaded (such as a font file) does not exist.
14.0	Known Errors and Omissions.
SPR 12398	Following GPAMReposition to [0, 0], the printout starts on the second line.
SPR 12537	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 with a nonnull password will cause the job to be printed.  Security mode is useful only to prevent a job from being printed when the printer is not monitored.
SPR 12541	Canceling PostScript print jobs, or restarting a print job from a location other than the current location, sometimes causes one or more subsequent print jobs to be lost.  PostScript printers sometimes fail to recognize the endoffile character (04) 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 PostScript 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.
SPR 12543	Restart from a location other than current will fail if a job was created by an application which does not paginate the document, such as Art Designer.
SPR 15310	Use of F10 softkey Home from the DevSave screen causes the next DevHelp display to be blank.  To clear problem, use the cancel key, which displays the installation menu.  Note: Hitting go while in the blank display will cause keyboard to lock.
SPR 15317	For systems using CTNet and GPS, it is necessary to install CTNet before GPS if you are using the sysinit.jcl to install these services.  If GPS is installed before CTNet, an erc 4594 will occur while trying to print to devices on other nodes.
Dotted lines (line type 2) do not print correctly in drivers using the Vector Rasterization facility, including the LaserJet, Epson and CT Matrix drivers.
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, embedded 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.
More than two drivers installed on an AWS will cause it to crash with erc 430 (no memory available to load the exit run file).
If the master is rebooted diskless workstations having the Font Service installed will may give an error code of 13903 when attempting to print or access Document Designer because the font database file is no longer accessible.  Deinstall the Font Service and reinstall it to reopen the font database file.
Excessive rapid swapping of a context that is copying a file to a printer installed for direct printing may cause a crash on the workstation where the printer is installed.
Should a print job get stuck in the queue and all efforts to Restart or, if desired, to Delete, the job are unsuccessful, then deinstalling the device driver and reinstalling it will allow the job to print.
When printers are powered off, not connected or offline, the timeout period must elapse before printer commands can be completed.
If a printer is paused, the deletion of the first print job in the wait queue of the status screen will show a false idle state.  All subsequent print jobs will back up until a restart command is issued.
Changing a printer from spooled to direct will show the printer to be spooled on remote nodes.  This can be fixed by issuing a setup from the affected nodes' print manager.
END