I am still writing my HLASM LE enabled "shim" routine which allows COBOL program to, relatively, easily invoke the C language based "sqlite" SQL database engine. One requirement, due to sqlite's use of mutex semaphores is that the LE enclave be running with POSIX(ON). Instead of getting the S0C6 which I got in the past, I have the HLASM program do a CEE3INF in order to verify that the routine is running with POSIX(ON). If not, it returns a return code which is identical to SQLITE_MISUSE, which seemed the closest match. Of course, this requires that the caller actually check the return code. If not, the user program can just waste time. Which I don't like.
So I thought it might be a good idea to use the CEESGL function to "throw an exception" instead of just returning a return code which could be ignored. Does this sound reasonable? I was thinking of using a severity of 4 (the maximum) because POSIX(ON) is required to use the library, and a facility of "SQL" (3 characters) just because. -- As of next week, passwords will be entered in Morse code. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
