Conference decalp::rtrnotes

***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

    Reliable Transaction Router(TM) (RTR) V3.1C(126) for Windows 95

***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

    Reliable Transaction Router(TM) (RTR) V3.1C  for Windows 95


  � Digital Equipment Corporation 1988, 1997. All rights reserved.

  Restricted Rights: Use, duplication, or disclosure by the U.S. Government
  is subject to restrictions as set forth in subparagraph (c) (1) (ii) of
  DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as
  applicable.

  This software is proprietary to and embodies the confidential technology
  of Digital Equipment Corporation. Possession, use, or copying of this
  software and media is authorized only pursuant to a valid written license
  from Digital or an authorized sublicensor.


*************    D I G I T A L  E Q U I P M E N T  C O R P . ***********


README95.TXT      05-FEB-1997


Reliable Transaction Router(TM) (RTR) is an open client/server middleware
for continuous computing.

RTR Engineering is pleased to announce that RTR V3.1C(126) for
Windows 95 is now available.  This release has gone to SSB and can
be ordered through normal channels.  It is provided here for the
convenience of Digital personnel who wish to evaluate this version of RTR.



COPYING THE KIT

The kit is available on the Easynet in the form of a self-extracting
archive file.  The file is available at this location:

    DECnet nodes:    DECALP::        (48.608)
                     TALER::         (2.865)
    Kit Location:

        Directory:  RTR$KITS:[RTRV3.W95]
        Filenames:  RTR_126.EXE

Note: When copying this file across the network, be sure to use
the 'image' or 'binary' file transfer option of your file transfer
utility. Copy the file to any convenient directory.

INSTALLATION

	FTP> binary
	200 Type set to I
	FTP> get rtr_126.exe

To unpack the archive file on Windows 95, simply execute the file:

    C:> rtr_126

Please refer to the Installation Guide supplied the directory 
[TALER|DECALP}::RTR$KITS:[RTRV3.W95] for further instructions.  
(the installation is the same as for Windows NT).


SUMMARY OF FEATURES

  This version is intended for implementation on client nodes
  only, although server and router functionality is included
  for the purpose of testing and debugging applications.

  The RTR Version 2 API routines are supported to facilitate
  the porting of existing applications to the W95 platform.

  Please see the Release Notes and Software Product Description
  for more details.  Release Notes may be found in the same
  directory as the kit, under the file names RELNOTES.TXT
  and RELNOTES.PS.

  
LIMITATIONS

  RTR for Windows 95 is designed as a console application.
  Please be aware that logging off the machine will stop
  all RTR processes.

  Remote commands may be sent from Windows 95 nodes, and
  Windows 95 nodes may be used in SET ENVIRONMENT commands
  and "/NODE=" aualifiers.  This feature requires the
  installation of a remote shell (rsh) daemon for Windows 95,
  which is not supplied with this kit.

  Please see the Release Notes and Software Product Description
  for more details.


KNOWN PROBLEMS

  If you get the %RTR-F-ERRACCNOD error message at the
  RTR command prompt, simply re-type the command.  It should
  work the second time.  If not, contact RTR Engineering.

  Please see the Release Notes and Software Product Description
  for more details.


PROBLEMS CORRECTED

  Please see the Release Notes for more details.


PROBLEM REPORTING

   For problem reporting:
    a. Send mail to the RTR Problem Manager, Jon Lehto at FFRANC::LEHTO.
    b. If you have any rtr log files or pertinent output from
       monitor pictures or RTR show commands, send it to us via E-mail.
    c. Send us as much other information as possible about the
       conditions which caused the failure, pointers to applications
       programs which caused the problem, command sequences, etc.

   Please exercise it. WE WANT YOUR FEEDBACK.



USING THE RTR NOTES CONFERENCE

    Requests for new features, functions or general RTR for Windows95
    discussions should be submitted in the Notes Conference at
    DECALP::RTRNOTES.  Please note that this notes conference is not an
    official problem reporting channel.


DOCUMENTATION

    The latest postscript versions of the RTR Version V3.1
    documentation can copied from DECALP::RTR$KITS:[DOC.RTR_V31].


