

CONVERGENT TECHNOLOGIES

RELEASE NOTICE FOR
6.1 CTMail (STA6000)

Revised Nov 30, 1987


SECTION   TITLE	PAGE
	1.0	Description of Programs	 2
		1.1  Mail Server	 3
		1.2  Modem Server	 4
		1.3  Communications Manager	 4
		1.4  Interactive Mail Manager	 5
	2.0	Changes from Release 5.0	 6
		2.1  SPRs Closed in This Release	 6
		2.2  Changes from Release 5.0	 10
	3.0	Contents of Distribution Diskettes	 16
	4.0	Installation Procedures	 17
		4.1  StandAlone Hard Disk Systems	 17
		4.2  Master Hard Disk Systems	18
		4.3  SRP Systems	20
		4.4  Local File Systems	22
		4.5  StandAlone Floppy Disk Systems	23
	5.0	Required Files	24
	6.0	System Software Compatibility	25
		6.1  Workstation Environment	25
		6.2  SRP Environment	25
	7.0	Hardware Information	26
		7.1  Hardware Configurations Supported	26
		7.2  Special Hardware Requirements	26
	8.0	Resource RequirementsUtilization	27
		8.1  Memory RequirementsUtilization	27
		8.2  Protected Mode Memory Utilization	28
		8.3  Disk RequirementsUtilization	29
	9.0	Restrictions	30
	10.0	Documentation Updates	31
	11.0	Known Errors and Omissions	32
