01-09-2018 07:44 AM
Write a .bat that runs putty with a script file. See https://stackoverflow.com/questions/39361444/automating-command-script-execution-using-putty for hints. When putty has finished, use the appropriate Windows command to show a message. See hints here: https://stackoverflow.com/questions/12514475/how-can-you-create-pop-up-messages-in-a-batch-script
01-09-2018 08:04 AM - edited 01-09-2018 08:05 AM
Thanks for the response....
Actually i need sas code which i will use while running sas macro on putty and once the sas program done...will receive message like done or exit 1...and popup will generate on desktop/laptop after receiving message on putty......
Hope you are getting my points....
01-09-2018 08:49 AM
SAS macros cannot be run on putty, they are parts of SAS programs. Putty is just a terminal emulator/SSH client that can't run any SAS code.
Please describe in detail what you are trying to do, where SAS programs will run, and where putty comes into play.
eg do you want to use putty from within a SAS program to control actions on another computer, or do you want to use putty from the commandline to run a SAS program on another computer?
01-09-2018 09:33 AM
We are using putty for command line to run sas program (UNIX command)..and once sas program done, we are receiving massage like done / exit 1....so for the same we will require SAS code which directly popup on desktop screen.....
Also we have sas macro which indicating through email...but my specific requirement is sas code which shows popup once my sas program done on putty...
01-10-2018 02:57 AM
AFAIK, putty (and other telnet type clients) does not have a mechanism that allows to trigger a pop-up on the client side when something happens on the server. You can only write a .bat that executes a putty with a script (which includes a "exit" command to the server when the SAS batch has finished) and displays a message once putty terminates.
01-10-2018 02:59 AM
PS I get the notion that you are trying to reinvent the wheel here. Things like that (messages when jobs terminate etc) are best handled by a proper scheduling system. No need to waste brain-cycles on that particular problem, that's been solved for a long time.