T.R | Title | User | Personal Name | Date | Lines |
---|
2.1 | Documentation in .TXT Format? | SUBWAY::BAUER | Evan Bauer, DBS Tech Support, NY | Sat Dec 23 1989 02:10 | 9 |
2.2 | .TXT versions now available | DECALP::CROSBY | for it is he | Sun Dec 24 1989 21:59 | 10 |
2.3 | Thank You | SUBWAY::BAUER | Evan Bauer, DBS Tech Support, NY | Thu Dec 28 1989 23:25 | 3 |
2.4 | DECwindows bookreader? | OSLACT::OLAV | Do it in parallel! | Fri Jan 05 1990 11:37 | 4 |
2.5 | Not yet planned | DECALP::DESHMUKH | Dipankar Deshmukh, Zurich | Fri Jan 05 1990 16:33 | 10 |
2.6 | | 35154::RABAHY | dtn 471-5160 | Wed Feb 28 1990 05:29 | 1 |
2.7 | | DECALP::SHRAGER | | Mon Mar 12 1990 16:37 | 15 |
2.8 | V1.1-1 kit & documentation is on DECALP::RTR$KITS:[RTRU1011] | DECALP::DESHMUKH | Dipankar Deshmukh, Zurich | Wed Oct 09 1991 16:23 | 0 |
2.9 | All kits location as of Feb 93 | TPVON::VON | Gregg von Sternberg - RTR/SFT Engineering | Wed Feb 24 1993 00:41 | 28 |
2.10 | Need More info on Network Objects | 9886::ONEILL | | Thu Apr 01 1993 23:39 | 14 |
2.11 | RTR usage of network objects | DECALP::DESHMUKH | Dipankar Deshmukh, Zurich | Fri Apr 02 1993 18:49 | 22 |
2.12 | More questions on the TASK 0 object. | 9886::BRUSSEAU | | Sat Apr 03 1993 03:36 | 24 |
2.13 | Yes, an RTR object can be defined, and TASK removed | YAMAN::CROSBY | spaetsuender | Wed Apr 07 1993 02:49 | 50 |
2.14 | Hmmm. Network Object Unknown error... | 9886::BRUSSEAU | | Wed Apr 07 1993 21:29 | 15 |
2.15 | This is odd, it works for me! | DECALP::CROSBY | spaetsuender | Thu Apr 08 1993 15:15 | 10 |
2.16 | I copied it incorrectly... | 9886::BRUSSEAU | | Thu Apr 08 1993 21:36 | 11 |
2.17 | It was a misspelling after all.... | 9886::BRUSSEAU | | Wed Apr 14 1993 01:47 | 10 |
2.18 | Can't find directory | 57852::KISER | | Tue Sep 07 1993 22:53 | 14 |
2.19 | Field Test 2 of RTR V2.1 is now available | TALER::DESHMUKH | Dipankar Deshmukh, Zurich | Wed Sep 08 1993 19:58 | 14 |
2.20 | RTR V2.1 kit available (official release) | TALER::ROGERS | | Wed Nov 17 1993 04:49 | 19 |
2.21 | RTR V2.1 PATCH01 Kit Availability | TALER::ROGERS | | Thu Nov 18 1993 02:16 | 49 |
2.22 | problem with install in rtrw11t3.zip | 11770::BJORGENSEN | | Wed Dec 01 1993 19:29 | 17 |
2.23 | RTR Remote Client MS-Windows Install | LENK::PULLEN | | Thu Dec 02 1993 11:34 | 35 |
2.24 | RTR V2.2 FT1 available | TALER::BANERJEE | | Wed Jan 19 1994 00:17 | 17 |
2.25 | RTR V2.2 FT1 docs available | LENK::ANDERS | Steve Anders, RTR Eng. Zurich | Wed Jan 19 1994 17:47 | 19 |
2.26 | FT2 of RTR V2.2 now available | TALER::BANERJEE | | Sat Feb 19 1994 01:22 | 29 |
2.27 | V2.2 SSB kit details will be tracked under note 469.* | TALER::DESHMUKH | Dipankar Deshmukh, RTR (US) Engg | Tue Apr 12 1994 02:12 | 31 |
2.28 | V3.1 (15) for Windows NT - Field test kit location | TALER::DESHMUKH | Dipankar Deshmukh, RTR (US) Engg | Tue May 02 1995 23:59 | 58 |
2.29 | V3.1 Front-end for Windows 3.1 - Field test kit location | TALER::GAISFORD | Phil Gaisford, RTR Eng., DTN 381 0790 | Wed Nov 15 1995 21:10 | 9 |
2.30 | V3.1 Front-end for Windows 3.1 - Field test 2 kit location | TALER::GAISFORD | Phil Gaisford, RTR Eng., DTN 381 0790 | Tue Jan 16 1996 02:01 | 164 |
2.31 | V3.1 for AIX - Field test kit location | DECALP::SMITH | | Thu Feb 01 1996 14:31 | 10 |
2.32 | ECO-1 for RTR V2.2D is now available | TALER::DESHMUKH | Dipankar Deshmukh, RTR (US) Engg | Tue Feb 20 1996 21:12 | 75 |
2.33 | RTR V3.1A for VMS/VAX Beta available | TALER::CAMPBELL | | Fri Mar 15 1996 10:44 | 9 |
2.34 | ECO-2 for RTR V2.2D is now available | TALER::LEHTO | | Wed Apr 03 1996 02:23 | 64 |
2.35 | Kits protected against access | GIDDAY::PARSONS | Sys & Net Mgt on WNT Support | Mon May 06 1996 07:18 | 8 |
2.36 | RE: Kits protected against access | TALER::WROBEL | Stan Wrobel | Thu May 09 1996 21:18 | 17 |
2.37 | Kits protected against access? | RDDAWG::P_COLE | | Tue May 21 1996 01:39 | 4 |
2.38 | Protections changed. | DECALP::ANDERS | Steve Anders, RTR Eng. Zurich | Tue May 21 1996 14:49 | 4 |
2.39 | ECO kit access limitation | TALER::LEHTO | | Tue May 21 1996 21:10 | 11 |
2.40 | RTR V3.1B (91) for Digital Unix is now available | DECALP::WROBEL | Stan Wrobel | Sat May 25 1996 02:29 | 104 |
2.41 | RTR V2.2D ECO3 kit is now available. | TALER::LEHTO | | Mon Jun 03 1996 21:43 | 92 |
2.42 | RTR V3.1B (96) for Digital Unix is now available | TALER::WROBEL | Stan Wrobel | Mon Jun 17 1996 23:34 | 104 |
2.43 | RTR V3.1B (96) for Solaris is now available | TALER::WROBEL | Stan Wrobel | Tue Jun 18 1996 01:10 | 141 |
2.44 | RTR V3.1B (100) FT for OpenVMS/Alpha is now available | TALER::WROBEL | Stan Wrobel | Mon Jun 24 1996 22:05 | 138 |
2.45 | RTR V3.1B (100) FT for OpenVMS/VAX is now available | TALER::WROBEL | Stan Wrobel | Mon Jun 24 1996 22:10 | 138 |
2.46 | RTR V3.1B(98) for AIX is now available | TALER::WROBEL | Stan Wrobel | Sat Jul 13 1996 04:09 | 97 |
2.47 | RTR 3.!B(103) for Windows 3.1 and Windows for Workgroups 3.11 is now available | TALER::WROBEL | Stan Wrobel | Fri Aug 09 1996 01:15 | 81 |
2.48 | RTR 3.1B(106) Field Test for VAX/VMS is now available | TALER::WROBEL | Stan Wrobel | Thu Sep 12 1996 03:59 | 203 |
2.49 | RTR 3.1B(106) for Alpha/VMS is now available | TALER::WROBEL | Stan Wrobel | Thu Sep 12 1996 04:01 | 202 |
2.50 | RTR V3.1B(111) FT5 for Alpha/VMS is now available | TALER::WROBEL | Stan Wrobel | Tue Oct 01 1996 21:30 | 256 |
2.51 | RTR V3.1B(111) FT5 for VAX/VMS is now available | TALER::WROBEL | Stan Wrobel | Tue Oct 01 1996 21:42 | 254 |
2.52 | RTR V3.1B(109) FT1 for Windows 95 is now available | TALER::WROBEL | Stan Wrobel | Thu Oct 03 1996 04:06 | 125 |
2.53 | RTR V3.1B(104) for Windows NT is now available | TALER::WROBEL | Stan Wrobel | Fri Oct 04 1996 22:35 | 60 |
2.54 | RTR V3.1B(114) FT for OpenVMS Alpha is now available | TALER::WROBEL | Stan Wrobel | Tue Oct 15 1996 03:28 | 228 |
2.55 | RTR V3.1B(114) FT for OpenVMS VAX is now available | TALER::WROBEL | Stan Wrobel | Tue Oct 15 1996 03:32 | 228 |
2.56 | RTRV3.1B(123) for OpenVMS VAX is now available | TALER::WROBEL | Stan Wrobel | Thu Dec 05 1996 03:14 | 124 |
2.57 | RTRV3.1B(123) for OpenVMS/Alpha is now available | TALER::WROBEL | Stan Wrobel | Thu Dec 05 1996 03:17 | 126 |
2.58 | RTR V2.2D ECO4 kit is now available | TALER::LEHTO | | Tue Dec 24 1996 02:04 | 110 |
2.59 | RTR V3.1C for Windows 95 & Windows NT is now available | TALER::WROBEL | Stan Wrobel | Thu Feb 06 1997 03:18 | 144 |
2.60 | RTR V3.1C for Windows NT is now available | TALER::WROBEL | Stan Wrobel | Sat Feb 08 1997 00:26 | 146 |
2.61 | RTR V3.1C for OpenVMS/VAX is now available | TALER::WROBEL | Stan Wrobel | Tue Feb 25 1997 02:47 | 0 |
2.62 | RTR V3.1C(128) for OpenVMS/Alpha is now available | DECALP::WROBEL | Stan Wrobel | Tue Feb 25 1997 02:52 | 130 |
| *********** 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 ***********
|
2.63 | RTR V3.1C(128) for OpenVMS/VAX is now available | DECALP::WROBEL | Stan Wrobel | Tue Feb 25 1997 02:54 | 130 |
| *********** 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 ***********
|
2.64 | RTR V3.1C on HP-UX is now available - Initial Field Test Release | TALER::WROBEL | Stan Wrobel | Tue Mar 04 1997 00:09 | 125 |
| *********** 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 ***********
|
2.65 | RTR V3.1C on Digital Unix is now available | TALER::WROBEL | Stan Wrobel | Tue Mar 04 1997 00:11 | 108 |
|
*********** 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 ***********
|
2.66 | RTR V3.1C for SunOS/Solaris is now available | TALER::WROBEL | Stan Wrobel | Tue Mar 04 1997 00:12 | 145 |
|
*********** 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 ***********
|
2.67 | RTRV3.1C for AIX is now available | SFRANC::WROBEL | Stan Wrobel | Fri Mar 14 1997 03:54 | 101 |
|
*********** 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 ***********
|