Execute Script in Terminal and Variables..
Hi,
I am trying to create a couple of scripts that can be run (ideally from an external file) which use the internal RDM variables and came across the "Execute Script in Terminal" feature. So I created a simple test script that has variables in it ($IP$ for example) and also an equivalent typing macro (saved in RDM).
When I use the "Execute Script in Terminal" button, and select either the typing macro or the script text file, both options do not resolve the variables - but just send the text ($IP$).
If I run the typing macro from the "Macro/Script" button - it does work and resolve the variables.
Is this working as designed?
Thanks,
Steve
All Comments (12)
Hello,
What type of script are you trying to run?
Are you able to provide an example?
Best regards,
Mark Beausejour
I create a "Typing Macro" script which simply contains
!$IP${ENTER}
I then started a SSH session to a host and used the "Execute Script in Terminal" button and selected the script I saved. When it executes it does not resolve the variable name - it just displays the text !$IP$
I also wanted to use the "Script File" option in the "Execute Script in Terminal" dialog, but again when I try to load a simple script (same content as above) - it does not resolve the variable names.
(When I used the Macro/Script button and select the macro I saved it does resolve the variables - however, I really wanted to use the "Script File" option if possible.)
Cheers,
Steve
RDM_ExecMacro.png
RDM_Script.png
Hello,
Thank you for your reply.
This has been assigned to one of our engineers.
Best regards,
Mark Beausejour
Hello Steve,
Could you tell us what version of RDM you are using? I'm using the latest stable version (12.5.4.0) and I'm unable to reproduce the issue. The $IP$ variable is resolved when using either the "Script file" option or the "typing macro" option.
Regards,
Hubert Mireault
I am using 12.5.4.0 - the latest...
The connections are sub-connections of a host entry - if that makes a difference.
Steve.
Even when using subconnections of a host entry, I wasn't able to reproduce it. Would it be possible for you to export the entries with which you can reproduce the issue and send it to me through a private message? You can export your entries by selecting them in the tree view and right click > Export > Export selection (.rdm). Please make sure not to include any sensitive information in the entries.
This should help us pinpoint the issue much more easily.
Regards,
Hubert Mireault
Hubert,
I have PM'd you the RDM file containing the Rebex SSH entry and the Macro.
Cheers,
Steve
The other thing I have noticed, which I don't really understand why is that the "Execute Script in Terminal" button only displays for a Rebex session and not for other session types - namely Putty. Is there a reason for that?
Cheers,
Steve
Thank you Steve, I'll take a look at the file.
The "execute script in terminal" button is only enabled for entries in which we can directly send the macro to the control. This is the case for the Rebex SSH/Telnet entries as well as our native SSH/Telnet entries, but not for an external application like PuTTY.
Regards,
Hubert Mireault
I can reproduce the issue using the export you've sent me, I'll be looking at this today but I might only get back at you about it Monday.
Regards,
Hubert Mireault
Hello,
I've managed to identify the issue with the Rebex+PuTTY terminals specifically in this scenario, and with that fixed, the issue can't be reproduced in our environment. The change will be available in the next RDM update. Thanks for the help figuring this out :)
Regards,
Hubert Mireault
Great service.
Thanks.