jEdit roller coaster

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

jEdit roller coaster

Robert L Hamilton

   This is a complete roller coaster. jEdit works for awhile and then the
   results do not show up although it must be parsing the code because if the
   netrexx code has an error,  the error messages show up. This is really going
   to be the way to learn netRexx AND get a handle on JAVA. . . I'm convinced of that.  It's taking some
   time to get it under control.

   thanks for the help and enjoy the day -- or evening -- whatever.

bobh

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: jEdit roller coaster

Kermit Kiser
Hi Bob -

I am not sure from your message exactly what you are doing but if you are running NetRexx scripts using the NetRexxScript plugin there is a known problem which could be causing the results that you are seeing. If the script executes the "EXIT" instruction, the NetRexx interpreter thinks you are done with it and closes the output stream. NetRexxScript currently has no way to detect that situation and reinitialize the interpreter so that output is routed to the display window. As a result the output will vanish until you restart jEdit. I hope to find a way to fix this in the next release but it may have to wait until NetRexx is open source and I can find a way to detect that situation.

Meanwhile - change all "EXIT" instructions to "RETURN" instructions and you should not have that problem.

-- Kermit


On 7/8/2010 11:27 AM, Robert Hamilton wrote:

   This is a complete roller coaster. jEdit works for awhile and then the
   results do not show up although it must be parsing the code because if the
   netrexx code has an error,  the error messages show up. This is really going
   to be the way to learn netRexx AND get a handle on JAVA. . . I'm convinced of that.  It's taking some
   time to get it under control.

   thanks for the help and enjoy the day -- or evening -- whatever.

bobh

_______________________________________________ Ibm-netrexx mailing list [hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

net2rexx and reyc status??

kenner
In reply to this post by Robert L Hamilton

So what's the latest? I still can't find anything on kenduh. I was successful on porting a standard mvs rexx exec to netrexx and creating the byte code which runs on OMVS and on Windoze XP. Funny, it runs faster on XP. What nett2rex generated was a good starting point but after changing all the I/O code the finished version had little resemblance to the original. I'll post if anyone shows interest and I'd run it thru Reyc if it ever sees the light of day. Uebrigens, I'm now converting Mark Swain's 3 sort routines. We'll see how that goes.


Kenneth Klein

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

newest challenge for the nettrexx newbee.

kenner
In reply to this post by Kermit Kiser

How can I tell from this where the bad character is? Can I find the renegade byte with VI? This source was ftped from mvs in ascii and I'm running it under omvs.


CP1ZA A00002T Thu 15:21:56 /u/a00002t/netrexx % Rexx2Nrx.sh sort1.rexx -verbose5
echo off
 Rexx2Nrx: The classic REXX to NetRexx converter
 copyright (c) Thomas Schneider, 2000-2002, all rights reserved
 29.09.2002 : default NetRexx and Java compilation added

File: sort1.rexx
================

classic REXX Parsing of file: sort1.rexx with rex_pars.nrx vs 4.01
Copyright (c) Thomas Schneider, 2000-2003, all rights reserved.

Exception in thread "main" netrexx.lang.NotCharacterException: @@▒▒▒▒@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
        at netrexx.lang.Rexx.padcheck(Rexx.nrx:818)
        at netrexx.lang.Rexx.c2x(Rexx.nrx:960)
        at rex_pars.in_token(rex_pars.nrx:2816)
        at rex_pars.in_expression(rex_pars.nrx:8219)
        at rex_pars.in_expression(rex_pars.nrx:8151)
        at rex_pars.in_CMD(rex_pars.nrx:9389)
        at rex_pars.in_statement(rex_pars.nrx:7543)
        at rex_pars.parser(rex_pars.nrx:7402)
        at rex_pars.process_infile(rex_pars.nrx:1613)
        at rex_pars.main(rex_pars.nrx:1527)
Exit 1

Kenneth Klein
Systems Specialist
502-868-3644
859-750-5179 (Cell)
502-868-2298 (Fax)
[hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: jEdit roller coaster

Robert L Hamilton
In reply to this post by Kermit Kiser
I restarted jEdit with the bat and with the jar  file; still no luck.

The thing was working before; something I've done has changed jEddit.

This thing has got to work . . . .

bobh

On Thu, Jul 8, 2010 at 2:18 PM, Kermit Kiser <[hidden email]> wrote:
Hi Bob -

I am not sure from your message exactly what you are doing but if you are running NetRexx scripts using the NetRexxScript plugin there is a known problem which could be causing the results that you are seeing. If the script executes the "EXIT" instruction, the NetRexx interpreter thinks you are done with it and closes the output stream. NetRexxScript currently has no way to detect that situation and reinitialize the interpreter so that output is routed to the display window. As a result the output will vanish until you restart jEdit. I hope to find a way to fix this in the next release but it may have to wait until NetRexx is open source and I can find a way to detect that situation.

Meanwhile - change all "EXIT" instructions to "RETURN" instructions and you should not have that problem.

-- Kermit



On 7/8/2010 11:27 AM, Robert Hamilton wrote:

   This is a complete roller coaster. jEdit works for awhile and then the
   results do not show up although it must be parsing the code because if the
   netrexx code has an error,  the error messages show up. This is really going
   to be the way to learn netRexx AND get a handle on JAVA. . . I'm convinced of that.  It's taking some
   time to get it under control.

   thanks for the help and enjoy the day -- or evening -- whatever.

bobh

_______________________________________________ Ibm-netrexx mailing list [hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]




_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: jEdit roller coaster

Kermit Kiser
Bob --

It is possible that you configured jEdit to run in "background" mode when you installed it. If that is the case, then closing the jEdit window does not actually shut it down. Try one of the following options to check if it fixes it:

1) Reboot PC and startup jEdit

or

2) Close jEdit window, then Go to "Start=>All Programs=>jEdit=>Quit jEdit Server", then startup jEdit

