home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!wupost!waikato.ac.nz!comp.vuw.ac.nz!zl2tnm!toyunix!don
- Newsgroups: comp.os.vms
- Subject: Re: Detecting directory of invoked .com
- Message-ID: <20541359@zl2tnm.gen.nz>
- From: don@zl2tnm.gen.nz (Don Stokes)
- Date: 25 Dec 92 09:17:56 GMT
- Sender: news@zl2tnm.gen.nz (GNEWS Version 2.0 news poster.)
- References: <1he98mINN1o3@gap.caltech.edu>
- Distribution: world
- Organization: The Wolery
- Lines: 24
-
- carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes:
- > First: You've got no reason to worry about being flamed. You've clearly
- > stated what you want to know, and you're NOT repeating a question that's
- > already been answered for you in the last week or so. If I understand your
- > question correctly (i.e., you want the device, too) then what you want is given
- > by the expression:
- > $ F$ELEMENT(0,"]", F$ENVIRONMENT("PROCEDURE")) + "]"
-
- Ummm, Carl....
-
- (1) That's a lexical, not a command.
- (2) Check out what happens if the command file is invoked by:
-
- $ @[dir1.][dir2]commandfile
- or
- $ @<dir>commandfile
-
- The previous posters' use of f$parse() to get the directory & device is
- the best solution.
-
- --
- Don Stokes, ZL2TNM (DS555) don@zl2tnm.gen.nz (home)
- Network Manager, Computing Services Centre don@vuw.ac.nz (work)
- Victoria University of Wellington, New Zealand +64-4-495-5052
-