
CONVERGENT TECHNOLOGIES

RELEASE NOTICE FOR
2.1 EXTENDED MULTIPLAN 

Revised December 19, 1985


SECTION   TITLE	PAGE
	1.0	Description of Program	 2
	2.0	Changes from Prior Version	 3
		2.1  Problems Closed in this Release	 3
		2.2  Changes from Release 2.0	 6
		     2.2.1  Support for Chart Designer
		             and Art Designer	 6
		     2.2.2  RDB Query Enhancement	 7
		     2.2.3  Miscellaneous Enhancements	 8
		2.3  Changes from Release 1.1	 8
	3.0	Contents of Distribution Diskettes	15
	4.0	Installation Procedures	16
		4.1  StandAlone Hard Disk Systems	16
		4.2  Master Hard Disk Systems	17
		4.3  MegaFrame SRP Systems	18
		4.4  Document Designer Recognition	19
	5.0	Required Files	20
	6.0	System Software Compatibility	20
	7.0	Resource RequirementsUtilization	20
		7.1  Memory RequirementsUtilization	20
		7.2  Disk RequirementsUtilization	21
	8.0	Supplementary Information	21
		8.1  Updating to Version 2.1 from 
		      Standard Multiplan	21
		8.2  Configuring the Sys.Printers Files	21
	9.0	New Status Codes	23
	10.0	Known Errors	24
1.0	Description of Program
{This document describes the 2.1 version of Extended Multiplan.  This section and the sections that follow provide a description of the product, contents of the Distribution Diskettes, installation procedures, and other information pertinent to this release of Extended Multiplan.}
{2.1 Extended Multiplan is a powerful spreadsheet program that serves as a financial planning tool.  It can be effectively used in budgeting, payroll, inventory, accounting, bidding and other business operations.  It is an interactive program in which you can enter words, numbers and formulas.  2.1 Extended Multiplan rapidly computes, sorts and displays relevant information, eliminating the need for many hours of slow, tedious manual calculation.}
{In addition to powerful spreadsheet capabilities, 2.1 Extended Multiplan is extensively integrated with other Convergent Technologies software products, including CTMail, Business Graphics Package, Word Processor, Document Designer, Chart Designer, Art Designer, and CTDBMS data base management system.}
{2.0	Changes from Prior Version
2.1 Extended Multiplan includes a number of enhancements.  The most significant functional changes are: 1) support for Chart Designer, 2) support for Art Designer, and 3) enhanced support for Document Designer.  The product is used as described in the Multiplan Reference Manual and the Extended Multiplan User's Guide.  The  Extended Multiplan Reference Manual, first edition, describes this product fully and is soon to be available.  It is available as a preliminary manual now.
}
{2.1	Problems Closed in this Release
SPR	A697, A1801, A2045:  A corrupt spreadsheet file was left on the disk if a disk full error occured during a Transfer Save operation.  In this release, the corrupt file is no longer left on the disk if such an error occurs.  In order to save the current spreadsheet, the user must remove unwanted files from the disk with the Transfer Delete command, and then retry the Transfer Save operation.}
{SPR	A887, A1400, A1403, A1404:  A number of messages could not be changed using the Nationalization kit.}
{SPR	A987:  A 31 character value in the Graph Options title field caused the error Name too long to appear, but all 31 characters were used anyway.}
{SPR	A1419: Blank cells in line graphs were graphed as zero values by the Business Graphics Package.  With Chart Designer 1.0, these blank cells may be left out of the graph entirely, or if the cell is in the middle of the line, interpolation may be performed.  Refer to the following section on Enhancements for more information.}
{SPR	A1669: If an existing nondefault format for a whole row (or column) was replaced with a nondefault format, the new format might not be set correctly.  If the new format was continuous, a long text value in the row would not be displayed correctly.}
{SPR	A1796, A3010: A sheet with external links received VALUE errors on return from the Business Graphics Package, or sometimes resulted in a fatal error.}
{SPR	A1822: A sheet with little free memory received Insufficient memory when the user tried to blank a large area of formatted cells.  Contents of cells were sometimes garbage after this happened.}
{SPR	A1993: When a file prefix was set using the Transfer Options path, the RDB List command returned the personal data base names with the file prefix, causing later failure of RDB commands using those data base names.}
{SPR	A2095, A3217, A3235: The SQRT function was off by a factor of 10 for some numbers between 1 and 0, like 0.01.  The STDEV function was not accurate in similar cases.}
{SPR	A3073: Could not view linked sheets using arrow keys in the from sheet field of the eXternal Copy command.}
{SPR	A3233: If R1C1 contained alpha text and a reference was made to R1C1 in another cell, zero was displayed in that cell.}
{SPR	A3339, A3340: If the AND or OR functions were applied to a range of cells, a fatal error sometimes occured.}
{SPR	A3341: The field width highlight of the Alpha command disappeared on color workstations when the first alpha character was typed.}
{SPR	A3385: The system hung if a spreadsheet with External links was returned to Document Designer.}
{o		The memory initialization logic failed if less than 4K bytes of memory was available for the spreadsheet.  It now works correctly with just 2K bytes, which is the minimum amount required.  (No SPR)}
{o		In ZOOM mode, parts of the menu were sometimes overwritten when a cell reference in a field was changed.  (No SPR)}
{o		It was sometimes possible to have multiple cell pointers after using the CHANGE WINDOW (F7) key when multiple windows were displayed.  (No SPR)}
{o		If the cell pointer was supposed to appear below row 128 on a sheet just loaded in Symbolic mode, the sheet appeared to be blank.  (No SPR)}
{o		If a volume specification was removed from the Transfer Options path, and the remaining path spec was shorter than the original volume name, the system would crash on the next Transfer Load command.  (No SPR)}
{o		Pressing the '?' key while in data entry mode caused an Invalid option error and a meaningless command area highlight.  (No SPR)}
{o		Blank cells for graph legends were sometimes sent to the Business Graphics Package as garbage data, instead of blanks.  (No SPR)}
{o		Longlived memory was reclaimed only on return from the Business Graphics Package.  Extended Multiplan now uses the ResetMemoryLL operation whenever the program is started.  (No SPR)}
{o		Line graphs with over 128 X values sometimes caused an Error 7677 in the Business Graphics Package.  (No SPR)}
{o		If an error occurred during the loading of a Symbolic file, the error message and line number were not displayed for a long enough time before processing continued.  (No SPR)}
{o		The Transfer Rename command failed with a disk error (code 203) if the current spreadsheet had other spreadsheets dependent on it.  (No SPR)
o		The RDB Query command sometimes returned incorrect results if an indexed CTDBMS relation was being queried from.  (No SPR)}