***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

  Reliable Transaction Router(TM) (RTR) V3.1C(126) for Windows NT

  � Digital Equipment Corporation 1988, 1997. All rights reserved.

  Restricted Rights: Use, duplication, or disclosure by the U.S. Government
  is subject to restrictions as set forth in subparagraph (c) (1) (ii) of
  DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as
  applicable.

  This software is proprietary to and embodies the confidential technology
  of Digital Equipment Corporation. Possession, use, or copying of this
  software and media is authorized only pursuant to a valid written license
  from Digital or an authorized sublicensor.


*************    D I G I T A L  E Q U I P M E N T  C O R P . ***********


RTR31C_126_README.TXT      07-FEB-1997


Reliable Transaction Router(TM) (RTR) is an open client/server middleware
for continuous computing.

RTR Engineering is pleased to announce that RTR V3.1C(126) for
Windows NT is now available.  This release has gone to SSB and can
be ordered through normal channels.  It is provided here for the
convenience of Digital personnel who wish to evaluate this version of RTR.



COPYING THE KIT

The kit is available on the Easynet in the form of a self-extracting
archive file.  The file is available at this location:

    DECnet nodes:    DECALP::        (48.608)
                     TALER::         (2.865)
    Kit Location:

        Directory:  RTR$KITS:[RTRV3.NT.INTEL]
        Filename:   RTR_126I.EXE

        Directory:  RTR$KITS:[RTRV3.NT.ALPHA]
        Filename:   RTR_126A.EXE

Note: When copying this file across the network, be sure to use
the 'image' or 'binary' file transfer option of your file transfer
utility. Copy the file to any convenient directory.

INSTALLATION

	FTP> binary
	200 Type set to I
	FTP> get rtr_126i.exe

To unpack the archive file on Windows NT, simply execute the file:

    C:> rtr_126i

Please refer to the Installation Guide supplied the directory 
[TALER|DECALP}::RTR$KITS:[RTRV3.NT.INTEL] for further instructions.  
(the installation is the same as for Windows 95).


SUMMARY OF FEATURES

  This version is intended for implementation on client nodes
  only, although server and router functionality is included
  for the purpose of testing and debugging applications.

  The RTR Version 2 API routines are supported to facilitate
  the porting of existing applications to the Windows NT platform.

  The ODBC over RTR client for Windows 95 & Windows NT
  is not yet ready, despite the comment in the Release
  Notes.  If you need this feature, please contact
  RTR Engineering.
  
  Please see the Release Notes and Software Product Description
  for more details.  Release Notes may be found in the same
  directory as the kit, under the file names RELNOTES.TXT
  and RELNOTES.PS.

LIMITATIONS

  RTR for Windows NT is designed as a console application.
  Please be aware that logging off the machine will stop
  all RTR processes.

  Remote commands may be sent from Windows NT nodes, and
  Windows NT nodes may be used in SET ENVIRONMENT commands
  and "/NODE=" qualifiers.  This feature requires the
  installation of a remote shell (rsh) daemon for Windows NT,
  which is not supplied with this kit.

  Please see the Release Notes and Software Product Description
  for more details.


KNOWN PROBLEMS

  If you get the %RTR-F-ERRACCNOD error message at the
  RTR command prompt, simply re-type the command.  It should
  work the second time.  If not, contact RTR Engineering.

  Please see the Release Notes and Software Product Description
  for more details.


PROBLEMS CORRECTED

  Please see the Release Notes for more details.


PROBLEM REPORTING

   For problem reporting:
    a. Send mail to the RTR Problem Manager, Jon Lehto at FFRANC::LEHTO.
    b. If you have any rtr log files or pertinent output from
       monitor pictures or RTR show commands, send it to us via E-mail.
    c. Send us as much other information as possible about the
       conditions which caused the failure, pointers to applications
       programs which caused the problem, command sequences, etc.

   Please exercise it. WE WANT YOUR FEEDBACK.



USING THE RTR NOTES CONFERENCE

    Requests for new features, functions or general RTR for Windows NT
    discussions should be submitted in the Notes Conference at
    DECALP::RTRNOTES.  Please note that this notes conference is not an
    official problem reporting channel.


DOCUMENTATION

    The latest postscript versions of the RTR Version V3.1
    documentation can copied from DECALP::RTR$KITS:[DOC.RTR_V31].


