That is a possibility. Until a few years ago rxapi was a shared memory application, so it could be put in ECSA or its own address space I think. This is something to worry about after we have established that the compiler generates the right code for USS use of ooRexx.
On 10 mei 2014, at 21:18, Dan Carter <gwcar...@ezlink.com> wrote: > How do we expect to do this? Do we plan to run rxapi as a system task, > started at IPL? > > -----Original Message----- > From: René Jansen [mailto:rvjan...@xs4all.nl] > Sent: Saturday, May 10, 2014 19:27 > To: Open Object Rexx Developer Mailing List > Cc: Open Object Rexx Developer Mailing List > Subject: Re: [Oorexx-devel] OOREXX on z/OS > > Hi Howard, > > I would think, trying to build on Linux (if you haven't done so already) to > make sure you are prepared to see what happens during a build, which tools > are involved, what artifacts are produced and how these are linked together. > Then, look for ways to have this work on z/OS, and try to have an inventory > of what needs to be done to have an initial port work under TSO, which I > image to involve lots of small programs to try out converting unix api to tso > macros. I am working on arranging an LPAR to work on. > > In the meantime, looking around for an svn client for z/OS would not be a bad > idea. > > René Vincent Jansen > > > On 9 mei 2014, at 17:55, Hobart Spitz <orexx...@gmail.com> wrote: > >> Where can I start? >> >> -- >> OREXXMan >> ---------------------------------------------------------------------- >> -------- Is your legacy SCM system holding you back? Join Perforce May >> 7 to find out: >> • 3 signs your SCM is hindering your productivity • >> Requirements for releasing software faster • Expert tips and >> advice for migrating your SCM now http://p.sf.net/sfu/perforce >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > • 3 signs your SCM is hindering your productivity • Requirements > for releasing software faster • Expert tips and advice for migrating > your SCM now http://p.sf.net/sfu/perforce > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > • 3 signs your SCM is hindering your productivity > • Requirements for releasing software faster > • Expert tips and advice for migrating your SCM now > http://p.sf.net/sfu/perforce > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
