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.
Optional descriptive text.
Folder in which to store the object.
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 Select Commit ID dialog box, select any committed version from the list.to the right of this field. Then, in the
Number of targets to process in parallel
Choose one of the following options:
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.
Enable asynchronous script execution for the 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 BMC Server Automation jobs.