| I don't know what the "official" position is, I suspect there isn't
one. But, my preference is to not use fileview, mostly because it is
slow. For customers/users who are DCL literate, I recommend starting
the accessory applications from session manager, and starting one or
more DECterms, with no Fileview. Fileview is useful for those who are
not command-language literate or people who hate typing. Finally, if
Mail, Notes, Calendar, Notepad, etc. are to be started always upon
login, I would consider running them from batch via a command in
DECW$LOGIN, especially since they are to run on the host. Otherwise,
your users are likely to get very bored while waiting to login and
work.
Then again, some would say the "preferred" way is to let the users make
most of these decisions :-).
Barry
|
| >What is the "preferred" way to add or modify applications for the
>non-privileged user, in the Session Manager or in FileView?
I have found the answer to my own question. If I add or modify applications in
the Session Manager, they are saved in the system's copy of
DECW$SM_GENERAL.DAT. However, as soon as a user saves her current settings,
she has her own copy of DECW$SM_GENERAL.DAT in her own directory, and will
never see any furthur additions I make. However, if I offer new applications
through FileView, each user has access to them with each new invocation of
FileView.
So, I have instructed each user to add a RemoteFileView application to her
Session Manager which uses DW_NET to run FileView on the large, CI-based,
fully supported and backed-up host system, and invoke all applications from
there. This way all of the data files associated with each application
(DECwrite, Notepad, Calendar, etc.) are stored in the user's directory on the
host, where they are backed-up. Mail and VAXnotes now run on the host, which is
in DECnet Area 3, instead of on the individual's workstation, which is in
a hidden area, so I avoid all of the problems and disadvantages of poor
man's routing. They can also use FileView to manipulate their files on the
host, where most all of the work is done anyway.
Stephen
|