We are in the process of converting to COBOL 6.2 and there are a number of compiler options you can use...many also work with 6.1 and 5.
I suggest you try : rules(noendperiod,noevenpack,laxperf,noslackbytes). While the "noendperiod" is not performance per se, it will help identify unstructured code. diagtrunc. This will look for numeric assignments where the receiver has fewer digits than the sender. zonedate(pdf). Helps discover invalid zone bits numcheck(zon,pac,bin,msg). Generates a NONNUMERIC check for numeric assignments. You will want to fix any found then turn this off. ARCH(nn). The architecture level of you z Server...12 = z14, 11 = z13, etc. PARMCHECK. Looks for disparate parameter lengths, which COBOL 6 does not like. When you are ready for production compile with OPT(2). If you use InterTest, you can not debug optimized code. Xpediter and IDz, which uses DEBUG, will. If you compile with COBOL 4, you can also turn on FLAGMIG4 to look for items that will not be compatible with the newer compilers. It's helpful, but not all inclusive. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
