Yes, POSIX ON is definitely required. Without it, I experienced the following:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The C application uses Unix Services and therefore has to run with POSIX ON - logic has been added to the C program to display the setting of the POSIX option. This C application is invoked from a COBOL program that is linked with a CEEUOPT module that has the POSIX option turned ON. The COBOL program is used in both a Batch and SPF environment. The C program is invoking some IBM C sub-routines that do Secure Socket Layer functions. When the COBOL program is executed in a Batch environment, everything works OK and the C program displays that the POSIX option is ON. When the same COBOL program is executed in the SPF environment with a different driver module (one that uses CALL ISPLINK SELECT PGM(...), the C program displays that the POSIX option is OFF and I get the following message: "GSKSSL: Unable to create log mutex: EDC5167I Access to the UNIX System Services version of the C RTL is denied" For the TSO execution, I placed a RPTOPTS(ON) in the COBOL program and it shows that POSIX is ON but the C program says that it is OFF??? +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The problem as stated earlier was due to the POSIX ON not being inherited to sub-modules once an CALL ISPLINK SELECT PGM(...) is invoked during the enclave. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
