> Do you mean output generated from lines of code before the execio was
executed?

No - the execio write successfully the file to the disk. If the file didn't
exist before I start the script,
it exist with the expected content after I start the script and the script
abended when it reach the 
execio statement. 

If the file already exist before I start the script, the execio change the
content of the first line, 
before it abended.

If the file that already exist before I start the script has two lines and
the script write only 1 line,
then after the script abended only the first line changed.

In my opinion this is also not correct. The original execio on the mainframe
overwrite an existing file.
On the other hand the original execio know the parameter open to reopen an
existing file if you
want to  extend an existing file. But in my opinion to modify an existing
file is the worst alternative,
because it is necessary to delete the file before.

Regards
Roger

-----Ursprüngliche Nachricht-----
Von: Jeremy Nicoll - ml sourceforge [mailto:jn.ml.sfrg...@letterboxes.org] 
Gesendet: Mittwoch, 4. Juli 2012 01:38
An: oorexx-users@lists.sourceforge.net
Betreff: Re: [Oorexx-users] Some problems with EXECIO and ::requires

"Roger Bilau" <s...@bilau.de> wrote:

> The first example stop always after the ADDRESS HOSTEMU line, Windows 
> show me two windows with a german messages, both with 'Open Object 
> REXX interface no longer works' and some additional text '. search for 
> problem solution .' and 'the program was closed about a problem .'.

That means the rexx interpreter has crashed...

>Strange is that the correct output is generated,

Do you mean output generated from lines of code before the execio was
executed?

> but the script never reached the exit statement. 

It can't after the interpreter has crashed...



I reported in bug #3535883 - see:

https://sourceforge.net/tracker/?func=detail&atid=684730&aid=3535883&group_i
d=119701

that execio crashed the interpreter under Win XP, but developers said the
problem didn't affect Win7 64.  Someone will need to find out whether your
problem is caused by the same or a different underlying reason.


--
Jeremy Nicoll - my opinions are my own

----------------------------------------------------------------------------
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will
include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users

Reply via email to