{2.2 	Changes from Release 2.0
2.2.1  Support for Chart Designer and Art Designer
	2.1 Extended Multiplan provides access to Chart Designer 1.0 and Art Designer 1.0 (they are equivalent as far as Extended Multiplan is concerned, so only Chart Designer will be mentioned from here on).  The Chart Designer program is much more capable and easier to use than its predecessor, the Business Graphics Package.  In addition, Extended Multiplan is able to access Chart Designer through the Context Manager, which speeds up Graph commands tremendously.}
{	If Chart Designer 1.0 and Context Manager (version 2.2 or later) are installed, Extended Multiplan will start the Chart Designer application when the user asks for the first graph.  From then on, the Context Manager will be used to quickly switch between the two programs, instead of the slow chaining method.}
{	Another feature offered by the combination of Extended Multiplan 2.1 and Chart Designer 1.0 is better line graphing capabilities.  In the past, blank cells in line graphs were treated as zeros by the Business Graphics Package, causing undesirable results.  With Chart Designer, blank cells are left out of line graphs.  If the user wishes, Chart Designer will connect the nonblank values in each line, to show an interpolated line.}
{2.2.2  RDB Query Enhancement
	2.1 Extended Multiplan offers improved data base query capability through an enhancement of the RDB Query command.  In the previous release, it was not possible to logically OR together criteria on two different field names, as in ((Salary < 40000) OR (NumDependents > 5)).  Such queries are now supported by a change in the handling of the Criteria area specified in the RDB Query command.}
{	Instead of ORing the criteria in each column, then ANDing the column results together, the RDB Query command now ANDs the criteria in each row, and then ORs the row results.  For simple queries, this reversal makes no difference.  However, more complex queries may require changes.}
{	Following are some examples that highlight the new functionality.  Refer to the Extended Multiplan Reference Manual for a complete discussion of the RDB commands.
1.	ORing criteria on one attribute is the same:  ((Count < 10) OR (Count >= 20))
                Count
             <10
             >=20}
{2.	ANDing criteria on  one or more attributes is the same: ((EmpId <= 900) AND (Salary < 10000))
                EmpId     Salary
             <=900     <10000}
{3.	ORing criteria on more than one attribute did not work at all in the previous release: ((NumDep > 5) OR (Salary < 9000))
                NumDep    Salary
             >5
                       <9000
	Note that the constants in the criteria area must be in different rows, to force them to be ORed together.}
{4. 	Complex criteria which assumed that AND operations occurred after OR operations must be changed:
 (((Salary < 10000) OR (Salary >= 90000))
  AND ((NumDep <= 1) OR (NumDep > 10)))
                Salary    NumDep
   OLD       <10000    <=1
             >=90000   >10
	The expression must be rewritten so that the ANDs occur before the ORs:
 (((Salary < 10000) AND (NumDep <= 1))
 OR ((Salary < 10000) AND (NumDep > 10))
 OR ((Salary >= 90000) AND (NumDep <= 1))
 OR ((Salary >= 90000) AND (NumDep > 10)))
                Salary    NumDep
             <10000    <=1
   NEW       <10000    >10
             >=90000   <=1
             >=90000   >10}
{2.2.3  Miscellaneous Enhancements
	Spreadsheets are now provided to accompany the examples of the Iteration option in the Extended Multiplan Reference Manual.}
{	The system date and time is now displayed after the Options command is completed.}
{	2.1 Extended Multiplan provides thorough nationalization and customization facilities for customers through a Nationalization Kit.  All messages are now modifiable, and international characters may be used almost anywhere.
}
{2.3	Changes from Release 1.1
Data Base Integration Overview	
	2.0 Extended Multiplan provides new spreadsheet capabilities through data base  integration.  To accomplish this, RDB (which stands for Relational Data Base) has been added as a new entry to the main Extended Multiplan command menu.  All data base operations are implemented as subcommands under this new entry.}
{	Details on how to use the RDB commands to do data base manipulation are fully explained in the Extended Multiplan Reference Manual, first edition.  A preliminary edition of this manual is available at the time of this writing.  A brief discussion of RDB is included in this document, along with a summary of commands.  Also, some limitations on the usage of personal and CTDBMS data bases are discussed.  It is suggested this you read that section carefully.}
{	With 2.0 Extended Multiplan, users are offered a rich set of primitives for the creation, structuring, query and manipulation of relational data bases.  Unlike standalone query packages, 2.0 Extended Multiplan allows the user to draw on the rich set of spreadsheet data analysis tools and formulas once the data is retrieved from the database.  Furthermore, 2.0 Extended Multiplan differs from other packages which have integrated data base capability in a number of important ways.  In particular, data bases created through 2.0 Extended Multiplan can handle more data than will fit into a standard Multiplan worksheet or into memory.  Also, users can run multiple queries simultaneously.  Finally, 2.1 Extended Multiplan can be used to interact with data bases created by Convergent's CTDBMS package, which includes full indexing, multiuser, field level security, and data base recovery features.}
{	There are two types of data bases accessible from the spreadsheet.  At the low end, singleuser access is provided with a new Personal Data Base Management tool.  At the high end, for large, mainframe type data base support, a multiuser spreadsheet accessibility to the Convergent Technologies Data Base Management System, CTDBMS, is also included.}
{	A Personal Data Base (PDB) is a singlefile,  singleuser data base.  It can reside in any directory of the file system and contains both data dictionary information (data about the structure of the data in the database) and the data itself.  It is only accessible through 2.0 Extended Multiplan and provides a flexible data base access path for the Extended Multiplan user who is not a CTDBMS customer.}
{	As personal data bases become larger their performance may begin to degrade, and it is for improved performance reasons that customers may choose to transfer their PDB data to a CTDBMS data base.  This transfer is easily accomplished through 2.0 Extended Multiplan.  CTDBMS also provides a host of other capabilities that the Extended Multiplan user may choose to take advantage of, including journalization, rollforward and rollback recovery, field level security, multikey indexing, and multiuser concurrency control.  CTDBMS also allows for data independent application systems and includes programmatic interfaces.  Transferring data from a CTDBMS data base to a PDB is also easily accomplished through 2.0 Extended Multiplan.}

{	Summary of Commands
	RDB Query retrieves records from a relational data base and displays them on the Extended Multiplan worksheet.  The user specifies which records to retrieve by using selection criteria and where to place the retrieved data in the spreadsheet.}  
{	RDB Store adds records to a relational data base from a userspecified area on the spreadsheet.}
{	RDB Modify makes changes to records in a relational data base.}
{	RDB Delete removes records from a relational data base.}
{	RDB Next allows subsequent sets of records to be displayed in the spreadsheet area specified by a previous RDB Query command.  This allows viewing of data bases which do not fit into a single spreadsheet.}
{	RDB Options allows selection of a CTDBMS data base.}
{	RDB Restructure creates, deletes, and modifies the structure of relational data bases.  Individual fields can be added, deleted, and modified.}  
{	RDB List displays information about the structure of existing databases.  It can also be used to list the personal data bases which currently exist.}
{	RDB Finish terminates a query that is in progress, that is, one on which an RDB Next command is possible.}
{	Limitations on Database Usage
A.  Currently, RDB Restructure cannot be used to alter the structure of CTDBMS data bases.  This is because CTDBMS has been designed to place its data bases under the centralized control of a data base administrator.  This administrator can accomplish the restructuring by modifying the data base schema and executing the DB Initialize command from the Executive.}
{B.  If you wish to copy a personal data base file, you must install version 10.0 (or higher) of the Convergent Executive.  This is because the file header of the PDB file contains a type code which previous versions of the Executive did not carry over to the copied file.  For the same reason, the command LCopy cannot be used to copy personal data base files.  Copying with an earlier Executive or with the LCopy command will cause the RDB  commands to be unable to access this relation.}
{Document Designer Support
	The support for the Document Designer included in this release allows Extended Multiplan to be a full member of the Document Designer Software Suite.  A document being edited by the Document Designer can now contain portions of active Extended Multiplan spreadsheets.  Active means that once inserted, the spreadsheet can continue to be edited provided the request  to edit comes from the Document Designer.  These subsequent edits are included in the spreadsheet portions of the Document Designer document.}  
{	This functionality is supported through a new communications facility available at Extended Multiplan entry and exit.  On the first entry from Document Designer for a particular document, either an existing spreadsheet can be loaded (using Transfer Load) or a new sheet can be created by keying in the new data.  On subsequent entries the object marked by the Document Designer will be loaded automatically.  Once loaded, the spreadsheet behavior is normal (that is, the user  need not be aware of the Document Designer relationship) until invocation of the Quit command.}
{	The Quit command now provides the user the additional capability to automatically return to the Document Designer with any portion of the currently active spreadsheet.  Once GO is pressed confirming the user's intention to Quit, a new prompt is displayed: Image Area:R1:255.  This is the area of the spreadsheet which will be displayed (the image) once the user has returned to the Document Designer.}
{	A default Image Area is proposed by Extended Multiplan, but the user can edit this to contain any rowcolumn reference or named area.  If a series of areas are specified, the smallest rectangle encompassing all of them is chosen.  The default Image Area proposed is the same as the current Print Options area the first time a sheet is returned to Document Designer.  On subsequent invocations of Extended Multiplan from Document Designer with a marked box, the default becomes the last Image Area used with this box.}
{	Return to the Document Designer automatically occurs once the user has pressed GO to the Image Area prompt.  No uservisible Extended Multiplan spreadsheet file is created, but the sheet is nonetheless saved on behalf of the Document Designer.  The entire spreadsheet is always transferred back to Document Designer, even if the user specified only a portion of the sheet in the Image Area.}
{	If no area is specified through the elimination of the default Image Area  (using the backspace or delete keys), no spreadsheet will be returned to the Document Designer.  All work will be lost in this case except for any work saved by the user through the Transfer Save command during the Extended Multiplan session.  The sheet sent by the Document Designer is retained unchanged.}
{	Once in the Document Designer, the user is prompted to confirm the assignment of the spreadsheet to the marked anchor character.  If no image was sent, this prompt will not appear.}
{	Two categories of error conditions can occur during Image Area creation and transfer to Document Designer.  In either case, the Extended Multiplan main command menu will return to the screen and the error condition will be displayed.  A Transfer Save can be invoked at this point to save the current work.  All other operations are also possible at this point.}
{	The two categories of conditions are file system errors (such as disk full, no available file headers, etc.) and Document Designer or communication path errors (in which case the Document Designer is no longer accessible).  In the first case, the user can clear disk space using the Transfer Delete command or by changing contexts and using the Executive (or any other application) to free the necessary space.  In the second case, Extended Multiplan cannot return to the Document Designer.  This occurs for reasons unrelated to Extended Multiplan.  In this case, the user should Transfer Save the work to a file, and invoke the Quit command to finish the Extended Multiplan session.  The Document Designer should then be reentered manually,  a new anchor character should be assigned, and Extended Multiplan reentered to attach the desired saved spreadsheet to the new anchor character.
}
{Miscellaneous Enhancements
	2.0 Extended Multiplan contains new byte streams which allow direct printing through the serial port on CWS machines and through the XC002 serial port expander module on NGEN machines.  In order to perform  direct printing on this new hardware, changes must be made to the Sys.Printers file.  For the CWS, you should user [Ptr]A as a device specification.  For the XC002, you should use [Ptr]1A, [Ptr]1B, [Ptr]1C, and [Ptr]1D as device specifications for the first XC002 and [Ptr]2A, [Ptr]2B, [Ptr]2C, and [Ptr]2D as device specifications for the second XC002.}
{	The help text has been expanded.  In particular, detailed descriptions exist for the new RDB functionality, iteration, and printing with manual paper feed.}
{	The Transfer Options command now allows CTNet node names as part of the path specification.  Spreadsheets can be loaded, saved, renamed, deleted and eXternally copied from a remote node using the path specifier.}
{3.0	Contents of Distribution Diskettes
The Extended Multiplan Distribution Diskettes are your master copy, and have been shipped writeprotected.  They should not be writeenabled, nor should they be used as a working copy.}
{If you are going to use the Graph Command, Extended Multiplan requires Chart Designer (or the Business Graphics Package) and special Graphics hardware to be present.}
{Extended Multiplan requires CTOS 9.1 or higher but if you will be graphing charts using Chart Designer, CTOS 9.6 is required.  If you have not yet installed the latest version of CTOS, do so before installing Extended Multiplan.}
{Distribution Diskette 1 contains the following files in the <CT> directory:
	XMultiplan.run	LptConfig.Sys
	Sys.Printers	PtrBConfig.Sys
Example spreadsheets are contained in the <Tutorial> directory on Distribution Diskette 1.  Copy these files to your working directory, if so desired.
	Spencer.mp	Expenses.mp
	Iteration1.mp	Iteration2.mp
	Iteration3.mp
Distribution Diskette 1 also has the directory <ReleaseNote> with the following file:
	ReleaseNotice
In addition to various standard system files, Distribution Diskette 1 contains the following file in the <Sys> directory:
	XMPCmInstall.sub	HdInstall.sub
	XMPCmInstall2.sub}	MfInstall.sub
{Distribution Diskette 2 contains the following file in the <CT> directory:
	Mp.Hlp1.0}
{4.0	Installation Procedures
2.1 Extended Multiplan 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.}
{Use the installation procedures described below (after updating the Standard Software revision level, if required).  Characters that you must type are shown in boldface.  Special keys, such as RETURN and GO, are shown in upper case.}
{4.1	StandAlone Hard Disk Systems
A.	Signon and set path at the standalone workstation.  If the Signon form is displayed, fill it in and press GO.  Set the path as follows:
Command   Path  RETURN
Path
  [Volume]	Sys       RETURN
  [Directory]	Sys       RETURN
  [Default file prefix]	          RETURN
  [Password]	(if any)  GO
  [Node]
	If your hard disk has a volume password on [Sys], fill this password into the [Password] field before pressing GO.}
{B.	Insert 2.1 Extended Multiplan Distribution Diskette 1 in drive [f0] and install as follows:
Command   Submit  RETURN
Path
  File list    [f0]<Sys>HdInstall.sub  RETURN
  [Parameters]                         GO
  [Force Expansion?]
  [Show Expansion?]
	This submit file will prompt you to insert the second Distribution Diskette at the appropriate time.}
{4.2	Master Hard Disk Systems
A.	Signon and set path at the master workstation.  If the Signon form is displayed, fill it in and press GO.  Set the path as follows:
Command   Path  RETURN
Path
  [Volume]	Sys  RETURN
  [Directory]	Sys  RETURN
  [Default file prefix]	RETURN
  [Password]	(if any)  GO
  [Node]
	If your hard disk has a volume password on [Sys], fill this password into the [Password] field before pressing GO.}
{B.	If you have a cluster system, disable the cluster workstations as follows:
	Command   Disable Cluster  GO
Disable Cluster
  [Time Interval (seconds)]
	At the conclusion of the installation procedure, you may resume cluster operations with the Resume Cluster command.}
{C.	Insert 2.1 Extended Multiplan Distribution Diskette 1 in drive [f0] and install as follows:
	Command   Submit  RETURN
Path
  File list     [f0]<Sys>HdInstall.sub  RETURN
  [Parameters]                          GO
  [Force Expansion?]
  [Show Expansion?]
	This submit file will prompt you to insert the second Distribution Diskette at the appropriate time.}
{4.3	MegaFrame SRP Systems
A.	Signon and set path at the cluster workstation.  If the Signon form is displayed, fill it in and press GO.  Set the path as follows:
Command   Path  RETURN
Path
  [Volume]	Sys  RETURN
  [Directory]	Sys  RETURN
  [Default file prefix]	RETURN
  [Password]	(if any)  GO
  [Node]
	If your MegaFrame hard disk has a volume password on [Sys], fill this password into the [Password] field before pressing GO.}
{B.	Since the MegaFrame SRP is a cluster system, be certain that all system activity ceases for the duration of the installation.  Do not disable the cluster workstations.}
{C.	Insert 2.1 Extended Multiplan Distribution Diskette 1 in drive [f0] and install as follows:
	Command   Submit  RETURN
Path
  File list     [f0]<Sys>MfInstall.sub  RETURN
  [Parameters]                          GO
  [Force Expansion?]
  [Show Expansion?]
	This submit file will prompt you to insert the second Distribution Diskette at the appropriate time.}
{4.4	Document Designer Recognition
	If you plan to use Extended Multiplan with Document Designer and Context Manager, the Context Manager configuration file used must contain a command for Extended Multiplan with the new field :DDObjectEdited:258.  If Context Manager version 2.0 (or 2.2 if Chart Designer will be used for graphing) has been installed, the appropriate Context Manager configuration file can be easily updated to allow Extended Multiplan to be invoked from the Document Designer.  Insert Extended Multiplan Distribution Diskette 1 into drive [f0] and issue the following Submit command:

Command   Submit  RETURN
Submit
  File list [f0]<Sys>XMpCmInstall.sub  GO
  [Parameters]	
  [Force Expansion?]
  [Show Expansion]}
{	This installation defines a required partition size of 300K.  This is considered to be an adequate partition size for most medium sized spreadsheets.  If larger sheets are required, or if less than 10 remains free during Extended Multiplan usage,  this partition size will have to be increased.  This is accomplished by using the CM Config File Editor command or the CM Add Application command.  See the 2.0 or 2.2 Context Manager Release Notice for more information.}
{	When using Document Designer without Context Manager, the chaining model of communication is supported.  For correct functioning of Extended Multiplan in this environment, the file [Sys]<Sys>DDConfig.Sys is required.  This file must include an entry for Extended Multiplan and should look like so:
	:CommandName:Extended Multiplan
:RunFileName:[Sys]<Sys>XMultiplan.run
:DDObjectEdited:258
:}
{5.0	Required Files
The following files are required to run Extended Multiplan:
XMultiplan.run	Mp.Hlp1.0
Sys.Printers}
The Extended Multiplan Distribution Diskette installation submit file does not overwrite existing printer configuration files.  They are included as an example, and should be used only if they are correct for your particular configuration (see your System Administrator).}
{6.0	System Software Compatibility
2.1 Extended Multiplan requires CTOS 9.1 or higher.  If you have not yet installed the latest version of CTOS, do so before installing Extended Multiplan.}
{This product is compatible with version 1.0 Document Designer and version 1.0 Chart Designer which requires version 2.2 of the Context Manager for Multipartition usage.  For graphics capabilities, use Chart Designer version 1.0 or Business Graphics Package version 10.0.}
{7.0	Resource RequirementsUtilization
7.1	Memory RequirementsUtilization
2.1 Extended Multiplan will run reasonably well in a 250K memory partition with spreadsheets that typically utilize 16 of the maximum sheet area.  As Spreadsheets increase in complexity, 250K will prove to be inadequate and increasing partition size will directly increase maximum sheet size.}  
{7.2	Disk RequirementsUtilization
2.1 Extended Multiplan requires about 860 disk sectors, or 430K bytes of disk space.  Additionally, each saved sheet requires space proportional to its size.
}
{8.0	Supplementary Information


8.1	Updating to Version 2.1 from Standard 	Multiplan
Users who are upgrading to 2.1 Extended Multiplan directly from standard Multiplan should read the Engineering Update for 1.0 Extended Multiplan .  The basic differences between the two versions are discussed in that document.  Also included is a section on worksheet compatibility between standard and Extended Multiplan.
}
{8.2	Configuring the Sys.Printers Files
The Sys.Printers file provided on Distribution Diskette 1 is only a representative example of a possible printer configuration for Extended Multiplan.  The actual contents of your Sys.Printers file depends greatly on your installation.}
{Many Convergent applications use the Sys.Printers file, including the Word Processor and the Business Graphics Package.  The format is as follows:
name: spec: text type: graphics type
where	name is the friendly name for the printer or plotter}
{spec is configuration information for the printer or plotter.  Extended Multiplan now supports alternative printerspooler specs in this field, which means that if one printerspooler cannot print, the second one is tried.  This is done by typing one spec, optional blanks andor tabs, then a comma, optional blanks and tabs, then the second spec, for example:

[SPL], [Lpt][Sys]<Sys>LptConfig.Sys

The Sys.Printers file included on Distribution Diskette 1 contains alternatives for all printers.  When using alternatives it is suggested that both specs be valid (though one erroneous spec will not cause a problem).}
{text type is used by the Word Processor to determine the text type of the printer.  A nonblank entry in this field indicates that this device is usable for printing (and can be used by Extended Multiplan).  PrinterPlotters should have entries in both the third and fourth fields.}
{graphics type is used only by the Business Graphics Package.}
{Below is an example of a Sys.Printers line for a line printer, using one of the example configuration files included on the distribution diskette:
Lpt:   Lpt[Sys]<Sys>LptConfig.Sys:  Draft:  :}
{In addition, you must provide configuration files for each type of printer which you have.  During installation, 2.1 Extended Multiplan will prompt you for confirmation to copy two example printer configuration files to your hard disk.  In general, you should NOT overwrite your own prepared configuration files if they already exist.}
{This Sys.Printers file format is common to Extended Multiplan, Business Graphics, and the Word Processor.  You may choose to use the same file for both the Word Processor and Extended Multiplan.  If you wish to do so, add the following text line to your .user configuration file to change the Extended Multiplan default printer file name (see the System Programmer's Guide):
:SysPrinters:[Sys]<Sys>Wp.Printers:
A description of this file is provided in the Printing Guide.}
{9.0	New Status Codes
Because Extended Multiplan has been integrated with CTDBMS, status codes in the CTDBMS and ISAM range (31003199, 39004099) may appear.  CTDBMS error codes are fully documented in the Status Codes Manual.  A number of new error codes have also been introduced as a result of the new database functionality.  All of them are in the range 1220012499.  A partial list of them occurs below.  All other error codes in this range should be referred to Convergent Technologies' Technical Support.
A new edition of the Status Codes Manual will be available shortly which contains descriptions of all of the data management errors which may occur  during use of the RDB command.}
{Decimal 
 Value 	Meaning
12237	Can not open database.
The specified database cannot be opened.  The other status code gives the reason for the failure.
12242	Can not create database.
The specified database cannot be created.  The other status code gives the reason for the failure.
12246	Can not add field.
The specified field  cannot be added to the relation.  The other status code gives the reason for the failure.
12247	Can not delete field.
The specified field  cannot be deleted from the relation.  The other status code gives the reason for the failure.
12258	Illegal query specification.
The specified query is illegal.  The other status code gives the reason for the failure.
12281	Can not modify field.
The specified field cannot be modified.  The other status code gives the reason for the failure.
12283	Illegal type conversion.
An attempt was made to change an alpha field into a numeric or vice versa.
12419	File is not a personal data base.
The name specified in the relation area does not correspond to a personal data base file.} 
{10.0	Known Errors
There are no known errors in 2.1 Extended Multiplan.}