I just wanted to CORRECT the erroneous statement that I made below. If an Enterprise COBOL program is statically link-edited with an AMODE(24) program, it will "of course" be marked as AMODE(24) - and will work that way.
It still is NOT what I would recommend in this situation, but I did want to correct what I said before others worried about it. "Bill Klein" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > There is ABSOLUTELY no way that you will get an Enterprise COBOL CICS > program to work if it is marked as AMODE(24). All the "IGY" and "CEE" > routines that it will need to run will have problems. You could get an > RMODE program, but that isn't what you are asking for. > > If the programmer wants to force RMODE(24), then use the > PROCESS RMODE(24) > statement as the first line of the source code. This should > > This should work unless your compiler was installed with NOALLOWCBL > > How does the COBOL program access the HLASM program (or vice versa), EXEC > CICS LINK? CALL "literal" or CALL identifier. Depending on the type of ILC > has the "responsible" programmer read what IBM has to say about these. > > "McKown, John" <[EMAIL PROTECTED]> wrote in message > news:<[EMAIL PROTECTED]>... > > We have a problem. We have a very old CICS application which is written > > in HLASM and OS/VS COBOL 2.4. We want to convert the COBOL to Enterprise > > COBOL. We have having many problems due mainly to lack of knowledge > > about the code base. The programmer doing this is convinced that a/the > > major problem is that Enterprise COBOL links as AMODE(31). He wants to > > force the load module to AMODE(24). The only way that I can see to do > > this is via the AMODE(24) parm in the Binder. However, we use CA-Endevor > > for our program compiles and links. This means that we need a separate > > Endevor processor which invokes the binder with the AMODE(24) parm. Any > > ideas about another way to do this which would not require a new Endevor > > processor? I don't know a lot about Endevor, but I don't see a way to > > use the Binder's MODE command. And I don't know if this would be easier > > to implement in Endevor than the PARM. > > > > P.S. I am not as convinced as the programmer that the problems he is > > encountering are due to the AMODE. But he is insistant and has the > > political backing to force the issue. The only way to prove otherwise to > > allow him to do his work in AMODE(24) and see if he still has the same > > problems. He has already done a lot of "figure out this for me" type > > requests to Tech Services. > > > > -- > > John McKown > > Senior Systems Programmer > > HealthMarkets > > Keeping the Promise of Affordable Coverage > > Administrative Services Group > > Information Technology > > > > The information contained in this e-mail message may be privileged > > and/or confidential. It is for intended addressee(s) only. If you are > > not the intended recipient, you are hereby notified that any disclosure, > > reproduction, distribution or other use of this communication is > > strictly prohibited and could, in certain circumstances, be a criminal > > offense. If you have received this e-mail in error, please notify the > > sender by reply and delete this message without copying or disclosing ---------------------------------------------------------------------- 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
