[Info-vax] Bliss was Re: Learning VMS application programming

Jan-Erik Soderholm jan-erik.soderholm at telia.com
Sat Sep 13 17:58:44 EDT 2014


JF Mezei wrote 2014-09-13 19:40:
> On 14-09-13 06:48, Jan-Erik Soderholm wrote:
>
>> Define "market".
>> An OpenVMS desktop market? No.
>> A (real) market asking for an OpenVMS browser? Probably no.
>
>
> If  VMS itself moves to browser based management interfaces, then it
> must have a browser so you can manage the machine within the machine.

*OF COURSE* you expect to manage it from your normal desktop environment.
The whole point of adding a web based management is to lift it out of
the server environment to your normal desktop environment.

For basic setup (install and first network config), you can still
use the old server tools available.

> (consider when you reconfigure the network stack, you may wish to do
> this locally without using the network).
>

And how are you going to run the browser "localy" without a network?
Through the consol port?

> In other words, the browser shouldn't be seen as a desktop market thing,
> but rather as a tool required to manage your systems.
>

If web based management in it self whould require a local
web browser, then we can just stay with the old tools.

> One can argue that systems management can be done from a desktop and
> that the VMS servers need not have their own browsers. This philosophy
> has been used for network gear. But note that while CISCO has been
> pushing ackward web based management, serous network managers stll use
> text based config files, and telnet/ssh access to switches to do command
> line management, as well as stuff like SNMP.
>

Exactly.
That is probably true for many systems.
Why would VMS be any different?

The web based interface is an option for the daily management duties.





More information about the Info-vax mailing list