CUPS Configuration Management Plan
CUPS-CMP-1.0
Easy Software Products
Copyright 1997-1999, All Rights Reserved
1 Scope
2 References
3 File Management
4 Trouble Report Processing
5 Software Releases
A Glossary
B Coding Requirements
C Software Trouble Report Form
GIF89a¯ÿòÌÌÌ™™™fff333ÿÿÿÿÿÿÿÿÿ!ù,¯ÿBþXºÜþ0ÊI«½8ëÍ»ÿ`(Ždižhª2€0p,Ïtmßx®ï
;±Ýíˆndý !¸ ž³wà…MƒƒY~¿{,gÚ\‚äé 
Œ×Ø(tÙî!Ï=Ñ.ûz¯áÑŸ:ì;Ã9qöíÉë]/¿ºÉ¤Et/†'Îþt9ÀØ–ž_ÙÇ\|W•wArö¸Ý2Ô× 
tN°0Tï}¡û‰$!‚yMxî)ˆš‰Ôø@nB°U½ÊwE„§!ŠF H L8B 
c‰;ždŠ-æDVWdг€h±äÚ“P¶%#(4Fiå•Ï\hŠ:Re!\ÒÄ—X^¦%€¥À-$E€Ö/úHŽšlââöÌQX
¸1Nô¯b"œŠüjåÁÂE0…È8ö5GkZ|ÒÁwt„C»ÔQSÇo6ÔÙ[W„$²*Ž+4Pb-8¹P1þ'8"‘ФÄ$ Cyê‘„)>ãŠtè`Ð3‡‹¾z"«rE'Âqfä°Ë 
‘qÂ\|€„Ž¡ôö»%É(.—bڽȀíÉ`{¬EÇ1w’ »[Hß`(B6ö“  
†')ÊRŽÎa[ÃrbC!Tå°Œ 
2Q·ÈHZê#–®üË/àô¯FÝê(Û²% ºXË9öÀbÁ4f.ù-oý™XËB…IÎÒ7¹*@ÃÓŽÍT€hà‘ÌWâ™Ã$f:µyžn†ó†r„'téKv` 
Ç+dª– œ79sò|'=×¢Ìx¶òœÿ„¦œˆeÎ;*à$þ” IÝÆaÏ{–3ŽÅÁ 
P“ÍS[ÙL¨3©òQ7éÆò#ãûô0F×ðsE°t§@‘ØQÜ´´ ©:3ÓRíd ¥*MITnŒ£¨H]ØQÁd 
@òþ—¬rMœŽaO
rë^yÀ·(¸îéêû$uDòrã/a,I.°ÙUÀœb hˆ`¾B ë" 
Ü`HØxȸo1þ[á\8f^æ|\ý‚¢¢zø0(ˆ\ {ƒÄgäÞõ€çâ§Á˜0*\³n¼‹m¶/Äeª±ÿ†ì 
Ç,½DN2€œº+ùÉ|í0L¡Le*ð¸Ã>2ëf,eIPOËÅàr—±”80SAŸcFªatç»ãy¤¸ršçÌ¡5ïoõËsžï|¿8˙Φ¬þ,ï¼èà)ÁÌ;øk¡—†dDpÑòø2¢qfHã!Ë“~ÙŸ-í 
'g:,æ4y?ýäP‹Z›ž#ÏÕ´Î5AK‰k]ûš›ÒKõ¯‡më€õzØÈƫ؎Ý>B{PЪ.6hf]º?©ÌIŽuO„íM‚ÌÇÜcµ3˜ 
61‹NÒ[†W£ ¦m¿{ÂPâvζKnUˆ[ ònĽ±÷n?l:Áž3ušë¬sP[ÿnn¾çP…WõÔFj[Â÷ 
¹vÏ™à‰˜xú'ˆ£ÀÀ†p¸4.êãKÇ¿ÂÁ±o§¢ü"Á|Nk`îʘ
 
jl©ÌuˆËi™0pmC´«+‰÷6¤2éÏe`(ŽJ]¥iõð3ƒØí"p|ª!:qøFس 6£ 
@,þŠqüãoÌÇ®žÖüV“¶QÇ›Evî¹²É8ÙªS"æÀç‡x± àþ‡>—Iãg 
ïÝ>Y‰çN80æ§ ±¾GLLìÕµ…(1Þ¼!8}þ¬“*…ª‰Ùì:e»´œ 
ª¿ên_6ÂÃSÀ`eG;Ö„CƒCcˆ¿‡4¸yeî¯Í)oøByRm½0?íLîÅ`QÿjÓÙ/ºôÓN|Ý
þÙAÜŒÁ¸D5©D aævx ?жx°DM@•!h‰àÈ€Ž§® 
• á×B`ð¤ªE?›“”Þdƒ"8$Ý`Ki0…OðƒnΓ±µvtžè€I([,¹Ndɨh\'6X 
Pã—Š‰Éøt ¢‘¥˜¬è €ˆ†Ky™FˆŒë`š”yƒ„¨š €š‰ƒM©‡øFQhY„ 
9¶X¯×–í4š¤™Y\)"¹AN]‰xéz÷Gq07)©ñ™•Y€r°ŒŽi‹ z ™ÇäFÍÉT–ù› 
ËŽC œwI›üX]‹¹\ëY]þf lïYbj8ŸÈuœbŸÍÅtú©fÞןfBI—“*øé:ÛØUj Ò 
ˆõ¹ Õp $(~  ¡Ú ¡gù{îpZI?¡ƒîÀv:“a¦˜6¢§Ô]Ý‘(ªê)!ŸÚ¢: 
jwµ¡4ÚvíHÛǘ9ºXhó•üù£¥Á¢VÉ{Dº2š‰(°¤3š¤a÷ +У¥“p¢þò4Vº—  
E´¥è¤k°7ºhT*€¿èw`ÚžiÄ …S¦Æ¦mê Nêƒ#ú¢f€ xê†ý 
8z©7uÚp{Ú=~]7`«h‡ÚsÚg:…zd˜ó§ÎA-vþAñr¦'–AÚ)9–š¢âSi;£…š 1ªo"ª 
¦J;“º rº8Ui|é>¡Úœú
“ë¥Dfný2»ƒ–0j«®»ºK;zë¢Íö»—!µ—S»³r>K+6ˆ‹¨XÒ»; CÈ 
8Ê;¢»ÃÛ/Œ‹¥ž!¬s½VR½óõÏ‹Oâ[/çK¨þ˜Ñ:Í‹\Ý+ Sc:ïËž’º¶ë9Æ»
ô 8ly$ 
8©ÙÅmX2Ùh>—?¯!šHüÁ^LsP,Ÿ«Y‹âá¿ÿtšì‚£Y 
r¦Éš¥9ÇjžÄ8-ÆÇŒ¶iêPÂbA˜ù‰Ã¸š»³7RœCWRoìŠå MŒŠ”åt™ Œ›réÉq
å>}Lê}ÎǨ 5:àŒ|"þÇwÐsøæNΰ¹#R>~-N‰®èƒ ßcðÞÚÎÑ¥®åGÎâ툉Ýè*‚¸ 
=‚ž ºëâ…ëÀ>Û·žën^žmèÊëð¼ã>å×Λ«}êØ÷ 
“Œ¬ËIÁ·AÔNÍëv>]t.âÚLЫþíï¾ñnäÖÜæs¹¿±â°+† 
¬UØïî•.ç¬ÎìÍ.è´ÞŠG=ðù‚§ž¯”ë^äÛ®êh-‹êê!i!ÕvMíiªîþ¾òîá/þÑ-OÖGð,oñº!å’gOâ POìOôBþÈàhâ+?ï>ßÊVHÀsaõ™€õ$óSîõ—»ó8.žß¹ 
~áßÈ©ö»]ò3ëÆt_÷[ïôb¯ç‚Ü÷Õ«@u™ð;zܘ‘Ü@óŽ2’?ùƒ¸ÙlùF ¶™¯ù›N ž0œú£¶¤ÿ0#9:ß§½ž©Ÿ\#ÃÙæó2é+û‚ÀÓ¸_äM/ÓtaÚý3”]Ù«¿¸iîaF>ª}ŒØvÍïMÍ÷Ðëä©îrÜŒöqñ_ÀüªrâF®ò
ýþ¸—hT_ã4sx”ýÝî)ç.QgûàŸÏ%ì‹}i´ASû|þð@QÜ 
$J9€»-̱÷ÜôMØ‘hZ˜¦:°œ*ÏlßxÒ|ϼ¡ÅLÀ ¬Áfù9BÑdìÁ|«VV„¢“énKv
kB_ƒg 3ʳ8#Þ¬L=0;J¤äÈ@¤F|'i~±©  žaÊŠÆg;d*3²”©bPÏ¢TäHô¦?[† 
ÄäƒhN6ZM¢D:c*BR!$±ckƒ’V-uÛ@[øp„Ÿ]¼8ö-1{TήWÏ2ñ Šp=¸q«Ñ½es.‰„4+#Ëe¦¥W5µekxr䛓/XÍš5Iǃ=kÝúµì˰ûN–2qÅ[r¦yZ£QŽ›ÇÞtxŠäcK—Ííɹ 
iþ¡9¼m1oñ¢©/²8îìSté4l’Wm¾9óéÖÛÐãã{{üzÞ¿çøêöÞzà}œàL¨ "˜ 
ÄÐsà¶PGLUúå`MÞ  ¡†9¬§Û{pX¸¡wÚw߇¡¨ ‰í "MUXNx
+l´á¦ 
j²F:Á.êÆÛj¤³Búî ¼Ê«/£Ö’[н#í+ð¥ænJÞ¸«æ;ð©õ‹¨ _ËðÄŠÒ»*º? 
ƒÂwœÃyzh±°Øzl2,#oZ2È›r|òË‚°¼$Ç)ë 
óÍÙÔ,éfs€1Î@/øîÏPõÌiÐH·ðÃBkLtÒP¯bôS;NÝWÔXÏ 
ó’dlÍtÖ`°tžOc óÅa§}AÄ›²1vËjÇmþu+`ÍÍÁ·qwü6˜‚ì½sÞXŸ¨Ë$xM6àP³-iÉSÚ½AÙˆïë84–ø=xä8^!ä*L>Þ˜ƒk¹Œ({Iè^!ḘN$ê 
«®ç!ºû‚ÿÝ ë¯ßoî—Oü¨¾ÿî9í]ñÞ{ñÙÊ®ãlhŽ(èÌÃê¼~ÔS¢|öÕŸzýw¬Ë§|øÝ—*½ŒÈ×|úåwzþæ“)Nrû¾Ê?*ô¥ 
¿*÷ô7ú½~Múúú÷ª÷Ɉ•S3x*ûíP”ùH£°°àó(è¾í-Jƒú™ 
åAF{#\”g…Áœ)!),Ô #ÓÂǼjþ1œŒþh©²K„9$ƒYè)Ž ˆA È 
—‡)#1‰Óp"˜ð'Ã%n‰P´‡Ù¨-‹1³¢^\%ƈÔp„CLÖ5Ã
 This configuration management plan document provides the guidelines 
for development and maintainance of the Common UNIX Printing System 
("CUPS") Version 1.0 software. 
 The Common UNIX Printing System provides a portable printing layer for 
 UNIX® operating systems. It has been developed by Easy Software 
 Products to promote a standard printing solution for all UNIX vendors 
 and users. CUPS provides the System V and Berkeley command-line 
interfaces. 
CUPS uses the Internet Printing Protocol (IETF-IPP) as the basis for 
managing print jobs and queues. The Line Printer Daemon (LPD, RFC1179), 
Server Message Block (SMB), and AppSocket protocols are also supported 
with reduced functionality. 
CUPS adds network printer browsing and PostScript Printer 
Description ("PPD")-based printing options to support real world 
applications under UNIX. 
CUPS also includes a customized version of GNU GhostScript 
(currently based off GNU GhostScript 4.03) and an image file RIP that 
can be used to support non-PostScript printers. 
 This configuration management document is organized into the following 
sections: 
- 1 - Scope
- 2 - References
- 3 - File Management
- 4 - Trouble Report Processing
- 5 - Software Releases
- A - Glossary
- B - Coding Requirements
The following CUPS documentation is referenced by this document:
- CUPS-CMP-1.0: CUPS Configuration Management Plan 
- CUPS-IDD-1.0: CUPS System Interface Design Description 
- CUPS-SAM-1.0.x: CUPS Software Administrators Manual 
- CUPS-SDD-1.0: CUPS Software Design Description 
- CUPS-SPM-1.0: CUPS Software Programming Manual 
- CUPS-SSR-1.0: CUPS Software Security Report 
- CUPS-STP-1.0: CUPS Software Test Plan 
- CUPS-SUM-1.0.x: CUPS Software Users Manual 
- CUPS-SVD-1.0.x: CUPS Software Version Description 
The following non-CUPS documents are referenced by this document:
- IEEE 1387.4, System Administration: Printing (draft) 
- IPP/1.0: Additional Optional Operations - Set 1 
- RFC 1179, Line Printer Daemon Protocol 
- RFC 2565, IPP/1.0: Encoding and Transport 
- RFC 2566, IPP/1.0: Model and Semantics 
- RFC 2639, IPP/1.0: Implementers Guide 
Each source file shall be placed a sub-directory corresponding to the 
software sub-system it belongs to ("scheduler", "libcups", etc.) To 
remain compatible with older UNIX filesystems, directory names shall 
not exceed 16 characters in length. 
 Source files shall be documented and formatted as described in 
Appendix B, Coding Requirements. 
 Source files shall be placed under the control of the Concurrent 
Versions System ("CVS") software. Source files shall be "checked in" 
with each change so that modifications can be tracked.Documentation on the CVS software is included with the whitepaper, 
"CVS II: Parallelizing Software Development". 
 A Software Trouble Report ("STR") shall be submitted every time a user 
or vendor experiences a problem with the CUPS software. Trouble reports 
are maintained in a database with one of the following states: 
- STR is closed with complete resolution
- STR is closed without resolution
- STR is active
- STR is pending (new STR or additional information available)
Trouble reports shall be processed using the following steps. 
 When a trouble report is received it must be classified at one of the 
following levels:
- Request for enhancement
- Documentation error
- Unable to print a file
- Unable to print to a printer
- Unable to print at all
The scope of the problem should also be determined as:
- Specific to a machine
- Specific to an operating system
- Applies to all machines and operating systems
Once the level and scope of the trouble report is determined the 
software sub-system(s) involved with the problem are determined. This 
may involve additional communication with the user or vendor to isolate 
the problem to a specific cause.When the sub-system(s) involved have been identified, an engineer 
will then determine the change(s) needed and estimate the time required 
for the change(s). 
 Corrections are scheduled based upon the severity and complexity of 
the problem. Once all changes have been made, documented, and tested 
successfully a new software release snapshot is generated. Additional 
tests are added as necessary for proper testing of the changes. 
 The user or vendor is notified when the fix is available or if the 
problem was caused by user error. 
 CUPS uses a three-part version number separated by periods to 
represent the major, minor, and patch release numbers: 
major.minor.patch
1.0.0
 Beta-test releases are indentified by appending the letter B followed 
by the build number: 
major.minor.patchbbuild
1.0.0b1
 A CVS snapshot is generated for every beta and final release and uses 
the version number preceded by the letter "v" and with the decimal 
points replaced by underscores: 
v1_0_0b1
v1_0_0
 Each change that corrects a fault in a software sub-system increments 
the patch release number. If a change affects the software design of 
CUPS then the minor release number will be incremented and the patch 
release number reset to 0. If CUPS is completely redesigned the major 
release number will be incremented and the minor and patch release 
numbers reset to 0: 
1.0.0b1    First beta release
1.0.0b2    Second beta release
1.0.0      First production release
1.0.1b1    First beta of 1.0.1
1.0.1      Production release of 1.0.1
1.1.0b1    First beta of 1.1.0
1.1.0      Production release of 1.1.0
2.0.0b1    First beta of 2.0.0
2.0.0      Production release of 2.0.0
 Software releases shall be generated for each successfully completed 
software trouble report. All object and executable files shall be 
deleted prior to performing a full build to ensure that source files 
are recompiled. 
 Software testing shall be conducted according to the CUPS Software 
Test Plan, CUPS-STP-1.0. Failed tests cause STRs to be generated to 
correct the problems found. 
 When testing has been completed successfully a new distribution image 
is created from the current CVS code "snapshot". No production release 
shall contain software that has not passed the appropriate software 
tests. 
- C 
- A computer language. 
- parallel 
- Sending or receiving data more than 1 bit at a time. 
- pipe 
- A one-way communications channel between two programs. 
- serial 
- Sending or receiving data 1 bit at a time. 
- socket 
- A two-way network communications channel. 
- ASCII 
- American Standard Code for Information Interchange 
- CUPS 
- Common UNIX Printing System 
- ESC/P 
- EPSON Standard Code for Printers 
- FTP 
- File Transfer Protocol 
- HP-GL 
- Hewlett-Packard Graphics Language 
- HP-PCL 
- Hewlett-Packard Printer Control Language 
- HP-PJL 
- Hewlett-Packard Printer Job Language 
- IETF 
- Internet Engineering Task Force 
- IPP 
- Internet Printing Protocol 
- ISO 
- International Standards Organization 
- LPD 
- Line Printer Daemon 
- MIME 
- Multimedia Internet Mail Exchange 
- PCL 
- Page Control Language 
- PPD 
- PostScript Printer Description 
- SMB 
- Server Message Block 
- TFTP 
- Trivial File Transfer Protocol 
These coding requirements provide detailed information on source file 
formatting and documentation content. These guidelines shall be applied 
to all C and C++ source files provided with CUPS. 
 All source files names shall be 16 characters or less in length to 
ensure compatibility with older UNIX filesystems. Source files 
containing functions shall have an extension of ".c" for ANSI C and 
".cpp" for C++ source files. All other "include" files shall have an 
extension of ".h". 
 The top of each source file shall contain a header giving the name of 
the file, the purpose or nature of the source file, the copyright and 
licensing notice, and the functions contained in the file.  The file 
name and revision information is provided by the CVS "$Id: cmp.shtml,v 
1.4 1999/09/22 20:06:18 mike Exp $" tag:
/*
 * "$Id$"
 *
 *   Description of file contents.
 *
 *   Copyright 1997-1999 by Easy Software Products, all rights
 *   reserved.
 *
 *   These coded instructions, statements, and computer programs are
 *   the property of Easy Software Products and are protected by
 *   Federal copyright law.  Distribution and use rights are outlined
 *   in the file "LICENSE.txt" which should have been included with
 *   this file.  If this file is missing or damaged please contact
 *   Easy Software Products at:
 *
 *       Attn: CUPS Licensing Information
 *       Easy Software Products
 *       44145 Airport View Drive, Suite 204
 *       Hollywood, Maryland 20636-3111 USA
 *
 *       Voice: (301) 373-9603
 *       EMail: cups-info@cups.org
 *         WWW: http://www.cups.org
 *
 * Contents:
 *
 *   function1() - Description 1.
 *   function2() - Description 2.
 *   function3() - Description 3.
 */
 The bottom of each source file shall contain a trailer giving the name 
of the file using the CVS "$Id: cmp.shtml,v 1.4 1999/09/22 20:06:18 
mike Exp $" tag. The primary purpose of this is to mark the end of a 
source file; if the trailer is missing it is possible that code has 
been lost near the end of the file: 
/*
 * End of "$Id$".
 */
 Functions with a global scope shall be capitalized ("DoThis", 
"DoThat", "DoSomethingElse", etc.) The only exception to this rule 
shall be the CUPS interface library functions which may begin with a 
prefix word in lowercase ("cupsDoThis", "cupsDoThat", etc.) 
Functions with a local scope shall be declared "static" and be 
lowercase with underscores between words ("do_this", "do_that", 
"do_something_else", etc.) 
 Each function shall begin with a comment header describing what the 
function does, the possible input limits (if any), and the possible 
output values (if any), and any special information needed: 
/*
 * 'do_this()' - Compute y = this(x).
 *
 * Notes: none.
 */
static float     /* O - Inverse power value, 0.0 <= y <= 1.0 */
do_this(float x) /* I - Power value (0.0 <= x <= 1.0) */
{
 ...
 return (y);
}
 Methods shall be in lowercase with underscores between words 
("do_this", "do_that", "do_something_else", etc.) 
 Each method shall begin with a comment header describing what the 
method does, the possible input limits (if any), and the possible 
output values (if any), and any special information needed: 
/*
 * 'class::do_this()' - Compute y = this(x).
 *
 * Notes: none.
 */
float                   /* O - Inverse power value, 0.0 <= y <= 1.0 */
class::do_this(float x) /* I - Power value (0.0 <= x <= 1.0) */
{
 ...
 return (y);
}
 Variables with a global scope shall be capitalized ("ThisVariable", 
"ThatVariable", "ThisStateVariable", etc.) The only exception to this 
rule shall be the CUPS interface library global variables which must 
begin with the prefix "cups" ("cupsThisVariable", "cupsThatVariable", 
etc.) Global variables shall be replaced by function arguments whenever 
possible. 
Variables with a local scope shall be lowercase with underscores 
between words ("this_variable", "that_variable", etc.) Any local 
variables shared by functions within a source file shall be declared 
"static". 
 Each variable shall be declared on a separate line and shall be 
immediately followed by a comment block describing the variable: 
int this_variable;   /* The current state of this */
int that_variable;   /* The current state of that */
 All type names shall be lowercase with underscores between words and 
"_t" appended to the end of the name ("this_type_t", "that_type_t", 
etc.) 
 Each type shall have a comment block immediately before the typedef: 
/*
 * This type is for CUPS foobar options.
 */
typedef int cups_this_type_t;
 All structure names shall be lowercase with underscores between words 
and "_str" appended to the end of the name ("this_struct_str", 
"that_struct_str", etc.) 
 Each structure shall have a comment block immediately before the 
struct and each member shall be documented in accordance with the 
variable naming policy above: 
/*
 * This structure is for CUPS foobar options.
 */
struct cups_this_struct_str
{
  int this_member;   /* Current state for this */
  int that_member;   /* Current state for that */
};
 All class names shall be lowercase with underscores between words 
("this_class", "that_class", etc.) 
 Each class shall have a comment block immediately before the class and 
each member shall be documented in accordance with the variable naming 
policy above: 
/*
 * This class is for CUPS foobar options.
 */
class cups_this_class
{
  int this_member;   /* Current state for this */
  int that_member;   /* Current state for that */
};
 All constant names shall be uppercase with underscored between words 
("THIS_CONSTANT", "THAT_CONSTANT", etc.) Constants defined for the CUPS 
interface library must begin with an uppercase prefix 
("CUPS_THIS_CONSTANT", "CUPS_THAT_CONSTANT", etc.) 
Typed enumerations shall be used whenever possible to allow for type 
checking by the compiler. 
 Comment blocks shall immediately follow each constant: 
enum
{
  CUPS_THIS_TRAY,   /* This tray */
  CUPS_THAT_TRAY    /* That tray */
};
 All source code shall utilize block comments within functions to 
describe the operations being performed by a group of statements: 
/*
 * Clear the state array before we begin...
 */
for (i = 0; i < (sizeof(array) / sizeof(sizeof(array[0])); i ++)
  array[i] = STATE_IDLE;
/*
 * Wait for state changes...
 */
do
{
  for (i = 0; i < (sizeof(array) / sizeof(sizeof(array[0])); i ++)
    if (array[i] != STATE_IDLE)
      break;
  if (i == (sizeof(array) / sizeof(array[0])))
    sleep(1);
} while (i == (sizeof(array) / sizeof(array[0])));
B.9.2.a Indentation
 All code blocks enclosed by brackets shall begin with the opening 
brace on a new line. The code then follows starting on a new line after 
the brace and is indented 2 spaces. The closing brace is then placed on 
a new line following the code at the original indentation: 
{
  int i; /* Looping var */
 /*
  * Process foobar values from 0 to 999...
  */
  for (i = 0; i < 1000; i ++)
  {
    do_this(i);
    do_that(i);
  }
}
 Single-line statements following "do", "else", "for", "if", and 
"while" shall be indented 2 spaces as well. Blocks of code in a 
"switch" block shall be indented 4 spaces after each "case" and 
"default" case: 
switch (array[i])
{
  case STATE_IDLE :
      do_this(i);
      do_that(i);
      break;
  default :
      do_nothing(i);
      break;
}
B.9.2.b Spacing
 A space shall follow each reserved word ("if", "while", etc.) Spaces 
shall not be inserted between a function name and the arguments in 
parenthesis. 
B.9.2.c Return Values
 Parenthesis shall surround values returned from a function using 
"return": 
return (STATE_IDLE);
B.9.2.d Loops
 Whenever convenient loops should count downward to zero to improve 
program performance: 
for (i = sizeof(array) / sizeof(array[0]) - 1; i >= 0; i --)
  array[i] = STATE_IDLE;
| Summary of Problem: | ________________________________________ | 
|---|
| Problem Severity: | __1=RFE __2=Documentation-Error
 __3=Unable-to-Print-a-File
 __4=Unable-to-Print-to-a-Printer
 __5=Unable-to-Print-at-All
 | 
|---|
| Problem Scope: | __1=Machine 
__2=Operating-System __3=All | 
|---|
| Detailed Description of Problem: | ________________________________________ ________________________________________
 ________________________________________
 ________________________________________
 ________________________________________
 ________________________________________
 | 
|---|