1.0	Description of Programs
This Release Notice describes CTMail version 6.1.  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 CTMail.
CTMail is a software product that allows users on Convergent workstations to send messages and files to, and receive messages and files from, other users on Convergent workstations.  Each user of the CTMail system is registered with the system under a particular mail user name.  Each mail user belongs to a specific mail center, which acts as a post office for the purposes of sending and receiving mail.  A mail center can consist of a single standalone workstation, or of an entire cluster of workstations.  Communication links between mail centers, in the form of direct RS232 connections, using asynchronous autodial modems, or using CTNet, allow mail messages and files to be transmitted to mail users at remote mail centers.
One or more mail centers can be grouped together to form an organization.  Centers within an organization automatically exchange information about their users.  This information is used to maintain a new directory called the All User Directory, a copy of which resides on each mail center in the organization.  The All User Directory may contain information pertaining to each mail user in the organization, and provides the basis for several additional features, including the ability to address mail to people by their simple name (e.g., John Smith), the automatic verification and correction of recipient names, and automatic dialing from an online phone directory.
CTMail is comprised of the Mail Server, the Modem Server, the Communications Manager, and the Interactive Mail Manager.  Although the Modem Server is part of the CTMail product, it is packaged on a separate diskette, and it has a separate release notice.  This is to allow the Modem Server to be sold for use with other software products, such as CTNet and MTE.  There are four optional components of the CTMail suite: the TelexTWX Manager, the Terminal Mail Manager, the Phone Memo Manager, and ClusterShare Mail.  Use of the mail system from the point of view of a nonadministrative user is described in the CTMail User's Reference Manual, Fourth Edition.  Use of Mail on a PC or PCcompatible equipped with ClusterCard and ClusterShare is described in the ClusterShare Mail User's Reference Manual, First Edition.  Setup and maintenance of the mail system are covered in the CTMail Administrator's Reference Manual, Fifth Edition and the Modem Server Reference Manual, First Edition.  The programmatic interfaces to CTMail are explained in the CTMail Programmer's Reference Manual, First Edition.
1.1		Mail Server
The Mail Server is an installed system service that is responsible for the overall process of accepting mail messages for delivery from their originators, routing them through the mail system to their destination mail center(s) and distributing them to the mail users that are their ultimate recipients.  When the mail system is configured to use CTNet as the method of transport, Mail Servers on different mail centers communicate directly through the CTOS distributed operating system to accomplish the delivery of mail.  The Mail Server also regulates user access to the system, maintains distribution lists, keeps track of undelivered messages, and provides temporary storage for mail that is in the process of being delivered.  If the mail center belongs to an organization, then the Mail Server is also responsible for exchanging messages with other mail centers for the purpose of keeping All User Directories, organization member lists, and organization distribution lists up to date.
Each installation of the Mail Server corresponds to a single mail center.  The Mail Server must be installed at a standalone workstation or at the master workstation in cluster configurations, before using the Interactive Mail Manager or the Communications Manager.  The Mail Server services a set of CTOS requests which enable programs running on any of the workstations in the cluster to send and receive mail messages, add and delete mail users of that mail center, and perform other related tasks.  Initial setup of a mail center is accomplished using the Configure Mail Center command, which must be invoked before the Mail Server can be installed.  This command creates and initializes all of the files that must be present for the Mail Server to operate.  The file MailMsg.bin, which must be present in the [Sys]<Sys> directory where the Mail Server is installed, contains all of the textual strings used by the Mail Server and its related utilities.
1.2		Modem Server
The Modem Server is an installed system service that allows sharing of a single modem or direct communications line among several separate programs.  Programs which need to access a modem or communications line (such as the Communications Manager, Terminal Mail Manager, and TelexTWX Manager) can do so via a series of requests to the Modem Server.  These requests are for operations such as dialing calls, receiving calls, sending data, receiving data, etc.  The Modem Server translates these requests into commands to the modem to perform the desired operations.  The Modem Server can communicate over direct RS232 cables at data rates between 110 and 19200 baud.  With the use of any of the autodialautoanswer modems supported (Bizcomp 1012, RacalVadic VA212, Ventel MC120031, Hayes Smartmodem 1200, and the modem built into the TM001 module), the Modem Server can also communicate over the telephone lines to any directdial location at a data rate of 300 or 1200 baud.  In addition, the ModemGen feature allows the Modem Server to be used with virtually any other Bell 103 or 212A compatible asynchronous autodial modem that has an RS232 interface.  (See the Modem Server Reference Manual, First Edition).
Note:  Although the Modem Server is included in the CTMail product, it is packaged on a separate diskette, and it has a separate version number and release notice.  The version number of the Modem Server that is included with this version of CTMail is 4.2.  Since it is intimately involved in the operation of CTMail, this release notice still contains some discussion of the Modem Server.
1.3		Communications Manager
The Communications Manager is an installed system service that is responsible for the transmission of mail messages and files between different mail centers in the case where CTNet is not being used.  Communications Managers can be installed anywhere in a cluster, and there can be up to eight of them installed at one time for each mail center.  The Communications Manager communicates with the mail center in which it is installed by issuing requests to the Mail Server.  Under the direction of the Mail Server, it exchanges data with Communications Managers installed at other mail centers by means of a communications line or modem.  The actual establishment of a connection and transmission of data on the line is accomplished by issuing appropriate requests to the Modem Server, which must have been previously installed at that workstation and configured to handle that line.
1.4		Interactive Mail Manager
The Interactive Mail Manager is the user's way of communicating with the mail system.  It is a highly interactive, multiwindow program that allows word processorstyle editing of mail messages.  The Interactive Mail Manager also translates simple keyboard commands into requests to the Mail Server, thus providing a userfriendly means of sending and receiving mail, maintaining distribution lists, and obtaining directories of mail users and mail centers.  Most of the administrative operations, such as adding and removing mail users and mail centers, are also performed through the Interactive Mail Manager.  The Interactive Mail Manager maintains a set of File Folders for the user, which are used for storing messages that have already been sent, messages that have been received, or messages that are in the process of being edited.  The Interactive Mail Manager also includes the facility of printing, either directly to a printer or by means of the Printer Spooler or the Generic Printing System, the contents of any mail message, attachment, distribution list, user directory, etc.
2.0	Changes from Release 5.0
2.1	SPRs Closed in This Release
{SPR 10490, 11327
In previous versions of CTMail, the Search command worked only in message and text file windows.  In 6.1, the command works in all window types, including folder summaries, distribution lists, and file, center, and user directories.  Also, the Open command accepts the partial selections that can result from the Search command, and operates as though the entire item had been selected.  In previous, attempting to open such a partial selection could fatal errors.}
{SPR 11309
The cursor position was not updated correctly when a user typed a diacritical key combination in nonEnglish language configurations.}
{SPR 11325
Attempting to file a message in a folder whose name was identical to the name of a currently open window (such as Message) resulted in a fatal error 10027.}
{SPR 11393
The confirmation prompt for removing a center's mailbox directory when the center was being removed incorrectly implied that pressing CANCEL would cancel the entire command.}
{SPR 11457
Attempting to change the password for a mail center that was distributed through another mail center resulted in a Mail Server malfunction with error code 10202.}
{SPR 11485
Making several changes that involved removing mailbox directories in a single session could eventually result in fatal error 10820.}
{SPR 11628, 11978
If a remote center that was set up to distribute through a communications manager was reconfigured to distribute through another center and then configured back again to distribute through a communications manager, the Mail Server would sometimes erroneously believe that there was mail to be sent to that mail center, resulting in repeated connections with no mail transferred.}
{SPR 11655
The performance of CTMail 5.0 was worse that than of previous releases, particular as regards reading mail into the In Tray.}
{SPR 11779
It was not possible to add a mail user with a node name in the mailbox directory specification unless CTNet was installed.}
{SPR 11890
The Interactive Mail Manager failed to check properly for the maximum length of CTOS file names (50 characters) when dealing with received attachments.  This could result in a fatal error 205.}
{SPR 11960
If an administrator forwarded an Organization Update message from Dead Mail, it could result in spurious entries in the All User Directory.}
{SPR 11969
Under certain circumstances, incorrectly addressing a mail message to SimpleNameCenter could result in Dead Mail due to error 10175 (circular routing).}
{SPR 11980
Attempting to install the 5.0 Mail Server under PMOS with an Nls.Mail.sys file resulted in a general protection fault.}
{SPR 12027, 12396
Misleading or inaccurate comments in the MailCenter.config file have been corrected.}
{SPR 12031
The Center type parameter was not shown in the mail center description display.}
{SPR 12040
Invoking the Attach Folder feature without typing in a folder name caused a fatal error 210.}
{SPR 12041
The In Tray and folders occasionally became corrupt and thus required reorganization, particularly when running under limited memory.}
{SPR 12052
When a message sent from a user in an organization to someone in a different organization was replied to, the message would be sent to a person with the same simple name in the replying center's organization.}
{SPR 12062
Mail Server malfunction messages were improperly logged on SPR's running CTOS II.  As a result, they were displayed as hexadecimal digits, rather than as ASCII text.}
{SPR 12111
Automatic expansion of the Distribution Lists file did not take place if the Maximum number of Distribution Lists in a center parameter in the MailCenter.config file was set to 8.}
{SPR 12156
Under some circumstances, the information displayed in the Print Queue window became corrupted.}
{SPR 12158
Under some circumstances, error 10112 (center already connected) would be chronically encountered when mail center attempted to communicate via the Communications Manager.}
{SPR 12199
Certain obscure combination of commands involving cancelling print jobs from the Print Queue window caused the Interactive Mail Manager to hang.}
{SPR 12257
Pressing HELP and CANCEL after displaying the Print Queue window caused Status field of the Printer Status menu to be blanked.}
{SPR 12258
The cursor was not repositioned correctly after invoking an F1 command while in the File message menu.}
{SPR 12288
Under previous versions of CTMail, it was possible to create a file folder that was so large it could not be displayed, given the amount of memory available to the Interactive Mail Manager.  In 6.1, the system warns the user when adding a messages to a folder threatens to make it too large to be displayed.  Also, if folder cannot be fully displayed due to memory limitations, the Interactive Mail Manager displays as much of the folder as it can and instructs the user to remove or move messages to make the folder smaller.}
{2.2	Changes from Release 5.0
1.	The 6.1 Interactive Mail Manager runs in protected mode under CTOSVM 2.0.  It has also been modified to make use of up to 600K of memory, if available, resulting in improved performance under large memory systems.}
{2.	The Mailbox Queue feature allows the administrator to display a summary of the queue of messages being held for delivery to a remote mail center.  The Date, Message ID, From, To, Attach, and Subject fields of each message are shown, as well as the message priority.  The administrator can select messages from this display and then either discard them or cause them to be moved from the delivery queue to the Dead Mail directory.}
{3.	The procedure for moving an attachment from the attachment directory to a working directory has been streamlined.  In 6.1 CTMail, whenever a user files or discards an incoming message with attachments, a form comes up which allows the user to specify whether the attachments should be moved to a different directory, discarded or left in the attachment directory.  Destination directory and Directory password blanks are provided for the user to specify where the attachments should be put, and a Confirm each? option is provided to allow selective moving or discarding.  The default settings for all four of these options can be set via the User Profile command.}
{4.	The Folder Directory and all file directories are now automatically displayed in alphabetical order.}
{5.	6.1 CTMail allows the user to Mark, Bound, and Delete a number messages at a time from the In Tray or from a file folder.  Blocks of messages can also be copied or moved to other file folders.}
{6.	In previous versions of CTMail, once a message had been sent it was forever marked as readonly and could not be edited.  In 6.1, if a user makes an attempt to edit a message, the system asks for confirmation to edit a new copy of the message.  If the user presses GO, the system removes the Message ID from the message and resets the Date field to the current time, leaving the user free to modify and resend the message.}
{7.	The 5.0 Interactive Mail Manager was capable of recovering if the master crashed or was rebooted only if the Mail.run file was loaded off of a local file system disk.  The 6.1 Interactive Mail Manager can usually recover from a master reboot even if the Mail.run file is loaded from the master itself, including the case of a diskless cluster workstation.  The Interactive Mail Manager will appear to hang for several seconds until the cluster comes up again.  If for any reason the master fails to reboot within 90 seconds, the Interactive Mail Manager aborts its retry attempts and exits to the Executive or Context Manager, usually with error 210.}
{8.	The MailCenter.config file has been significantly simplified in 6.1.  The entries for Name Registry Filename, Distribution Lists Filename, To Be Delivered Filename, Mail Server Status Filename, User Directory Filename, Maximum Number of Distribution Lists in a Center, Maximum Number of Users, Centers, and Comm Agents, Maximum Number of Messages in Center Mailboxes, Maximum Number of Messages in User Mailboxes, Number of Large Buffers, and Size of Large Buffers in Bytes have been removed from the standard MailCenter.config file present on the first Distribution Diskette.  These entries will still be accepted if present in a MailCenter.config file, so old files need not be changed.}
{9.	A new submit file, MailLfsInstall.sub, has been provided, which simplifies the process of adding the CTMail software to a cluster workstation with local file system.  This submit file, copies Mail.run to the local disk, creates the Mail command, merges the CTMail request files with those on the local file system, and adds Mail to the user's Context Manager configuration file.  MailLfsInstall.sub, as well as four other submit files that it calls, is copied to the [Sys]<Sys> directory of the master workstation from the distribution diskettes during installation, so that they may be used by the administrator or user at a later date.}
{10.	The Change Mailbox Directory and Change Folder Directory commands allow the administrator to change the mail directories for existing users and centers.}
{11.	Support has been added to the Mail Server and Interactive Mail Manager for the optional gateway between CTMail and the SMTP mail systems on the Defense Data Network (DDN).  New menus for configuring DDN Managers and DDN centers have been added.  The DDN Manager mail gateway and other DDN software are currently available on a limited basis only.}
{12.	CTMail 6.1 allows users to employ various search criteria in getting subsets of the All User Directory.  The user may request a display of the users at a particular mail center, a display of users whose simple names match a wildcard string, or the combination of these two criteria.  For convenience in creating distribution lists and addressing messages, the simple names may be displayed in First Last order, if desired.  This command can be invoked by pressing Users (F3) and then Select (F4) from the Home menu, by pressing Select (F4) from the Center Directory menu (in which case the Center name field is filled in with the name of the selected mail center), or by pressing CodeU at any time.}
{13.	The time required to display Distribution List summaries has been significantly reduced, particular for the full directory of lists that an administrator gets.  In addition, lists which belonged to users and organizations that have since been removed are displayed at the end of the administrator's list summary, in order to allow the administrator to delete them.  In 6.1, Distribution lists can be removed directly from the Distribution Lists summary by using the Delete key, addition to the previous method of opening them and using the Remove softkey.  Also, when a user is removed, the system allows the administrator to automatically delete all of the distribution lists owned by that user.}
{14.	In previous versions of CTMail, Dead Mail messages could be forwarded by the Administrator, but there was no convenient way to forward any attachments that went with the message.  CTMail 6.1 solves this problem, both filling in the Attach field when the Forward key is pressed for a Dead Message, and providing the necessary operations to actually send the attachments when the forwarded dead message is sent.}
{15.	In previous versions of CTMail, new mail was received from the Mail Server every time a user filed or discarded a message from the In Tray.  This sometimes caused unwelcome delays, particularly when running in limited memory and with bitmap displays.  In 6.1, new mail is read only when the user enters mail for the first time and thereafter when the users explicitly presses the In Tray key.  Also the performance of reading and updating the In Tray have been improved.}
{16.	In previous versions of CTMail, the only way to remove a filed outgoing message from a folder was to use the Delete key while in the folder summary, as no Discard softkey was displayed for a filed, outgoing message.  In 6.1, the Discard softkey is display at the F4 position for this window type only.  The Discard command remains on F6 for all other window types.}
{17.	The 6.1 Mail Server can now be configured to support as many as three simultaneous connections across CTNet.  Moreover, in previous versions of CTMail, there was no way to view the status of additional net connection.  CTMail 6.1 uses the Next key to toggle between Network Mail Status 1,  Network Mail Status 2, and Network Mail Status 3.}
{18.	In CTMail 6.1, if the administrator presses the Next key while in the Communications Manager Status display, the system brings up the status display for the next Communications Manager.  This makes it easier to quickly check the status of several Communication Managers installed at a mail center.}
{19.	In CTMail 6.1, the Communications Manager status display shows the name of the center being called, as well as the phone number.  This make it easier to identify centers whose communications links are not operating.}
{20.	When a mail user was removed and then readded, specifying the same Folder Directory, previous versions of CTMail would always create a new In Tray.  CTMail 6.1 asks for confirmation before overwriting the In Tray, allowing the user or administrator to choose whether to keep an existing In Tray file.}
{21.	When generating Transport Error messages and Communications Error messages, 6.1 CTMail puts the center name of the center experiencing the problem into the subject field of the error message.  This makes it easier for the Administrator to locate  a particular center's error messages in the In Tray or in a file folder.}
{22.	When generating Delivery failure messages, 6.1 CTMail puts the first 60 characters of the subject field of the original message into the subject field of the error message.  This makes it easier for the user to locate the original message in a file folder.}
{23.	When a user replies to a message, the system brings up first the File Incoming Message form and then the File Outgoing Message form.  If the User Profile does not specify a default outgoing folder, then 6.1 CTMail enters the folder that the user typed into the File Incoming Message form as the default for the File Outgoing Message form.  This simplifies the process of filing both messages in the same folder.}
{24.	In previous versions of CTMail, the Signoff command displayed the message Please close all windows. if any user windows were on the screen.  In 6.1 CTMail, all user windows are closed automatically.  Confirmation is requested for any message windows which have been edited but not filed.}
{25.	In previous versions of CTMail, when replying to a forwarded message, the system filled in the To field with the name of the sender of the original message.  In 6.1, the system fills in the name of person who forwarded message, which is the more commonly desired action.  As before, the user has the option to edit the To field if another recipient is desired.}
{3.0	Contents of Distribution Diskettes
The CTMail Distribution Diskettes are your master copies, and have been shipped writeprotected.  They should not be writeenabled, nor should they be used as a working copy.}
{Various features of CTMail 6.1 have additional software dependencies which are explained in section 6.0 (system software compatibility).}
{The first CTMail Distribution Diskette contains the following files in the <CT> directory:
MailServer.run	MMailServer.run	CommunicationsManager.run	MailCenter.config	MCommunicationsManager.run	MailServerUtil.run	ConfigureMailCenter.run	DeInstallCommMgr.run	Request.8.sys	MRequest.8.sys	MailMsg.bin	MailCm.sub	MailLfs.sub	MailLfsInstall.sub	MailRqI.sub	MailRqII.sub}
{The diskette also contains the following file in the <Lib> directory:
Mail.lib}
{The diskette also contains the following file in the <ReleaseNote> directory:
ReleaseNotice}
{The <Sys> directory of the first Distribution Diskette contains the following files:
HdInstall.sub	MfInstall.sub}
{The second CTMail Distribution Diskette contains the following file in the <CT> directory:
Mail.run}
{4.0	Installation Procedures
CTMail 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 only with standard software at revision level 9.1 or higher.  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.	Install the Modem Server from the Modem Server Distribution Diskette and configure it to support the communications lines you will be using for CTMail.  See the Modem Server Release Notice for instructions on how to install the Modem Server.}
{B.	Sign on 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.}
{C.	Insert CTMail Distribution Diskette 1 of 2 in drive [f0].  (Do not press the RESET button.)
D.	Install the product as follows:
Command   Install  GO}
{E.	At the appropriate time, a message will appear prompting you to insert Distribution Diskette 2 of 2.  After you have done this, press GO, and the remainder of the CTMail software will be installed automatically.  Save the Distribution Diskettes as archive copies.}
{F.	The copy of the MailCenter.config file that is included on CTMail Distribution Diskette 1 of 2 is intended only as an example, and must be edited to conform to your system requirements before the Mail Server can be installed.  For instructions on how to modify the MailCenter.config file and bring up your mail center, consult the CTMail Administrator's Reference Manual, Fifth Edition.}
{4.2	Master Hard Disk Systems
A.	Install the Modem Server from the Modem Server Distribution Diskette and configure it to support the communications lines you will be using for CTMail.  See the Modem Server Release Notice for instructions on how to install the Modem Server.}
{B.	Sign on 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.}
{C.	Disable the Cluster workstations as follows:

Command   Disable Cluster  GO
Disable Cluster}
{D.	Insert CTMail Distribution Diskette 1 of 2 in drive [f0].  (Do not press the RESET button.)}
{E.	Install the product as follows:
Command   Install  GO}
{F.	At the appropriate time, a message will appear prompting you to insert Distribution Diskette 2 of 2.  After you have done this, press GO, and the remainder of the CTMail software will be installed automatically.  Save the Distribution Diskettes as archive copies.}
{G.	Resume cluster operations as follows: 

Command   Resume Cluster  GO}
{H.	The copy of the MailCenter.config file that is included on CTMail Distribution Diskette 1 of 2 is intended only as an example, and must be edited to conform to your system requirements before the Mail Server can be installed.  For instructions on how to modify the MailCenter.config file and bring up your mail center, consult the CTMail Administrator's Reference Manual, Fifth Edition.}
{I.	Submit the file [Sys]<Sys>MailLfsInstall.sub on each of the cluster workstations with local disk to copy the 6.1 Interactive Mail Manager to the local disk, create the Mail command, merge the CTMail requests, and add Mail to the Context Manager configuration file.  This submit file provides complete instructions on how to select among various options in setting up Mail on the cluster station.}
{4.3	SRP Systems
Installation on SRP systems requires a Cluster workstation with at least one floppy disk drive.
Important Note:  The prebuilt 3.2 and 3.3 SRP operating systems are not sysgen'ed with a large enough stack to support the loading of several loadable request files at a time.  Thus, the installation of several system services such as CTMail, CTNet, and Generic Printing System on the standard OS can result in unpredictable results.  You may need to sysgen operating systems with larger stacks for successful operation.}
{A.	Install the Modem Server from the Modem Server Distribution Diskette and configure it to support the communications lines you will be using for CTMail.  See the Modem Server Release Notice for instructions on how to install the Modem Server.}
{B.	Sign on 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 hard disk has a volume password on [Sys], fill this password into the [Password] field before pressing GO.}
{C.	Insert CTMail Distribution Diskette 1 of 2 in drive [f0].  (Do not press the RESET button.)}
{D.	Install the product as follows:
Command   Submit  RETURN
Submit
  File list	[f0]<Sys>MfInstall.sub  GO
  [Parameters]
  [Force expansion?]
  [Show expansion?]}
{E.	At the appropriate time, a message will appear prompting you to insert Distribution Diskette 2 of 2.  After you have done this, press GO, and the remainder of the CTMail software will be installed automatically.  Save the Distribution Diskettes as archive copies.}
{F.	Edit the file [Sys]<Cmd>WsAdminAgent.txt and add the following entries:

MReset Mail Server
            [Sys]<Sys>MailServerUtil.run

MDeinstall Communications Manager
            [Sys]<Sys>DeinstallCommMgr.run

Each entry should be on one line.  See the MegaFrame CTOS Administrator's Manual for details about SRP master utilities.}
{G.	The copy of the MailCenter.config file that is included on CTMail Distribution Diskette 1 of 2 is intended only as an example, and must be edited to conform to your system requirements before the Mail Server can be installed.  For instructions on how to modify the MailCenter.config file and bring up your mail center, consult the CTMail Administrator's Reference Manual, Fifth Edition.}
{H.	Install the Mail Server on the SRP by modifying the InitFp00.jcl, InitCp00.jcl, or InitTp00.jcl file to include the following commands:
	$Run [Sys]<Sys>MCreatePartition.run,160K,MS
$Run [Sys]<Sys>MInstallServer.run,
                  MS,[Sys]<Sys>MailServer.run
	The 160K figure is just an example.  Enter the actual amount of memory required by the Mail Server for your configuration according to the formula provided in section 8.1.}
{I.	Install the Communications Manager on the SRP by modifying the InitCp00.jcl or InitTp00.jcl file to include the following commands:
	$Run [Sys]<Sys>MCreatePartition.run,28K,COM
$Run [Sys]<Sys>MInstallServer.run,COM,
          [Sys]<Sys>CommunicationsManager.run,
          MgrName,MgrPswd
	where MgrName and MgrPswd represent the parameters in the Install Communications Manager command (see the CTMail Administrator's Reference Manual, Fifth Edition.  Note that before a particular Communications Manager can be installed, it must be set up in the Interactive Mail Manager.  Also, the Modem Server must be installed as a system service (see the Modem Server Reference Manual, First Edition) before the Communications Manager can be.
Note:  Each of these servers changes the name of its partition once has been successfully installed.}
{J.	Submit the file [Sys]<Sys>MailLfsInstall.sub on each of the cluster workstations with local disk to copy the 6.1 Interactive Mail Manager to the local disk, create the Mail command, merge the CTMail requests, and add Mail to the Context Manager configuration file.  This submit file provides complete instructions on how to select among various options in setting up Mail on the cluster station.}
{4.4	Local File Systems
To install or update the CTMail software on a cluster workstation with local file system, do not use the procedure for installing CTMail from the Distribution Diskettes.  Instead, do the following:}
{A.	Make sure that the correct version of CTMail has been installed on the master using the procedures in Section 4.2 or Section 4.3, as appropriate.}
{B.	Install the CTMail software on the local hard disk as follows:
Command   Submit  RETURN
Submit
  File list	[Sys]<Sys>MailLfsInstall.sub GO
  [Parameters]
  [Force expansion?]
  [Show expansion?]}
{C.	Further instructions for specifying the operating system level, desired location for the Mail.run file, and name of the Context Manager configuration file are provided on the screen.}
{4.5	StandAlone Floppy Disk Systems
CTMail is not supported on standalone floppy disk systems.}
{5.0	Required Files
The following files are copied to the Sys directory of a master workstation:
Mail.run	MailServer.run	MailServerUtil.run	Request.8.sys	CommunicationsManager.run	DeinstallCommMgr.run	ConfigureMailCenter.run	MailCenter.config	MailMsg.bin	MailCm.sub	MailLfs.sub	MailLfsInstall.sub	MailRqI.sub	MailRqII.sub}
{The following files are copied to the Sys directory of an SRP master:
Mail.run	MailServer.run	MailServerUtil.run	MRequest.8.sys	CommunicationsManager.run	DeinstallCommMgr.run	ConfigureMailCenter.run	MailCenter.config	MailMsg.bin	MailCm.sub	MailLfs.sub	MailLfsInstall.sub	MailRqI.sub	MailRqII.sub}
{6.0	System Software Compatibility
6.1	Workstation Environment
6.1 CTMail runs only on CTOS I versions 9.1 through 9.8 and on CTOSVM version 2.0 or later.  The following product release levels are the minimum guaranteed to be compatible with 6.1 CTMail:
	9.1 CTOS I
	2.0 CTOSVM
	2.0 Terminal Mail Manager
	1.1 TelexTWX Manager
	1.0 Phone Memo Manager}
	4.2 Modem Server
{Mail notification will work with:
	9.1 Executive*
	9.2 Word Processor*
	1.0 Document Designer*
	1.0 Extended Multiplan*
	2.0 Art Designer*
{Protected mode operation of the Mail Server and Communications Manager on a CP002 processor require:
	1.0 PMOS* and
	9.7 CTOS I*
* Higher release levels also will work.
CTMail 6.1 is compatible with all previous versions of CTMail for purposes of exchanging mail between centers.}
{6.2	SRP Environment
The 6.1 Mail Server and Communications Manager run only on SRP CTOS (for the FP, SP, CP, or TP) version 3.2 or higher.  CTOS SRP versions 1.3 and above are also supported.}
{7.0	Hardware Information
7.1	Hardware Configurations Supported
CTMail is supported on NGEN, IWS, AWS and CWS workstations and on the SRP.}
{7.2	Special Hardware Requirements
The Voice Mail feature of CTMail may be accessed only from an NGEN with a TM001 Voice Processor module and the Telephone Server of 1.0 Voice Data Services installed.}
{The Communications Manager may be employed in electronic mail systems that extend beyond a single cluster.  It is an alternative to CTNet as a means of transporting mail and attachments between clusters.  For a direct, dedicated connection between two clusters, a crossed RS232 cable is required.}
{For communication between workstations that will be conducted over telephone lines, a Bell 103 or 212A compatible asynchronous autodial modem is required for each Communications Manager that will so communicate.  In version 6.1 CTMail, the following modems are supported for purposes of autodial and autoanswer:
	TM001 builtin modem
	Bizcomp 1012 Versamodem
	Hayes Smartmodem 1200
	RacalVadic VA212
	Ventel MC120031}
{Other asynchronous autodial modems can be used by means of the ModemGen feature.  See the Modem Server Reference Manual, First Edition for specific configuration information for several other modems.  This manual also specifies the kind of cable required for a modem connection.  Connection of pins other than 1, 2, 3, 4, 5, 6, 7, 8, and 20 may cause spurious results.}
{8.0	Resource RequirementsUtilization
8.1	Memory RequirementsUtilization
The total memory requirement of the Mail Server (in Kilobytes = 1024 bytes) can be calculated as follows:
Memory = 122K	+ (4K if on an SRP)
	+ (9K   * number of processes)
	+ (0.5K * number of sector buffers)}
{Thus, the Mail Server requires approximately 137K in the minimum configuration (1 process, 2 large buffers, 13 sector buffers).  The minimum Mail Server configuration for use with CTNet (2 processes, 4 large buffers, 21 sector buffers) is approximately 150K.  The default memory utilization is 155K.  Specifying more than the minimum number of sector buffers improves the performance of the mail center at the cost of additional memory utilization.  Since the Mail Server is always installed at the master workstation in cluster configurations, it has no impact upon the memory requirements of cluster workstations.}
{The figures given above are the absolute minimum requirements for the Mail Server.  The performance of the Mail Server can be sensitive to the amount of memory it has to run in, particularly when the Name Registry contains a large number of users and centers.  Specifying an insufficient number of sector buffers in the MailCenter.config file, can result not only in poorer performance of the mail system, but also in a noticeable drop in system and cluster performance.  Calculate the suggested minimum number of sectors buffers using the following formula:
 Sector Buffers >= 10 + (Centers + Users)  5
where Centers is the number of mail centers displayed in the center directory and Users is the number of mail users and aliases displayed in the user directory.  Each sector buffer adds 12 K to the memory requirements of the Mail Server.}
{Each installation of the Communications Manager requires approximately 26K (28K on SRP's).  This memory requirement may be at the master workstation or at a cluster workstation, depending upon where the Communications Manager is installed.}
{The Interactive Mail Manager is a swapping program, and will utilize all available memory whenever it is run.  The Interactive Mail Manager requires an absolute minimum of about 170K to run.  The responsiveness of the program is very sensitive to the amount of memory available, and at least 200K is required for reasonable performance.  On an NGEN workstation with the VoiceData Server installed (i.e., if the Voice Mail or Dialing features are to be used), then at least 225K is required for reasonable performance.  Unlike the Mail Server and the Communications Manager, the Interactive Mail Manager is not an installed system service, so it does not permanently reserve memory.}
{8.2 Protected Mode Memory Utilization
The main reason to run servers in protected mode under or PMOS is to achieve a memory savings in the first Megabyte of memory, as this allows more programs (servers andor contexts) to be run on the machine at the same time.  The amount of memory which is saved in the first Megabyte of memory is occupied by the server in the region above one Megabyte.  For the Mail Server, the amount saved in the first Megabyte is a constant 114K and for the Communications Manager it is 20K.  To calculate the remaining memory requirement in the first Megabyte of memory, first determine the total memory requirement from section 8.1, and then subtract the amount saved.}
The Mail Server, Communications Manager, and Interactive Mail Manager all run in protected mode under CTOSVM, and all of their memory utilization is potentially above the one Megabyte boundary.
{8.3	Disk RequirementsUtilization
The amount of disk space required for CTMail depends upon the number of mail users and mail centers in the system, the values of parameters in the MailCenter.config file, and the partitioning of files between the master workstation and the local file systems on the cluster.  In general, approximately 1300 sectors (including run files) are required to bring up a mail center with only one user, and at least 200 sectors per additional mail user and 60 sectors per additional mail center are required.  (Note:  Only mail centers which are distributed through a Communications Manager or through CTNet have this disk space requirement.  Mail centers which are distributed through another mail center have no mailbox or mailbox directory and thus consume no disk space.)  These estimates do not include the storage requirements of attachments and large messages.  Actual disk utilization will increase as the mail system becomes more heavily used.
Important Note:  It is very unwise to run the mail system in a condition of being nearly out of disk space, as the mail delivery system becomes unable to deliver mail when insufficient room exists for temporary files and attachments.}
{9.0	Restrictions
1.	On SRP's running operating systems less than the CTOS SRP 1.4, the Mail Server should only be installed on the FP or CP.  The Mail Server will successfully install on other boards such as the TP or SP, but the dates filled into messages when they are sent will be incorrect.}
{10.0	Documentation Updates
Standard documentation for CTMail:
1.	CTMail User's Reference Manual, Fourth Edition.
2.	CTMail Administrator's Reference Manual, Fifth Edition.
3.	Modem Server Reference Manual, First Edition.
4.	CTMail Programmer's Reference Manual, First Edition.
5.	Phone Memo Manager Manual, First Edition.}
{11.0	Known Errors and Omissions}
{1.	If a message greater than 64K in length (approximately 2550 screen pages) is sent, status code 10001 is returned.  If such a message is filed, this status code is returned when the user attempts to open up the message.}
{2.	New mail notification does not appear in programs such as the Executive and Word Processor for any period that the default path is set to be on another CTNet node.}