LabVIEW
Command Line support
Most of the problem is clear, except the actual problem.
@lvbms wrote:
The problem statement is : After executing parameter from the command line, it doesn't return to the command prompt even it is exited the command line. Which is a normal behavior with any cmd line executable.
Surly, if I type "ipconfig" from the command line, it returns to the command line?
I'd expect the LabVIEW exe to behave the same: if the exe quits, the command line should be returned to the user.
Not sure if there still is a misunderstanding, or that this is how CL behaves, or if it's something you or the used library caused... Can you post a (minimal, complete and verifiable) example?
Search LabVIEW like a graph! 
@lvbms wrote:
You are right wiebe@CARYA.
"Automation" is the name of Labview executable.
Which gets started from the command line and UI appears if no parameters are passed.
However if we passed any parameter like -h for help or -v for version. It will return help info about the all the parameters that can be used from command line and exit.
However if it is passed with script name with -r parameter it will execute the script and return to command line or exit.
The problem statement is : After executing parameter from the command line, it doesn't return to the command prompt even it is exited the command line. Which is a normal behavior with any cmd line executable.
Hope I'm clear now.
Actually, no, that's only normal if you already have the command line open from the beginning. Any other time, it opens up the CLI, completes the task, then closes it again. (Try running "ping" from the run window.)
