On Fri, 1 May 2009 08:38:59 -0500, Chase, John <jch...@ussco.com> wrote:
>> Thanks for pointing out the benefit of TRUNC(OPT) to me. > >But then there's this in the "Notes" for TRUNC in the Installation & >Customization Guide: > >" 2. TRUNC=BIN is the recommended option when interfacing with other >products that have S/390-format binary data (such as CICS, DB2, FORTRAN, >and PL/I). This is especially true if there is a possibility of having >more than 9 digits in a fullword or more than 4 digits in a halfword." > >So, we're stuck with TRUNC(BIN) in CICS, where arguably we'd want the >"best" performance. :-( I think that if you use the CICS integrated translator then TRUNC() becomes mostly irrelevant in the CICS environment. The integrated translator will use COMP-5 internally. Why IBM didn't choose to use COMP-5 fields during translation before this for COBOL3 I never understood. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
