Network Shell Script Jobs let you run a Network Shell script on one or more servers.
To create a Network Shell Script Job you must first add a script to the Depot. See Adding a Network Shell script.
If a Network Shell Script Job runs a local script (that is, the script is copied to one or more remote servers and then executed locally on those servers), you must identify a staging directory that holds the script on each target server. To accomplish this, you must assign a value to the
STAGING_DIR property on all target servers. Only a local script requires a staging directory. For more information see Setting values for system object properties and Changing property values for one or more system objects.
If a Network Shell Script Job includes BLCLI commands that read or write to a local path (a path on the machine where the BLCLI is running), the user must have read or write access to the path at the operating system level. Otherwise the command fails. The "user" in this context is the operating system user, not the BMC Server Automation user. Typically, on Windows the operating system user should have the necessary read and write privileges.
For example, consider a Network Shell Script Job that invokes a BLCLI command that exports an object to a specified directory. In a typical Linux setup, the BLCLI process runs as the user bladmin. If bladmin does not have write access to the specified directory, the command fails.