[Info-vax] Changing SMTP server presented hostname in UCX

[Bill Gunshannon]

In article <lunjit$6jc$1 at dont-email.me>,
	David Froble <davef at tsoft-inc.com> writes:
> Simon Clubley wrote:
> 
>> Like I said yesterday, the Unix approach of using text configuration
>> files looks very appealing when compared to a half baked interface to
>> a binary database.
> 
> Well it's not just the "Unix approach".  I have text files such as:
> 
> $ ! Define printer forms types
> $
> $ define/form/width=132/length=66/notruncate/nowrap/margin=(BOTTOM=3) 
> DEFAULT 0
> $ define/form/width=96/length=66/notruncate/nowrap/margin=(BOTTOM=3) WP 98
> $ define/form/width=80/length=66/notruncate/nowrap/margin=(BOTTOM=3) DFE 99
> $
> AS800> t sys$manager:queues.com
> $! Start system queues
> $
> $ start /queue /manager
> $
> $
> $! Define form numbers
> $
> $ @SYS$MANAGER:FORMS
> $
> $
> $ initialize -
>          / queue -
>          / start -
>          / batch -
>          / job_limit=4 -
>          / base_priority=3 -
>          / wsdefault=300 -
>          / wsquota=500 -
>          / wsextent=1500 -
>          / cpudefault=INFINITE -
>          / cpumaximum=INFINITE -
>          SYS$BATCH
> $
> $ initialize -
>          / queue -
>          / start -
>          / batch -
>          / job_limit=4 -
>          / base_priority=3 -
>          / wsdefault=300 -
>          / wsquota=500 -
>          / wsextent=1500 -
>          / cpudefault=INFINITE -
>          / cpumaximum=INFINITE -
>          SY_BATCH
> 
> I consider the mod way back where, once a queue was set up, in 
> subsequent re-boots of the system, re-defining the queues was not 
> required, to be a big mistake.  Sooner or later, it's not "if" but 
> "when",  something is going to get screwed up, and nobody will know what 
> to do to fix it.  With the text files being used on every re-boot, 
> that's a test of the commands, and unless you lose the text files, you 
> always have a reference on how queues and such are set up.  I've had 
> customers print the text files and keep them in a folder.
> 
> Tell me it's "too hard" for some sys admins.  I ain't listening ....
> 
> 
>> If VSI want to sell systems to new non-existing VMS customers, it's
>> going to have to produce something a lot better than this current
>> mess. You should not have to shut everything down and reboot the
>> system just to update the TCP/IP hostname (which is clearly what
>> the intended usage model here is.)
> 
> I think we all acknowledge that TCP/IP on VMS could use lots of work, or 
> a total re-design and re-write.

Or just use MultiNet.  I always found that to be a great product.

bill

-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
billg999 at cs.scranton.edu |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>