Are you running the command on Application server?
Try providing the complete path qith server name in NSH format.
Yes. I am executing the command in the Appserver. The path I provided is in NSH format. I tried inputting with //servername/path which threw an error "Cannot use remote path for file transfer"
the path must be local and you must not be 'cd'd' into a server. so in the screenshot above 'pwd' shows you are cd'd to some server. so you need to run 'cd //@/' first to get you back to 'home' and then your path should be local to there.
you are still cd'd into a server there:
prime% cd //blapp85-red6x64
blapp85-red6x64% cd //@/
see how cd //@/ returns me to / of the system i started nsh on ?
Thank you Bill. I cd'd to @ and it worked fine. The actual problem is now resolved.
Per my understanding '@' refer to the Appserver on which the Job is running? In such case, if I have all the files stored in server A, and the Job is executed in the Appserver 'server B'; how shall I use this command?
My script requires me to cd to a specific location like /tmp/; create files based on the analysis. If I append the line cd //@/ to the script, will not the execution path move to the Appserver's working directory even if I have server A as the target server? Please clarify as I am confused here.
Thank you in advance
@ is the system that the nsh binary was started on. so if you start nsh on your desktop (including nsh here) and cd over to some host then do cd //@/ it gets you back to / of your desktop.
why are all the files stored on appserver A ? if you are running a script and need to get the output, won't they be stored on the appserver running the job ?