cmp.html   [plain text]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "">
<TITLE>CUPS Configuration Management Plan</TITLE>
<META NAME="author" CONTENT="Easy Software Products">
<META NAME="copyright" CONTENT="Copyright 1997-2002, All Rights Reserved">
<META NAME="docnumber" CONTENT="CUPS-CMP-1.1">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=iso-8859-1">
<STYLE TYPE="text/css"><!--
BODY { font-family: serif }
H1 { font-family: sans-serif }
H2 { font-family: sans-serif }
H3 { font-family: sans-serif }
H4 { font-family: sans-serif }
H5 { font-family: sans-serif }
H6 { font-family: sans-serif }
SUB { font-size: smaller }
SUP { font-size: smaller }
PRE { font-family: monospace }
<CENTER><A HREF="#CONTENTS"><IMG SRC="images/cups-large.gif" BORDER="0" WIDTH="431" HEIGHT="511"><BR>
<H1>CUPS Configuration Management Plan</H1></A><BR>
Easy Software Products<BR>
Copyright 1997-2002, All Rights Reserved<BR>
<H1 ALIGN="CENTER"><A NAME="CONTENTS">Table of Contents</A></H1>
<BR><B><A HREF="#1">1 Scope</A></B>
<LI><A HREF="#1_1">1.1 Identification</A></LI>
<LI><A HREF="#1_2">1.2 System Overview</A></LI>
<LI><A HREF="#1_3">1.3 Document Overview</A></LI>
<B><A HREF="#2">2 References</A></B>
<LI><A HREF="#2_1">2.1 CUPS Documentation</A></LI>
<LI><A HREF="#2_2">2.2 Other Documents</A></LI>
<B><A HREF="#3">3 File Management</A></B>
<LI><A HREF="#3_1">3.1 Directory Structure</A></LI>
<LI><A HREF="#3_2">3.2 Source Files</A></LI>
<LI><A HREF="#3_3">3.3 Configuration Management</A></LI>
<B><A HREF="#4">4 Trouble Report Processing</A></B>
<LI><A HREF="#4_1">4.1 Classification</A></LI>
<LI><A HREF="#4_2">4.2 Identification</A></LI>
<LI><A HREF="#4_3">4.3 Correction</A></LI>
<LI><A HREF="#4_4">4.4 Notification</A></LI>
<B><A HREF="#5">5 Software Releases</A></B>
<LI><A HREF="#5_1">5.1 Version Numbering</A></LI>
<LI><A HREF="#5_2">5.2 Generation</A></LI>
<LI><A HREF="#5_3">5.3 Testing</A></LI>
<LI><A HREF="#5_4">5.4 Release</A></LI>
<B><A HREF="#6">A Glossary</A></B>
<LI><A HREF="#6_1">A.1 Terms</A></LI>
<LI><A HREF="#6_2">A.2 Acronyms</A></LI>
<B><A HREF="#7">B Coding Requirements</A></B>
<LI><A HREF="#7_1">B.1 Source Files</A></LI>
<LI><A HREF="#7_1_1">B.1.1 Naming</A></LI>
<LI><A HREF="#7_1_2">B.1.2 Documentation</A></LI>
<LI><A HREF="#7_2">B.2 Functions</A></LI>
<LI><A HREF="#7_2_1">B.2.1 Naming</A></LI>
<LI><A HREF="#7_2_2">B.2.2 Documentation</A></LI>
<LI><A HREF="#7_3">B.3 Methods</A></LI>
<LI><A HREF="#7_3_1">B.3.1 Naming</A></LI>
<LI><A HREF="#7_3_2">B.3.2 Documentation</A></LI>
<LI><A HREF="#7_4">B.4 Variables</A></LI>
<LI><A HREF="#7_4_1">B.4.1 Naming</A></LI>
<LI><A HREF="#7_4_2">B.4.2 Documentation</A></LI>
<LI><A HREF="#7_5">B.5 Types</A></LI>
<LI><A HREF="#7_5_1">B.5.1 Naming</A></LI>
<LI><A HREF="#7_5_2">B.5.2 Documentation</A></LI>
<LI><A HREF="#7_6">B.6 Structures</A></LI>
<LI><A HREF="#7_6_1">B.6.1 Naming</A></LI>
<LI><A HREF="#7_6_2">B.6.2 Documentation</A></LI>
<LI><A HREF="#7_7">B.7 Classes</A></LI>
<LI><A HREF="#7_7_1">B.7.1 Naming</A></LI>
<LI><A HREF="#7_7_2">B.7.2 Documentation</A></LI>
<LI><A HREF="#7_8">B.8 Constants</A></LI>
<LI><A HREF="#7_8_1">B.8.1 Naming</A></LI>
<LI><A HREF="#7_8_2">B.8.2 Documentation</A></LI>
<LI><A HREF="#7_9">B.9 Code</A></LI>
<LI><A HREF="#7_9_1">B.9.1 Documentation</A></LI>
<LI><A HREF="#7_9_2">B.9.2 Style</A></LI>
<B><A HREF="#8">C Software Trouble Report Form</A></B><HR>
<H1><A NAME="1">1 Scope</A></H1>
<H2><A NAME="1_1">1.1 Identification</A></H2>
 This configuration management plan document provides the guidelines for
 development and maintenance of the Common UNIX Printing System (&quot;CUPS&quot;)
 Version 1.1 software.
