On Fri, 13 Nov 2020 07:54:22 -0600, Kirk Wolf wrote:
>
>For more information:
>https://dovetail.com/docs/zos-utilities/dsp-ref_getpds.html
>https://dovetail.com/docs/zos-utilities/dsp-ref_putpds.html
>https://dovetail.com/docs/cozinstall/changes.html
>Co:Z is available free under our Community License
><https://dovetail.com/docs/cozinstall/licenses.html>.
>>
Impressive! But I can still add suggestions:
//DDNAME: format?
-M option, as for /bin/cp to translate "_.-" (Oops! Option name conflict!)
upp[ercase]=y[es]|n[o]
file member names uppercased? (default=no: lower case)
Also "ASIS" for putpds in case UNIX directory contains foobar,
FooBar, and FOOBAR? (Does upp=yes for getpds actually mean
ASIS?)
-l line-separator
nl | cr | lf | crlf | crnl
How about the equivalent of FILEDATA(RECORD) as supported by JCL?
"crnl"? "lfcr"? Damn IBM for conflating LF and NL! (I fear ISVs started it!)
Long member names? I understand PDSE supports long aliases (is that
only for program objects?) I could envision storing long UNIX member
names with generated member names and the original UNIX names
as aliases. Are they simply ignored? Warning? Likewise subdirectories?
Should multiply-linked files be stored as aliases? Which name wins?
(How does ISPF behave when an alias or a member having an alias
is edited?) Should getpds render aliases as (symbolic?) links?
>> >FWIW: It's a pity that the IBM C library doesn't have any support for
>> BLDL/NOTE/POINT processing of PDS/Es -- see my old RFE and vote if you agree:
>> >
>> https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=80811
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
