I don't think I would categorize this as a bug. This syntax is consistent
with other MPE commands. The lockword goes with the filename portion of the
file.group.account syntax. RENAME, BUILD, FILE, COPY, (and others I'm sure)
all follow the same syntax.

:file foo=foo.pub/password
                 ^
Invalid character in MPE file name. (CIERR 583)
:file foo=foo/password.pub

Compare this to the syntax for job card:

!job fum,username/USERPASS.account/ACCTPASS,group/GROUPPASS

The parser looks for a lockword or password immediately following the object
it applies to. I grant you that group and account passwords don't apply a
the file level but I thing the syntax is consistent and even expected.

Doug.

Doug Werth                             Beechglen Development Inc.
[log in to unmask]                               Cincinnati, Ohio

----- Original Message -----
From: "Ted Ashton" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, August 09, 2000 17:55 PM
Subject: Re: Rename with lockword


> Thus it was written in the epistle of Michael Berkowitz,
> > It appears that you cannot rename a file in a different group for the
> > purpose of putting on a lockword as the following shows.
> >
> > :BUILD ABC.MS
> > :RENAME ABC.MS,ABC.MS/X
> >                      ^
> > Invalid character in MPE file name. (CIERR 583)
> > :CHGROUP MS
> > :RENAME ABC,ABC/X
> > :
> >
> > Short of going into the group itself, isn't this a bug, probaly related
to
> > POSIX naming.
>
> I would submit that it is, instead, a syntax error.  Give this one a try:
>
> :RENAME ABC.MS,ABC/X.MS
>