Object Rexx multiple version coexistence

Mario Sacco

unread,

Apr 8, 2013, 11:29:48 AM4/8/13

to

It's possible install more OORexx versions on the same computer (e.g.
versions 3.2 and 4)?

Clearly the right interpreter has to be addressed by explicit directory
reference, but I'm not sure if the interpreters share some common
file/library that could cause the exclusion of the other versions.

Thanks.

LesK

unread,

Apr 8, 2013, 5:43:17 PM4/8/13

to

You can't do that.

--

Les (Change Arabic to Roman to email me)

Jeremy Nicoll - news posts

unread,

Apr 8, 2013, 6:28:47 PM4/8/13

to

LesK <5mr...@tampabay.rr.com> wrote:

>On 4/8/2013 11:29 AM, Mario Sacco wrote:
>> It's possible install more OORexx versions on the same computer (e.g.
>> versions 3.2 and 4)?
>>
>> Clearly the right interpreter has to be addressed by explicit directory
>> reference, but I'm not sure if the interpreters share some common
>> file/library that could cause the exclusion of the other versions.
>>
>> Thanks.

>You can't do that.

I would guess that the stumbling block is the rxapi service (in Windows
terms), which provides cross-system resources for the rexx runtime
environments.

I don't see why you couldn't stop & start more than one instance of rxapi,
though presumably one can't run more than one at a time, unless Vx.y.z of
the rexx interpreter is clever enough only to talk to the corresponding
version of rxapi.

I'm not sure that there's any reason why a rexx.exe run from one folder,
picking up the DLLs within that folder, would not be able to coexist with
another rexx.exe & DLL set from another folder. If you wanted specific
execs to run under a particular interpreter you could force that my mapping
different extensions onto different interpreters.

--
Jeremy C B Nicoll - my opinions are my own.

Email sent to my from-address will be deleted. Instead, please reply
to newsre...@wingsandbeaks.org.uk replacing "aaa" by "284".

LesK

unread,

Apr 8, 2013, 6:46:30 PM4/8/13

to

On 4/8/2013 6:28 PM, Jeremy Nicoll - news posts wrote:
> LesK <5mr...@tampabay.rr.com> wrote:
>
>> On 4/8/2013 11:29 AM, Mario Sacco wrote:
>>> It's possible install more OORexx versions on the same computer (e.g.
>>> versions 3.2 and 4)?
>>>
>>> Clearly the right interpreter has to be addressed by explicit directory
>>> reference, but I'm not sure if the interpreters share some common
>>> file/library that could cause the exclusion of the other versions.
>>>
>>> Thanks.
>
>> You can't do that.
>
> I would guess that the stumbling block is the rxapi service (in Windows
> terms), which provides cross-system resources for the rexx runtime
> environments.
>
> I don't see why you couldn't stop & start more than one instance of rxapi,
> though presumably one can't run more than one at a time, unless Vx.y.z of
> the rexx interpreter is clever enough only to talk to the corresponding
> version of rxapi.
>
> I'm not sure that there's any reason why a rexx.exe run from one folder,
> picking up the DLLs within that folder, would not be able to coexist with
> another rexx.exe & DLL set from another folder. If you wanted specific
> execs to run under a particular interpreter you could force that my mapping
> different extensions onto different interpreters.
>
>
>

RTFM41: readme.pdf

Jeremy Nicoll - news posts

unread,

Apr 8, 2013, 6:57:52 PM4/8/13

to

LesK <5mr...@tampabay.rr.com> wrote:

>RTFM41: readme.pdf

Perhaps a little more detail in your reply?

Mark Miesfeld

unread,

Apr 8, 2013, 10:16:45 PM4/8/13

to

On Apr 8, 3:57 pm, Jeremy Nicoll - news posts

<jn.nntp.scrap...@wingsandbeaks.org.uk> wrote:
>
> Perhaps a little more detail in your reply?
>
> --

It is possible to have more than one version of ooRexxx installed on a
system and to switch back and forth between them. You can only have
one ooRexx running at any one time. Jeremy was correct that the main
obstacle is rxapi.

Here is a rather long transcipt showing this:

C:\work.ooRexx>cd \rexx

C:\Rexx>dir
Volume in drive C is Win7
Volume Serial Number is D25E-50D5

Directory of C:\Rexx

