I develop a vendor product that performs date simulation for applications that acquire the system date. This process currently works for applications that use the TIME macro (SVC 11) to get the date, but Language Environment (in some cases) does not use the TIME macro to get the system date, so which module and instruction do I need to zap in order to make my product work? Does going to OS/390 mean that I need to place Language Environment in the LNKLST? What does Language Environment perform before giving control to the application? What does Language Environment perform during abend processing? What are the performance considerations? What RUNTIME options should we look at? I do not have OS/390 UNIX System Services running, but would like to put on SMP fixes to LE. However, then I receive error messages, indicating that I have to have OS/390 UNIX System Services running to install Language Environment maintenance. Is this true? I have heard that migrating my COBOL applications from using the VS COBOL II run-time library to Language Environment is transparent to the users. Is this true? On some of the Language Environment notes, I see the term Language Environment-conforming. How do we make an assembler program Language Environment-conforming and what are the benefits? Can VS COBOL II - COMP/LIB be used in the z/OS 1.1, 1.2, and 1.3 environment? Do I need to write my user-written condition handler in assembler? Can we prevent the ABEND C03 even if all the files are not properly closed? Since LIBKEEP is no longer available under Language Environment, what do I use in its place? When Language Environment is placed in the LNKLST will any CICS regions be affected?
