

	Software
	Reference
	Document
		
Document Exchange Utility
Version R3.1.100
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.
Copyright  1993 Unisys Corporation
All rights reserved.
RESTRICTED RIGHTS LEGEND.  Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 252.2277013  and FAR 52.22714 for commercial computer software
TRADEMARKS:
BTOS, CTOS are trademarks of Unisys Corp.
UNIX is a trademark of ATT.
Contents
Section 1	
General Description		1
Section 2	
New Release Functionality		2
General Functionality		2
Document Exchange To DEF		2
Document Exchange From DEF		3
Section 3	
Product Interdependencies		4
System Software Compatibility		4
Workstation Environment		4
SRP Environment		4
Hardware Information		4
Hardware Configurations Supported		4
Resource RequirementsUtilization		5
Memory RequirementsUtilization		5
Disk RequirementsUtilization		5
Supplementary Information		5
Invoking Document Exchange Utility		5
Disk and File Maintenance		5
Section 4	
Migration Requirements		6
Compatibility with Previous Versions		6
Common Compatibility Issues		6
Section 5	
Customer Product Information		7
Software		7
Documentation		7
Section 6	
Support		7
Section 7	
Installation Procedure		8
Local Installation (Hard Disk Systems)		8
Remote Installation (Server Hard Disk Systems)		10
Required Files		11
Section 1	
General Description	
This Software Reference Document describes the version R3.1.100 release of Document Exchange Utility.  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 Document Exchange Utility.
The Document Exchange Utility is a standalone translation tool that allows the user to create 3.0 version OFIS Document Designer documents from DEF documents and allows the user to create DEF documents from a variety of Wp style documents, including  OFIS Document Designer R3.1.100 and OFIS Document Writer R1.1.100.  From the command line, this utility provides all the controls of the DOCUMENT EXCHANGE menu in OFISDocument Designer R3.1.100 and OFIS Document Writer R1.1.100 with the added benefit of the ability to translate multiple documents in one pass.  The Document Exchange Utility has also been enhanced to provide the same subset translation facilities as OFIS Writer 1.1 when used in conjunction with the OFIS Bridge DCA translation facility.
Instructions on how to use the Document Exchange Utility are provided in this document.  General information about the Document Exchange Format (DEF) can be found in the CTOS OFIS Document Designer  OFISDocument Writer System Administration Guide, Section 4, Exchanging Documents.  
Section 2	
New Release Functionality	
General Functionality	
The Document Exchange Utility provides the capability to exchange documents between users of different versions of OFIS Document Designer, OFIS Document Writer, OFIS Designer, Document Designer and OFIS Writer.  It can also be used for import and export of information about documents to and from other publishing software or application software.
Document Exchange To DEF	
The following menu is used for document exchange to DEF:
Document Exchange To DEF		

From Document(s)        	
[To DEF file(s)]        	
[Target (o, 2, 1 or w)] 	
[Output (b, s, or a)]   	
[Overwrite OK?]         	
[Confirm each?]         	
[Continue on error?]    	


The Document Exchange Utility will translate multiple documents listed in the From Document(s) field to DEF files having file names listed in the To DEF file(s) field.  If names are not listed in the To DEF file(s) field, output file names will be created from respective input file names with the suffix .def appended.  If the input file names end in .doc, the .doc suffix will be stripped from the file name before the suffix .def is appended.  The Target field is used to tailor the DEF output to a known publishing product.  This reduces the number of unreadable DEF codes and optimizes translation.  The default target is OFIS Document DesignerOFIS Document Writer.  This is also the target codes generated if 'o' is entered in this field.  If '2' is entered, OFIS Designer 2.x or Document Designer 2.x compatible codes are generated.  If '1' is selected, OFIS Designer 1.x or Document Designer 1.x compatible codes are generated.  If 'w' is selected, OFIS Writer or Word Processor compatible codes are generated.  The Output field is used to control the output of individual attributes or style definitions of attributes.  This option defaults to the output of both attributes and styles.  This is also the case if 'b' is entered in this field.  If 's' is entered, only style definitions are output and if 'a' is entered, only attributes are output.  The predecessors of OFIS Document Designer  OFIS Document Writer are only capable of recognizing attributes (style DEF sequences will be shown as unrecognized DEF code errors).  
Document Exchange From DEF	
The following menu is used for document exchange from DEF:
Document Exchange From DEF		

