	README.TXT for RDM for Windows v2.2	3/11/93
	===================================

This document contains hints and release notes for version
2.2 of Interleaf RDM for Windows.

=====================< CONTENTS >========================

This file has the following sections:

Part 1: RDM Requirements

Part 2: Setup and Configuration Notes

Part 3: RDM Initialization File Setup

Part 4: Setting up the RDM Password file

Part 5: RDM File "Bill of Materials"

Part 6: RDM Operation Description 

Part 7: Last Minute Corrections and "Bugs"

==============< Part 1: RDM Requirements >================

RDM for Windows requires a MINIMUM of 4MB of memory
running under Windows 3.1 with DOS 5.0.  RDM is only
supported in Enhanced mode.

This version of RDM requires communications with a UNIX
"RDM Server" which performs the actual ORACLE database
operations.  To accomplish this, RDM requires the TCP/IP
kernel (PC/TCP Plus Version 2.11 [or 2.2]) provided by FTP 

Software, Inc.  FTP Software can be reached at (508)685-4000.

Before starting an RDM installation on the PC, make sure
RDM v2.2 has been installed and tested on a supported UNIX
platform.  This will greatly simplify any troubleshooting 
procedures.

=======< Part 2: Setup and Configuration Notes >==========

You must modify rdm.ini for your site before running RDM.
The following entry must be in your services file:

    exec	512/tcp

The PC hosts file must contain an entry for the UNIX machine that 
will be running the CI.

The UNIX RDM server /etc/hosts file must contain an entry for the
client PC.

Before starting an RDM client on the PC, make sure that it is known to the
UNIX node acting as its RDM Server (PC is listed in the /etc/hosts file).
Otherwise, you may encounter the following error message when starting RDM:

	"End of file on read"

========< Part 3: RDM Initialization File Setup >=========

WINDOWS\RDM.INI
---------------
The following variables control RDM and are installation specific.

RDM_INSTANCE
	The database account that you want to use.
RDM_HOST
	The UNIX machine name that will be running the CI.
RDM_COMMAND
	The command used on the RDM_HOST to start the CI. 
	This could be a shell script that sets up a particular 
	environment before starting the CI.
RDM_PASSWORD_FILE
	The location and name of the encrypted password 
	file used by RDM to define the remote UNIX user from 
	which the remote CI process is started; as well as 
	the name and password of the operating system user 
	used to control access to RDM vaults (usually rdm).  
	This file is created by the rdmcrypt utility.
RDM_WORK_AREA
	The directory used as the base directory in file 
	dialogue box operations in check-in and check-out
	operations while running RDM. This is a DOS path.
RDM_APPLICATION_LAUNCH
	A yes/noquery/no response to determine whether RDM
	should ask whether to launch the appropriate viewing/editing
	utility when checking-out an object. 'Yes' launches only after
	verifying with the user, 'noquery' launches without verification.
RDM_REPORT_NAME
	The name of the report file that is created on the 
	PC when an administrator runs an RDM Report from 
	the Utilities menu.

The following variables control the RDM Help mechanism.

RDM_HELP_EXE	
	The name (and path) of the executable used to display 
	help text.
RDM_HELP_ARGS
	The arguments used for the help executable to start 
	the display.
RDM_HELP_DIR
	The directory containing the help text files.

The following variables are only used for WorldView Review.

RDM_PL_REVIEW	
	This is the mounted UNIX directory where RDM will 
	place Worldview PL files. RDM will place these files 
	here from the UNIX side. This value is a DOS path.
RDM_WV_AREA	
	The directory used as a working directory for 
	WorldView Review notes. This is a mounted UNIX 
	directory (from a DOS viewpoint) where RDM will 
	look for WorldView notes from the UNIX side. Notes
	are placed here by WorldView running on the PC. 
	WorldView will read the review documents from 
	RDM_PL_REVIEW.  This value is a DOS path. 
RDM_WV_PATH
	This is the path and/or name of the Worldview 
	executable. If left blank or commented out, this 
	value defaults to:
			iview.exe
	This variable is useful if you do not have 
	Worldview in your path, or if the Worldview 
	executable changes its name.


=======< Part 4: Setting up the RDM Password file >=======

RDM2.2\BIN\RDMTEMP.FTP	
----------------------
Template unencrypted RDMPSWD.FTP file