***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

    Reliable Transaction Router(TM) (RTR) V3.1C(128) for OpenVMS/Alpha

		RTR31C_128_README.TXT      24-FEB-1997


Reliable Transaction Router(TM) (RTR) is an open client/server middleware
for continuous computing.

RTR Engineering is pleased to announce that RTR V3.1C(128) for
OpenVMS/Alpha is now available.  This release has gone to SSB and can
be ordered through normal channels.  It is provided here for the
convenience of Digital personnel who wish to evaluate this version of RTR.

Please contact RTR Engineering before introducing this version of
RTR in a production environment.  

******************************  IMPORTANT ***********************************
This kit is a Mandatory Update for users of RTR V3.1B(123).  Especially for
those running DECnet on Alpha machines, this update is absolutely necessary.
*****************************************************************************


COPYING THE KIT

The kit is available on the Easynet in the form of a 'PCSI' file
compressed into a self-extracting archive.  The file is available
at the following location:

    DECnet nodes:    DECALP::        (48.608)
                     TALER::         (2.865)
    Kit Location:

        Directory:  RTR$KITS:[RTRV3.VMS.ALPHA]
        Filenames:  RTR31C_128_AXP.EXE

Note: When copying these files across the network, be sure to use
the 'image' or 'binary' file transfer option of your file transfer
utility. Copy the file to any convenient directory.


