Jeff Vance writes:
> If this was DOS or UNIX cases 1 and 4 should appear as:
>
> 2  COPY a,b      <-- if b is a dir you get ./b/A, if b does not exist you get
>                      a file named b.  For B to name a group you would need to
>                      use /ACCT/B.
> 4  COPY a,./dir  <-- if ./dir is a directory you get ./dir/A, if ./dir does
>                      not exist you get a file named ./dir as a copy of a
>
> My purpose is to make it clearer when reading scripts or JCL what the
> copy command is doing.  This comes at the cost of being inconsistent with
> two extremely popular operating systems.
>
> My question to you is do you prefer consistency with DOS and UNIX, or do
> you prefer the CI to force upon you a rule that makes the COPY command more
> evident?

I prefer the Unix interpretation, especially in case #4, because one of the
benefits to HFS names is making MPE *more* Unix-like.  If you're porting from
Unix to MPE, you will want case #4, because you're used to doing "cp a dir" all
of the time on Unix.
--
Mark Bixby                      E-mail: [log in to unmask]
Coast Community College Dist.   Web: http://www.cccd.edu/~markb/
District Information Services   1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support               +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)