| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2564.1 | and the name is ... | VNABRW::EHRLICH_K | With the Power & the Glory | Wed Apr 14 1993 16:32 | 11 |
| Hi jeanne,
and the right name for the pak is ... A1-DIST-SHR ...
The license is only need for 'implementing' the DSO (Distributed
Sharing Option).
For further info see the DSO README.TXT file. You can find it in TIMA STARS
or I can copy it to your system, if you like!
Have fun
Charly_from_CSC_Vienna
|
| 2564.2 | Obj 73 is the FCS. No PAK needed | IOSG::SHOVE | Dave Shove -- REO2-G/M6 | Wed Apr 14 1993 17:27 | 8 |
| If you have object 73 on your system, then the File Cab Server is
running. The process name will be node$SRV73
You only need a PAK if you want to have the Distributed Server Option
(DSO) - this is only needed if users on another ALL-IN-1 IOS system
want to be able to access shared drawers on your system.
Dave.
|
| 2564.3 | thanks! | ODIXIE::LAROE | Jeanne LaRoe DTN 385-2926 | Wed Apr 14 1993 18:54 | 5 |
| Thanks for the quick replies! I just want TeamLinks users to be able to
access their IOS file cabinet, so we tried it out and it worked!
Regards,
Jeanne
|
| 2564.4 | You're all set | CHRLIE::HUSTON | | Wed Apr 14 1993 20:11 | 10 |
|
It sounds like the 3.0 documentation is out of date. The two licenses
you mentioned were changed to just the DSO shortly before SSB so it
is possible that the documentation never caught up.
As the other say, the only FCS license is the DSO pak and you only
need that if you want distributed sharing.
--Bob
|
| 2564.5 | History..... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Thu Apr 15 1993 10:50 | 18 |
| Originally, we intended that V3.0 would ship with the distribution
included. Then fairly late on, we found a problem with how distributed
sharing worked, but we fixed it before the kit shipped. However we
weren't (at that stage) happy about the amount of testing we'd done to
include it in the kit. So what we did was leave the code in, but turn
it off with the licence. So the V3.0 kit should have had release notes
that told you to ignore those bits of the doc. set.
Later when we shipped the distributed bit, it turned out that the code
was actually working fine (since we're all very clever engineers :-) )
so all we needed to do was to ship the PAK that turned it on again.
The documentation with the DSO "kit" should have explained the new PAK
name.
Well that was what was supposed to happen anyway....
Graham
|
| 2564.6 | | IOSG::STANDAGE | It's a Burgh kind of thing | Thu Apr 15 1993 10:58 | 14 |
|
>>The documentation with the DSO "kit" should have explained the new
>>PAK name.
The read_me_first that comes with the DSO kit does explain the change
in PAK name, but of course this is not much use for those people with
just V3.0 who are thinking of purchasing the DSO option.
Kevin.
|
| 2564.7 | | CSOA1::LENNIG | Dave (N8JCX), MIG, Cincinnati | Wed May 12 1993 15:05 | 12 |
| Just to clarify things for me, since I was asking about something
similar in a previous note...
Is this DSO PAK required on the source, target or both nodes? That is,
given an IOS system with with lots of docs in my file cabinet, and
another IOS system where I would like to put some/many of them, where
do I need to load this PAK? ie Given a DEC MTS machine where I keep
running up against my document quota and a non-MTS system with IOS
installed that I would like to move things to, does loading the "DSO"
PAK on my non-MTS node allow this??
Dave
|
| 2564.8 | Need it on the "other" system | CHRLIE::HUSTON | | Wed May 12 1993 15:27 | 11 |
|
The DSO allows a FCS to accept connections from other FCS servers.
You do not need the DSO on the node you are logged into. If you want
to store anything or retrieve anything on a different cluster, then
the FCS on that other cluster will need the DSO.
In your case you need it on the non-MTS system.
--bob
|