INSTALLATION

   First, extract the archive by running the executable file:

	$ RUN RTR31C_128_AXP.EXE

   The result will be a file named DEC-AXPVMS-RTR-V0301-C128-1.PCSI 

   To install the PCSI file, you will need to define the logical
   PCSI$SOURCE as the device:[directory] where the kit resides, and
   install it with the Polycenter command "PRODUCT INSTALL RTR".
   It is recommended to install RTR from a fully-privileged SYSTEM
   account.  If you need more information about the options provided,
   please use the "PRODUCT INSTALL/HELP RTR" command.

   Here are some minimum quota requirements which accounts using
   RTR will need:

	BYTLM: at least 80000 (for accounts running RTR applications)
	       at least 150000 (for accounts running the RTR ACP.  This
			may need to be increased to accomodate large
			numbers of application programs and/or users.
			The formula to use is:
				32K + 32K * n
			where 'n' equals the number of application
			processes plus the number of users in the
			ACP's group).

   RTR users require the following Privileges/and or User Rights:

	All users:  NETMBX, TMPMBX, SYSLCK and RTR$INFO(User Right)

	System Manager (that is, the account that starts up
		RTR and creates facilities):  OPER or
		RTR$OPERATOR(User Right)



LIMITATIONS

   The minimum VMS version supported is OpenVMS 6.1 for both VAX
   and Alpha architectures.  RTR is compatible with OpenVMS 7.0
   and 7.1.

   This release supports TCP/IP, and was coded to Digital's UCX
   system-level programming interface.  While UCX is recommended,
   RTR has been shown to work with TCPware from Process Software,
   as well.

   The recommended DECnet/OSI version for those wishing to use the
   DECnet Phase V transport is 6.3-ECO5 or higher.


PROBLEM REPORTING

   For problem reporting:
    a. Send mail to Jon Lehto at FFRANC::LEHTO.
    b. If there is a dump file, set its protection to W:R, and send
       us a pointer to it in your mail.  Do the same for the file
       at SYS$LOGIN:RTR_ERROR.LOG.
    c. Send us as much other information as possible about the
       conditions which caused the failure, pointers to applications
       programs which caused the problem, command sequences, etc.

   Please exercise it. WE WANT YOUR FEEDBACK.


USING THE RTR NOTES CONFERENCE

Requests for new features, functions or general RTR for OpenVMS
discussions should be submitted in the Notes Conference at
DECALP::RTRNOTES.  Please note that this notes conference is not an
official problem reporting channel.


DOCUMENTATION

Release notes are provided in the PCSI file.  More up-to-date versions
will be placed in the RTR$KITS:[RTRV3.VMS.VAX] directory as they
become available.

The latest postscript versions of the RTR Version V3.1C
User Manuals and SPDs can copied from DECALP::RTR$KITS:[DOC.RTR_V31].


***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

    Reliable Transaction Router(TM) (RTR) V3.1C(128) for OpenVMS/VAX

		RTR31C_128_README.TXT      24-FEB-1997


Reliable Transaction Router(TM) (RTR) is an open client/server middleware
for continuous computing.

RTR Engineering is pleased to announce that RTR V3.1C(128) for
OpenVMS/VAX is now available.  This release has gone to SSB and can
be ordered through normal channels.  It is provided here for the
convenience of Digital personnel who wish to evaluate this version of RTR.

Please contact RTR Engineering before introducing this version of
RTR in a production environment.  

******************************  IMPORTANT ***********************************
This kit is a Mandatory Update for users of RTR V3.1B(123).  Especially for
those running DECnet on Alpha machines, this update is absolutely necessary.
*****************************************************************************


COPYING THE KIT

The kit is available on the Easynet in the form of a 'PCSI' file
compressed into a self-extracting archive.  The file is available
at the following location:

    DECnet nodes:    DECALP::        (48.608)
                     TALER::         (2.865)
    Kit Location:

        Directory:  RTR$KITS:[RTRV3.VMS.VAX]
        Filenames:  RTR31C_128_VAX.EXE

Note: When copying these files across the network, be sure to use
the 'image' or 'binary' file transfer option of your file transfer
utility. Copy the file to any convenient directory.


INSTALLATION

   First, extract the archive by running the executable file:

	$ RUN RTR31C_128_VAX.EXE

   The result will be a file named DEC-VAXVMS-RTR-V0301-C128-1.PCSI 

   To install the PCSI file, you will need to define the logical
   PCSI$SOURCE as the device:[directory] where the kit resides, and
   install it with the Polycenter command "PRODUCT INSTALL RTR".
   It is recommended to install RTR from a fully-privileged SYSTEM
   account.  If you need more information about the options provided,
   please use the "PRODUCT INSTALL/HELP RTR" command.

   Here are some minimum quota requirements which accounts using
   RTR will need:

	BYTLM: at least 80000 (for accounts running RTR applications)
	       at least 150000 (for accounts running the RTR ACP.  This
			may need to be increased to accomodate large
			numbers of application programs and/or users.
			The formula to use is:
				32K + 32K * n
			where 'n' equals the number of application
			processes plus the number of users in the
			ACP's group).

   RTR users require the following Privileges/and or User Rights:

	All users:  NETMBX, TMPMBX, SYSLCK and RTR$INFO(User Right)

	System Manager (that is, the account that starts up
		RTR and creates facilities):  OPER or
		RTR$OPERATOR(User Right)



LIMITATIONS

   The minimum VMS version supported is OpenVMS 6.1 for both VAX
   and Alpha architectures.  RTR is compatible with OpenVMS 7.0
   and 7.1.

   This release supports TCP/IP, and was coded to Digital's UCX
   system-level programming interface.  While UCX is recommended,
   RTR has been shown to work with TCPware from Process Software,
   as well.

   The recommended DECnet/OSI version for those wishing to use the
   DECnet Phase V transport is 6.3-ECO5 or higher.


PROBLEM REPORTING

   For problem reporting:
    a. Send mail to Jon Lehto at FFRANC::LEHTO.
    b. If there is a dump file, set its protection to W:R, and send
       us a pointer to it in your mail.  Do the same for the file
       at SYS$LOGIN:RTR_ERROR.LOG.
    c. Send us as much other information as possible about the
       conditions which caused the failure, pointers to applications
       programs which caused the problem, command sequences, etc.

   Please exercise it. WE WANT YOUR FEEDBACK.


USING THE RTR NOTES CONFERENCE

Requests for new features, functions or general RTR for OpenVMS
discussions should be submitted in the Notes Conference at
DECALP::RTRNOTES.  Please note that this notes conference is not an
official problem reporting channel.


DOCUMENTATION

Release notes are provided in the PCSI file.  More up-to-date versions
will be placed in the RTR$KITS:[RTRV3.VMS.VAX] directory as they
become available.

The latest postscript versions of the RTR Version V3.1C
User Manuals and SPDs can copied from DECALP::RTR$KITS:[DOC.RTR_V31].


***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

    Reliable Transaction Router(TM) (RTR) V3.1C(129) for HP-UX

***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********


RTR31C_129_README.TXT      03-MAR-1997

Reliable Transaction Router(TM) (RTR) is an open client/server middleware
for continuous computing.

RTR Engineering is pleased to announce that RTR V3.1C(129) for
Hewlett Packard's HP-UX Operating System is now available.
This is an initial Field Test Release and is presumably not fit for
introduction into a production environment.

***********************************************************************
   This is a limited beta edition of RTR V3.1C for HP-UX.
   WE WANT TO HEAR FROM YOU ABOUT BUGS AND ANY OTHER PROBLEMS that you
   have installing or using the product. Formal Release Notes are not
   yet available, so this file is the best source of information on the
   latest developments.  You will find information below regarding
   where and how to report problems.
***********************************************************************


COPYING THE KIT

The kit is available on the Easynet in the form of a file package
for use with the 'update' command. The file is available at this location:

    DECnet nodes:    DECALP::        (48.608)
                     TALER::         (2.865)
    Kit Location:

        Directory:  RTR$KITS:[RTRV3.HP]
        Filenames:  RTR31c_129.PKG

Note: When copying this file across the network, be sure to use
the 'image' or 'binary' file transfer option of your file transfer
utility. Copy the file to any convenient directory.

INSTALLATION

	FTP> binary
	200 Type set to I
	FTP> get rtr31c_129.pkg


	First, delete any old versions, if any:
	# rmfn -l RTR_312

	Determine the current directory, for example:
	# pwd
	/usr/users/rtrkit

	Use the update command, specifying the full path name
	of the current directory:
	# update -s /usr/users/rtrkit/rtr31c_129.pkg '*'



SUMMARY OF FEATURES

  This version supports full client, server and router functionality.


  
LIMITATIONS

  - TCP/IP is the only network transport currently supported.

  - Remote commands (i.e., those using the /NODE qualifier)
    are not yet fully supported.  (HP uses remsh instead of
    rsh as on the other Unix platforms).


KNOWN PROBLEMS

  - If an RTR ACP process dies by any means other than the RTR STOP RTR
    command, it is highly recommended that you immediately issue the
    RTR STOP RTR command in order to update RTR's shared memory tables.
    Likewise with the RTR Command Server, it is recommended to type
    RTR DISCONNECT SERVER whenever a Command Server dies in an unplanned manner.
    Failure to do so may result in RTR trying to connect to processes
    that no longer exist, which may have undesirable results.



PROBLEMS CORRECTED

  As this is the initial Field Test kit, no problems have been
  reported.


PROBLEM REPORTING

   For problem reporting:
    a. Send mail to Jon Lehto at FFRANC::LEHTO.
    b. If you have any rtr log files or pertinent output from
       monitor pictures or RTR show commands, send it to us via E-mail.
    c. Send us as much other information as possible about the
       conditions which caused the failure, pointers to applications
       programs which caused the problem, command sequences, etc.

   Please exercise it. WE WANT YOUR FEEDBACK.



USING THE RTR NOTES CONFERENCE

    Requests for new features, functions or general RTR for Windows95
    discussions should be submitted in the Notes Conference at
    DECALP::RTRNOTES.  Please note that this notes conference is not an
    official problem reporting channel.


DOCUMENTATION

    The latest postscript versions of the RTR Version V3.1C
    documentation can copied from DECALP::RTR$KITS:[DOC.RTR_V31].


***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

   Reliable Transaction Router(TM) (RTR) V3.1C (129) for Digital UNIX

		RTR31C_129_README.TXT 03-MAR-1997


Reliable Transaction Router(TM) (RTR) provides transactional and fault
tolerant client/server messaging middleware.

RTR Engineering is pleased to announce that RTR V3.1C for Digital UNIX is now
available for copying over the Easynet.  This release has gone to SSB and can
be ordered through normal channels.  It is provided here for the
convenience of Digital personnel who wish to evaluate this version of RTR.
                                

Please use the RTR notesfile to post questions or provide additional 
information.

COPYING THE KIT

The kit is available on the Easynet in the form of a 'tar' file.
The file is available at this location:

    DECnet nodes:    DECALP::        (48.608)
                     TALER::         (2.865)
    Kit Location:

	Directory:  RTR$KITS:[RTRV3.OSF.ALPHA]
	Filenames:  RTR31B_129.TAR

Note: When copying these files across the network, be sure to use
the 'image' or 'binary' file transfer option of your file transfer
utility. Copy the file to any convenient directory.


FTP> bin
200 Type set to I
FTP> get RTR31B_129.TAR rtr31b_129.tar

To unpack the tar file on Digital UNIX:

    # tar -xvf rtr31b_129.tar  


INSTALLATION & IVP

The installation guide is available on the kit directory.
The following are brief installation instructions:-

1) Login or "su" to root. 

2) Make sure RTR is not running using either:-

	# rtr stop rtr
	# rtr disco server

   or


	# ps aux | grep -i rtr
        # kill [PID of any rtr processes]
        


