This is on z/VSE, but the LE environment on z/VSE is very close to the LE environment on z/OS so it should not matter.
Here is the situation. I author of the IPv6/VSE APIs. When an IP program calls EZASOKET or uses the EZASMI macro or use any of the LE IP functions, my code is all in "LE compatable assembler". (The code is not LE-enabled nor does it use the LE stack, but it does respect R12.) Everything has been working for over 10 years, but now I have a new situation. I now need, under some conditions, to call an IBM system service that is written using LE. Known constants: 1) I can not require that the caller be LE-enabled. (I know of several vendor and customer written applications that are written in non-LE assembler.) 2) Performance is critical so I can not create and destroy the LE environment every call. 3) I don't want a 'separate version' of each interface program for either LE or non-LE environments 4) IBM does not plan on providing the system service without LE in the near future. (Maybe later, but not right now.) Known environments: 1) Batch with an LE environment already established 2) Batch without an LE environment established. 3) CICS called from the normal application domain 4) CICS called from the socket domain 5) CICS called from the VSAM interface 6) CICS called from the PLT (is LE available?) I am looking for any thoughts or suggestions. -- Tony Thigpen
