No, there's currently no way to test this, other than maybe enabling signal on failure and trapping the situation that way.
Rick On Tue, Jul 21, 2009 at 5:01 PM, James Johnson<j...@iland.net> wrote: > Okay, I can accept that. > > Is there a way to test if a DIRECT_ENVIRONMENT is available? > I could issue some command and check the return code. But how do > I tell the difference between an unregistered environment, RC=30, and a > command > handler error which could also be 30? > > James Johnson > > > Rick McGuire wrote: >> The subcommand handers accessed by RXSUBCOM are the older legacy style >> of subcommand handlers that must be registered with the rxapi daemon. >> The DIRECT_ENVIRONMENT handers are the new style, which is totally >> managed by the interpreter instance and not registered in process. >> Since RXSUBCOM is just an interface to the RexxXXXXXXSubcom APIs, it >> has no knowledge of the direct ones. >> >> Rick >> >> On Tue, Jul 21, 2009 at 4:08 PM, James Johnson<j...@iland.net> wrote: >> >>> I have an application that uses the new 4.0 APIs to establish an >>> Interpreter instance. I pass to the "RexxCreateInterpreter" a set of >>> options, >>> one of which is "DIRECT_ENVIRONMENTS". >>> >>> When I issue the command "rxsubcom query rxpipe", I get a return code of >>> 30. I was expecting that a "DIRECT_ENVIRONMENTS" is just another form >>> of a "SubCom" environment. The command "address rxpipe" works and >>> invokes my sub command handler. >>> >>> If the "Address" command recognizes my environment, why doesn't >>> "RxSubCom Query"? >>> >>> James Johnson >>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >>> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> > > > ------------------------------------------------------------------------------ > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