3) See if RTR is installed:

	# setld -i | grep -i rtr

   This displays any installed RTR for example:-

   RTRBASE310                      RTR API & Management Utility
   RTRBASE311      installed       RTR API & Management Utility 
	

4) If any RTR V3.x is present, deinstall it; for example:-

	# setld -d RTRBASE311
    
5) Install this kit:

	# cd [unpacked kit location]	! Point to kit location.
	# setld -l .			! Install the kit from disk
	# setld -v RTRBASE313		! Run the installation
					!  verification procedure.


(*) If you want to deinstall this kit:

	# setld -d RTRBASE313		! Deinstalls the kit.


USING THE RTR NOTES CONFERENCE

Requests for new features, functions or general RTR for Digital UNIX
discussions should be submitted in the Notes Conference at
DECALP::RTRNOTES.  Please note that this notes conference is not an
official problem reporting channel.


DOCUMENTATION

The latest postscript versions of the RTR Version V3.1C
documentation can copied from DECALP::RTR$KITS:[DOC.RTR_V31].


***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

   Reliable Transaction Router(TM) (RTR) V3.1C (129) for Solaris

		RTR31C_129_README.TXT	03-MAR-1996

Reliable Transaction Router(TM) (RTR) provides transactional and fault
tolerant client/server messaging middleware.

