On Thu, 7 May 2020 11:28:04 -0500, Lionel B Dyck wrote:
>The answer on how the aliases are maintained is unknown but this is what the
>man page says (below). I did test it and using -X and -I works in both
>directions. There are no additional files in the USS directory so perhaps they
>are including the z/OS PDS directory info along with the load module in the
>USS file so that they can 'restore' it properly since there is meaningful info
>in the directory which would have the alias info, among other things.
>
I'm confident that cp uses Program Management services for
program objects in PDSE. But a binary copy such as cat with
following chmod suffices for zFS to zFS.
Long ago I used Binder to relink an object with alias from PDSE
to hfs, then from hfs to PDSE. The aliases were restored. And in
another experiment, I created an object with aliases in hfs. The
aliases appeared as "additional files". I didn't try executing them.
>What it doesn't do is tag the file in USS as binary (imho it should).
>
Does it make a difference? What mode bits does it set?
'
>======================================================================
>-X
>
> Specifies that the data to be copied is an executable. Cannot be used
>
> with -F, -T, or -B.
>
>
>-I (UNIX to MVS only)
>
> When the specified file has an alias and the file is copied from UNIX
>
> to MVS, the alias information is also copied.
>
>
>
> Restriction: The -I option can only be used with the -X option.
>
>
>
> Attention: If the -I option is specified when the data set that is
>
> copied from MVS to z/OS UNIX does not have an alias, that option is
>
> ignored.
>
Why should this be documented as a special case ("Attention")? It's not
special if the test is performed at the top of the loop rather than at the
bottom.
>=======================================================================
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
