This is not going to be the most helpful reply but I found POSIX(ON) to be a series of traps for the unwary. I had working, fairly complex C++ code. I had, based on KISS, gone with the default of POSIX(OFF). I added SSL/TLS support to the product via GSK, which demands POSIX(ON). Lots of long-forgotten little "things" stopped working or worked differently. I don't remember them all so I am not going to attempt an inventory here, and in any event, my inventory would be different from yours. My point is just ... beware.
As I recall, for each "feature" that is affected by POSIX(ON), the manuals are quite explicit. However, there is no single inventory, no place where the manual says "POSIX(ON) changes all of the following behaviors." Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Juergen Weber Sent: Friday, January 24, 2014 1:20 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: POSIX(ON) costs or disadvantages Hello, has anybody knowledge/experience of the consequences of POSIX(ON) ? Some C runtime library functions require POSIX(ON) (especially pthreads and friends). Why is POSIX(ON) not set by default for 31 bit code? I tried to search in documentation for costs and disadvantages of POSIX(ON), the only thing I could find was in z/OS Language Environment Programming Reference: "The default value for AMODE 64 is POSIX(ON)." So, why is this not for AMODE(31) ? "One of the effects of POSIX(ON) is the enablement of POSIX signal handling semantics, which interact closely with the Language Environment condition handling semantics." ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
