topic Re: Shipping PATH to a Custom Tool in Server Management - Systems Insight Manager

Shipping PATH to a Custom Tool

David J. Nelson — Mon, 02 Jul 2007 16:39:55 GMT

I wrote a Perl script that I snapped into SIM under Custom Tools. When I run the script from the command line, everything works. When I run it from SIM, nothing works.

After toiling for a while, I found that if I front-end my Perl script with batch file that sets up PATH information, it works.

Any ideas?

Re: Shipping PATH to a Custom Tool

David Claypool — Tue, 03 Jul 2007 14:57:50 GMT

Which OS are we talking about? If it's *nix the $PATH may need to be exported.

Re: Shipping PATH to a Custom Tool

David J. Nelson — Tue, 03 Jul 2007 15:04:28 GMT

Ahh... if it were only *nix! :)

This is Windows 2003...

Re: Shipping PATH to a Custom Tool

David Claypool — Tue, 10 Jul 2007 12:40:01 GMT

Okay, how are you using it? For example:

CustomTool1: set

[When run shows the values of all environment variables including path]

CustomTool2: path

[When run shows the value of the current path]

CustomTool3: joe.bat (which contains 'echo %PATH%')

[When run shows the value of the current path]

CustomTool4: echo %path%

[When run shows '192.168.1.1:5989ath' because %p is a reserved replaceable parameter for HP SIM for the IP address of the WBEM proxy (See online help for HP SIM at https://localhost:50000/mxhelp/mxportal/en/useTools_customTools_ref.html#SubstitutionTable or the HP SIM User Guide)]

CustomTool5: echo %PATH%

[When run shows error dialog "One of the tool's parameterized strings failed to expand."]