<H2><A NAME="1_2">1.2 System Overview</A></H2>
<P>CUPS provides a portable printing layer for UNIX&reg;-based operating
 systems. It has been developed by<A HREF=""> Easy
 Software Products</A> to promote a standard printing solution for all
 UNIX vendors and users. CUPS provides the System V and Berkeley
 command-line interfaces.</P>
<P>CUPS uses the Internet Printing Protocol (&quot;IPP&quot;) as the basis for
 managing print jobs and queues. The Line Printer Daemon (&quot;LPD&quot;) Server
 Message Block (&quot;SMB&quot;), and AppSocket (a.k.a. JetDirect) protocols are
 also supported with reduced functionality. CUPS adds network printer
 browsing and PostScript Printer Description (&quot;PPD&quot;) based printing
 options to support real-world printing under UNIX.</P>
<P>CUPS also includes a customized version of GNU Ghostscript (currently
 based off GNU Ghostscript 5.50) and an image file RIP that are used to
 support non-PostScript printers. Sample drivers for HP and EPSON
 printers are included that use these filters.</P>
<H2><A NAME="1_3">1.3 Document Overview</A></H2>
 This configuration management document is organized into the following
<LI>1 - Scope</LI>
<LI>2 - References</LI>
<LI>3 - File Management</LI>
<LI>4 - Trouble Report Processing</LI>
<LI>5 - Software Releases</LI>
<LI>A - Glossary</LI>
<LI>B - Coding Requirements</LI>
<H1><A NAME="2">2 References</A></H1>
<H2><A NAME="2_1">2.1 CUPS Documentation</A></H2>
<P>The following CUPS documentation is referenced by this document:</P>
<LI>CUPS-CMP-1.1: CUPS Configuration Management Plan</LI>
<LI>CUPS-IDD-1.1: CUPS System Interface Design Description</LI>
<LI>CUPS-IPP-1.1: CUPS Implementation of IPP</LI>
<LI>CUPS-SAM-1.1.x: CUPS Software Administrators Manual</LI>
<LI>CUPS-SDD-1.1: CUPS Software Design Description</LI>
<LI>CUPS-SPM-1.1.x: CUPS Software Programming Manual</LI>
<LI>CUPS-SSR-1.1: CUPS Software Security Report</LI>
<LI>CUPS-STP-1.1: CUPS Software Test Plan</LI>
<LI>CUPS-SUM-1.1.x: CUPS Software Users Manual</LI>
<LI>CUPS-SVD-1.1: CUPS Software Version Description</LI>
<H2><A NAME="2_2">2.2 Other Documents</A></H2>
<P>The following non-CUPS documents are referenced by this document:</P>
<LI><A HREF="">
Adobe PostScript Printer Description File Format Specification, Version
<LI><A HREF="">
Adobe PostScript Language Reference, Third Edition.</A></LI>
<LI>IPP: Job and Printer Set Operations</LI>
<LI>IPP/1.1: Encoding and Transport</LI>
<LI>IPP/1.1: Implementers Guide</LI>
<LI>IPP/1.1: Model and Semantics</LI>
<LI><A HREF="">RFC 1179, Line Printer
 Daemon Protocol</A></LI>
<LI><A HREF="">RFC 2567, Design Goals
 for an Internet Printing Protocol</A></LI>
<LI><A HREF="">RFC 2568, Rationale
 for the Structure of the Model and Protocol</A> for the Internet
 Printing Protocol</LI>
<LI><A HREF="">RFC 2569, Mapping
 between LPD and IPP Protocols</A></LI>
