Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!ucbvax!wiscvm.arpa!MANAGER%UMDHEP.BITNET
From: MANAGER%UMDHEP.BITNET@WISCVM.ARPA
Newsgroups: fa.info-vax
Subject: RE:
Message-ID: <8509121413.AA13692@UCB-VAX.ARPA>
Date: Thu, 12-Sep-85 10:25:48 EDT
Article-I.D.: UCB-VAX.8509121413.AA13692
Posted: Thu Sep 12 10:25:48 1985
Date-Received: Fri, 13-Sep-85 04:22:03 EDT
Sender: daemon@ucbvax.ARPA
Reply-To: info-vax@ucb-vax.arpa
Organization: The ARPA Internet
Lines: 23


        It appears I was lacking in the description of my friend's
        problem...

        I already tried the obvious logical name redirection
        techniques BEFORE posting to info-vax. The solution is
        NOT obvious. Performing REPLY/ENABLE can apparently only
        be done with a terminal as the parameter. Any logical name
        I tried that translated to a disk file was not accepted by
        the enable request. REPLY/STATUS sends its output to the
        device that was previously ENABLEd, not to anything like
        SYS$OUTPUT or SYS$COMMAND (I tried).

        I got one response about everything going into OPCOM being
        readable by a program. I haven't messed with unlocking
        locked files, but that seems to be a reasonable technique
        (thanks Ron).

        If anyone comes up with any other suggestions (please try
        them yourself before posting to the net), let me/us know.

        Thanks for all the help so far,
        Todd (and by proxy), Kees