Path: utzoo!attcan!uunet!mcvax!unido!iaoobelix!woerz
From: woerz@iaoobelix.UUCP (Dieter Woerz)
Newsgroups: comp.os.vms
Subject: Re: old prompt question which I never saw answered.
Keywords: DCL Prompt
Message-ID: <212@iaoobelix.UUCP>
Date: 13 Jul 88 23:38:04 GMT
References: <8806280841.AA18214@ucbvax.Berkeley.EDU>
Reply-To: woerz@iaoobelix.UUCP (Dieter Woerz)
Organization: Fraunhofer Institut fuer Arbeitswirtschaft und Organisation
Lines: 29

In article <8806280841.AA18214@ucbvax.Berkeley.EDU> WIZARD@RITA.ACS.WASHINGTON.EDU ("The Bandit . . . ", on RITA) writes:
> ...

>The problem is that VMS tries to be "smart" about issuing prompts.
>If your input and output device specifications are NOT identical, the prompt
>is simply NOT issued.  For you normal interactive session, SYS$INPUT has the
>same translation as SYS$OUTPUT, and so prompts are issued.  For your normal
>batch job, SYS$INPUT <> SYS$OUTPUT, and your batch log file does NOT contain
>the prompts.   There is no reasonable work-around that I know of at this time.

> ...

This is not completely right.
If a prompt is issued, it is always written to the SYS$INPUT. I think
that has todo with reissuing the prompt, when broadcast messages are
written to the terminal. And the prompt is only written, if SYS$INPUT
is a terminal.

------------------------------------------------------------------------------

Dieter Woerz
Fraunhofer Institut fuer Arbeitswirtschaft und Organisation
Abt. 453
Holzgartenstrasse 17
D-7000 Stuttgart 1
W-Germany

BITNET: iaoobel.uucp!woerz@unido.bitnet
UUCP:   ...{uunet!unido, pyramid}!iaoobel!woerz