Let me know how it goes.

-- Kermit


On 7/8/2010 1:56 PM, Robert Hamilton wrote:
I restarted jEdit with the bat and with the jar  file; still no luck.

The thing was working before; something I've done has changed jEddit.

This thing has got to work . . . .

bobh

On Thu, Jul 8, 2010 at 2:18 PM, Kermit Kiser <[hidden email]> wrote:
Hi Bob -

I am not sure from your message exactly what you are doing but if you are running NetRexx scripts using the NetRexxScript plugin there is a known problem which could be causing the results that you are seeing. If the script executes the "EXIT" instruction, the NetRexx interpreter thinks you are done with it and closes the output stream. NetRexxScript currently has no way to detect that situation and reinitialize the interpreter so that output is routed to the display window. As a result the output will vanish until you restart jEdit. I hope to find a way to fix this in the next release but it may have to wait until NetRexx is open source and I can find a way to detect that situation.

Meanwhile - change all "EXIT" instructions to "RETURN" instructions and you should not have that problem.

-- Kermit



On 7/8/2010 11:27 AM, Robert Hamilton wrote:

   This is a complete roller coaster. jEdit works for awhile and then the
   results do not show up although it must be parsing the code because if the
   netrexx code has an error,  the error messages show up. This is really going
   to be the way to learn netRexx AND get a handle on JAVA. . . I'm convinced of that.  It's taking some
   time to get it under control.

   thanks for the help and enjoy the day -- or evening -- whatever.

bobh

_______________________________________________ Ibm-netrexx mailing list [hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]




_______________________________________________ Ibm-netrexx mailing list [hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: jEdit roller coaster

Robert L Hamilton
That seemed to work; quit and do a start.

thnx

bobh

On Thu, Jul 8, 2010 at 7:09 PM, Kermit Kiser <[hidden email]> wrote:
Bob --

It is possible that you configured jEdit to run in "background" mode when you installed it. If that is the case, then closing the jEdit window does not actually shut it down. Try one of the following options to check if it fixes it:

1) Reboot PC and startup jEdit

