This space contains documentation for TrueSight Server Automation 8.9.03 and the later service packs for 8.9. For earlier releases, see BMC Server Automation 8.9.

Network Shell Script Job - General

The General panel lets you provide basic information that identifies a Network Shell Script Job. It also includes options defining how the job is deployed to servers.

Field definitions


Identifying name.


Optional descriptive text.

Save in

Folder in which to store the object.

NSH Script

Click Browse and navigate to the script that is the basis of this Network Shell Script Job.
If you selected a script to begin this procedure, this field is already complete. An information line beneath the NSH Script text box identifies the type of script you have selected.

Script Version

If you have set up a Git Repository for version management of NSH scripts, you can choose the version of the NSH script to associate with the job.

The default version is Latest, that is, the most recently saved version of the script, which might include changes that have not yet been committed to the Git repository.

To choose any previous version that has been committed into the Git repository, click Browse to the right of this field. Then, in the Select Commit ID dialog box, select any committed version from the list.

Number of targets to process in parallel

Choose one of the following options:

  • Unlimited — Simultaneously runs the job on as many servers as possible. Application Server settings control the number of targets the job can access.
  • Limited — Specifies the maximum number of targets on which the job can run simultaneously. Limiting the number of targets is useful when a job might temporarily disrupt the functionality of a target server, and you want to limit that disruption to a small fraction of your managed servers.
    If you want the job processed serially at the target servers, set this value to 1. Note, however, that although this is the best approach for achieving serial processing, it does not always guarantee full serial processing at all targets; the first two or three targets might still run in parallel.

Set execution override

Select if this job should always execute as if your current role and user are scheduling the job. After you click this option, the job definition shows the role:user combination under which the job executes.

Clear execution override

Remove an existing execution override.

Execute Asynchronously

Enable asynchronous script execution for the job.
This option is useful in larger scale environments, as it enables you to execute more scripts simultaneously. This option would be useful for any script that executes for a period of time with limited output, such as a monitor script that reboots a machine and waits for the machine to come back online.
However, note that this option is not recommended for scripts that generate medium to large amounts of output to stdout/stderr.

NEW IN 8.9.04Show Only Script Logs

Select this option to display only the per-target script logs for the specified Network Shell Script Job.

Change Automation Options:
Change Task Template Enabled

Publish the job as a task template in BMC Remedy ITSM, to support the Change-Initiated Job (CIJ) use case of BMC Change Automation for execution of the job without the involvement of the Operations team.

This option is available if this job type was selected to support the creation of ITSM task templates and a connection to BMC Remedy ITSM was set up. For more information, see Enabling Change Automation for TrueSight Server Automation jobs.

Where to go from here

Network Shell Script Job - Targets

Was this page helpful? Yes No Submitting... Thank you