Title: | POLYCENTER Console Manager |
Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
Moderator: | CSC32::BUTTERWORTH |
Created: | Thu Aug 06 1992 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1541 |
Total number of notes: | 6564 |
Hi, This note is cross-posted in the VCS notesfile entry 2014. I have some implementation questions about VCS 1.4. 1) When doing VCS RECONFIGURE you get some message in the default WINDOW 'VCS system has been reconfigured' . To avoid receiving this messages, you delete the default event *, create other events via VCS EDIT NOTI etc... Suppose, you don't want a event * but still having a VCS RECONFIGURE messages in another window. For instance, DCint and OSCint gave the opportunity to activate different windows (OPER,SECURITY,SUPERVISOR,HARDWARE,...) Is it possible to redirect the VCS RECONFIGURE message to the window SUPERVISOR ? 2) Talking about DCint, OSCint and different windows. I know you have one WINDOW resource file per node, namely VCS$ENS_WINDOW_<node>.DAT But is it still not possible to have multiple WINDOW resource file per node ? The reason I asked it that somebody thought he heard saying that it's possible. This should be very interesting when you have for instance a resource file per event (OPER,SECURITY,HARDWARE,...) Any advise is welcome, Geert PS I will post this note in the console manager notesfile to. If it's not already there, it is interested to put it on the wishlist for our OSC platform.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
76.1 | Console Manager already does it all!!! | OPG::PHILIP | And through the square window... | Wed May 12 1993 16:33 | 45 |
Geert, >> 1) When doing VCS RECONFIGURE you get some message in the >> default WINDOW 'VCS system has been reconfigured' . >> To avoid receiving this messages, you delete the >> default event *, create other events via VCS EDIT NOTI etc... >> Suppose, you don't want a event * but still having a >> VCS RECONFIGURE messages in another window. For instance, >> DCint and OSCint gave the opportunity to activate different >> windows (OPER,SECURITY,SUPERVISOR,HARDWARE,...) Is it possible >> to redirect the VCS RECONFIGURE message to the window SUPERVISOR ? Yes, you can do this in Console Manager V1.0, you can even change the events priority if you want! For VCS, I think you can do this if you know the event name for the reconfigure event, this is a number for the VCS reserved events, although I dont know what it is off the top of my head. >> 2) Talking about DCint, OSCint and different windows. I know you >> have one WINDOW resource file per node, namely >> VCS$ENS_WINDOW_<node>.DAT >> But is it still not possible to have multiple WINDOW >> resource file per node ? The reason I asked it that somebody >> thought he heard saying that it's possible. >> This should be very interesting when you have for instance >> a resource file per event (OPER,SECURITY,HARDWARE,...) In Console Manager V1.0 the eventlist window creates a resource file on the Console Manager host system for each remote display a different file is used based upon server, screen and display name, so for instance if you display the eventlist to screen 0 and 1 of a dual headed workstation, they both use different resource files, which will be different again if the eventlist is displayed to a second workstation. For VCS, you are stuck with using the resource file on the remote X-Windows server. I hope this helps you. Cheers, Phil | |||||
76.2 | WOTVAX::ELLISM | Are you all sitting too comfybold square on your botty? - Then w | Thu May 13 1993 14:38 | 7 | |
about the resource file name sfor VCS. If your windows usin different executables. I.e. you copy the WINDOW executable, to say STORAGE, the the resource file name does change, and you can have different resources for different event classes. Martin | |||||
76.3 | Same resource file | OPG::PHILIP | And through the square window... | Thu May 13 1993 15:04 | 11 |
Martin, It will use the same resource file, it is coded to do this we have no plans to change it for the next release. Why would you want to copy the action routine executables to a different name? just create a new action definition in the database which calls cm_eventlist. Cheers, Phil | |||||
76.4 | WOTVAX::ELLISM | Are you all sitting too comfybold square on your botty? - Then w | Fri May 14 1993 11:31 | 5 | |
Phil, I was refering to VCS Martin | |||||
76.5 | OPG::PHILIP | And through the square window... | Fri May 14 1993 18:09 | 6 | |
Martin, Ok, sorry if I confused anyone. Cheers, Phil | |||||
76.6 | OSCint | BACHUS::WILLEMSG | Mon May 17 1993 16:53 | 4 | |
Apparently it's possible to do it via OSCint. (see OSC notesfile) Geert | |||||
76.7 | WOTVAX::ELLISM | Are you all sitting too comfybold square on your botty? - Then w | Fri May 21 1993 12:04 | 7 | |
Geert, you don't need OSCint to do it. All they do is actually rename the executables and create the actions in the ENS database for you. Believe me, I know - that's how we did it in DCINT before VCS V1.4 Martin | |||||
76.8 | resource files | BACHUS::WILLEMSG | Tue May 25 1993 10:46 | 8 | |
Martin, Yep. Thanks for the feedback. Geert |