This file should contain exactly 4 uncommented lines (comment lines
have a ';' in column 1 of a line). The lines represent the
following:

Line 1:	RDM Vault Owner Username (OS user)
Line 2:	RDM Vault Owner Password
Line 3:	OS Username you will be running the Remote CI under (OS user)
Line 4:	OS Password for the Remote CI user

OS user:
========
	In the above explanation, 'OS user' is a valid account on the
	operating system(s) you will be connected to; i.e. UNIX or
	VMS. Since Vaults can reside on multiple machines running
	different operating systems, the Username and Password must
	be the same for the Vault user on every system.

Note:	
=====
	If there is no password for a user, the Password line should
	have the value 'NONE' (the four letters in uppercase). Blank
	lines are not permitted.

Example:
========
	Change the following 4 lines to represent your configuration.
	The Vault Owner was specified during your UNIX RDM
	installation as the owner of the RDM hierarchy.
rdm
rdmpswd
demo
demopswd


To Finish:
==========
	Once finished editing these entries, use the RDMCRYPT utility
	supplied to encrypt this file as follows:

	C:\RDM2.2\BIN> rdmcrypt rdmtemp.ftp rdmpswd.ftp
	C:\RDM2.2\BIN> del rdmtemp.ftp (for security)

=======< Part 5: RDM File "Bill of Materials" >===========

\rdm2.2:
	readme.txt
\rdm2.2\bin:
	rdmcrypt.exe
	rdmjam.exe
	rdmtemp.ftp
	wvreview.exe
\rdm2.2\help:
	fultext.msg
	fultext.stp
	help.cat
	help.cfg
	help.cix
	help.dct
	help.log
	help.ref
	map
	synonyms.fth
\rdm2.2\help\docfiles:
	access.dsm
	access.pl
	checkin.dsm
	checkin.pl
	checkout.dsm
	checkout.pl
	create.dsm
	create.pl
	dispatch.dsm
	dispatch.pl
	index.dsm
	index.pl
	mvdel.dsm
	mvdel.pl
	newrev.dsm
	newrev.pl
	otoc.dsm
	otoc.pl
	overview.dsm
	overview.pl
	reedit.dsm
	reedit.pl
	relation.dsm
	relation.pl
	review.dsm
	review.pl
	route.dsm
	search.dsm
	search.pl
	select.dsm
	select.pl
\rdm2.2\ui:
	data.dic
	egavid.bin
	jpllib.lib
	menulib.lib
	msgfile.bin
	scrlib.lib
	smvars
	smvars.bin
	winkeys.bin
	xsmsetup.bin
\pctcp:
For all PC/TCP installations:
=============================
	ftpcntrl.dll
	services
	system.ftp
	winsock.dll
Only for installations not currently running PC/TCP 2.2:
========================================================
	pctcpapi.dll
	vpctcp.386
	wftplib.dll
	winetlib.dll
	wnet386.dll
	wtelnet.dll
\windows:
	rdm.ini
	vbrun100.dll

==============< Part 6: RDM Operation Description >==================

This is a short description on how the RDM Jam User Interface works.

The RDM Jam Interface is implemented using a client server model.
The UI running on the PC is the client and RDM Server; the rdmci5

process (CI), running on the UNIX machine is the server. The programs 

communcate with sockets using TCP/IP. 

The CI is started on the UNIX machine using the name and password
of the login user specified in the second entry of the password 
file.

When the UI starts you are presented with the login screen. After
RDM user name and password are entered, the UI starts the CI on 
the UNIX machine using the value of the RDM_COMMAND variable in 
the rdm.ini file. If the CI is started the returned version 
message is checked for compatible version numbers.

File transfer during check-in and check-out is accomplished using
ftp. The startup shells of the users in the RDM password file must
be standard shells. The first entry in the RDM password file is 
the UNIX user that has permission to modify RDM vaults. This user 
is used for transferring files during 
check-in and check-out.

File transfers also occur when writing reports. The report is 
written on the UNIX machine using the users work area path as 
specified in the database. This must be a UNIX path. The file is 
then transferred to the directory on the PC as specified by the 
user on the report screen. This must be a PC path. The file
on the UNIX machine is then deleted.

========< Part 7: Last Minute Corrections and "Bugs" >===========

See "RDM for Windows Release Notes" supplied with your manual set.