home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!caen!sol.ctr.columbia.edu!mary.fordham.edu!bdowning
- From: bdowning@mary.fordham.edu (Brian Downing)
- Subject: Re: RECALL/OUTPUT=filename (supplement)
- Organization: Fordham University
- References: <0096067B.0FC65A80.27950@swdev.si.com>
- Message-ID: <11SEP199207512134@mary.fordham.edu>
- News-Software: VAX/VMS VNEWS 1.41
- Sender: news@ctr.columbia.edu (The Daily Lose)
- Date: Fri, 11 Sep 1992 11:51:00 GMT
- X-Posted-From: mary.fordham.edu
- X-Posted-Through: sol.ctr.columbia.edu
- Lines: 29
-
- In article <0096067B.0FC65A80.27950@swdev.si.com>, tillman@swdev.si.com ("Brian Tillman, Smiths Industries, VAX Support, x8425") writes...
- >Brian Downing (bdowning@mary.fordham.edu) writes:
- >
- >> Try $ DEFINE/EXECUTIVE SYS$OUTPUT filename
- >> $ RECALL/ALL
- >> $ DEASSIGN SYS$OUTPUT
- >>
- >>That works for me. $ SHOW LOGICAL/PROCESS SYS$OUTPUT
- >>shows that SYS$OUTPUT is defined for both supervisory and executive modes.
- >
- >This only works for you because you have SYSNAM privilege, perhaps.
- >DEFINE/EXECUTIVE_MODE is allowed only if you have SYSNAM. It is converted to
- >/SUPERVISOR_MODE if you do not have SYSNAM.
-
- I've been told by a few users that I missed the mark. The original user
- wanted access to recall info from within a command procedure. Anyway, I
- don't have SYSNAM privs either so, the executive stuff is erroneus. It
- probably was defaulting to super anyhow. I was too quick to reply to the
- post.
-
- Sorry for the wasted bandwidth, and thanks to those few VMS wizards
- who set aside time from their very busy days to write me and let me know.
-
- ;^)
-
- Brian Downing VAX User Assistant, Fordham University, New York, New York
- Internet: bdowning@mary.fordham.edu Bitnet: bdowning@fordmulc.bitnet
- void random_witticism(char *, ... ) { ... }
-
-