this may sound backward .. but it worked for us. We don't have same issue. Our 7.5x to 7.6x macro is not executing the std out error, otherwise macro works fine. What we did was continue using version of the macro we upgraded from (6.3p 20) runmacro - until we/bmc can resolve the issue. The impact to business was big as automation to Tec/Netcool was dependent of that. We still have the issue, so we have moved to Web Services as a primary bridge. Macro called externally.
So in your instance, try the 7.1 ./bin/runmacro only, does this connect and execute? _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