or

2) Close jEdit window, then Go to "Start=>All Programs=>jEdit=>Quit jEdit Server", then startup jEdit

Let me know how it goes.

-- Kermit



On 7/8/2010 1:56 PM, Robert Hamilton wrote:
I restarted jEdit with the bat and with the jar  file; still no luck.

The thing was working before; something I've done has changed jEddit.

This thing has got to work . . . .

bobh

On Thu, Jul 8, 2010 at 2:18 PM, Kermit Kiser <[hidden email]> wrote:
Hi Bob -

I am not sure from your message exactly what you are doing but if you are running NetRexx scripts using the NetRexxScript plugin there is a known problem which could be causing the results that you are seeing. If the script executes the "EXIT" instruction, the NetRexx interpreter thinks you are done with it and closes the output stream. NetRexxScript currently has no way to detect that situation and reinitialize the interpreter so that output is routed to the display window. As a result the output will vanish until you restart jEdit. I hope to find a way to fix this in the next release but it may have to wait until NetRexx is open source and I can find a way to detect that situation.

Meanwhile - change all "EXIT" instructions to "RETURN" instructions and you should not have that problem.

-- Kermit



On 7/8/2010 11:27 AM, Robert Hamilton wrote:

   This is a complete roller coaster. jEdit works for awhile and then the
   results do not show up although it must be parsing the code because if the
   netrexx code has an error,  the error messages show up. This is really going
   to be the way to learn netRexx AND get a handle on JAVA. . . I'm convinced of that.  It's taking some
   time to get it under control.

   thanks for the help and enjoy the day -- or evening -- whatever.

bobh

_______________________________________________ Ibm-netrexx mailing list [hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]




_______________________________________________ Ibm-netrexx mailing list [hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]




_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: jEdit roller coaster

Robert L Hamilton
In reply to this post by Kermit Kiser
2) worked; but how do we stay out of that loop?

I really need to get jEdit into a more rational mode.  Is NetRexx the problem?

thanx

bobh

On Thu, Jul 8, 2010 at 7:09 PM, Kermit Kiser <[hidden email]> wrote:
Bob --

It is possible that you configured jEdit to run in "background" mode when you installed it. If that is the case, then closing the jEdit window does not actually shut it down. Try one of the following options to check if it fixes it:

1) Reboot PC and startup jEdit

or

2) Close jEdit window, then Go to "Start=>All Programs=>jEdit=>Quit jEdit Server", then startup jEdit

Let me know how it goes.

-- Kermit



On 7/8/2010 1:56 PM, Robert Hamilton wrote:
I restarted jEdit with the bat and with the jar  file; still no luck.

The thing was working before; something I've done has changed jEddit.

This thing has got to work . . . .

bobh

On Thu, Jul 8, 2010 at 2:18 PM, Kermit Kiser <[hidden email]> wrote:
Hi Bob -

I am not sure from your message exactly what you are doing but if you are running NetRexx scripts using the NetRexxScript plugin there is a known problem which could be causing the results that you are seeing. If the script executes the "EXIT" instruction, the NetRexx interpreter thinks you are done with it and closes the output stream. NetRexxScript currently has no way to detect that situation and reinitialize the interpreter so that output is routed to the display window. As a result the output will vanish until you restart jEdit. I hope to find a way to fix this in the next release but it may have to wait until NetRexx is open source and I can find a way to detect that situation.

Meanwhile - change all "EXIT" instructions to "RETURN" instructions and you should not have that problem.

-- Kermit



On 7/8/2010 11:27 AM, Robert Hamilton wrote:

   This is a complete roller coaster. jEdit works for awhile and then the
   results do not show up although it must be parsing the code because if the
   netrexx code has an error,  the error messages show up. This is really going
   to be the way to learn netRexx AND get a handle on JAVA. . . I'm convinced of that.  It's taking some
   time to get it under control.

   thanks for the help and enjoy the day -- or evening -- whatever.

