Re^5: Perl Scripts on systems without perl environments.

The end of support is exactly why this solution is being put into place. Then windows support is new and needs to have the same sort of automation that was available for the old OS/2 functionality.

OS/2 has Rexx native, windows does not. So a change begins, and the two databases must be kept in sync until the OS/2 is gone.

Oh, and that is an end of SALES support. You won't be able to buy new copies of OS/2 after that. IBM typically supports products for three to seven years after dropping sales.

Skip

Comment on Re^5: Perl Scripts on systems without perl environments. Download Code

Replies are listed 'Best First'.
Re^6: Perl Scripts on systems without perl environments. by husker (Chaplain) on Nov 07, 2005 at 22:25 UTC
So what you really need is a Rexx-to-Perl converter. Develop in Rexx for OS/2 .. when it works, translate to Perl for the Windows platform, and run PAR on the result.	[reply]
Re^7: Perl Scripts on systems without perl environments. by parv (Parson) on Nov 08, 2005 at 00:42 UTC
That reminds there is/may be a Rexx-to-NetRexx converter; use NetRexx language to write (access) Java code (libraries) in Rexx.	[reply]