<LI><A HREF="">RFC 2616, Hypertext
 Transfer Protocol -- HTTP/1.1</A></LI>
<LI><A HREF="">RFC 2617, HTTP
 Authentication: Basic and Digest Access</A> Authentication</LI>
<H1><A NAME="3">3 File Management</A></H1>
<H2><A NAME="3_1">3.1 Directory Structure</A></H2>
 Each source file shall be placed a sub-directory corresponding to the
 software sub-system it belongs to (&quot;scheduler&quot;, &quot;cups&quot;, etc.) To remain
 compatible with older UNIX filesystems, directory names shall not
 exceed 16 characters in length.
<H2><A NAME="3_2">3.2 Source Files</A></H2>
 Source files shall be documented and formatted as described in Appendix
 B, Coding Requirements.
<H2><A NAME="3_3">3.3 Configuration Management</A></H2>
 Source files shall be placed under the control of the Concurrent
 Versions System (&quot;CVS&quot;) software. Source files shall be &quot;checked in&quot;
 with each change so that modifications can be tracked.
<P>Documentation on the CVS software is included with the whitepaper,
 &quot;CVS II: Parallelizing Software Development&quot;.</P>
<H1><A NAME="4">4 Trouble Report Processing</A></H1>
 A Software Trouble Report (&quot;STR&quot;) 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:
<LI>STR is closed with complete resolution</LI>
<LI>STR is closed without resolution</LI>
<LI>STR is active</LI>
<LI>STR is pending (new STR or additional information available)</LI>
 Trouble reports shall be processed using the following steps.
<H2><A NAME="4_1">4.1 Classification</A></H2>
 When a trouble report is received it must be classified at one of the
 following levels:
<LI>Request for enhancement</LI>
<LI>Documentation error</LI>
<LI>Unable to print a file</LI>
<LI>Unable to print to a printer</LI>
<LI>Unable to print at all</LI>
 The scope of the problem should also be determined as:
<LI>Specific to a machine</LI>
<LI>Specific to an operating system</LI>
<LI>Applies to all machines and operating systems</LI>
<H2><A NAME="4_2">4.2 Identification</A></H2>
 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.
<P>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).</P>
<H2><A NAME="4_3">4.3 Correction</A></H2>
 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.
<H2><A NAME="4_4">4.4 Notification</A></H2>
 The user or vendor is notified when the fix is available or if the
 problem was caused by user error.
<H1><A NAME="5">5 Software Releases</A></H1>
<H2><A NAME="5_1">5.1 Version Numbering</A></H2>
 CUPS uses a three-part version number separated by periods to represent
 the major, minor, and patch release numbers:
 Beta-test releases are indentified by appending the letter B followed
 by the build number:
 A CVS snapshot is generated for every beta and final release and uses
 the version number preceded by the letter &quot;v&quot; and with the decimal
 points replaced by underscores:
 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.1.0b1    First beta release
1.1.0b2    Second beta release
1.1.0      First production release
1.1.1b1    First beta of 1.1.1
1.1.1      Production release of 1.1.1
1.1.1b1    First beta of 1.1.1
1.1.1      Production release of 1.1.1
2.0.0b1    First beta of 2.0.0
2.0.0      Production release of 2.0.0
<H2><A NAME="5_2">5.2 Generation</A></H2>
 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.
<H2><A NAME="5_3">5.3 Testing</A></H2>
 Software testing shall be conducted according to the CUPS Software Test
 Plan, CUPS-STP-1.1. Failed tests cause STRs to be generated to correct
 the problems found.
<H2><A NAME="5_4">5.4 Release</A></H2>
 When testing has been completed successfully a new distribution image
 is created from the current CVS code &quot;snapshot&quot;. No production release
 shall contain software that has not passed the appropriate software