bobh

_______________________________________________ Ibm-netrexx mailing list [hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]




_______________________________________________ Ibm-netrexx mailing list [hidden email]

_______________________________________________
Ibm-netrexx mailing list
[hidden email]




_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: jEdit roller coaster

Kermit Kiser
The only thing that I recall that causes this problem is the use of the EXIT instruction in a NetRexx script. As I said before, you should be OK if you use RETURN to end your scripts rather than EXIT.

Have you checked your test scripts to make sure they do not use EXIT instructions? If so, can you share a code example that causes the problem?

Unfortunately, Mike did not document exactly what happens when the NetRexxA interface is used to interpret scripts containing EXIT instructions so it may be a while before we can fix this problem. Sometime after the open source release of NetRexx, I plan to put out a new NetRexxScript release that fixes these issues.

-- Kermit


On 7/8/2010 7:17 PM, Robert Hamilton wrote:
2) worked; but how do we stay out of that loop?

I really need to get jEdit into a more rational mode.  Is NetRexx the problem?

thanx

bobh

On Thu, Jul 8, 2010 at 7:09 PM, Kermit Kiser <[hidden email]> wrote:
Bob --

It is possible that you configured jEdit to run in "background" mode when you installed it. If that is the case, then closing the jEdit window does not actually shut it down. Try one of the following options to check if it fixes it:

1) Reboot PC and startup jEdit

or

2) Close jEdit window, then Go to "Start=>All Programs=>jEdit=>Quit jEdit Server", then startup jEdit

Let me know how it goes.

-- Kermit



On 7/8/2010 1:56 PM, Robert Hamilton wrote:
I restarted jEdit with the bat and with the jar  file; still no luck.

The thing was working before; something I've done has changed jEddit.

This thing has got to work . . . .

bobh

On Thu, Jul 8, 2010 at 2:18 PM, Kermit Kiser <[hidden email]> wrote:
Hi Bob -

I am not sure from your message exactly what you are doing but if you are running NetRexx scripts using the NetRexxScript plugin there is a known problem which could be causing the results that you are seeing. If the script executes the "EXIT" instruction, the NetRexx interpreter thinks you are done with it and closes the output stream. NetRexxScript currently has no way to detect that situation and reinitialize the interpreter so that output is routed to the display window. As a result the output will vanish until you restart jEdit. I hope to find a way to fix this in the next release but it may have to wait until NetRexx is open source and I can find a way to detect that situation.

Meanwhile - change all "EXIT" instructions to "RETURN" instructions and you should not have that problem.

-- Kermit



_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: jEdit roller coaster

Robert L Hamilton
I get this :

  this is a comment 
Thu Jul 08 21:13:08 CDT 2010


from this nrx  code:

say  "  this is a comment  "

say date()

Using RETURN works and jEdit keeps 'running' .

Thanks and Enjoy the Day

bobh






_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: newest challenge for the nettrexx newbee.

Thomas.Schneider.Wien
In reply to this post by kenner
Hello Kenneth,
   1.) You might use the option -TT (trace Tokens) to get a trace of the tokens to find the place more exactly.
   2.) When this does NOT help, please send me the your file sort1.rexx privately to [hidden email] so that I
can investigate the problem.
Tom.
=============================================================================
   could you please send me the source file
Am 08.07.2010 22:24, schrieb [hidden email]

How can I tell from this where the bad character is? Can I find the renegade byte with VI? This source was ftped from mvs in ascii and I'm running it under omvs.


CP1ZA A00002T Thu 15:21:56 /u/a00002t/netrexx % Rexx2Nrx.sh sort1.rexx -verbose5
echo off
 Rexx2Nrx: The classic REXX to NetRexx converter
 copyright (c) Thomas Schneider, 2000-2002, all rights reserved
 29.09.2002 : default NetRexx and Java compilation added

