As someone has already noted, if you compile your VS COBOL II program with TRUNC(BIN) then it will treat *all* binary items the same as COMP-5 items (in Enterprise COBOL). This will, however, have
SIGNIFICANT PERFORMANCE impact !!! On the other hand, the only time that a COMP-5 data item works differently from a BINARY or COMP (or COMP-4) item (on the mainframe) is *IF* you try and use values greater than the PICTURE clause allows. This is an "ugly" thing to do and is NEVER recommended. I would START by trying to "pass" COMP-5 (Enterprise COBOL) items to and from BINARY (or COMP) VS COBOL II items and see if there are any problems. If there are, then I would check your application "logic" to see WHY you need to use values greater than the PICTURE allows. "Stocker, Herman" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > Hi, > > I have been asked to check around and see if there is any known > patch/subroutine/exit that will allow a cobol 2 compiled program to use a > comp5 field. This can be either free or a $ item. They are looking at a > short time work around that they can use until we get to LE and E/Cobol. > > Thank you for your assistance. > ---------------------------------------------------------------------- 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
