

	Software
	Release
	Announcement
		
OFIS Mail
Version 8.0.0
Additional copies of this document can be ordered through your branch representative or from Unisys Corporation, Corporate Software and Publications Operations, 32550 Haggerty Road North, Plymouth, Michigan 48170.
	
Distribution lists:
SA
System:	CTOS
Release	OFIS Mail 8.0.0
Part Number:	43575612000
NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT.  Any product and related material disclosed herein are only furnished pursuant and subject to the terms and conditions of a duly executed Program Product License or Agreement to purchase or lease equipment.  The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such License or Agreement.  Unisys cannot accept any financial or other responsibility that may be the result of your use of the information or software material, including direct, indirect, special or consequential damages.
You should be careful to ensure that the use of this information andor software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used.
The information contained herein is subject to change without notice.  Revisions may be issued to advise of such changes andor additions.
The names, places, andor events used in this publication are not intended to correspond to any individual, group, or association existing, living, or otherwise.  Any similarity or likeness of the names, places, andor events with the names of any individual, living or otherwise, or that of any group or association is purely coincidental and unintentional.
TRADEMARKS:

BTOS, CTOS are trademarks of Unisys Corp.
>>>The page break before this heading contains the template that automatically generates your table of contents.  Do not delete it.
Contents
Section 1
General Description		1
Mail Service		2
Modem Service		3
Communications Manager		4
Interactive Mail Manager		4
Section 2	
New Release Functionality		5
Changes from OFIS Mail 1.2.3		5
Changes from CTMail 7.0.1		9
Additional new functionality		11
Section 3	
Product Interdependencies		14
Software		14
Operating System Requirements		14
Memory Requirements		14
Disk Requirements		16
Recommended Additional Software		16
Hardware		17
Requirements		17
Recommended Additional Hardware		18
Section 4	
Migration Requirements		19
Compatibility with Previous Versions		19
Section 5	
Corrections		20
UCFs and SPRs Closed		20
Section 6	
Restrictions and Known Limitations		26
OFIS Mail Limitations		26
Section 7	
Customer Product Information		28
Software		28
Documentation		28
Requirement		28
Recommended Additional Manuals		28
Section 8	
Support		29
Support Category		29
Support Centers		29
Section 9	
Ordering Procedures		30
Section 10	
List of Files on Product Media		31
Contents of the Distribution Diskettes		31
Section 11	
Installation Procedures		32
Overview		32
Types of Systems		33
Required Files		33
Common Installation Issues		33
Installing OFIS Mail in a CTOS environment		34
Installing OFIS Mail in a BTOS environment		36
Additional XE520 Information		37
Using Installation Manager		38
Server or XE530 Installation		38
Cluster Workstation Installation		39
Local File Systems		39
Section 1
General Description	
This Software Release Announcement describes OFIS Mail version 8.0.  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 OFIS Mail.
OFIS Mail is a software product that allows users on Unisys workstations to send messages and files to, and receive messages and files from, other users on Unisys workstations.  Each user of the OFIS Mail 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 BNet II, 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 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.
OFIS Mail is comprised of the Mail Service, the Modem Service, the Communications Manager, and the Interactive Mail Manager.  Although the Modem Service is part of the OFIS Mail product, it is packaged on a separate diskette, and it has a separate release notice.  This is to allow the Modem Service to be sold separately for use with other software products, such as BNET II.
Additionally, the Phone Memo Manager has been included in this release.  The Phone Memo Manager allows users such as receptionists and secretaries to send memos to other users of the electronic mail system about phone calls that were received for them. Like the Modem Service it is packaged on a separate diskette and has a separate release notice.
There are many optional products that tie into OFIS Mail as well: the TelexTWX Manager, the Terminal Mail Manager, OFIS Access X.400, OFIS Access SMTP, OFIS Access Professional, OFIS Access 1100, OFIS Access A Series, and ClusterShare Mail.
Use of the mail system from the point of view of a nonadministrative user is described in the CTOS OFIS Mail User's Guide.  Use of Mail on a PC or PCcompatible equipped with ClusterCard and ClusterShare is described in the ClusterShare Mail User's Reference Manual.  Setup and maintenance of the mail system are covered in the CTOS OFIS Mail Administration Guide and the CTOS Modem Service Operations and Programming Guide.  The programmatic interfaces to OFIS Mail are explained in the OFIS Mail Programming Guide.
Mail Service	
The Mail Service 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 BNET II as the method of transport, Mail Services on different mail centers communicate directly through the CTOS distributed operating system to accomplish the delivery of mail.  The Mail Service 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 Service 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 Service corresponds to a single mail center.  The Mail Service must be installed at a standalone workstation or at the server workstation in cluster configurations, before using the Interactive Mail Manager or the Communications Manager.  The Mail Service 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 Service can be installed.  This command creates and initializes all of the files that must be present for the Mail Service to operate.  The file MailMsg.bin, which must be present in the [Sys]<Sys> directory where the Mail Service is installed, contains all of the textual strings used by the Mail Service and its related utilities.
Modem Service	
The Modem Service 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 Service.  These requests are for operations such as dialing calls, receiving calls, sending data, receiving data, etc.  The Modem Service translates these requests into commands to the modem to perform the desired operations.  The Modem Service can communicate over direct RS232 cables at data rates between 110 and 19200 baud.  With the use of most any autodialautoanswer modem (See the CTOS Modem Service Operations and Programming Guide).
Note:	Although the Modem Service is included in the OFIS Mail product, it is packaged on a separate diskette, and it has a separate version number and release notice.  The version number of the Modem Service that is included with this version of OFIS Mail is 5.0.  Since it is intimately involved in the operation of OFIS Mail, this release notice still contains some discussion of the Modem Service.
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 BNET II 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 Service.  Under the direction of the Mail Service, 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 Service, which must have been previously installed at that workstation and configured to handle that line.
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 Service, 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.
Section 2	
New Release Functionality	
OFIS Mail version 8.0 constitutes a merge of the CTOS product, CTMail 7.0.1, and the BTOS product, OFIS Mail 1.2.3. It includes all of the features of both products in a single, unified collection of programs.
Changes from OFIS Mail 1.2.3	
1.	Message recovery
The Interactive Mail Manager periodically saves copies of any messages being edited by the user.  If the workstation or the Interactive Mail Manager crashes for any reason, the Interactive Mail Manager redisplays the message(s) when it is reentered by the user.  Unlike the OFIS Document Designer, there is no replay; the recovered message(s) are displayed immediately. Due to the keyboard buffering method employed for recovery, the last few keystrokes typed in a message may not be saved.
2.	Indication of unopened mail in the In Tray
Messages which have been read into the In Tray, but not yet opened by the user are preceded by a '+' in the In Tray display to distinguish them from messages which have already been examined by the user.
3.	Option to print messages in a folder or In Tray
The user can print all messages or a specific range of messages in a folder or in the In Tray by selecting them with Mark and Bound before pressing the Print key.
4.	Option to forward any message in a folder
In previous versions of the Interactive Mail Manager, the user had the option to forward only mail that had been received from a remote user. A function key has been added to allow the user to forward any mail stored in a folder.
5.	Option to read mail into an open In Tray
In previous versions of the Interactive Mail Manager, the user had to close the In Tray in order to read new mail from the mailbox at the server. A function key has been added to allow the user to read mail from the mailbox at the server into the In Tray without having to close the In Tray first.
6.	Automatic reorganization of In Tray if full
If, when the user is reading new mail, the In Tray becomes full, the Interactive Mail Manager automatically reorganizes it to make room for the incoming mail.  As in a manual reorganization, the In Tray and related windows are first closed, the systems pauses for several seconds or minutes as the In Tray is reorganized, and then the In Tray window is reopened.  At this point, the system automatically resumes the process of reading new mail.
7.	Prompt for reorganization of folders if full when filing
If, when the user if filing a message into a folder, the folder is full, the Interactive Mail Manager prompts for reorganizing the folder.  The user can abort this operation by pressing Cancel.  If the user confirms by pressing Go, the folder and related windows are first closed, the systems pauses for several seconds or minutes as the folder is reorganized, and then the folder window is reopened.  At this point, the system finishes filing the message into the folder.
8.	When a message is forwarded the subject field is copied
Whenever a user invokes the Forward function to pass the current incoming message along to other recipients, the Interactive Mail Manager copies the contents of the incoming message's Subject field into the Subject field of the new message which it creates.
9.	Add path to attach field when message filed and files moved
Whenever the user employs the File message and attachments menu to move the attachment(s) to another directory while filing a message, the Interactive Mail Manager prepends the destination directory to the name(s) of the attachment(s) in the Attachment field of the filed message, so that the user has a permanent record of location the attachment(s).
10.	Minimum precedence for mail notification
If the system is running Standard Software 12.0 or greater and the user adds an entry of the form :MailNotification:Normal to his .user file (where the permissible values are Low, Normal, Urgent, and None), the system will only inform him of new mail if that mail's priority is greater than or equal to the specified threshold.  Thus, if the user specifies Normal, then he will only be notified of normal and urgent messages. This only controls mail notification in applications such as the Executive, Context Manager, and Document Designer; as before, the user is always notified of new mail in the Interactive Mail Manager. Therefore, if the user specifies None, then only the Interactive Mail Manager will display the notification message.
11.	Data compression in Communications Manager
The Communications Manager now employs a Run Length Encoding compression algorithm to reduce the amount of time (and thus money) required to transmit messages and attachments.  The amount of time saved depends upon the degree of repetition of bytes within the files sent.  For backwards compatibility, this feature is disabled when communicating with a pre7.0 Communications Manager at a remote mail center.
12.	In Progress restart in Communications Manager
The Communications Manager keeps track of how far it has gotten in transmitting a message and its associated attachments to another mail center.  If the link is disconnected before transmission is complete, the Communications Manager picks up from where it left off when the link is reestablished, rather than starting over at the beginning of the message, as it did in previous versions.  This can result in a substantial savings in the total connect time required to transmit a mail message, particularly when running over noisy telephone lines.  For backwards compatibility, this feature is disabled when communicating with a pre7.0 Communications Manager.
13.	Force Connection feature
The Change Connections menu for an opened mail center has a new option that allows the administrator to cause the local mail  center to attempt a connection to a remote mail center as soon as possible.  The Force function key (F1) instructs the Mail Service to attempt a connection to the indicated mail center irrespective of the connection times (if any) set up for that center and the amount of mail (if any) queued up for delivery to that center.  It also resets the backoff algorithm used to insure that chronically unreachable centers are called less frequently.  The Force condition remains in effect until the center is successfully connected to, at which time it is cancelled.
14.	Remove center for entire organization
In previous versions, a mail center could be removed from the center directory, even though it was still part of an organization.  This would cause organization update messages to go into Dead Mail, because the center would not be recognized.  Now, attempting to remove such a center produces an error message.  However, when the administrator at an organization capital attempts to remove a center, he is given the option of causing the center to be automatically removed from the entire organization.
15.	Configurable Communications Manager dial timeout
The Add Communications Manager and Modify Connection Information menus now contain a Dial time out option.  This allows the administrator to configure the period of time, up to 255 seconds, that the Communications Manager will wait for the phone to be answered when making a modem call.
16.	Configurable Communications Manager dial prefix
The Add Communications Manager and Modify Connection Information menus now contain a Dial prefix option.  This allows the administrator to prepend remote center phone numbers with a dial string prefix (e.g. 9=) to accommodate different PBX switches.
17.	Support for forwarding system messages
Previous versions of OFIS Mail did not support the forwarding of system messages which had gone into Dead Mail.  System messages are messages addressed to Mail Server, which are used to confirm message delivery, update the organization, etc.  The FORWARDED DEAD MESSAGE header caused the messages to be unrecognizable as system messages.  In 8.0, when the administrator forwards a system message, the FORWARDED DEAD MESSAGE header is omitted, so this problem is obviated.  Also, unlike forwarding a regular dead message, the name of the originator is not put into the Copies field of the forwarded dead message.
18.	Option to send Facsimiles via the TelexTWX Manager
A function key has been added to the TelexTWX (codeT) soft key menu to allow users to send Facsimiles via the 1.3 TelexTWX Manager software. Note that the Facsimile service offered by the TelexTWX Manager software is text only and send only.
Changes from CTMail 7.0.1	
1.	Support for the OFIS Access X.400 gateway and interface
The Interactive Mail Manager been modified to include menus for configuring the OFIS Access X.400 gateway and for addressing messages to remote X.400 mail users. Additionally, the Interactive Mail Manager has been modified to include menus for configuring EN3 module addresses and network paths to run on the Unisys BLAN and OSI networks.
2.	To Be Delivered Status
A function key has been added to the Maint function key strip to allow users to view a queue of both confirmed and unconfirmed outgoing message. The confirmation records may be deleted or moved to dead mail similar to the message queue feature. Users with administrative privileges are allowed to view and disposition ToBeDelivered records for the entire mail center, while users with standard privileges may only view the status of messages that they sent.
3.	Alternate User feature
If a user has registered his folder directory on a server workstation, he may allow another user on the cluster or network to access his in tray. The alternate user may then either forward or reply to any message in the In Tray. Any message dispositioned by an alternate user will have a string appended to the subject field indicating who the alternate user was and the message will be filed in a folder named Processed by <original user name>. Alternate users will not be able to view folders or any other part of the primary users mail configuration. A field has been added to Add Local User menu for specifying an Alternate Password. Any user attempting to use the alternate access feature will be required to enter this password before they can access the In Tray.
4.	Text and menu color selection
Options have been added to the user profile menu for setting the color of text and the layout of the Interactive Mail Manager.
5.	Mail Receipt Alarm
An option has been added to the user profile menu for requesting an audible alarm upon receipt of new mail when the Interactive Mail Manager is in an active memory partition.
6.	Multiple folder message filing
The Interactive Mail Manager has been modified to allow a mail message to be filed in up to 8 folders (delimited by commas) sequentially.
7.	Option to attach distribution lists
The Send Message form of the Interactive Mail Manager has been modified to provide an option  to attach a distribution list when sending mail.
8.	Communications Agent Log
The Mail Service has been modified to work with a new utility program Communications Manager Status Log for recording incoming and outgoing mail connections. Before this utility is invoked the Enable Communications Manager Status Log command must be issued.
9.	OFIS Access Professional Gateway
The Interactive Mail Manager has been modified to include the necessary menus and options for configuring the new OFIS Access Professional gateway, which allow OFIS Mail users to exchange messages and attachment files with users of IBM's PROFS system.
10.	Additional privileges for standard users
The Interactive Mail Manager has been modified to allow standard users limited modification of their own user records such as password, autoforward, simple name, and phone number.
11.	Autoforward tracking
If a mail message is autoforwarded, that fact is indicated in the subject field of the message.  The names of both the original recipient and the user to whom the message was autoforwarded are both indicated.
12.	DDN renamed to SMTP
The forms for configuring a DDN manager and center have been renamed to SMTP for consistency with the current SMTP Manager software. 
Additional new functionality	
1.	Phone Memo Manager
The Phone Memo Manager has been added to the OFIS Mail product offering. The Phone Memo Manager is an interactive program that allows editing and sending of phone memos commonly used by secretaries and receptionists.
2.	Support for multiple bulletin boards
The public bulletin board feature of OFIS Mail 1.2.3 has been modified to allow the mail administrator to create and maintain an unlimited number of bulletin boards at a mail center. Bulletin Boards are mail folders that reside at the server work station and are sharable by all users on at a mail center.
3.	Blind CC Option
The Send Message form of the Interactive Mail Manager has been modified to include a Blind CC field in the new message form. The recipients' message will not contain the information from the Blind CC field of the original message. The Blind CC option is enabled by entering the string :Allow Blind Copies:Yes in the MailCenter.config file and then running the Configure Mail Center program and overwriting the MailCenter.cnfg file. If this string is not present or it is set to No then the Blind copies field will not be displayed.
4.	Folder Search
A function key has been added to the opened folder menu for searching the message summary screen. Additionally, an option for searching the entire contents of a mail folder for the user supplied string has been added to the menu.
5.	Default message priority option
The profile menu of the Interactive Mail Manager has been modified to include an option for a default message priority. In the past the Interactive Mail Manager has always defaulted to Normal when sending a message.
6.	New Installation Scripts
New installation scripts have been developed for compatibility with the 12.0 Standard Software and the Unisys Software Install product.
7.	Discarding of attachments from folders
In previous versions of the Interactive Mail Manager when one discarded a message from a file folder there was no option presented to discard the attachments. This has led to many directory full errors as a result. The 8.0 Interactive Mail Manager will provide an option to disposition any attachments present when discarding filed messages.
8.	Improved Mail Service performance
In the previous version of OFIS Mail the maximum number of sector buffer the administrator could allocate for the mail service was 87. This maximum has been increased to 10,000. With this increased memory allocation the mail service can cache some of its configuration files in memory allowing much quicker access to the user and center directories. Additionally, another option has been added to MailCenter.config for increasing Mail Service performance. If the entry for :Number of large copy buffers:0 is increased to 1 or more, the Mail Service will allocate an additional 60k of memory for the copying files as necessary. With these parameters tuned properly, the mail service will no longer cause sluggish system performance when updating the user directory or the NameRegistry information as it did in prior versions.
9.	CodeDelete has been implemented
Pressing CodeDelete in the Interactive Mail Manager menus will now erase a complete line of text. This has been added for consistency with the Standard Software editor as well as other products.
10.	Configurable maximum attachment size per message option
An option has been provided to allow the administrator to limit the total size (in sectors) of all the attached files that may be sent in a single message. If a user attempts to send a message with  a total attachment size in excess of the configured maximum then an error message will be displayed and the send operation will be canceled. The maximum attachment size option is enabled by changing the parameter Maximum attachment size per message:0 to any value greater than zero in the MailCenter.config file and then invoking the Configure Mail Center command and overwriting the MailCenter.cnfg file. If this string is not present or it is set to 0 then the maximum attachment size is unlimited.
Section 3	
Product Interdependencies	
Software	
Operating System Requirements	
The following operating system release levels are the minimum guaranteed to be compatible with OFIS Mail 8.0:
CTOS II 3.3
CTOSVM 2.3
BTOS II 3.0.1
CTOS I 3.3
CTOS 9.10
BTOS 8.2.1
CTOS XE 3.0
CTOS SRP 1.4.7
BTOS XE 7.2.2
Higher release levels will also work.
OFIS Mail 8.0 is compatible with all previous versions of OFIS Mail CTMail, and BMail and for purposes of exchanging mail between centers.
Memory Requirements	
The total memory requirement of the Mail Service (in Kilobytes = 1024 bytes) can be approximated as follows:
Memory = 167K
+ (10K  * Number of Mail Service processes)
+ (0.5K * Number of sector buffers)
+ (60K  * Number of large copy buffers)
Thus, the Mail Service requires approximately 185K in the minimum configuration (1 process, 15 sector buffers, 0 large copy buffers).  The minimum Mail Service configuration for use with BNet II (2 processes, 30 sector buffers) is approximately 202K.  The default memory utilization is approximately 217K.  Specifying more than the minimum number of sector buffers or large copy buffers improves the performance of the mail center at the cost of additional memory utilization.  Since the Mail Service is always installed at the server 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 Service.  The performance of the Mail Service 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 Service.
Each installation of the Communications Manager requires approximately 36K.  This memory requirement may be at the server 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 the available memory of the partition in which it is run.  The Interactive Mail Manager requires an absolute minimum of about 185K to run.  The responsiveness of the program is very sensitive to the amount of memory available, and at least 220K is required for acceptable performance and 300K for good performance.  The maximum amount of memory that the Interactive Mail Manager can take advantage of is about 550K.  On a CTOS workstation with the VoiceData Services installed (i.e., if the Voice Mail or Dialing features are available), then an additional 24K must be added to each of these figures.
The amount of memory available to the Interactive Mail Manager also affects the maximum size of file folder that can be displayed.  Users running the Interactive Mail Manager in small memory partitions should avoid building up large file folders.  Unlike the Mail Service and the Communications Manager, the Interactive Mail Manager is not an installed system service, so it does not permanently reserve memory.
Disk Requirements	
The amount of disk space required for OFIS Mail 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 server workstation and the local file systems on the cluster.  In general, approximately 2300 sectors (including run files) are required to bring up a mail center with only one user, and at least 210 sectors per additional mail user and 22 sectors per additional mail center are required.  (Note:  Only mail centers which are distributed through a Communications Manager or through BNET II 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.
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.
Recommended Additional Software	
Modem Service 5.0 or higher
BNet II 1.0 or higher
CTNet 3.2 or higher
OFIS Access X.400 1.0.2c or higher
OFIS Access 1100 1.0
OFIS Access A Series 1.0
OFIS Access Professional 1.0
TCPIP 1.0 or higher
Terminal Mail Manager 2.1 or higher
TelexTWX Manager 1.2 or higher
ClusterShare Mail 1.0
Hardware	
Requirements	
OFIS Mail is supported on the following processors:

B25CPU, B25EV
B28CPU, B28EV, B28EXP
286i
B38CPU, B38EV, B38LCW
B39
SG2000
XE520
XE530
Graphics Modules:

B25GRE (GC001)
GC002
GC003
B25AG1 ,B25AG2
B25GPP
B25VG1, B25VG2 (GCx041)
B25VG3, B25VG3 (GCx042)
Monitors (when used with a graphics module as a supported configuration):

B25D1 (VM001)
B25D2 (VM002)
B25CD3 (VC002)
B25PD7
B25PD8
VM003
B25CA1 (VC003)
B25GS1
B25VA1
Recommended Additional Hardware	
The Voice Mail feature of OFIS Mail may be accessed only from a CTOS workstation with a VP002 Voice Processor module and the Telephone Service of 1.0 or later 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 BNET II 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 , Bell 212A, v.29 or v.32 compatible asynchronous autodial modem is required for each Communications Manager that will so communicate. Most asynchronous autodial modems can be used by means of the ModemGen feature.  See the CTOS Modem Service Operations and Programming Guide 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.
Section 4	
Migration Requirements	
None.
Compatibility with Previous Versions	
OFIS Mail 8.0 is compatible with all previous versions of OFIS Mail, BMail and CTMail.
Section 5	
Corrections	
UCFs and SPRs Closed	
The following problems have been corrected in this release of OFIS Mail:
SPR 15345 
The notes fields of phone memos were not saved when the memos were filed into mail folders.
SPR 15500
The priority of print jobs sent from the Interactive Mail Manager to GPS devices was always set to the default of 5 and could not be overridden.
SPR 15556
The Interactive Mail Manager displayed error code 10224 or 10225 with no description when an administrator attempted to remove an organization member center.
SPR 16092, 16231
An incorrect parameter in the OpenMailConnection request caused error code 215 to be returned when signing on to mail on an XE520 or XE530.
UCF 14545093
Closing Bulletin Board window also closed Bulletin Board message.
UCF 14545522
Organization updates could be lost if the server workstation was rebooted prior to the update messages being written to disk.
UCF 14551832
The Change Folder Directory feature returned an incorrect error message if the old folder directory did not exist. The Interactive Mail Manager reported that new folder directory did not exist when it was actually the old folder directory that was missing.
UCF 14552600
It was not possible to access dead mail when signed on to mail on a remote node.
UCF 14553240
It was not possible to make organization member lists as large a the maximum limit which is equivalent to the CTOS Xblock size.
UCF 14553762
Attempting to print folder contents in excess of 64k bytes caused the Interactive Mail Manager to abort with error code 212.
UCF 14555765, 42596604
The Mail Service would occasionally malfunction with error code 10108 when running with BNET II on an intensely active network.
UCF 14559493
If the Mail Service at the Server workstation was suspended the Interactive Mail Manager displayed the message Master Went Down. The Interactive Mail Manager now displays the message Mail Suspended.
UCF 14561617
The Interactive Mail Manager would occasionally abort with error code 10809 when trying to automatically reorganize the In Tray.
UCF 14562761, 25932536, 26001161, 26073511, 31058155, 42661708
The Interactive Mail Manager did not display the first character of an incorrectly spelled recipients name when it attempted to automatically correct it.
UCF 16030236
Messages addressed to a bulletin board were sometimes delivered instead to a user's In Tray.
UCF 16033014
The last mail service deinstalled via MReset Mail Server crashed the XE with status code 245.
UCF 16035963
The copy key did not work for copying file names longer than 36 characters from file directory windows into the attach field.
UCF 16088498
AutoForwarding to an alias name did not work.
UCF 16106003
The Interactive Mail Manager allowed users to move text from messages in the In Tray into a new mail message thereby removing portions of text from the original messages.
UCF 16124681, 26147999, 31055342
The profile options for color didn't work when running VGA on a GC004.
UCF 16175617
The autoreorg In Tray feature would cause a message to be lost if a disk full error was encountered.
UCF 16251801, 42576069, 42620025
Notification of new mail sometimes became erratic, either failing to indicate the presence of new mail or indicating that there was new mail when none was, in fact, present.
UCF 16299031
Using the Context Manager running multiple mail contexts across BNET II would cause the Interactive Mail Manager to display the message Master Went Down. The Interactive Mail manager now displays the message Notification Off under these circumstances.
UCF 16314579
It was not possible to access a bulletin board when signed on to a remote center across BNET II.
UCF 16314609
When opening a mail message, the UserNameCenterName were sometimes displayed instead of the simple name if BNet was used.
UCF 16442500
The Generic Mail Center feature returned misleading error messages when incorrectly configured.
UCF 16470643
The Interactive Mail Manager could not print to a non GPS spooled printer on an XE520 if GPS requests were loaded into [Sys]<Sys>Request.sys.
UCF 16486043
Standard users were allowed to rename bulletin boards thereby creating new local folders.
UCF 16492884
Installation of OFIS Mail failed on systems running BTOSII 3.2 due to overlapping request codes.
UCF 25105664, 42689190
The Interactive Mail Manager did not properly display unique attachment names when two or more attachments of the same name were sent from different directories.
UCF 25908562
Under certain conditions the Interactive Mail Manager would prompt for printing to a disk file instead of a printing to the designated printer.
UCF 25961897
The MReset Mail Server command sometimes failed to work on the XE520.
UCF 25997751
A Mail Transport Error Type 1 with status code 10228 was encountered when attempting send a message addressed to an X.400 recipient using the CodeM command if the OFIS Access X.400 gateway was installed on a different mail center from the center in which the message was sent.
UCF 26071275
The Mail Service caused system hangs and dead mail during periods of heavy mail traffic, mail folder reorganizations, and organization updates due to error 10069, Folder Access Method timeouts.
UCF 26081092, 42592617
If a users profile was set up to automatically file incoming mail messages and the user replied to an incoming message while the default folder was open, the original incoming message would be lost when the reply was sent.
UCF 26154022
When updating a distribution list, if a name in the list was not recognized, the error message returned showed the unrecognized user name incorrectly.
UCF 26157188, 26160669, 42688819, 42723941, 42729728
Printing to spooled (nonGPS) printers did not work on certain newer versions of the OS. Error code 212 was returned in several cases if a print job  was attempted.
UCF 26166632
If a user filed a message with two or more attachments and indicated that the attachments should be moved to another directory with confirmation, but then denied moving the second attachment file and confirmed discarding it, then the second attachment file was not discarded.
UCF 42517810, 42735400
Printing did not work if a user was pathed to a remote node when running the Interactive Mail Manager.
UCF 42576425, 42742431, 42778168
The user file entry :MailDefaultPrinter: did not work if the specified printer did not appear in the example list of printers in the Mail Print form. In this case, the first printer in the GPS.printers file became the default printer.
UCF 42650722, 42652008, 42676934, 42682845
During a large organization update, the Mail Service would cause cluster performance to become extremely slow. This was most often observed on XE's and SRP's. The 8.0 Mail Service contains performance improvements and allows the administrator to specify a larger number of buffers, which make organization updates run faster and more smoothly.
UCF 42661651
Mail connections were not recoverable when a user was signed on to a remote center across BNET II and an intermediate node crashed.
UCF 42760277
The Interactive Mail Manager displayed the attachment file password if the password caret  was removed by the user.
UCF 42764345
The Interactive Mail Manager incorrectly displayed the message Master Went Down when a user was signed on as two different mail users while running the Context Manager.
UCF 42782602
Users could not reply to incoming messages from X.400 centers.
UCF 42793566
Error 10069 (FAM Timeout) recorded during organization updates, accompanied by slow system performance.
Section 6	
Restrictions and Known Limitations	
OFIS Mail Limitations	
1.	Messages up to 64K in length (approximately 2550 screen pages) are supported in OFIS Mail.  If a larger message 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.	Attachment files up to 16 Megabytes (32768 sectors) in length are supported in OFIS Mail.  If a larger attachment file is sent, then the Delivering message... status message stays on the screen and control is never returned to the user.  The only way to regain control is to type ActionFinish.
3.	New mail notification does not appear in programs such as the Executive and OFIS Document Designer for any period that the default path is set to be on another BNET II node.
4.	Message recovery may fail if the user signs on to Mail in the same context using a different mail user name before signing on using the mail user name under which the original message was being edited.  Message recovery will also fail if the user deletes the file [sys]<$000>UserNum>Mail.tmp1 prior to attempting the recovery, where UserNum is the five digit number representing the context in which Mail.run was run.
5.	If MInstallServer.run is used to try to install the Mail Service on an XE, error code 2450 (no such subparameter) is written to the PLog and the installation will fail.
6.	OFIS Mail 8.0 is shipped with Modem Service 5.0.  Although, OFIS Mail 8.0 itself supports the SG2000, Modem Service 5.0 does not.  In addition, Modem Service 5.0 does not support use of the modem built into the TM001 Voice Processor module.  In order to use this modem with OFIS Mail, Modem Service 4.5 must be used instead of Modem Service 5.0.
7.	Using the parallel port to print directly from Mail (without GPS or the Spooler) to certain laser printers may fail on CTOS 2.3, CTOS 2.4, BTOS 8.2.1, and BTOS 8.3.  The symptom is that only the first line of the mail message is printed.
8.	Using a serial port to print directly from Mail (without GPS or the Spooler) may fail with status code 67 on CTOS 2.3.
9.	The MReset Mail Service command (used to deinstall, suspend, and resume the Mail Service on XE520s running pre12.0 Standard Software sometimes deinstalls the Mail Service, despite the fact that the user has indicated that the Mail Service should be suspended or resumed.  If the administrator instead uses the command line interface (via the MCli command or by connecting a terminal to the CLI port of the board where the Mail Service is installed), and invokes the command by typing

    Run [Sys]<Sys>MailServiceUtil.run,Suspend
or
    Run [Sys]<Sys>MailServiceUtil.run,Resume

then the command works correctly.
10.	Neglecting to power down any workstations in the cluster that load Mail.run from the server's disk (see p. 33 Common Installation Issues, 1) and updating the Mail.run file while the Interactive Mail Manager is running on one of these workstations (for example, by overwriting the run file just after rebooting the server) is likely to cause the Interactive Mail Manager to fail with status code 80 (Protection violation).  Subsequent invocations of the Interactive Mail Manager will work correctly.
Section 7	
Customer Product Information	
Software	
Style ID	Product Name
MBXB25 XM2	OFIS Mail 8.0
Documentation	
Requirement	
Part Number	Manual Name
39151592800	CTOS OFIS Mail User's Guide and Getting Started with OFIS Mail
39151584800	CTOS OFIS Mail Administration Guide
41630336000	CTOS Modem Service Operations and Programming Guide
Recommended Additional Manuals	
39151600800	OFIS Mail Programming Guide
43575026100	Phone Memo Manager User's Guide and Phone Memo Manager Quick Reference Card
Section 8	
Support	
The support offered for this product is a standard offering for BTOS and CTOS software and it is covered under the SURETY Support Agreement.
Support Category	
OFIS Mail 8.0 is supported by all four categories of the Unisys SURETY Service (listed below).
Support Centers	
The USA locations are the Customer Support Centers (CSCs).
Unisys SURETY Service Offering	Telephone Number

Intro	19008609106
Basic	19008609106
Basic Plus	19003280440
Comprehensive	19003280440
Europe and Africa locations are the Unisys Support Centers.
North and South America (except the USA), Pacific and Asia locations are the Resource Control Centers.
User Communication Forms (UCFs) must be coordinated through a Unisys Customer Support Center (CSC), Unisys Support Center, or Resource Control Center.
Section 9	
Ordering Procedures	
Please complete and return the attached Program Maintenance Request form to order this product.  Media provided by Unisys Corporation may not be returned for credit.
You can order manuals from the following address:
Unisys Corporation
Publications Distribution Center
13250 Haggerty Road North
Plymouth, Michigan 48170
Section 10	
List of Files on Product Media	
Contents of the Distribution Diskettes	
The OFIS Mail distribution diskettes are your master copy and have been writeprotected.  The contents of the diskettes cannot be overwritten unless the writeprotect tabs are removed.  Do not remove the writeprotect tabs and do not use these diskettes as your working copy.
Distribution Diskette 1 contains the following files in <Unisys>:
	CommMgrLog.run		MailLfsInstall.sub
	CommunicationsManager.run		MailMsg.bin
	ConfigureMailCenter.run		MailRqI.sub
	DeInstallCommMgr.run		MailRqII.sub
	MailCenter.config		MailService.run
	MailCm.sub		MailServiceUtil.run
	MailLfs.sub		Request.8.txt
The diskette also contains the following files in <Sys>:
	AdminInstall.files		LFSInstall.sub
	Delete.fls		LInstall.run
	HDInstall.sub		ServerInstall.sub
	Install.cmds		SRPInstall.sub
	Install.ctrl		Submit.fls
	Install.jcl		XeInstall.sub
	Install.sub		Xe530Install.sub
	InstallConfig.sys
The diskette also contains the following file in <Lib>:
	Mail.lib
Distribution Diskette 2 contains the following files in <Unisys>:
	Mail.run		MailMenus.sys
Distribution Diskette 3 contains the following files in <ReleaseNote>:
	ReleaseNotice 		ReleaseNotice.def
Section 11	
Installation Procedures	
Overview	
The OFIS Mail should only be used on BTOS or CTOS Information Processing Systems that are equipped with a hard disk or in clusters where the server is equipped with a hard disk.
Use the following installation procedures to install OFIS Mail on your workstation.  Characters that you must type are shown in boldface.  Special keys, such as RETURN and GO, are shown in upper case.  For details on using the Executive and its commands, see the CTOS Executive User's Guide and the CTOS Executive Reference Manual.
The terms CTOS I and CTOS II may be encountered in some of the installation procedures. CTOS I refers to any CTOS or BTOS version which loads individual request files of the form [Sys]<Sys>Request.?.sys. (This includes BTOS 8.2.1 on real mode processors) while CTOS II refers to CTOS and BTOS revision levels which load the single request file [Sys]<Sys>Request.sys. (This includes CTOS II 3.3, CTOS I 3.3, CTOSVM 2.3 or higher,  BTOS II 3.0.1 or higher,  CTOS VM 9.10, CTOS XE 3.0, CTOS SRP 1.4.7, and BTOS XE 7.2.2.)
Since OFIS Mail 8.0 is the first CTOS  BTOS merged release, there are three installation methods to choose from, namely the CTOS Install command, the BTOS Software Install or XESoftware Install commands, and the 12.0 Installation Manager which runs on both the CTOS and BTOS platforms.
Types of Systems	
The following information explains how to install OFIS Mail on three types of systems:
	Standalone and cluster workstations with hard disks
	Server hard disk systems
Note:	You cannot install the OFIS Mail on systems that contain only a floppy disk (unless your target installation device is the server workstation).
Required Files	
The following files are copied to the Sys directory of a server workstation or XESRP:
	Mail.run		MailLfsInstall.sub
	CommMgrLog.run		MailMsg.bin
	CommunicationsManager.run		MailRqI.sub
	ConfigureMailCenter.run		MailRqII.sub
	DeInstallCommMgr.run		MailService.run
	MailCenter.config		MailServiceUtil.run
	MailCm.sub		Request.8.txt
	MailLfs.sub	
Common Installation Issues	
1.	If you are installing OFIS Mail to a workstation server it is suggested that you power down all workstations attached to the server to ensure that [Sys]<Sys>Sys.cmds and [Sys]<Sys>Mail.run files can be updated.

If you are installing OFIS Mail to an SRP, XE520, or XE530 server it is recommended that you power down all cluster workstations except the one being used to install the software. This will ensure that [Sys]<Sys>Sys.cmds and [Sys]<Sys>Mail.run files on the server can be updated.
2.	If your mail system requires the Modem Service you must first install the Modem Service from the Modem Service Distribution Diskette and configure it to support the communications lines you will be using for OFIS Mail.  See the Modem Service Release Notice for instructions on how to install the Modem Service. Likewise, see the Phone Memo Manager Release Notice for instructions on how to install the Phone Memo Manager.
3.	After installing OFIS Mail 8.0 on either a workstation or XE server, submit the MailLfsInstall.sub file (copied to the server during installation) to get the Mail command and associated run file copied to a cluster workstation with a local hard disk, submit the file [Sys]<Sys>MailLfsInstall.sub.  (See section 4.6 Local File Systems for more details).
4.	The file MailServer.run has been renamed to MailService.run in this release. After installation to the server is complete you must edit the file [Sys]<Sys>Sysinit.jcl and change all references of MailServer.run to MailService.run in order for the OFIS Mail 8.0 Service to install when the server is rebooted.
5.	Installation on XE or SRP systems requires a Cluster workstation with at least one floppy disk drive.
Installing OFIS Mail in a CTOS environment	
1.	Sign on and set path on the workstation being used to do the installation.  If the Signon form is displayed, fill it in and press GO.  Set the path as follows:
	Command   Path
Path
  [Volume]	Sys
  [Directory]	Sys
  [Default file prefix]
  [Password]	(if any)	GO
  [Node]
If your [Sys] disk volume has a volume password, fill this password into the [Password] field before pressing GO.
2.	Insert OFIS Mail Distribution Diskette 1 of 3 in drive [f0].  (Do not press the RESET button.)
3.	Install the product as follows:
	Command   Install		GO
4.	You will be prompted to select your system configuration. Move the highlighted bar to select the configuration of the system which is to have OFIS Mail 8.0 installed (Workstation Server, Cluster Workstation, XE520 Server, or XE530 Server) and hit GO. At the appropriate time, a message will appear prompting you to insert Distribution Diskette 2 of 3.  After you have done this, press GO, and the remainder of the OFIS Mail software will be installed automatically.  Save the Distribution Diskettes as archive copies
5.	OFIS Mail Distribution Diskette 3 of 3 contains the Release Notes in Document Designer (version 3.0) format and DEF format.  If you want the release notes copied to hard disk you must insert OFIS Mail Distribution Diskette 3 of 3 in the floppy drive, path to the directory where the release notes are to be copied, then use the following command:
	Command   LCopy
LCopy
  [File name(s)]	[f0]<ReleaseNote>*	GO
  [File prefix from]
  [File prefix to]
6.	The copy of the MailCenter.config file that is included on OFIS Mail Distribution Diskette 1 of 2 is intended only as an example, and must be edited to conform to your system requirements before the Mail Service can be installed.  For instructions on how to modify the MailCenter.config file and bring up your mail center, consult the CTOS OFIS Mail Administration Guide.
7.	Submit the file [Sys]<Sys>MailLfsInstall.sub on each of the cluster workstations with local disk to copy the 8.0 Interactive Mail Manager to the local disk, create the Mail command, merge the OFIS Mail 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.
Installing OFIS Mail in a BTOS environment	
The BTOS commands Software Installation and XESoftware Installation can be used to install OFIS Mail 8.0 to a workstation server or XE520 server, respectively.
Note:	XESoftware Installation can only be used to install OFIS Mail 8.0 on an XE520.  To install OFIS Mail 8.0 on an XE530 you must use the 12.0 Installation Manager (see Section 4.4: Installation using the 12.0 Installation Manager) or the CTOS Install command (See section 4.2: Installation using CTOS Install).
1.	Sign on and set path at the server workstation.  If the Signon form is displayed, fill it in and press GO.  Set the path as follows:
	Command   Path
Path
  [Volume]                    Sys
  [Directory]                  Sys
  [Default file prefix]   
  [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.
2.	Insert OFIS Mail Distribution Diskette 1 of 3 in drive [f0].  (Do not press the RESET button.)
3.	Install the product as follows:
	Command   Software Installation		GO
or if installing to an XE 520:
	Command   XESoftware Installation		GO
4.	At the appropriate time, a message will appear prompting you to insert Distribution Diskette 2 of 3.  After you have done this, press GO, and the remainder of the OFIS Mail software will be installed automatically.  Save the Distribution Diskettes as archive copies.
5.	The copy of the MailCenter.config file that is included on OFIS Mail Distribution Diskette 1 of 2 is intended only as an example, and must be edited to conform to your system requirements before the Mail Service can be installed.  For instructions on how to modify the MailCenter.config file and bring up your mail center, consult the CTOS OFIS Mail Administration Guide.
6.	Submit the file [Sys]<Sys>MailLfsInstall.sub on each of the cluster workstations with local disk to copy the 8.0 Interactive Mail Manager to the local disk, create the Mail command, merge the OFIS Mail 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.
Additional XE520 Information	
If you are installing OFIS Mail on an XE520 running a version of Standard Software older than 12.0, then complete the following steps:
1.	Edit the file [Sys]<Cmd>WsAdminAgent.txt and add the following entries:
	MInstall Mail Service	[Sys]<Sys>MailService.run
	MInstall Communications Manager	[Sys]<Sys>CommunicationsManager.run
	MReset Mail Service	[Sys]<Sys>MailServiceUtil.run
	MDeinstall Communications Manager	[Sys]<Sys>DeinstallCommMgr.run
2.	Install the Mail Service on the XE520 by modifying the InitFp00.jcl, InitCp00.jcl, or InitTp00.jcl file to include the following command:
	$Run [Sys]<Sys>MailService.run
3.	Install the Communications Manager on the XE520 by modifying the InitCp00.jcl or InitTp00.jcl file to include the following commands:
	$Run [Sys]<Sys>CommunicationsManager.run, MgrName, MgrPswd
where MgrName and MgrPswd represent the parameters in the Install Communications Manager command (see the CTOS OFIS Mail Administration Guide.  Note that before a particular Communications Manager can be installed, it must be set up in the Interactive Mail Manager.  Also, the Modem Service must be installed as a system service (see the CTOS Modem Service Operations and Programming Guide) before the Communications Manager.
Using Installation Manager	
The Installation Manager can be used to install OFIS Mail to a cluster workstation, server workstation, or XE530 server.
Note:	Do not use Installation Manager to install OFIS Mail 8.0 on an XE520.
Server or XE530 Installation	
The instructions in this section can be used to install OFIS Mail 8.0 on a workstation server or an XE530, as well as updating a server workstation from a cluster workstation with a floppy drive.
1.	Insert OFIS Mail Distribution Diskette 1 of 3 in drive [f0].  (Do not press the RESET button.)
2.	Invoke the Installation Manager with the following command:
	Command   Floppy Installation		GO
3.	When prompted select 'ExamineChange Options' from the menu and press GO.
4.	Move the highlighted bar to select Public installation and type Y, then press GO.
5.	You will be prompted to have the Mail.Lib file and the Release Notes copied to your local hard disk, as well as to have the Mail command added to the Context Manager configuration file.  Select (by pressing the MARK key) all of the options you want installed.  Press GO when all selections have been made.  If you select the option to add the Mail command to the Context Manager configuration file, you will next be prompted for the name of the Context Manager Config file, for which the default is [Sys]<sys>CmConfig.sys.
6.	At the appropriate time you will be prompted to insert OFIS Mail Distribution Diskette 2 of 3 into the floppy drive.
7.	If the Copy Release Notes option was selected you will be prompted to insert OFIS Mail Distribution Diskette 3 of 3 into the floppy drive at the appropriate time.
Cluster Workstation Installation	
If OFIS Mail 8.0 has been installed on the server using the Public installation option you can select Install from Server option, after invoking Installation Manager, to have the Mail command created, the request codes merged, and the Mail.run file copied to the local hard disk, you will also be prompted if the Mail command is to be added to the Context Manager Configuration file.
If OFIS Mail 8.0 has not been installed on the server as a public command installation to the cluster workstation should be done without selecting the public installation option.
Local File Systems	
To install or update the OFIS Mail software on a cluster workstation with local file system, you can use the procedure for installing OFIS Mail from the Distribution Diskettes with the exception that you should select the Workstation Cluster configuration.  A simpler and more efficient method for updating local file systems is as follows:
1.	Make sure that the OFIS Mail 8.0 has been installed on the server.
2.	Install the OFIS Mail software on the local hard disk as follows:
	Command   Submit
Submit
  File list                        [Sys]<Sys>MailLfsInstall.sub		GO
  [Parameters]
  [Force expansion?]
  [Show expansion?]
3.	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.