Hello Listers, ARS 6.3 Patch 21 MS SQLServer 2000 I am trying to update a runmacro used in an Escalation Run Process. Is there anyway to debug the runmacro to see why it stopped working? The macro logs in as a valid user. Performs a query passed in by the -p parameter and Reports To File a simple tab delimited ARS Report.
This newly recorded macro works in the WUT but will not produce any output when executed with runmacro. I have all of the paths specified. and the servername is fully qualified in the macro as well as with the -x parameter. Workflow.log doesn't get activated by the runmacro and there is little to see in the API, SQL and Escalation logs. I guess I'm looking for the verbose switch? TIA, John J. Reiser Software Development Analyst Remedy Administrator/Developer Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
