| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 989.1 | | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Mon May 06 1991 17:31 | 16 |
| We run DECmcc client/server all the time.
Put DECmcc on system "A". Log into system "B". From system
"B" SET HOST "A". Login to system "A". Do a
SET DISPLAY/CREATE/NODE="A"
Use theSession manager pull down menu on system "B" and select
the Security option. Add system "A" and the account you logged
into on system "A".
Now all you have to do is
$ MAN/ENT/INT=DECW
And you'll be running DECmcc on system "A", displaying and
interacting on system "B".
JCE
|
| 989.2 | batch job - instead of set host | MOLAR::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Tue May 07 1991 10:41 | 11 |
| If you VMS license says you can only have two interactive users, then
you can only run two MCC kernels on your server system.
You could submit a batch job to the server - which connects to the
client workstation then runs MCC - as John stated in .1 - Just submit
the job to batch instead of the set host.
DECmcc v2.0 will have distributed capabilities (I do not know when v2.0
is scheduled though).
/keith
|
| 989.3 | re:.0,.1.,.2 | BARREL::LEMMON | | Tue May 07 1991 11:22 | 9 |
| The bottom line here is that the Iconic Map and FCL must be executed
on the same system that MCC is installed on. PMs will not be distributed
in the V1.2 timeframe.
There are mechanisms (like the ones already mentioned) to "pipe" the
iconic map interface to another display but you still need to run them on
the VAXserver.
/Jim
|
| 989.4 | *VERY* high priority for remideal services | CLARID::PATEL | We'll get it right on the night | Fri Jun 28 1991 05:29 | 48 |
| re .1 and .3 (better late than never)
The mechanism in .1 IS NOT RUNNING DECMCC IN CLIENT SERVER MODE (I
THINK) it is using the Xwindows client server capabilities -- which can
be applied to any XWindows based application.
The situation at PEUGOT is MOST DEFINITELY NOT UNIQUE. "We" in the
Service delivery organization have had this requirement for operating
distributed PM for as long as I can remember. The objective is to be
able to run ONE Kernel which serves multiple PM (irrespective of where
they are on the network).... currently the cost to the field of not
having this capability is high, we have in Europe near on 100+ accounts
where we could use this for the delivery of service, sorry to get long
winded but let me explaine....
We have DECmcc Kernel running at the customer site, the AM's are there
too. We then provide a capability to run up a PM at the Service Center
which connects to the Customer site Kernel over a Dial up link (for
those in the know this would be a DSNlink connection), the result being
now we have a PM (ICONIC) running in the CSC depicting what is happening
at the Customer site Graphically without having to have a large bandwidth
connection to transport X packets. Good init.
+-------------+
| Mcc Kernel |
| |
+-------------+
|
|
PSTN Dial up DSNlink (some limitations here
| (we can discus if interested
^
|
+-------------+
| Mcc PM |
| |
+-------------+
CSC
What I understood from the 1.2 requirements was that all major modules
would be implemented in a distributed manner, allowing us to customize
the operation of MCC as above, IS THIS NOT THE CASE. Note this is one
of the features that would enable Digital Services to deliver truly
cost effective services to large numbers of customers.
Your understanding and help in this are would be greatly appreciated.
Amrit Patel
|
| 989.5 | | NSSG::R_SPENCE | Nets don't fail me now... | Mon Jul 01 1991 15:26 | 7 |
| Hmmm, I never read anything for V1.2 that looked like client server.
I think that is for V2.x.
I agree that we need it (I have custemers too that want it) but first
we have to walk before we run.
s/rob
|
| 989.6 | CCan't blame me for trying ;-) | CLARID::PATEL | We'll get it right on the night | Tue Jul 02 1991 04:57 | 14 |
| re .5, agreed this may have been read in. My understanding for 2.x was
to deliver a director to director communications capability. 1.2 to
implement the MM's using RPC so that they can ALL be distributed.
Sorry if I sounded a little off, the main concern I have is that
product requirements for the use of a product in Service Delivery
always seem to get onto the "back burner".
This capability for starting up a process at a customer site that
effectively links to a PM running in DEC, operating with an MCC system
at the customer site -- WOULD really help us to become cost effective.
Amrit
|