Re: [Oorexx-devel] ooRexx 4.0 Beta / possible change to rxapi ?

[Mark M. <mie...@gm...>]

On Fri, Apr 10, 2009 at 12:47 AM, Rainer Tammer <ta...@ta...> wrote:

> Mark Miesfeld wrote:
>> ... cut for clarity ...
>>
>> I think if you look closely enough, you will see that as you start
>> running the examples, rxapi gets started.

> # ps -ef | grep rxa;ps -ef | grep rex
>     foo  950374  970922   0 09:39:43  pts/1  0:00 /usr/bin/rexx
> ./sfserver.rex
>
> Sorry, there is no rxapi started. The old rxapi.pid file is still there.
> User foo can not overwrite the PID file.

Okay, I didn't realize you forced things so rxapi couldn't start at
all.  It turns out that none of the Unix services require the function
that rxapi provides.

On Windows, if rxapi is not running the interpreter tries to start it.
 I'm sure it is the same on Unix.  On Windows, if you stop the rxapi
service, then when you start a Rexx program, the interpreter starts
rxapi as a normal process.

If you force things so rxapi can not run no matter what, then any Rexx
programs that require the function rxapi provides will fail.

Try this program:

do i = 1 to 5
  line = 'Line:' i
  queue line
end
say 'Done'

E:\work.ooRexx\3.x\main\samples>myTest.rex
     5 *-*   queue line
Error 48 running E:\work.ooRexx\3.x\main\samples\myTest.rex line 5:
Failure in system service
Error 48.1:  Failure in system service: SYSTEM QUEUE

So, the bottom line is the Unix samples run because they don't require
any of the rxapi function.

--
Mark Miesfeld