well - nexec will run a command via the rscd on a remote system.
if you want to call nsh (or nexec) in the external command of a blpackage, or from w/in a batch file via a blpackage you need to have nsh installed on the target of the deploy job. normally target servers do not have nsh installed.
is there a reason you can't do this in a nsh script job directly? why do you need to call a batch file to call a nsh script?
or can you re-write the nsh script in batch ?
is there a reason you can't do this in a nsh script job directly?
why do you need to call a batch file to call a nsh script?
The nsh script that I made is for update internal properties in a custom class depending on the action made in the .bat
Is possible to execute blcli commands from a .bat to update internal properties in a custom class?
is the blcli installed on the target server? if not, no.
what would make more sense is to have a nsh script job run whatever you need to run against the target to get the values you want, and then make the blcli calls w/ that information from the nsh script.
or use compliance and the 'persist' function to do the same.
OK, Thank you, I'll try to do ...