export file permissions

[Kroboth, Joe]

> -----Original Message-----
> From: filepro-list-bounces+joe_kroboth=chernay.com at lists.celestial.com
> [mailto:filepro-list-
> bounces+joe_kroboth=chernay.com at lists.celestial.com] On Behalf Of
> Kroboth, Joe
> Sent: Thursday, June 17, 2010 3:52 PM
> To: filepro-list at lists.celestial.com
> Subject: RE: export file permissions
> 
> 
> > (assuming you created and used the file all within processing, thus
> the
> > remove() )
> >
> > The point about the different create and remove options is the proper
> > way to create the file depends on what you need to do with it, which
> > you
> > have not disclosed. Also, "umask 0" is possibly unnecessarily
> > permissive. Again, because I don't know what you actually need to do
> > with the file. umask 0 ensures anything and anyone anywhere can do
> > anything to the file, as long as filepro has closed (released it's
> > write
> > lock) on it, which I have included in the example code.
> >
> > --
> > bkw
> 
> Brian,
> 
> Thanks for your detailed instructions. Glad I asked. Seems like you
> have run into this more than a few times :-)
> 
> filePro feature request: Add a way to set the permissions of files
> created with create or open.
> 
> Joe
> 


I found sort of a work around.  I set PFUMASK then used the jsfile to create the file first.



       Then: jsfile "1":cr file_name ; jsfile "1":cr-                          |
 31  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
       | If:                                                                   |
       Then: the_file=create(file_name)                                        |
 32  -------   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -

Seems to work.


Joe