Re: insane request: force load module to RMODE(24) AMODE(24)
If this is really old code, what difference does it make if it runs in AMODE(24). I'm sure code that old wouldn't take up enough storage cause any problems. Eric Bielefeld Sr. z/OS Systems Programmer Milwaukee, Wisconsin 414-475-7434 - Original Message - From: Ted MacNEIL [EMAIL PROTECTED] Subject: Re: insane request: force load module to RMODE(24) AMODE(24) Why would anybody want to run in AMODE(24) in this day and age? As anybody told the programmer to get into the new millenium? -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
On 17 Jun 2008 09:39:50 -0700, in bit.listserv.ibm-main you wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL Sent: Tuesday, June 17, 2008 11:21 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: insane request: force load module to RMODE(24) AMODE(24) ... 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). Why would anybody want to run in AMODE(24) in this day and age? As anybody told the programmer to get into the new millenium? - He is convinced that parts of the code simply cannot use AMODE(31) without extensive rewriting, which he does not have the time or the knowledge to do. The assembler is very crufty and tricky in the bad sense of the word. Why can't I use RMODE(ANY), AMODE(31) with QSAM I/O? (rhetorical question - I do know why - this code may similar tricks such as using the high byte of a register for flags). This whole thing sounds like I could have a lot of fun upgrading this application and possibly rewriting the Assembler part in COBOL. I doubt your company would be interested in a cross border consultant even though I am a US citizen. -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
If this is really old code, what difference does it make if it runs in AMODE(24). I'm sure code that old wouldn't take up enough storage cause any problems. Who said anything about storage problems? I sure didn't. I would be more concerned about addressability. - Too busy driving to stop for gas! -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
Thats what I get for not reading the entire thread before posting a reply. Someone after my post pointed out that with the new Cobol, you coudn't use AMODE(24). Had I read that, I wouldn't have posted. Eric Bielefeld Sr. z/OS Systems Programmer Milwaukee, Wisconsin 414-475-7434 - Original Message - From: Ted MacNEIL [EMAIL PROTECTED] Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@BAMA.UA.EDU Sent: Wednesday, June 18, 2008 10:11 AM Subject: Re: insane request: force load module to RMODE(24) AMODE(24) If this is really old code, what difference does it make if it runs in AMODE(24). I'm sure code that old wouldn't take up enough storage cause any problems. Who said anything about storage problems? I sure didn't. I would be more concerned about addressability. -- 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
insane request: force load module to RMODE(24) AMODE(24)
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 it. -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
On Tue, 17 Jun 2008 08:52:32 -0500, McKown, John wrote: ... 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. For testing purposes, I'd link edit the module outside of Endevor. That might mean that you have to link it into a different load library, but it would provide a simple test. -- Tom Marchant -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
Could you/he contact the vendor and ask them the question? It seems to me that CA should be able to either point him in the right direction (since he is the one using the product, not you) or tell him it can't be done. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Tuesday, June 17, 2008 9:53 AM To: IBM-MAIN@BAMA.UA.EDU Subject: insane request: force load module to RMODE(24) AMODE(24) 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 it. -- 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 -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant Sent: Tuesday, June 17, 2008 9:02 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: insane request: force load module to RMODE(24) AMODE(24) On Tue, 17 Jun 2008 08:52:32 -0500, McKown, John wrote: ... 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. For testing purposes, I'd link edit the module outside of Endevor. That might mean that you have to link it into a different load library, but it would provide a simple test. -- Tom Marchant I guess that we may need to do this. But it is going to be a nightmare! All the source is in Endevor controlled libraries. The load library in the DFHRPL is Endevor controlled. Linking into this environment outside of Endevor is another political nightmare. -- 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 it. -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
On Tue, 17 Jun 2008 09:21:25 -0500, McKown, John wrote: I guess that we may need to do this. But it is going to be a nightmare! All the source is in Endevor controlled libraries. The load library in the DFHRPL is Endevor controlled. Linking into this environment outside of Endevor is another political nightmare. Understood. But can you add another data set to the DFHRPL concatenation to test? -- Tom Marchant -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant Sent: Tuesday, June 17, 2008 9:46 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: insane request: force load module to RMODE(24) AMODE(24) On Tue, 17 Jun 2008 09:21:25 -0500, McKown, John wrote: I guess that we may need to do this. But it is going to be a nightmare! All the source is in Endevor controlled libraries. The load library in the DFHRPL is Endevor controlled. Linking into this environment outside of Endevor is another political nightmare. Understood. But can you add another data set to the DFHRPL concatenation to test? -- Tom Marchant I'll take that up with the CICS person. We may end up doing that. Thanks. -- 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 it. -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Tuesday, June 17, 2008 9:53 AM To: IBM-MAIN@BAMA.UA.EDU Subject: insane request: force load module to RMODE(24) AMODE(24) Snipped 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. John, It's been a while since I worked with Endeavor, but ISTR there is (or was in that shop) a capability to specify binder control cards (in a separate library type that was an optional part of the source package) which would allow you to override the PARM AMODE value. I know I used it for a similar purpose as your programmer, to guarantee RMODE(24) and AMODE(24). Don't forget to tell the programmer to also use the Enterprise COBOL option DATA(24) if he is calling AMODE(24) assembler. Who is your Endeavor administrator? That person (the one who controls the Endeavor processes) may be more help here. In the shop where I used it the Endeavor admins were in the system assurance/operations control area. HTH Peter This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Tuesday, June 17, 2008 8:53 AM To: IBM-MAIN@BAMA.UA.EDU Subject: insane request: force load module to RMODE(24) AMODE(24) SNIP 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. SNIP Have the programmer do a call that causes a static link to an assembler routine that is AMODE(24) RMODE(24). This should force BINDER (unless your Endevor processor overrides it) to mark the resulting load module AMODE(24) RMODE(24). The assembler routine only needs to be a DC to create a table or some such. Regards, Steve Thompson -- All opinions expressed by me are my own and may not necessarily reflect those of my employer. -- -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
On Tue, Jun 17, 2008 at 9:52 AM, McKown, John [EMAIL PROTECTED] wrote: SNIP 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 mu problems. He has already done a lot of figure out this for me type requests to Tech Services. Has he tried using DATA(24) in his Enterprise Cobol compiles? In my limited experience, that usually does the trick when calling old subroutines. -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
[snip] Who is your Endeavor administrator? That person (the one who controls the Endeavor processes) may be more help here. In the shop where I used it the Endeavor admins were in the system assurance/operations control area. HTH Peter We do have a lady who is, as we affectionately call her, the change queen. She has consented to create a new CICS/Enterprise COBOL processor for this one function. So, no problem any more. Well, at least this is not a problem. I'm not sure what will happen if this RMODE/AMODE doesn't magically fix all the problems. -- 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 it. -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
You can use the Process Group parameter on the add/update panel. Don't know how it works internally, but we use it to specify MQ includes on linkedits for our cobol processor. Works reasonably well, but is sort of a PITA because I aways forget the name of the processor group if I go a long time between compiles - Original Message From: McKown, John [EMAIL PROTECTED] To: IBM-MAIN@BAMA.UA.EDU Sent: Tuesday, June 17, 2008 9:52:32 AM Subject: insane request: force load module to RMODE(24) AMODE(24) 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 it. -- 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 -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
-snip 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. --unsnip- ISTR that if the program wasn't capable of 31-bit mode, the compiler wouldn't mark it that way. You programmer is full of something I can't mention here, in the interests of propriety. After Endevor links the program, run a separate step to re-link the program, assigning the same entry point. The second link should run just fine and you can mark it AMODE=24 and RMODE=24 via binder arms. ASnd when it still fails, you can point out to the so-called superiors that this guy doesn't really know sh** from shinola. He sounds like a very arrogant person, or very ignorant person. Either way, he needs to be put in his place. -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
John McKown of the IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 06/17/2008 08:52:32 AM: 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. Compile with the NODYNAM option and you will get AMODE(24). Regards, John K -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
... 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). Why would anybody want to run in AMODE(24) in this day and age? As anybody told the programmer to get into the new millenium? - Too busy driving to stop for gas! -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
Okay. Sorry for resonding to my own post, but I never saw the original problem statement, until it was echoed in a subsequent post. I still believe AMODE(24) is passé, but now I know the reason. - Too busy driving to stop for gas! -Original Message- From: Ted MacNEIL [EMAIL PROTECTED] Date: Tue, 17 Jun 2008 16:21:21 To:IBM-MAIN@BAMA.UA.EDU Subject: Re: insane request: force load module to RMODE(24) AMODE(24) ... 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). Why would anybody want to run in AMODE(24) in this day and age? As anybody told the programmer to get into the new millenium? - Too busy driving to stop for gas! -- 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 -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL Sent: Tuesday, June 17, 2008 11:21 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: insane request: force load module to RMODE(24) AMODE(24) ... 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). Why would anybody want to run in AMODE(24) in this day and age? As anybody told the programmer to get into the new millenium? - He is convinced that parts of the code simply cannot use AMODE(31) without extensive rewriting, which he does not have the time or the knowledge to do. The assembler is very crufty and tricky in the bad sense of the word. Why can't I use RMODE(ANY), AMODE(31) with QSAM I/O? (rhetorical question - I do know why - this code may similar tricks such as using the high byte of a register for flags). -- 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 it. -- 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
insane request: force load module to RMODE(24) AMODE(24)
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 it. -- 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 -- 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
Fw: insane request: force load module to RMODE(24) AMODE(24)
If it was originally compiled with DYNAM, it wouldn't work with CICS any way. It must already be NODYNAM. NODYNAM doesn't force AMDOE(24) unless an AMDOE(24) program is statically linked-in. John P Kalinich [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... John McKown of the IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 06/17/2008 08:52:32 AM: 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. Compile with the NODYNAM option and you will get AMODE(24). Regards, John K -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
On 17 Jun 2008 09:29:32 -0700, [EMAIL PROTECTED] (Ted MacNEIL) wrote: Why would anybody want to run in AMODE(24) in this day and age? As anybody told the programmer to get into the new millenium? We have some assembly language programs that are called to connect with cash machines that use AMODE(24). A consultant spent a couple of months trying to get around that limitation, but management said it wasn't worth fixing. -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
We have some assembly language programs that are called to connect with cash machines that use AMODE(24). A consultant spent a couple of months trying to get around that limitation, but management said it wasn't worth fixing. Short term it may not be worth it but over the long run it would save a lot of headaches and money. Mangement has a bad tendency to only see as far as the next quarter and misses opportunities to resolve longer term problems. What are they going to do if this stops working down the road? Hire a super expensive consultant to try to fix it, if they can find one, that is. Jon L. Veilleux [EMAIL PROTECTED] (860) 636-2683 This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
On Tue, 17 Jun 2008 15:16:36 -0400, Veilleux, Jon L wrote: ... What are they going to do if this stops working down the road? Hire a super expensive consultant to try to fix it, if they can find one, that is. Sure, they can fine one, depending on what you mean by super expensive. There are a lot of people on this list who would gladly look at it for $300 per hour. Maybe even for less -- Tom Marchant -- 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
Re: insane request: force load module to RMODE(24) AMODE(24)
On 17 Jun 2008 12:17:29 -0700, [EMAIL PROTECTED] (Veilleux, Jon L) wrote: Short term it may not be worth it but over the long run it would save a lot of headaches and money. Mangement has a bad tendency to only see as far as the next quarter and misses opportunities to resolve longer term problems. What are they going to do if this stops working down the road? Hire a super expensive consultant to try to fix it, if they can find one, that is. The long term solution is what's happening now - replace the system. -- 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
insane request: force load module to RMODE(24) AMODE(24)
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