I wondered about the initial statement saying that the intent was to allow the user access to the HFS file with the usual MPE command set.
I assumed that for MPE file manipulation by the user, the HFS file had to reside in the typical spaces where MPE files normally are in the classic MPE sense. However in the example below, there is a 3rd subdirectory shown thus making file manipulation with MPE slightly outside MPE.
And of course it would probably easier for the user to manipulate the file with MPE, if the files in question only have 8 characters, be in all CAPS, have no file extension, and start with a letter. It could be very well an HFS file but would have the look and feel of an MPE file as far as MPE commands were needed.
I think this was all assumed by all who replied, but not otherwise mentioned.
Tracy Johnson
Office (757) 766-4318
[log in to unmask]
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Lars Appel
Sent: Wednesday, March 27, 2013 2:40 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] access to posix files by a user who didnt create or doesnt own them
John Pitman wrote:
> In the end I am streaming a job that goes to shell then executes a
> script to
>
> Chmod 777 /DIR1/DIR2/dir3/*
Well, something similar to this should also work without an extra job...
:xeq /bin/sh "-c ' chmod 777 /DIR1/DIR2/dir3/* '"
As an alternative to chmod, you should also be able to use the MPE ALTSEC command with the NEWACD (or some related option) to set (or modify) the ACD on the respective files...
e.g. ALTSEC /DIR1/DIR2/dir3/somefile ;NEWACD=(R,W:@.SOMEACCT)
However, I am not sure if ALTSEC allows wildcards for filenames. MPEX may help.
Lars.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