File: sort1.rexx
================

classic REXX Parsing of file: sort1.rexx with rex_pars.nrx vs 4.01
Copyright (c) Thomas Schneider, 2000-2003, all rights reserved.

Exception in thread "main" netrexx.lang.NotCharacterException: @@▒▒▒▒@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
        at netrexx.lang.Rexx.padcheck(Rexx.nrx:818)
        at netrexx.lang.Rexx.c2x(Rexx.nrx:960)
        at rex_pars.in_token(rex_pars.nrx:2816)
        at rex_pars.in_expression(rex_pars.nrx:8219)
        at rex_pars.in_expression(rex_pars.nrx:8151)
        at rex_pars.in_CMD(rex_pars.nrx:9389)
        at rex_pars.in_statement(rex_pars.nrx:7543)
        at rex_pars.parser(rex_pars.nrx:7402)
        at rex_pars.process_infile(rex_pars.nrx:1613)
        at rex_pars.main(rex_pars.nrx:1527)
Exit 1

Kenneth Klein
Systems Specialist
502-868-3644
859-750-5179 (Cell)
502-868-2298 (Fax)
[hidden email]
_______________________________________________ Ibm-netrexx mailing list [hidden email]


--
Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Tom. (ths@db-123.com)
Reply | Threaded
Open this post in threaded view
|

Re: newest challenge for the nettrexx newbee.

kenner

This is on z/os 1.10 omvs but on XP SP3 it makes it to the netrexx compiler:  

CP1ZA A00002T Mon 14:12:59 /u/a00002t/netrexx % rx2n.sh sort1
short version of Rexx2Nrx with short output (verbose1, with timing info)
Rexx2Nrx: The classic REXX to NetRexx converter
copyright (c) Thomas Schneider, 2000-2002, all rights reserved
          for support e-mail: [hidden email]
Exception in thread "main" netrexx.lang.NotCharacterException: @@▒▒▒▒@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
        at netrexx.lang.Rexx.padcheck(Rexx.nrx:818)
        at netrexx.lang.Rexx.c2x(Rexx.nrx:960)
        at rex_pars.in_token(rex_pars.nrx:2816)
        at rex_pars.in_expression(rex_pars.nrx:8219)
        at rex_pars.in_expression(rex_pars.nrx:8151)
        at rex_pars.in_CMD(rex_pars.nrx:9389)
        at rex_pars.in_statement(rex_pars.nrx:7543)
        at rex_pars.parser(rex_pars.nrx:7402)
        at rex_pars.process_infile(rex_pars.nrx:1613)
        at rex_pars.main(rex_pars.nrx:1527)
Exit 1

Furthermore, on omvs the pp.log is nothing but unintelligable characters.



Windoze:

File: sort1.rexx
================

 
       77 lines of file: sort1.rexx parsed (no warnings, no errors)

File: sort1
===========

Line 67: Warning: Exposed unknown Stem 'foo' has NO initial value!
Line 67: Warning: Exposed unknown Stem 'foo' has NO initial value!
Line 48: Warning: Global unknown Id 'e' has NO initial value!
Rexx Type & Code analysis used:      0.03 seconds
classic REXX Code & Type analysis completed (3 warnings, no errors)

File: sort1
===========

Rexx to NetRexx translation used:     0.05 seconds (0.00100 sec/line)
Rexx2Nrx translation of: 'sort1' completed (3 warnings, no errors)
NetRexx portable processor, version 2.05
Copyright (c) IBM Corporation, 2005.  All rights reserved.
Program sort1.nrx
  93 +++ method sort1() static public ;                                          
     +++                ^^^^^^
     +++ Error: Not allowed for a constructor
Compilation of 'sort1.nrx' failed [one error]
Translate time: 0.4s