RTR Engineering is pleased to announce that RTR V3.1C for Solaris (also
known as Sun OS) is now available for copying over the Easynet.  
This release has gone to SSB and can be ordered through normal channels.
It is provided here for the convenience of Digital personnel who wish to
evaluate this version of RTR.

Please use the RTR notesfile to post questions or provide additional 
information.

COPYING THE KIT

The kit is available on the Easynet in the form of a compressed 'tar' file.
The file is available at this location:

    DECnet nodes:    DECALP::        (48.608)
                     TALER::         (2.865)
    Kit Location:

	Directory:  RTR$KITS:[RTRV3.SUN]
	Filenames:  RTR31C_129_TAR.Z

Note: When copying these files across the network, be sure to use
the 'image' or 'binary' file transfer option of your file transfer
utility. Copy the file to any convenient directory.


FTP> bin
200 Type set to I
FTP> get RTR31C_129_TAR.Z rtr31C_129.tar.Z

To unpack the tar file on Solaris:

    # uncompress rtr31C_129.tar.Z
    # tar -xvf rtr31C_129.tar  


INSTALLATION & IVP

The installation guide is available on the kit directory.
The following are brief installation instructions:-

1) Login or "su" to root. 

2) Make sure RTR is not running using either:-

	# rtr stop rtr
	# rtr disco server

   or


	# ps aux | grep -i rtr
        # kill [PID of any rtr processes]
        


3) See if RTR is installed:

	# pkginfo -l rtr

   This displays any installed RTR for example:-

   PKGINST:  rtr
      NAME:  Reliable Transaction Router
  CATEGORY:  system,middleware
      ARCH:  sun4m
   VERSION:  312
   BASEDIR:  /opt
    VENDOR:  DIGITAL
    PSTAMP:  pianos.zuo.dec.com960614004857
  INSTDATE:  Jun 14 1996 12:51
    STATUS:  completely installed
     FILES:     56 installed pathnames
                10 directories
                 2 executables
                 1 setuid/setgid executables
             17319 blocks used (approx)
 

4) If any RTR V3.x is present, deinstall it; for example:-

	# pkgrm rtr
    