<H1 TYPE="A" VALUE="1"><A NAME="6">A Glossary</A></H1>
<H2><A NAME="6_1">A.1 Terms</A></H2>
<DD>A computer language.</DD>
<DD>Sending or receiving data more than 1 bit at a time.</DD>
<DD>A one-way communications channel between two programs.</DD>
<DD>Sending or receiving data 1 bit at a time.</DD>
<DD>A two-way network communications channel.</DD>
<H2><A NAME="6_2">A.2 Acronyms</A></H2>
<DD>American Standard Code for Information Interchange</DD>
<DD>Common UNIX Printing System</DD>
<DD>EPSON Standard Code for Printers</DD>
<DD>File Transfer Protocol</DD>
<DD>Hewlett-Packard Graphics Language</DD>
<DD>Hewlett-Packard Page Control Language</DD>
<DD>Hewlett-Packard Printer Job Language</DD>
<DD>Internet Engineering Task Force</DD>
<DD>Internet Printing Protocol</DD>
<DD>International Standards Organization</DD>
<DD>Line Printer Daemon</DD>
<DD>Multimedia Internet Mail Exchange</DD>
<DD>PostScript Printer Description</DD>
<DD>Server Message Block</DD>
<DD>Trivial File Transfer Protocol</DD>
<H1><A NAME="7">B Coding Requirements</A></H1>
 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.
<H2><A NAME="7_1">B.1 Source Files</A></H2>
<H3><A NAME="7_1_1">B.1.1 Naming</A></H3>
 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 &quot;.c&quot; for ANSI C and
 &quot;.cxx&quot; for C++ source files. All other &quot;include&quot; files shall have an
 extension of &quot;.h&quot;.
<H3><A NAME="7_1_2">B.1.2 Documentation</A></H3>
 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 &quot;$Id$&quot; tag:
 * &quot;$Id$&quot;
 *   Description of file contents.
 *   Copyright 1997-2002 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 &quot;LICENSE.txt&quot; 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
 *       44141 Airport View Drive, Suite 204
 *       Hollywood, Maryland 20636-3111 USA
 *       Voice: (301) 373-9600
 *       EMail:
 *         WWW:
 * 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 &quot;$Id$&quot; 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 &quot;$Id$&quot;.
<H2><A NAME="7_2">B.2 Functions</A></H2>
<H3><A NAME="7_2_1">B.2.1 Naming</A></H3>
 Functions with a global scope shall be capitalized (&quot;DoThis&quot;, &quot;DoThat&quot;,
 &quot;DoSomethingElse&quot;, etc.) The only exception to this rule shall be the
 CUPS interface library functions which may begin with a prefix word in
 lowercase (&quot;cupsDoThis&quot;, &quot;cupsDoThat&quot;, etc.)
<P>Functions with a local scope shall be declared &quot;static&quot; and be
 lowercase with underscores between words (&quot;do_this&quot;, &quot;do_that&quot;,
 &quot;do_something_else&quot;, etc.)</P>
<H3><A NAME="7_2_2">B.2.2 Documentation</A></H3>
 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 &lt;= y &lt;= 1.1 */
do_this(float x) /* I - Power value (0.0 &lt;= x &lt;= 1.1) */
  return (y);
<H2><A NAME="7_3">B.3 Methods</A></H2>
<H3><A NAME="7_3_1">B.3.1 Naming</A></H3>
 Methods shall be in lowercase with underscores between words
 (&quot;do_this&quot;, &quot;do_that&quot;, &quot;do_something_else&quot;, etc.)
<H3><A NAME="7_3_2">B.3.2 Documentation</A></H3>
 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 &lt;= y &lt;= 1.0 */
class::do_this(float x) /* I - Power value (0.0 &lt;= x &lt;= 1.0) */
  return (y);
<H2><A NAME="7_4">B.4 Variables</A></H2>
<H3><A NAME="7_4_1">B.4.1 Naming</A></H3>
 Variables with a global scope shall be capitalized (&quot;ThisVariable&quot;,
 &quot;ThatVariable&quot;, &quot;ThisStateVariable&quot;, etc.) The only exception to this
 rule shall be the CUPS interface library global variables which must
 begin with the prefix &quot;cups&quot; (&quot;cupsThisVariable&quot;, &quot;cupsThatVariable&quot;,
 etc.) Global variables shall be replaced by function arguments whenever
<P>Variables with a local scope shall be lowercase with underscores
 between words (&quot;this_variable&quot;, &quot;that_variable&quot;, etc.) Any local
 variables shared by functions within a source file shall be declared
<H3><A NAME="7_4_2">B.4.2 Documentation</A></H3>
 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 */
