On Thu, 8 Jun 2023 09:58:39 +0000, David Frenzel wrote: > >I can see that z/OS 2.1 received the same certification back in 2013 >(https://www.opengroup.org/openbrand/register/brand3601.htm). >Timothy, are you stating that z/OS 3.1 now has the same certification that 2.1 >has or is this certification for 3.1 implying any changes as to how USS works >and whether anything has been improved from 2.x? > Timothy has been conspicuously quiet on this topic since his initial announcement of UNIX® Certification.
>I just spent hours on an issue where it turned out that some utilities honor >the file tag for code pages while others simply ignore it and use some >hard-coded value. I stopped counting the endless hours of time wasted because >some weird code page issue appeared in USS. Hopefully, nobody is going to >scream "POSIX compliance" at me now.. > That raises nasty questions concerning utilities such as "od" and "cksum" that intuitively seem "binary" or code page independent. Should they be exempt from autoconversion: o always? o never? o depending on (which?) environmental setting? o when the file is tagged binary? What is the effective tagging of pipes? What should od do with a file containing packed decimal data? can shell scripts be tagged? What should happen with: #! /bin/sh -x printf 'π\n' printf 'π\n' | od -to1 printf '\317\200\012' ??? Does the UNIX® Certification apply when C programs are compiled in Enhanced ASCII mode and to Ported/Rocket utilities? Are there settings/options which can allow the user to be utterly oblivious to EBCDIC? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
