On Wed, 31 Jul 2019 19:10:49 +0000, Jousma, David wrote:
>Well, in the end, it may not have been so hard to accomplish. I have to run
>compares against the original and SMPE installed jar files, but the gist of it
>is
>
>++ JAR(MAJV831P) /* $java_home/lib/ext/PKKeyM.jar */
> DISTLIB (AAJVHFS)
> SYSLIB (SAJV80M)
> PARM (PATHMODE(0,6,4,4))
> LINK ('../lib/ext/PKKeyM.jar').
>
>Followed by inline by the output of GIMDTS of the transformed jar file read
>from PATH seemed to work.
>____________
I'm curious about how comprehensive SMPE's support of zFS objects is.
For example, does the GIMDTS SYSUT2 reflect the values of extended
(admittedly non-POSIX) attributes such as CCSID and FILEFMT, and are
the restored by the RECEIVE; APPLY sequence? It's a shame if these
valuable (at least to z/OS) metadata are not supported.
ISPF, for example, has good support for combinations such as CCSID=UTF-8
and FILEFMT=RECORD. These matter in text files; less in .jar.
Is there an extended compare utility that compares metadata also?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