<H2><A NAME="7_5">B.5 Types</A></H2>
<H3><A NAME="7_5_1">B.5.1 Naming</A></H3>
 All type names shall be lowercase with underscores between words and
 &quot;_t&quot; appended to the end of the name (&quot;this_type_t&quot;, &quot;that_type_t&quot;,
<H3><A NAME="7_5_2">B.5.2 Documentation</A></H3>
 Each type shall have a comment block immediately before the typedef:
 * This type is for CUPS foobar options.
typedef int cups_this_type_t;
<H2><A NAME="7_6">B.6 Structures</A></H2>
<H3><A NAME="7_6_1">B.6.1 Naming</A></H3>
 All structure names shall be lowercase with underscores between words
 and &quot;_str&quot; appended to the end of the name (&quot;this_struct_str&quot;,
 &quot;that_struct_str&quot;, etc.)
<H3><A NAME="7_6_2">B.6.2 Documentation</A></H3>
 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 */
<H2><A NAME="7_7">B.7 Classes</A></H2>
<H3><A NAME="7_7_1">B.7.1 Naming</A></H3>
 All class names shall be lowercase with underscores between words
 (&quot;this_class&quot;, &quot;that_class&quot;, etc.)
<H3><A NAME="7_7_2">B.7.2 Documentation</A></H3>
 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 */
<H2><A NAME="7_8">B.8 Constants</A></H2>
<H3><A NAME="7_8_1">B.8.1 Naming</A></H3>
 All constant names shall be uppercase with underscored between words
 (&quot;THIS_CONSTANT&quot;, &quot;THAT_CONSTANT&quot;, etc.) Constants defined for the CUPS
 interface library must begin with an uppercase prefix
 (&quot;CUPS_THIS_CONSTANT&quot;, &quot;CUPS_THAT_CONSTANT&quot;, etc.)
<P>Typed enumerations shall be used whenever possible to allow for type
 checking by the compiler.</P>
<H3><A NAME="7_8_2">B.8.2 Documentation</A></H3>
 Comment blocks shall immediately follow each constant:
  CUPS_THIS_TRAY,   /* This tray */
  CUPS_THAT_TRAY    /* That tray */
<H2><A NAME="7_9">B.9 Code</A></H2>
<H3><A NAME="7_9_1">B.9.1 Documentation</A></H3>
 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 &lt; (sizeof(array) / sizeof(sizeof(array[0])); i ++)
  array[i] = STATE_IDLE;

 * Wait for state changes...

  for (i = 0; i &lt; (sizeof(array) / sizeof(sizeof(array[0])); i ++)
    if (array[i] != STATE_IDLE)

  if (i == (sizeof(array) / sizeof(array[0])))
} while (i == (sizeof(array) / sizeof(array[0])));
<H3><A NAME="7_9_2">B.9.2 Style</A></H3>
<H4 TYPE="a">B.9.2.a Indentation</H4>
 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 &lt; 1000; i ++)
 Single-line statements following &quot;do&quot;, &quot;else&quot;, &quot;for&quot;, &quot;if&quot;, and &quot;while&quot;
 shall be indented 2 spaces as well. Blocks of code in a &quot;switch&quot; block
 shall be indented 4 spaces after each &quot;case&quot; and &quot;default&quot; case:
switch (array[i])
  case STATE_IDLE :
  default :
<H4>B.9.2.b Spacing</H4>
 A space shall follow each reserved word (&quot;if&quot;, &quot;while&quot;, etc.) Spaces
 shall not be inserted between a function name and the arguments in
<H4>B.9.2.c Return Values</H4>
 Parenthesis shall surround values returned from a function using
return (STATE_IDLE);
<H4>B.9.2.d Loops</H4>
 Whenever convenient loops should count downward to zero to improve
 program performance:
for (i = sizeof(array) / sizeof(array[0]) - 1; i &gt;= 0; i --)
  array[i] = STATE_IDLE;
<H1 ALIGN="RIGHT"><A NAME="8">C Software Trouble Report Form</A></H1>
<TR><TH ALIGN="RIGHT">Summary of Problem:</TH><TD ALIGN="LEFT">
<TR><TH ALIGN="RIGHT">Problem Severity:</TH><TD ALIGN="LEFT">__1=RFE
<BR> __2=Documentation-Error
<BR> __3=Unable-to-Print-a-File
<BR> __4=Unable-to-Print-to-a-Printer
<BR> __5=Unable-to-Print-at-All</TD></TR>
<TR><TH ALIGN="RIGHT">Problem Scope:</TH><TD ALIGN="LEFT">__1=Machine
 __2=Operating-System __3=All</TD></TR>
<TR><TH ALIGN="RIGHT" VALIGN="TOP">Detailed Description of Problem:</TH><TD
<BR> ________________________________________
<BR> ________________________________________
<BR> ________________________________________
<BR> ________________________________________
<BR> ________________________________________</TD></TR>