| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5895.1 | use a workstation | VFOVAX::GALVIN | Team USA in '94 World Cup! | Tue Mar 08 1994 15:07 | 18 |
| Walt,
You get the old argument about what the SPD *supports* and what is
*tolerable*... I would NOT recommend an X terminal display for MCC,
unless it's just for *show*... If you want to do any IMPM
manipulation, you'll save yourself alot of trouble upfront by getting a
more powerful workstation... I recommend a minimum of a 3100/m76. Put
alot of memory in the beast and put a large pagefile, ie: 1-200k
blocks to make things move...
You haven't shared what the customer's expectations of using the IMPM
are, so I would assume s\he would like to do realtime monitoring...
this is NOT possible with a VXT. The marketing folks might kill me...
but, I've been there... Hope this helps.
/Mic
|
| 5895.2 | the VXT2000+'s are for display | BWTEAL::W_MCGAW | | Thu Mar 10 1994 18:29 | 17 |
| Hi Mic,
The customer is trying to use the VXT2000+'s for "watching" only. He
will be maintaining all of the mcc information on a VS4000-90 and wants
the VXT's to be as operator consoles for different areas. The people
using the VXT's will only be watching for notifications and alarms
occurring. The real problem here is the piece about the mouse. If it
is bumped during initialization of MCC, the map is a mess. If he shuts
down and restarts MCC (without bumping the mouse) it comes up (and
works) fine. This did not happen on vaxstations and I don't believe it
was a problem on vxt2000 or vt1200 displays either.
The customer just wants to know the bottom line... Is he supported on
the VXT2000+ (and happy) or not supported (and fuming) ;-)
Thanks,
Walt
|
| 5895.3 | Works for us! | KAOFS::CARSWELL | | Fri Mar 11 1994 10:28 | 19 |
|
Walt,
We use VXT2000 and VXT2000+ running/displaying MCC Map and Notification
Windows from a VAX 4400 platform, with no problems. The 4400 engine has 96M
of memory and lots of disk space, and the operator workstations(VXT's), create
a X-Session on the 4400. We then initiate a SCHEDULER job that determines the
workstation being run from, SETs DISPLAY, and then MANA/ENTER/INTERF=DECW.
We usually have at least two 'MCC Stations' in operation at a given time,
and have never experienced the problem you are describing.
What version of INFOSERVER software and VXT software is running
on your INFOSERVER.(Assumming thats how you are booting the VXT's). We have
Version 3.0 of the INFOSERVER and 2.1 of the VXT software.
Regards,
Gord C.
|
| 5895.4 | the problem was fixed accidentally | BWTEAL::W_MCGAW | | Fri Mar 11 1994 13:12 | 14 |
| Hi Gord,
Thanks for the response! I called the customer back to follow up on
the call and found out that he is using V2.2 Infoserver software and
V1.3 VXT software. The good news is that he had received an iconic map
exe file from engineering to fix another open problem he had and it
solved several problems including the one I entered this note for. It
sure would be nice to have actual CSCPAT_nnnn patches from MCC
engineering that we could supply to customers instead of having to
escalate. The customer gets the patch from engineering but we are left
out of the loop (fat, dumb but unhappy :-(
Thanks again,
Walt
|
| 5895.5 | | SCCA::dave | Ahh, but fortunately, I have the key to escape reality. | Fri Mar 11 1994 18:42 | 1 |
| CSCPAT numbers are from the CSC, not Engineering.
|
| 5895.6 | regarding CSCPAT numbers | BWTEAL::W_MCGAW | | Mon Mar 14 1994 12:01 | 9 |
| re: .5
This is true... but from what I understand, the CSC can not assign
CSCPAT numbers to a patch unless it is delivered through the
appropriate channels and has met all of the criteria for becoming a
fully distributable patch.
Thanks,
Walt
|