It is not out of the question - but it does "violate" the SMPE approach - to have two sets of COBOL customization on one machine.
Basically, you assemble and link one set of compiler options into LOADLIBA and the other set into LOADLIBB. Then programmers who formerly used LPAR A use //STEPLIB DD DSN=LOADLIBA,DISP=SHR // DD the real compiler load library And programmers who formerly used LPAR B use //STEPLIB DD DSN=LOADLIBB,DISP=SHR // DD the real compiler load library Various other combinations involving LPA and/or only two load libraries are obviously possible. Just make sure everybody finds the right options load module FIRST. I know for a fact that this works. At Syspoint we are using this approach to support multiple customers with different customization requirements on a single compile server. Yes, I know it won't be painless for you - involves proc changes, etc. For that matter, you can just have two complete installs of COBOL and customize them separately. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Alan Schwartz Sent: Wednesday, March 29, 2006 10:18 AM To: [email protected] Subject: Changing Cobol Default Options I'm merging two lpars and, not surprising, there are some customization differences in COBOL and LE. Most are easily changed and don't really affect how jobs run. However I have two differences that concern me. LPARA (the sending lpar) has INTDATE=ANSI and LPARB (the receiving lpar) has INTDATE=LILIAN. Also LPARA has OPT as the default for TRUNC while LPARB uses STD. I've asked IBM about these but they just quote me ---------------------------------------------------------------------- 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
