Subject: | |
From: | |
Reply To: | |
Date: | Wed, 29 Mar 1995 07:35:07 GMT |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
[This note has been sent to the following InterNet address(es):
[log in to unmask]
it has also been sent to the following JP Morgan address(es) :
To : SSWPROD.OAS@TRSSW
]
On Tue, 28 Mar 1995 14:11:00 PST Ken Sletten - Code 331A said:
>Jeff wrote after HP wrote:
>>>2. Choose one: you would prefer to control this feature
>>> via sysgen or online via a command.
>>Given current sysgen methodology I would prefer online via a command,
>>else I'll have to reboot to set it. Anything to save reboots.
>
>Our site concurs with Jeff's comments. Especially the "Anything
>to save reboots" part. I.e: even if something is changed only
>rarely, unless there is some technical reason that it needs to be in
>SYSGEN, then SYSGEN - NOT.......
This seems to me to be another case where a Global Variable (like HPSYSNAME)
could be
set by ONLY the System Manager (perhaps with its own password also) so that
this kind of switch
could be toggled _without_ rebooting the whole system.
This kind of facility seems to becoming a necessity on the system and along
with it the need for a sort
of "WORM" (Write once, Read many) global variable/register-like facility (as a
non-destructive alternative
to message files) which would allow multiple users to receive some data set by
a separate process and
would save a considerable amount of CI programming among other things.
Any comments ?
Cheers,
John Dunlop ([log in to unmask])
|
|
|