On Thu, 9 Apr 2015 12:59:35 -0500, Dana Mitchell wrote:
>#
>
>export outzfs="alloc path('/u/tzeke/$3') PATHDISP(KEEP,DELETE)
>PATHOPTS(OWRONLY,OCREAT,OEXCL)\
>PATHMODE(SIRUSR,SIWUSR,SIRGRP,SIWGRP,SIROTH,SIWOTH)"
>
>#
>
>tso -t "OCOPY INDD(INMVS) OUTDD(OUTZFS) TEXT CONVERT(YES) PATHOPTS(USE)"
>
>...
>
>If I look at the file after the OCOPY, permissions are this:
>
>-rw-r--r-- 1 DMITCHE SYS1 281556 Apr 9 12:56 shzbinf
>
>I've tried different combinations of PATHMODEs, and it appears it doesn't let
>me assign update for the group or everyone, any idea what would be
>interfereing with that? PATHMODE coded on DD in JCL seems to work just as
>expected....
>
Could it be umask? What's your umask value? Is umask propagated through
TSO and OCOPY? (JCL presumes umask 000.) Could you just chmod it after
the TSO call? Could you create it before the TSO call (and omit ,OCREAT,OEXCL)?
Does it need to be a shell script? I'm more comfortable with Rexx for this
sort of thing, even Rexx invoked by a shell script. In Rexx I'd use LINKMVS
IEBGENER rather than TSO OCOPY.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
