Re: [Oorexx-devel] CMS/TSO Pipelines support for Rexx

2009-05-14 Thread James Johnson
Rony G. Flatscher wrote: James, please lookup rexxpg.pdf, chapter 9, Rexx C++ Application Programming Interfaces. There you will find the C++ APIs documented, and among the documentation you will find the new options and there the option named DIRECT_ENVIRONMENTS which supplies a context

Re: [Oorexx-devel] CMS/TSO Pipelines support for Rexx

2009-05-14 Thread Rick McGuire
Sounds like a bug to meif you can provide a sample to debug it, that would be useful. Rick On Thu, May 14, 2009 at 4:37 PM, James Johnson j...@iland.net wrote: Rony G. Flatscher wrote: James, please lookup rexxpg.pdf, chapter 9, Rexx C++ Application Programming Interfaces. There you

Re: [Oorexx-devel] CMS/TSO Pipelines support for Rexx

2009-05-14 Thread Rick McGuire
James, The CallProgram() API was not performing any path or extension resolution at all, so I'm a bit puzzled with your statement that this worked on the first invocation...it should not have worked at all. I've fixed this, but I'd like to verify with a sample program from you. If you'll open a

Re: [Oorexx-devel] CMS/TSO Pipelines support for Rexx

2009-05-14 Thread James Johnson
I went back and check my source code and I supply an extension on the first invocation. When I remove the extension it fails with error code 3001. Do you still need a sample program? Rick McGuire wrote: James, The CallProgram() API was not performing any path or extension resolution at all,

Re: [Oorexx-devel] CMS/TSO Pipelines support for Rexx

2009-05-12 Thread Rony G. Flatscher
James, please lookup rexxpg.pdf, chapter 9, Rexx C++ Application Programming Interfaces. There you will find the C++ APIs documented, and among the documentation you will find the new options and there the option named DIRECT_ENVIRONMENTS which supplies a context for the purpose you need.

Re: [Oorexx-devel] CMS/TSO Pipelines support for Rexx

2009-05-12 Thread Rick McGuire
James, The legacy-style APIs are being retired and will not be enhanced in the future. That API was one designed over 20 years ago specifically for OS/2 and unfortunately got propagated as standard which it was never intended to be. New APIs will be based on the API system. The other bad news

[Oorexx-devel] CMS/TSO Pipelines support for Rexx

2009-05-11 Thread James Johnson
I have a library that implements CMS/TSO Piprlines support for the PC. I have interfaced this library to ooRexx 4.0. To accomplish this I had to make so changes to the 4.0 beta. 1) The interface is thru a SubCom environment. I had to modify the subcom CommandHandler to pass a CallContext