From DEF file(s)                      	
[To document(s)]                      	
[Pass through unrecognized DEF codes] 	
[Overwrite OK?]                       	
[Confirm each?]                       	
[Continue on error?]                  	


The Document Exchange Utility will translate multiple DEF files listed in the From DEF file(s) field to documents having file names listed in the To Document(s) field.  If names are not listed in the To document(s) field the output file names will be created from the respective input file names with the suffix .doc appended.  If the input file names end in .def, the .def suffix will be stripped from the file name before the suffix .doc is appended.  
Section 3	
Product Interdependencies	
System Software Compatibility	
Workstation Environment	
For protected mode operation, OFIS Document Designer 3.1 requires:
BTOS II 3.0 or higher	CTOS II 3.3 or higher
CTOS III 1.0 or higher	CTOS III 1.0 or higher
CTOSXE 3.0 or higher

For real mode operation, OFIS Document Designer 3.1 requires 
CTOS I 3.3
SRP Environment	
OFIS Document Designer is a workstationonly product and uses the XE520 and XE530 only as a server.  The supported software is CTOSXE 3.0 or higher.
Hardware Information	
Hardware Configurations Supported	
Document Exchange Utility 3.1 is supported on the following workstations:
B26	B28	B28	B38	B39

EV, EXP and LCW systems are supported.
	
Supergen Series 1000	, 2000, 3000	 and 5000
The Document Exchange Utility is character based and has no special video requirement.
Resource RequirementsUtilization	
Memory RequirementsUtilization	
The Document Exchange Utility requires 200K to operate.  If the Document Exchange Utility exits with an error code of 7649 or 7899, additional memory may be required to complete the function.
Disk RequirementsUtilization	
To install Document Exchange Utility you need about 700 sectors of disk space.
To perform translations with the Document Exchange Utility you need additional sectors of disk space for temporary files equivalent to the largest size of document to be translated.  
Supplementary Information	
Invoking Document Exchange Utility	
Document Exchange Utility is invoked from the Executive.
Disk and File Maintenance	
Consult the OFIS Document Designer  OFIS Document Writer System Administration Guide for information on temporary files, old files, new files, and other files created by Document Exchange Utility.
Section 4	
Migration Requirements	
Compatibility with Previous Versions	
Common Compatibility Issues	
DEF translation has been enhanced to allow the transfer of objects and voice.  The target field in the DEF menu has been extended to produce a DEF output maximized for a particular previous version.  
Note:	If the document has an object or box and the resulting DEF file is to be read in an earlier version supporting documents with objects, select the target that corresponds to the earlier version.
If during DEF the Word Processor or OFIS Writer target option is chosen, then characters above 7Fh will be output literally, as the $(SOn) DEF code (to represent these characters in hexadecimal) is not recognized in Word Processor or OFIS Writer.  This may make the file unsuitable for transmission via 7bit ASCII media.
If during DEF a target version earlier than Document Exchange Utility  Document Writer is selected, then the paragraph attribute for keep together, keep prior and keep following will be replaced by keep together braces at appropriate places.
Section 5	
Customer Product Information	
Software	
The Document Exchange Utility is part of the OFIS Document Designer  OFIS Document Writer installation package.
Documentation	
Instructions on how to use the Document Exchange Utility are provided in this document.  General information about the Document Exchange Format (DEF) can be found in the CTOS OFIS Document DesignerOFIS Document Writer System Administration Guide, section 4, Exchanging Documents.  
Section 6	
Support	
The Document Exchange Utility is a tool supplied with OFIS Document Designer  OFIS Document Writer.  Support for this utility is covered under the support agreement for OFIS Document Designer  OFIS Document Writer.
Section 7	
Installation Procedure	
The Document Exchange Utility should be used only on Unisys CTOS Information Processing Systems which are equipped with hard disk, or in clusters where the server is equipped with hard disk.
Use the installation procedures described below (after updating the Standard Software revision level, if required).  Characters that you must type are shown in boldface.  Special keys, such as RETURN and GO, are shown in upper case.
Local Installation (Hard Disk Systems)	
A local installation is used for standalone workstations and cluster workstations where it is desired to have the Document Exchange Utility command and run file installed on that workstation.  If the command and run file are to be put on the server (as in an SRP server or for use with diskless workstations), see the following section on Remote Installations.
1.	Sign on with the system volume password if applicable.  The   Document Exchange Utility installation gives the user the opportunity to change the path and password.
2.	Insert the Document Exchange Utility Distribution Diskette into drive [f0].  Install the product as follows:
From the Executive, use the Software Installation command or Installation Manager command to initiate the installation procedure, leaving the parameter fields blank.  Press GO.  If using the Software Installation command, go to step 2.2.
2.1	If using the Installation Manager command, do the following:
  Command Installation Manager			RETURN
  [Noninteractive?]		GO
