[Info-vax] File Protection issue - one more try

[Jan-Erik Soderholm]

samizahra wrote 2011-02-10 23:55:
> The user account login.com has this line:
>              $ set protection=(g:rwed,w:re)/default
>
> I use edit and create a new file FILE_TEST.COM
> the protection on this file will be:
>               FILE_TEST.COM;1      [GRP1500,DPS]
> (RWED,RWED,RWED,RE)
>
> Then the same user account will submit a batch job:
>                submit/queue=SMASH$KICKOFF$BATCH -
>                            /name="testing File prot.." -
>                            /log=IMOACT:[DPS]FILE_TEST.log -
>                                              IMOACT:[DPS]FILE_TEST.Com
>
> The protection on the log file FILE_TEST.log is:
>                FILE_TEST.LOG;1      [GRP1500,DPS]
> (RWED,RWED,RE,)
>
>
> My question is:
>
> why the batch job creates the log file without world protection?
> How can I force the batch job to create log file with this protection
> (RWED,RWED,RWED,RE)
>
> Sami

When the "set prot" command is executed, as part of the login
process, the log file has already been created ! The command
in the login.com files is "to late", so to speak.

Just doing "set protection=(....)/default" does *not* change
the protaction of already existing files !

An ACL on the IMOACT:[000000]DPS.DIR file with a "option:default"
option would probably solve your problem.

You could also have some other process (such as a separate
batch job submitted at the end of the FILE_TEST.Com file)
that only set the protection on the actual log file. Or some
batch job runed regulary that does that ? Or...