FYI

David Ashley

-------- Original Message --------
Subject:        Re: Fwd: [Fwd: ooRexx on CMS.]
Date:   Mon, 20 Dec 2010 13:25:08 -0600
From:   David Ashley <[email protected]>
To:     Dave Jones <[email protected]>



Dave -

I am replying to you and to our developer mailing list so that this
conversations is documented.

The first thing you need to do is to join the ooRexx developer mailing list at
https://lists.sourceforge.net/lists/listinfo/oorexx-devel. This will get you
into a conversation with all the active developers. Rick McGuire is our
architect and he also has the most CMS experoence of any of our group. If you
want to tackle CMS first then he is the person you need to create a plan with.

We can all help you with C/C++, Subversion. tools and SourceForge issues. We are
trying to maintain a single source tree for all platforms and we will want to
continue that with an new platforms. There will be issues obviously with ASCII
to EBCDIC conversions and other such issues but Rick and myself can guide you
through those issues.

After you join the mailing list we can begin in ernest. We look forward to your
contributions.

David Ashley
ooRexx Project Team

On 12/20/2010 09:45 AM, Dave Jones wrote:
 Hi, David.

 You're in luck...I'm an expert CMS developer. I know a some C, having
 written a few short and simple programs (fwiw, I dislike C) and
 practically no C++ at all, so I would need help with things like "what
 does this C++ code really do?". I've used ooRexx on both Intel Linux and
 zLinux quite a bit, but mostly in the "classic" style.

 I believe that the port of ooRexx to CMs will be the more difficult one
 simply because the CMS environment is so radically different from all of
 the others. At least with z/OS, you can start with a port of USS, with
 all of it's normal Unix style tools and environment; CMS offers no such
 comparable environment.

 The other main issue with ooRexx on CMS is that ooRexx, being coded in
 C/C++, will require the support of LE; that, in it self, isn't the
 problem because CMS has the latest version of LE available; it's that LE
 itself isn't all that well integrated into the CMS world....you can not,
 for example, code things like CMS Pipeline stages, subcom handlers, or
 RSK routines in any HLL that requires LE. You can write standalone
 programs that require LE with few if any restrictions.

 We do have both z/VM 5.4 and 6.1, plus the latest z/VM C/C++ compiler
 here as well as HLASM R6 and a bunch of other IBM CMs development tools,
 so that should pose no problem.

 What would you like to do first?

 Happy Holidays as well.
 DJ


 On 12/20/2010 08:21 AM, David Ashley wrote:
 Dave -

 We really have two problems in getting ooRexx ported to z/OS and CMS.

 1. Hardware to develop the ports.
 2. Developer expertise in those environments.

 We have had several offers for problem one but practically no offers on
 problem two. None of the current development team have the knowledge to
 do ports on these platforms and we need that before we can even proceed
 with any planning.

 If you know volunteers with even partial knowledge in this area we would
 be more than happy to have them join our team.

 Thanks
 W. David Ashley
 ooRexx Project Team

 -------- Original Message --------
 Subject:     [Fwd: ooRexx on CMS.]
 Date:     Mon, 20 Dec 2010 06:35:41 +0000
 From:     Chip Davis<[email protected]>
 Organization:     Aresti Systems, LLC
 To:     David Ashley<[email protected]>



 David,

 I keep looking for mainframers interested in shepherding an ooRexx
 port to z/VM and z/OS.  Would you like to contact Dave and see if he
 is willing to help?

 -Chip-

 -------- Original Message --------
 Subject: ooRexx on CMS.
 Date: Fri, 17 Dec 2010 11:54:25 -0600
 From: Dave Jones<[email protected]>
 To: Chip Davis<[email protected]>

 Hi, Chip.

   That's the Open Source evolution of IBM Object REXX, supported by a
   team of developers lead by Rick McGuire (an original developer of IBM
   OREXX), is freakishly powerful, and currently runs on every major
   platform (32/64-bit Windows, Mac, UNIX/Linux, looking into Android) --
   except z/VM and Z/OS.

   Believe me, it's not for lack of desire, interest, or love of CMS.  We
   simply don't have access to the necessary resources (hardware and
   wetware) in order to effect a proper port of the (predominately C/C++)
   code.

   If you would be interested in contributing in some way to the effort
   to port ooRexx to IBM's Flagship Operating System (and/or z/OS ;-)
   please go to the ooRexx website www.oorexx.com and contact the Project
   Manager, David Ashley.

 I can make the hardware and software resources need to do a port of
 ooRexx over to z/VM (CMS, that is), as well as z/OS. Please pass that
 along to the proper folks.

 The "hard" part of this port might focus on the fact that CMS is such a
 different environment that the ones you mentioned....for example,
 process and thread support.

 Happy Holidays, too.


------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to