04/06/2013 10:53 AM <DIR> .
04/06/2013 10:53 AM <DIR> ..
04/06/2013 11:19 AM <DIR> ooRexx
10/31/2011 07:18 PM <DIR> ooRexx.3.0.0.release
10/31/2011 07:24 PM <DIR> ooRexx.3.0.1.release
10/31/2011 07:30 PM <DIR> ooRexx.3.1.0.release
10/31/2011 07:31 PM <DIR> ooRexx.3.1.1.release
10/31/2011 07:33 PM <DIR> ooRexx.3.1.2.release
11/05/2011 12:40 PM <DIR> ooRexx.3.2.0.debug
11/05/2011 12:38 PM <DIR> ooRexx.3.2.0.release
03/06/2012 08:26 AM <DIR> ooRexx.4.0.0.release
10/31/2011 04:41 PM <DIR> ooRexx.4.0.1.release
07/14/2012 05:07 PM <DIR> ooRexx.4.1.0.release
02/22/2013 09:16 AM <DIR> ooRexx.4.1.1.release
03/05/2013 07:57 PM <DIR> ooRexx.4.1.2.debug
03/20/2013 07:00 AM <DIR> ooRexx.4.1.2.release
03/16/2013 08:44 AM <DIR> ooRexx.4.1.fixes.release
03/30/2013 03:46 PM <DIR> ooRexx.4.2.0.now
07/11/2012 08:53 AM <DIR> static.ooRexx.4.0.0.release
07/11/2012 08:53 AM <DIR> static.ooRexx.4.1.0.release
02/06/2013 07:46 AM 9,137,247 ooDialog-4.2.2.8944-x86_64.exe
01/16/2012 10:26 AM 13,353,435 ooRexx-4.1.0-windows.x86_64.exe
06/14/2012 07:23 AM 13,155,623 ooRexx-4.1.1-windows.x86_64.exe
02/06/2013 08:27 AM 13,092,368 ooRexx-4.1.2.windows.x86_32.exe
02/06/2013 07:45 AM 13,184,407 ooRexx-4.1.2.windows.x86_64.exe
08/09/2012 10:40 AM 47 xcopy.txt
6 File(s) 61,923,127 bytes
20 Dir(s) 1,057,370,112 bytes free

C:\Rexx>rexx -v
Open Object Rexx Version 4.1.3 - Internal Test Version
Build date: Apr 5 2013
Addressing Mode: 64

Copyright (c) IBM Corporation 1995, 2004.
Copyright (c) RexxLA 2005-2012.
All Rights Reserved.
This program and the accompanying materials are made available under
the terms of the Common Public License v1.0 which accompanies this
distribution or at
http://www.oorexx.org/license.html

C:\Rexx>sc stop rxapi

