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

[Jan-Erik Soderholm]

Simon Clubley wrote 2014-09-10 14:01:
> On 2014-09-10, Jan-Erik Soderholm <jan-erik.soderholm at telia.com> wrote:
>> David Froble wrote 2014-09-10 09:42:
>>>
>>> Well, I don't know, which is why I'd want to find out what happened before
>>> letting anything just run.  But that's just the way I am ..
>>
>> If I do a planned re-boot, I definitely do now want to lose
>> all pending/timed batch jobs! And there is no reason to "find
>> out" anything if I did the re-boot myself...
>>
>> And also, it would be a real mess if someone lost tens of
>> printouts for a stalled printer ("paper out", or similar)
>> just becuse of a re-boot.
>>
>> No, the only practical way is of course to let the queue
>> database, including all queues and entries, survive a re-boot.
>>
>
> What I've setup the backup procedures to do every night is to
> have the command procedure dump the queues, entries, and other
> details to text files which then get backed up as part of the
> backup routine.
>
> This gives me a reasonably up to date view of the queue configuration
> in human readable format which can be used to recreate the configuration
> if the queue manager database is corrupted for some reason.
>
> Simon.
>

Nice, of course. But do you also expect your queues to
be empty (even non-existant) simply becuse a reboot?
That was the question here.

And anyway, all our queue definitions are in the startup
sequence and everything *would* be created from scratch
if they should disapear for some reason.

Yes, we do get some "changes not made to running queue"
or similar messages, but that is a non-issue.

Loosing all entries after a reboot would be
a serious issue... :-)

Jan-Erik.