5) Install this kit:

	# cd [unpacked kit location]	! Point to kit location.
	# pkgadd -d pkg			! Install the kit from disk

             o  You can accept the defaults for most questions from the
                pkgadd utility.

             o  When asked for the "base directory" answer /opt.

             o  Ignore any warning about free blocks and answer "y" to the
                attached continue question.
 
6) Running the Installation Verification Procedure

          You may run the IVP separately from the installation procedure
          by typing the following:-

             # cd /opt/rtr/RTR313/examples/rtr
             # env BASEDIR=/opt /opt/rtr/RTR313/examples/rtr/rtr_ivp_osf.sh


(*) If you want to deinstall this kit:

	# pkgrm rtr		! Deinstalls the kit.


(*) It is recommended that you use all the latest patches for your
    Operating System software and for SunLink/DNI (Sun's DECnet
    product) before installing RTR.  Contact Sun Microsystem, Inc.
    for details.


USING THE RTR NOTES CONFERENCE

Requests for new features, functions or general RTR for Solaris
discussions should be submitted in the Notes Conference at
DECALP::RTRNOTES.  Please note that this notes conference is not an
official problem reporting channel.


DOCUMENTATION

The latest postscript versions of the RTR Version V3.1C
documentation can copied from DECALP::RTR$KITS:[DOC.RTR_V31].

[1] Digital, Reliable Transaction Router and the Digital logo are
    trademarks of Digital Equipment Corporation.
[2] Sun[R] and Solaris are registered trademarks and SunOS
    is a trademark of Sun Microsystems, Inc.
 
***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********

   Reliable Transaction Router(TM) (RTR) V3.1C (129) for AIX

		RTR31C_129_README.TXT	13-MAR-1997


Reliable Transaction Router(TM) (RTR) provides transactional and fault
tolerant client/server messaging middleware.

RTR Engineering is pleased to announce that RTR V3.1C for AIX is now
available for copying over the Easynet.  This kit has gone to SSB
and is provided here for the convenience of Digital personnel for
evaluation purposes.  For customers, please order through normal channels.

Please use the RTR notesfile to post questions or provide additional 
information.

COPYING THE KIT

The kit is available on the Easynet in the form of a compressed 'tar' file.
The file is available at this location:

    DECnet nodes:    DECALP::        (48.608)
                     TALER::         (2.865)
    Kit Location:

	Directory:  RTR$KITS:[RTRV3.AIX]
	Filenames:  RTR31C_129_TAR.Z

Note: When copying these files across the network, be sure to use
the 'image' or 'binary' file transfer option of your file transfer
utility. Copy the file to any convenient directory.


FTP> bin
200 Type set to I
FTP> get RTR31C_129_TAR.Z rtr31c_129.tar.Z

First decompress, then unpack the tar file on AIX:

    # uncompress rtr31c_129.tar.Z
    # tar -xvf rtr31c_129.tar  


INSTALLATION & IVP

The installation guide is available on the kit directory.
The following are brief installation instructions:-

1) Login or "su" to root. 

2) Make sure RTR is not running using either:-

	# rtr stop rtr
	# rtr disco server

   or


	# ps aux | grep -i rtr
        # kill [PID of any rtr processes]
        


3) See if RTR is installed:

	# ls /usr/bin/rtr  ( or use SMIT )


4) If any RTR V3.x is present, deinstall it; for example:-

	# smit install_remove  (SOFTWARE name is "RTR312")
    
5) Install this kit:

	# cd [unpacked kit location]	! Point to kit location.
	# smit install_latest		! Install the kit from disk


(*) If you want to deinstall this kit:

	# smit install_remove   (SOFTWARE name is RTR312) ! Deinstalls the kit.


USING THE RTR NOTES CONFERENCE

Requests for new features, functions or general RTR for AIX
discussions should be submitted in the Notes Conference at
DECALP::RTRNOTES.  Please note that this notes conference is not an
official problem reporting channel.


DOCUMENTATION

The latest postscript versions of the RTR Version V3.1C
documentation can copied from DECALP::RTR$KITS:[DOC.RTR_V31].


***********  D I G I T A L  I N T E R N A L  U S E  O N L Y  ***********