CP1ZA A00002T Mon 14:15:29 /u/a00002t/netrexx % cat sort1.rexx
/*  REXX                                                      */
/* ---------------------------------------------------------------- */
/* Algorithms and techniques for sorting a stemmed "array"          */
/* 18 Oct 1998 Rex Swain, Independent Consultant, www.rexswain.com  */
/* 02 Jan 1999 Added sort3(); added built-in timings                */
/* ---------------------------------------------------------------- */
trace o
/* ---------------------------------------------------------------- */
/* Suppose you want to sort the stem "foo."                         */
/*   so that:       is changed to:                                  */
/*     foo.0 = 4      foo.0 = 4                                     */
/*     foo.1 = 25     foo.1 = -3                                    */
/*     foo.2 = -3     foo.2 = 0                                     */
/*     foo.3 = 0      foo.3 = 12                                    */
/*     foo.4 = 12     foo.4 = 25                                    */
/* Due to limitations in the REXX language, the only reasonable way */
/* to do this is to pass the stem as a global to an internal        */
/* subroutine.                                                      */
/* ---------------------------------------------------------------- */
/* If you want to sort using the dead minimum amount of code, use   */
/* sort1, changing all occurences of "foo" to your stem name.       */
/* This is a vanilla "bubble sort".                                 */
trace i
/***********************
parse upper arg pulleddsn
if pulleddsn = "" then do
    say "Enter dataset name."
    pull pulleddsn
end
************************/
  "ALLOC DD(INDD) DA(calendar) SHR REUSE"
IF RC \= 0 THEN
DO
    SAY 'THERE IS A PROBLEM ALLOCATING YOUR DATASET.'
    SAY 'BE SURE YOU HAVE THE CORRECT DATASET'
    EXIT
END
  "EXECIO * DISKR INDD (STEM foo. FINIS)"
IF RC \= 0 THEN
DO
    SAY 'THERE IS A PROBLEM ALLOCATING YOUR DATASET.'
    SAY 'BE SURE YOU HAVE THE CORRECT DATASET'
    EXIT
END
sc = 0
say time(e)
call sort1
say time(E) sc
/*    /* foo. is now sorted */                                      */
do i = 1 to foo.0
    say foo.i
    end
trace o
exit 1
"EXECIO" foo.0  "DISKW indd (STEM foo. FINIS"
IF RC = 1 THEN SAY 'RETURN FROM WRITE IS GOOD, replaced' RC
else IF RC \= 0 THEN SAY 'RETURN FROM WRITE IS NOT GOOD' RC
else IF RC = 0 THEN SAY 'RETURN FROM WRITE IS GOOD' RC 'wrote' foo.0
"FREE FILE(INDD)"
RETURN Rc
/************************************************/

sort1: procedure expose foo. sc
 n = foo.0
 do i = 1 to n
    do j = i+1 to n
       if foo.i > foo.j then do
        trace o
          temp = foo.i
          foo.i = foo.j
          foo.j = temp
          sc = sc + 1
        trace o
       end
    end
 end
 return


Kenneth Klein
Systems Specialist
502-868-3644
859-750-5179 (Cell)
502-868-2298 (Fax)
[hidden email]



Thomas Schneider <[hidden email]>
Sent by: [hidden email]

07/09/2010 03:31 PM

Please respond to
[hidden email]; Please respond to
IBM Netrexx <[hidden email]>

To
IBM Netrexx <[hidden email]>
cc
Subject
Re: [Ibm-netrexx] newest challenge for the nettrexx newbee.





Hello Kenneth,
   1.) You might use the option -TT (trace Tokens) to get a trace of the tokens to find the place more exactly.
   2.) When this does NOT help, please send me the your file sort1.rexx privately to
[hidden email] so that I
can investigate the problem.
Tom.
=============================================================================
   could you please send me the source file
Am 08.07.2010 22:24, schrieb
kenneth.klein@...:

How can I tell from this where the bad character is? Can I find the renegade byte with VI? This source was ftped from mvs in ascii and I'm running it under omvs.



CP1ZA A00002T Thu 15:21:56 /u/a00002t/netrexx % Rexx2Nrx.sh sort1.rexx -verbose5

echo off

 Rexx2Nrx: The classic REXX to NetRexx converter

 copyright (c) Thomas Schneider, 2000-2002, all rights reserved

 29.09.2002 : default NetRexx and Java compilation added


File: sort1.rexx

================


classic REXX Parsing of file: sort1.rexx with rex_pars.nrx vs 4.01

Copyright (c) Thomas Schneider, 2000-2003, all rights reserved.


Exception in thread "main" netrexx.lang.NotCharacterException: @@▒▒▒▒@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

        at netrexx.lang.Rexx.padcheck(Rexx.nrx:818)

        at netrexx.lang.Rexx.c2x(Rexx.nrx:960)

        at rex_pars.in_token(rex_pars.nrx:2816)

        at rex_pars.in_expression(rex_pars.nrx:8219)

        at rex_pars.in_expression(rex_pars.nrx:8151)

        at rex_pars.in_CMD(rex_pars.nrx:9389)

        at rex_pars.in_statement(rex_pars.nrx:7543)

        at rex_pars.parser(rex_pars.nrx:7402)

        at rex_pars.process_infile(rex_pars.nrx:1613)

        at rex_pars.main(rex_pars.nrx:1527)

Exit 1


Kenneth Klein
Systems Specialist
502-868-3644
859-750-5179 (Cell)
502-868-2298 (Fax)

kenneth.klein@...


_______________________________________________
Ibm-netrexx mailing list
[hidden email]

 



--
Thomas Schneider Projects ReyC & LOGOS on
www.KENAI.com_______________________________________________
Ibm-netrexx mailing list
[hidden email]



_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: newest challenge for the nettrexx newbee.

alansam

Furthermore, on omvs the pp.log is nothing but unintelligable characters.

Probably because Java is writing the log files using UTF-8 encoding and your editor on OMVS is using EBCDIC.  Try getting a copy of viascii (look here: http://www-03.ibm.com/systems/z/os/zos/features/unix/tools/
I'd also recommend using a Telnet/SSH emulator like PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/) for doing UNIXy type things with z/OS rather than sticking with the UNIX shell under TSO/ISPF. Life gets much easier when you treat the UNIX side of z/OS as a real UNIX.  Horses for courses...

Alan.

 
--
Can't tweet, won't tweet!

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Alan

--
Needs more cowbell.
Reply | Threaded
Open this post in threaded view
|

Re: newest challenge for the nettrexx newbee.

Thomas.Schneider.Wien
Hello Alan
   could *you* please *put some light into this* (for me!)

I am *neither* currently aquainted to either OMVS or other (EBCDIC related) details....

I think, your msg. will solve the current problem of Kenneth,
But I would need the details, please !

Thomas.....
=========================================================================================
Am 13.07.2010 03:32, schrieb Alan Sampson:

Furthermore, on omvs the pp.log is nothing but unintelligable characters.

Probably because Java is writing the log files using UTF-8 encoding and your editor on OMVS is using EBCDIC.  Try getting a copy of viascii (look here: http://www-03.ibm.com/systems/z/os/zos/features/unix/tools/
I'd also recommend using a Telnet/SSH emulator like PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/) for doing UNIXy type things with z/OS rather than sticking with the UNIX shell under TSO/ISPF. Life gets much easier when you treat the UNIX side of z/OS as a real UNIX.  Horses for courses...

Alan.

 
--
Can't tweet, won't tweet!
_______________________________________________ Ibm-netrexx mailing list [hidden email]


--
Thomas Schneider Projects ReyC & LOGOS on www.KENAI.com

_______________________________________________
Ibm-netrexx mailing list
[hidden email]

Tom. (ths@db-123.com)