...
- From the early days of JobScheduler the distinction between Shell jobs and API jobs was introduced:
- Shell jobs include whatever can be executed from the command line of the respective shell (Unix or Windows)
- API jobs are coded in a programming/scripting language. JobScheduler exposes its API to supported languages.
- With PowerShell jobs such differences are leveled in a way that PowerShell jobs can include
- commands such as
- any calls to Windows commands and programs
- any PowerShell cmdlets
- any calls to .NET classes
- callback functions such as
spooler_init(), spooler_open(), spooler_process(), spooler_close(), spooler_exit() as known from API jobs:- without a callback function being specified script code is automatically executed within the scope of a
spooler_process()callback function.
spooler_process()for - without a callback function being specified script code is automatically executed within the scope of a
- commands such as
- At the time of writing a performance penalty is penalties are obseved for PowerShell jobs due to loading the .NET Framework for the PowerShell run-tme.:
- The the delay for PowerShell jobs starting compared to Shell job is about 1-2s. The effective delay depends on the users system performance.
- This this delay corresponds more or less to the time required to execute
PowerShell.exefrom the command line.
Feature Availability
...