This command will initiate a menu driven installation process. From the first menu of options, select Install New Software. 
The second menu prompts you for your installation source; select Floppy Installation if you are installing from the diskettes or Install from Server if you are installing from a server. 
The next menu sets the installation defaults.  Just press GO.
The next menu will display the command file where the commands will be installed.  If using a different command file, change the file name and press GO.  Follow any remaining displayed directions.
2.2	If using the Software Installation command, proceed as follows:
  Command   Software Installation			RETURN
  [Cmd file]		
  [Files to]		
  [Install file]		GO

This command will cause a series of Submit Commands to run, initiating the installation process.  It will display a boxed banner screen instructing you to enter some optional command file and password information.  Press GO and modify the default parameters if a custom installation is desired.  Press GO again to cause the run command begin.
The installation continues by displaying a message that instructs you to type the password of the destination volume and the volume name in the PATH command form.
  Path
  [Volume]	Sys	
  [Directory]		
  [Default file prefix]		
  [Password]		
  [Node]		

If necessary, enter the password for the destination volume.  
Press GO.  Follow any remaining displayed directions.
Save the Document Exchange Utility Distribution Diskette in a safe place as an archive.
Remote Installation (Server Hard Disk Systems)	
A remote installation is used for diskless workstations and workstations connected to an SRP server.  This installation puts the Document Exchange Utility command and run file onto the server workstation for access by all workstations booted from that server.  If it is desired to have the Document Exchange Utility command and run files installed on the hard disk at the local workstation, refer to the section above on Local Installation.
1.	Sign on with the system volume password if applicable.  The   Document Exchange Utility installation gives the user the opportunity to change the path and password.
2.	Insert the Document Exchange Utility Distribution Diskette into drive [f0].  Install the product as follows:
From the Executive, use the Software Installation command or Installation Manager command to initiate the installation procedure, leaving the parameter fields blank.  Press GO.  If using the Software Installation command, go to step 2.2.
2.1	If using the Installation Manager command, do the following:
  Command Installation Manager			RETURN
  [Noninteractive?]		GO
This command will initiate a menu driven installation process. From the first menu of options, select Install New Software. 
The second menu prompts you for your installation source; select Floppy Installation if you are installing from the diskettes or Install from Server if you are installing from a server. 
The next menu sets the installation defaults.  Just press GO.
The next menu will display the command file where the commands will be installed.  If using a different command file, change the file name and press GO.  Follow any remaining displayed directions.
2.2	If using the Software Installation command, proceed as follows:
  Command   Software Installation			RETURN
  [Cmd file]		
  [Files to]		
  [Install file]		GO

This command will cause a series of Submit Commands to run, initiating the installation process.  It will display a boxed banner screen instructing you to enter some optional command file and password information.  Press GO and modify the default parameters if a custom installation is desired.  Press GO again to cause the run command begin.
The installation continues by displaying a message that instructs you to type the password of the destination volume and the volume name in the PATH command form.
  Path
  [Volume]	Sys	
  [Directory]		
  [Default file prefix]		
  [Password]		
  [Node]		

If necessary, enter the password for the destination volume.  Press GO.  Follow the remaining displayed directions.
Save the Document Exchange Utility Distribution Diskette in a safe place as an archive.
Required Files	
Document Exchange Utility requires the following files.  They reside in [Sys]<Sys>.
DEF.run
OfdMsg.bin
Ofdd.styles
<End of Document>