SERVICE_NAME: rxapi
TYPE : 10 WIN32_OWN_PROCESS
STATE : 3 STOP_PENDING
(STOPPABLE, NOT_PAUSABLE,
IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

C:\Rexx>ren ooRexx ooRexx.4.1.fixes.debug

C:\Rexx>ren ooRexx.3.2.0.release ooRexx

C:\Rexx>sc start rxapi

SERVICE_NAME: rxapi
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE,
IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 3456
FLAGS :

C:\Rexx>rexx -v
Open Object Rexx Interpreter Version 3.2.0
Build date: Oct 30 2007
Copyright (c) IBM Corporation 1995, 2004.
Copyright (c) RexxLA 2005-2007.
All Rights Reserved.
This program and the accompanying materials
are made available under the terms of the Common Public License v1.0
which accompanies this distribution.
http://www.oorexx.org/license.html
C:\Rexx>
C:\Rexx>sc stop rxapi

SERVICE_NAME: rxapi
TYPE : 10 WIN32_OWN_PROCESS
STATE : 3 STOP_PENDING
(STOPPABLE, NOT_PAUSABLE,
IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

C:\Rexx>ren ooRexx ooRexx.3.2.0.release

C:\Rexx>ren ooRexx.4.2.0.now ooRexx

C:\Rexx>sc start rxapi

SERVICE_NAME: rxapi
TYPE : 10 WIN32_OWN_PROCESS
STATE : 2 START_PENDING
(STOPPABLE, NOT_PAUSABLE,
IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 2780
FLAGS :

C:\Rexx>rexx -v
Open Object Rexx Version 4.2.0 - Internal Test Version
Build date: Mar 30 2013
Addressing Mode: 64

Copyright (c) IBM Corporation 1995, 2004.
Copyright (c) RexxLA 2005-2012.
All Rights Reserved.
This program and the accompanying materials are made available under
the terms of the Common Public License v1.0 which accompanies this
distribution or at
http://www.oorexx.org/license.html

C:\Rexx>

If you look closely you can see that I have all the way from ooRexx
3.0.0 to a pretty current build from trunk installed. I switch
between any 2 versions by stopping rxapi, using sc (service control)to
stop rxapi, and swapping directory names.

I usually run sc to restart rxapi, but that isn't necessary. Simply
running a Rexx program will restart rxapi.

It is not necessary to use sc to stop rxapi either, you could use any
process killer.

--
Mark Miesfeld

LesK

unread,

Apr 9, 2013, 12:14:56 AM4/9/13

to

On 4/8/2013 10:16 PM, Mark Miesfeld wrote:
> On Apr 8, 3:57 pm, Jeremy Nicoll - news posts
> <jn.nntp.scrap...@wingsandbeaks.org.uk> wrote:
>>
>> Perhaps a little more detail in your reply?
>>
>> --
>
>
> It is possible to have more than one version of ooRexxx installed on a
> system and to switch back and forth between them. You can only have
> one ooRexx running at any one time. Jeremy was correct that the main
> obstacle is rxapi.
>

> C:\Rexx>
>
> If you look closely you can see that I have all the way from ooRexx
> 3.0.0 to a pretty current build from trunk installed. I switch
> between any 2 versions by stopping rxapi, using sc (service control)to
> stop rxapi, and swapping directory names.
>
> I usually run sc to restart rxapi, but that isn't necessary. Simply
> running a Rexx program will restart rxapi.
>
> It is not necessary to use sc to stop rxapi either, you could use any
> process killer.
>
> --
> Mark Miesfeld
>

So you use the regular install wizard and just point it at a new folder?

LesK

unread,

Apr 9, 2013, 12:55:10 AM4/9/13

to

On 4/8/2013 6:57 PM, Jeremy Nicoll - news posts wrote:
> LesK <5mr...@tampabay.rr.com> wrote:
>
>> RTFM41: readme.pdf
>
> Perhaps a little more detail in your reply?
>

Apologies Jeremy! I'm an old codger and some things are just automatic.

RTFM41: Read The (fine) Manual For Once

And I didn't mean it as flippant as it sounds :-)

Mark Miesfeld

unread,

Apr 9, 2013, 9:58:37 AM4/9/13

to

On Apr 8, 9:14 pm, LesK <5mr...@tampabay.rr.com> wrote:
> On 4/8/2013 10:16 PM, Mark Miesfeld wrote:
>
> > It is possible to have more than one version of ooRexxx installed on a
> > system and to switch back and forth between them. You can only have
> > one ooRexx
>

> So you use the regular install wizard and just point it at a new folder?

I use the regular install package and point it at the installed
folder. To get started, you install a version of ooRexx, then stop
rxapi and copy the entire folder to a new folder.

For instance, install ooRexx 4.0.0 to some location, say C:
\myPersonal.work\ooRexx. Stop rxapi. Copy C:\myPersonal.work\ooRexx
to C:\myPersonal.work\ooRexx.4.0.0. You now have 2 copies of ooRexx
4.0.0.

Then install ooRexx 4.1.0 to C:\myPersonal.work\ooRexx. You now have
ooRexx 4.1.0 installed at C:\myPersonal.work\ooRexx.

To switch between 4.1.0 and 4.0.0 you just do the renaming thing.

sc stop rxapi
ren C:\myPersonal.work\ooRexx C:\myPersonal.work\ooRexx.4.1.0
ren C:\myPersonal.work\ooRexx.4.0.0 C:\myPersonal.work\ooRexx
sc start rxapi

You can not have any opened files in either directory or you can not
rename them. This seems to be the biggest stumbling block for
people. For instance, neither directory can be the current working
directory in any running process on the system. If, from a command
prompt, you cd C:\myPersonal.work\ooRexx, you will not be able to
rename the directory.

Other than that it is just a process of file management.

--
Mark Miesfeld