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

[Jan-Erik Soderholm]

Bill Gunshannon wrote 2014-09-10 16:54:
> In article <lup62n$ae1$1 at news.albasani.net>,
> 	Jan-Erik Soderholm <jan-erik.soderholm at telia.com> writes:
>> David Froble wrote 2014-09-10 09:42:
>>> Jan-Erik Soderholm wrote:
>>>> David Froble wrote 2014-09-09 21:15:
>>>>
>>>>>
>>>>> 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...
>>>>
>>>> Now, if the *queues* does not survive a reboot, what
>>>> would you like to happen with any pending *entries*
>>>> on those queues ?
>>>>
>>>> Jan-Erik.
>>>
>>> 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.
>>
>
> OK, this is a real question from someone who never had to deal with
> VMS print queues.
>
> Is communication with the printer bi-directional?

Can be. Depends on the "driver" on VMS and the printer.
DCPS (Postscript printing) does "talk" to the printer
and can report error status back to VMS (OPERATOR.LOG
or whatever). Is different is you use LAT, telnet or
LPD printing, I would guess. Like:

%%%%%%%%%%%  OPCOM   1-SEP-2014 12:35:09.88  %%%%%%%%%%%
Message from user SYSTEM on HV06
Queue xxxxxx: %DCPS-W-NOT_READY, Printer is not ready



> Does the printer
> send back a signal that the job has finished physically printing?
> If not, based on the amount of memory in many printers today how do
> you deal with all the data for a (one or more!) printjobs that has
> already reached the printer when someone kicks the plug out :-)

The DCPS manual describes this error message:

 > PWRFAIL, The printer power was cycled while a job was active
 >
 > Explanation: Power to the printer was turned off and then
 > on while a job was printing.
 >
 > User Action: Check your print job to see if you need to
 > resubmit it for printing.

Check the DCPS manual, there are a lot of different
messages for all sorts of error status. Now, this
probably only works for the printers in the list
of "supported printers".

The SPD for DCPS says:

"Status and error messages sent to the user’s terminal,
  may be printed on the job trailer page or job log
  page, written to a log file, or displayed on the
  operator’s console."

Jan-Erik.


> bill
>