Re: Running REXX compiled in z/OS in CMS
For C/C++, COBOL, and PL/I that is true on z/VM also. We ship the LE runtime libraries for these as part of the z/VM base. The ancient FORTRAN product for z/VM is not LE-enabled. Wonder what it would take to get the REXX compiler so enabled? I guess we have to be careful what we wish for, but it would plug an annoying hole in the compiled code support area. Oh, well, another requirement….
Running REXX compiled in z/OS in CMS
Hi, Here's a question that's half way between z/OS and CMS: I would like to compile some REXX in z/OS in such a way that it can be run in CMS by people who don't have the REXX compiler. From reading the manual, I thought that just specifying options of ALTLIB and SLINE would be sufficient, but this doesn't seem to be the case. I can make it work by XEDITing the compiled exec and changing the processor name in the header from EAGRTPRC to DMSRTPRC, but that surely isn't what IBM intend us to do. Does anyone know the legitimate way of doing this? Thanks, Mark Gillis Principal Software Engineer Tel: +61 2 8898 2678 Fax: +61 2 8898 2600 mark.gil...@ca.com mailto:mark.gil...@ca.com http://www.ca.com/
Re: Running REXX compiled in z/OS in CMS
On Wed, 13 Apr 2011 18:37:51 +1000, Gillis, Mark mark.gil...@ca.com wro te: Hi, Here's a question that's half way between z/OS and CMS: I would like to compile some REXX in z/OS in such a way that it can be run in CMS by people who don't have the REXX compiler. From reading the manual, I thought that just specifying options of ALTLIB and SLINE would be sufficient, but this doesn't seem to be the case. I can make it work by XEDITing the compiled exec and changing the processor name in the header from EAGRTPRC to DMSRTPRC, but that surely isn't what IBM intend us to do. Does anyone know the legitimate way of doing this? Mark, I can't comment on whether there are any other issues with taking REXX co de written and compiled on z/OS and running it on z/VM, but I can tell you t hat in order to run code in CMS that has EAGRTPRC in the header, you need to install the free REXX Alternate Library on z/VM. You can get it here: http://www.ibm.com/software/awdtools/rexx/rexxzseries/altlibrary.html Just click on Alternate Library for REXX on z/VM in the 2nd paragraph. Tracy Dean IBM
Re: Running REXX compiled in z/OS in CMS
Thanks, Tracy. It sounds like we'll just need to require our customers to install the alternate library as a pre-req to our product. I'm a bit confused by all this though - IBM provide compiled REXX that has DMSRTPRC in the header and this doesn't seem to require the alternate library. If I edit a compiled REXX program and change EAGRTPRC to DMSRTPRC it works fine. If either works, why do we have an alternate library? Mark Gillis. -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Tracy Dean Sent: Wednesday, 13 April 2011 7:13 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Running REXX compiled in z/OS in CMS On Wed, 13 Apr 2011 18:37:51 +1000, Gillis, Mark mark.gil...@ca.com wro= te: Hi, Here's a question that's half way between z/OS and CMS: I would like to compile some REXX in z/OS in such a way that it can be run in CMS by people who don't have the REXX compiler. From reading the manual, I thought that just specifying options of ALTLIB and SLINE would= be sufficient, but this doesn't seem to be the case. I can make it work by XEDITing the compiled exec and changing the processor name in the header from EAGRTPRC to DMSRTPRC, but that surely isn't what IBM intend us to do. Does anyone know the legitimate way of doing this? Mark, I can't comment on whether there are any other issues with taking REXX co= de written and compiled on z/OS and running it on z/VM, but I can tell you t= hat in order to run code in CMS that has EAGRTPRC in the header, you need to install the free REXX Alternate Library on z/VM. You can get it here: http://www.ibm.com/software/awdtools/rexx/rexxzseries/altlibrary.html Just click on Alternate Library for REXX on z/VM in the 2nd paragraph. Tracy Dean IBM
Re: Running REXX compiled in z/OS in CMS
Mark, Many VM releases ago, VM Development wanted to have all customers benefit from performance improvements for some of the items that were written in REXX. You know about these parts like VMLINK, NOTE, SENDFILE, FILELIST and many others. However, we could not assume that all customers would install the REXX Alternate Library and customers would want to use these parts even before they got around to installing the REXX Alternate Library. So VM Development created a DMSRTPRC which is a library which is sufficient for the compiled REXX parts that are shipped with the VM product. It is not to be used by our customers for their own use because it is not supported for general use. There is no guarantee that your compiled part will run if you edit it to use DMSRTPRC. VM Development will not service DMSRTPRC if it does not work with your compiled part. We will service it if it fails with one of the parts that are compiled and shipped as part of VM. pdb (Doug Breneman) z/VM System Test IBM Endicott, NY From: Gillis, Mark mark.gil...@ca.com To: IBMVM@LISTSERV.UARK.EDU Date: 04/13/2011 04:26 PM Subject:Re: Running REXX compiled in z/OS in CMS Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU Thanks, Tracy. It sounds like we'll just need to require our customers to install the alternate library as a pre-req to our product. I'm a bit confused by all this though - IBM provide compiled REXX that has DMSRTPRC in the header and this doesn't seem to require the alternate library. If I edit a compiled REXX program and change EAGRTPRC to DMSRTPRC it works fine. If either works, why do we have an alternate library? Mark Gillis. -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Tracy Dean Sent: Wednesday, 13 April 2011 7:13 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Running REXX compiled in z/OS in CMS On Wed, 13 Apr 2011 18:37:51 +1000, Gillis, Mark mark.gil...@ca.com wro= te: Hi, Here's a question that's half way between z/OS and CMS: I would like to compile some REXX in z/OS in such a way that it can be run in CMS by people who don't have the REXX compiler. From reading the manual, I thought that just specifying options of ALTLIB and SLINE would= be sufficient, but this doesn't seem to be the case. I can make it work by XEDITing the compiled exec and changing the processor name in the header from EAGRTPRC to DMSRTPRC, but that surely isn't what IBM intend us to do. Does anyone know the legitimate way of doing this? Mark, I can't comment on whether there are any other issues with taking REXX co= de written and compiled on z/OS and running it on z/VM, but I can tell you t= hat in order to run code in CMS that has EAGRTPRC in the header, you need to install the free REXX Alternate Library on z/VM. You can get it here: http://www.ibm.com/software/awdtools/rexx/rexxzseries/altlibrary.html Just click on Alternate Library for REXX on z/VM in the 2nd paragraph. Tracy Dean IBM
Re: Running REXX compiled in z/OS in CMS
On: Thu, Apr 14, 2011 at 06:25:59AM +1000,Gillis, Mark Wrote: } Thanks, Tracy. It sounds like we'll just need to require our customers } to install the alternate library as a pre-req to our product. I'm a bit } confused by all this though - IBM provide compiled REXX that has } DMSRTPRC in the header and this doesn't seem to require the alternate } library. If I edit a compiled REXX program and change EAGRTPRC to } DMSRTPRC it works fine. If either works, why do we have an alternate } library? The DMSRTPRC library (at least as of the last time I looked at it) does not have all of the routines in it that the EAGRTPRC does. Only those needed to allow the execs that IBM supplies compiled to run. I am not sure if the alternate library has everything from EAGRTPRC in it, or just more than DMSRTPRC does. -- Rich Greenberg Sarasota, FL, USA richgr atsign panix.com + 1 941 378 2097 Eastern time. N6LRT I speak for myself my dogs only.VM'er since CP-67 Canines: Val, Red, Shasta, Zero Casey (At the bridge)Owner:Chinook-L Canines: Red Cinnar (Siberians) Retired at the beach Asst Owner:Sibernet-L
Re: Running REXX compiled in z/OS in CMS
Great - now it all makes sense. We'll just pre-req the alternate library for our product. Thanks. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Doug Breneman Sent: Thursday, 14 April 2011 6:37 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Running REXX compiled in z/OS in CMS Mark, Many VM releases ago, VM Development wanted to have all customers benefit from performance improvements for some of the items that were written in REXX. You know about these parts like VMLINK, NOTE, SENDFILE, FILELIST and many others. However, we could not assume that all customers would install the REXX Alternate Library and customers would want to use these parts even before they got around to installing the REXX Alternate Library. So VM Development created a DMSRTPRC which is a library which is sufficient for the compiled REXX parts that are shipped with the VM product. It is not to be used by our customers for their own use because it is not supported for general use. There is no guarantee that your compiled part will run if you edit it to use DMSRTPRC. VM Development will not service DMSRTPRC if it does not work with your compiled part. We will service it if it fails with one of the parts that are compiled and shipped as part of VM. pdb (Doug Breneman) z/VM System Test IBM Endicott, NY Inactive hide details for Gillis, Mark ---04/13/2011 04:26:40 PM---Thanks, Tracy. It sounds like we'll just need to require oGillis, Mark ---04/13/2011 04:26:40 PM---Thanks, Tracy. It sounds like we'll just need to require our customers to install the alternate libr From: Gillis, Mark mark.gil...@ca.com To: IBMVM@LISTSERV.UARK.EDU Date: 04/13/2011 04:26 PM Subject: Re: Running REXX compiled in z/OS in CMS Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU Thanks, Tracy. It sounds like we'll just need to require our customers to install the alternate library as a pre-req to our product. I'm a bit confused by all this though - IBM provide compiled REXX that has DMSRTPRC in the header and this doesn't seem to require the alternate library. If I edit a compiled REXX program and change EAGRTPRC to DMSRTPRC it works fine. If either works, why do we have an alternate library? Mark Gillis. -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Tracy Dean Sent: Wednesday, 13 April 2011 7:13 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Running REXX compiled in z/OS in CMS On Wed, 13 Apr 2011 18:37:51 +1000, Gillis, Mark mark.gil...@ca.com wro= te: Hi, Here's a question that's half way between z/OS and CMS: I would like to compile some REXX in z/OS in such a way that it can be run in CMS by people who don't have the REXX compiler. From reading the manual, I thought that just specifying options of ALTLIB and SLINE would= be sufficient, but this doesn't seem to be the case. I can make it work by XEDITing the compiled exec and changing the processor name in the header from EAGRTPRC to DMSRTPRC, but that surely isn't what IBM intend us to do. Does anyone know the legitimate way of doing this? Mark, I can't comment on whether there are any other issues with taking REXX co= de written and compiled on z/OS and running it on z/VM, but I can tell you t= hat in order to run code in CMS that has EAGRTPRC in the header, you need to install the free REXX Alternate Library on z/VM. You can get it here: http://www.ibm.com/software/awdtools/rexx/rexxzseries/altlibrary.html Just click on Alternate Library for REXX on z/VM in the 2nd paragraph. Tracy Dean IBM
Re: Running REXX compiled in z/OS in CMS
One thing that HP does for VMS is ship all the runtime libraries for all their compilers (even the weird ones like BLISS and PROLOG) as part of the base OS. That way ISV vendors (or the base OS vendor) don't have this kind of problem. Paying to create, free to use always seemed like a good compromise to me. -- db (PS - at least one required system utility is written in each language to force the marketroids to continue this policy. Score one to the Visigoths.)
Re: Running REXX compiled in z/OS in CMS
IBM on z/OS does that too. It is LE. For better or worse. I am fairly sure that all the current IBM compilers on z/OS use LE as their run-time. COBOL, C, FORTRAN, and PL/I all do, I'm certain. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of David Boyes Sent: Wednesday, April 13, 2011 4:09 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Running REXX compiled in z/OS in CMS One thing that HP does for VMS is ship all the runtime libraries for all their compilers (even the weird ones like BLISS and PROLOG) as part of the base OS. That way ISV vendors (or the base OS vendor) don't have this kind of problem. Paying to create, free to use always seemed like a good compromise to me. -- db (PS - at least one required system utility is written in each language to force the marketroids to continue this policy. Score one to the Visigoths.)
Re: Running REXX compiled in z/OS in CMS
John, For C/C++, COBOL, and PL/I that is true on z/VM also. We ship the LE runtime libraries for these as part of the z/VM base. The ancient FORTRAN product for z/VM is not LE-enabled. Mike Donovan From: McKown, John john.mck...@healthmarkets.com To: IBMVM@LISTSERV.UARK.EDU Date: 04/13/2011 05:12 PM Subject:Re: Running REXX compiled in z/OS in CMS Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU IBM on z/OS does that too. It is LE. For better or worse. I am fairly sure that all the current IBM compilers on z/OS use LE as their run-time. COBOL, C, FORTRAN, and PL/I all do, I'm certain. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets® 9151 Boulevard 26 • N. Richland Hills • TX 76010 (817) 255-3225 phone • john.mck...@healthmarkets.com • www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets® is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. –The Chesapeake Life Insurance Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of David Boyes Sent: Wednesday, April 13, 2011 4:09 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Running REXX compiled in z/OS in CMS One thing that HP does for VMS is ship all the runtime libraries for all their compilers (even the weird ones like BLISS and PROLOG) as part of the base OS. That way ISV vendors (or the base OS vendor) don’t have this kind of problem. Paying to create, free to use always seemed like a good compromise to me. -- db (PS – at least one required system utility is written in each language to force the marketroids to continue this policy. Score one to the Visigoths.)
Re: Running REXX compiled in z/OS in CMS
On Wed, 13 Apr 2011 14:33:55 -0400, Wayne T Smith wtsm...@maine.edu wro te: Are you implying compiling and using the alternate library runs faster than uncompiled Rexx Absolutely not. or that it's just a way to get compiled Rexx to run where the compiler is not licensed? Correct - assuming the code has been compiled to allow this, per Mark's original post. Tracy Dean, IBM
