...
Start-JobSchedulerJob [-Job] <String> [[-Directory] <String>] [[-Parameters] <Hashtable>] [[-Environment] <Hashtable>] [[-At] <String>] [[-Timezone] <String>] [[-AuditComment] <String>] [[-AuditTimeSpent] <Int32>] [[-AuditTicketLink] <Uri>] [-WhatIf] [-Confirm] [<CommonParameters>]
DESCRIPTION
...
-At <String>
Specifies the point in time when the job should start:
* now
** specifies that the job should start immediately
* now+1800
** specifies that the job should start with a delay of 1800 seconds, i.e. 30 minutes later.
* yyyy-mm-dd HH:MM[:SS]
** specifies that the job should start at the specified point in time.
Required? | false |
Position? | 5 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
Timezone
-Timezone <String>
Specifies the time zone to be considered for the start time that is indicated with the -At parameter.
Without this parameter the time zone of the JobScheduler Master is assumed.
This parameter should be used if the JobScheduler Master runs in a time zone different to the environment
that makes use of this cmdlet.
Find the list of time zone names from https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
Required? | false |
Position? | 6 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
...
-AuditComment <String>
Specifies a free text that indicates the reason for the current intervention, e.g. "business requirement", "maintenance window" etc.
The Audit Comment is visible from the Audit Log view of JOC Cockpit.
This parameter is not mandatory, however, JOC Cockpit can be configured to enforece Audit Log comments for any interventions.
Required? | false |
Position? | 67 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
...
-AuditTimeSpent <Int32>
Specifies the duration in minutes that the current intervention required.
This information is visible with the Audit Log view. It can be useful when integrated
with a ticket system that logs the time spent on interventions with JobScheduler.
Required? | false |
Position? | 78 |
Default value | 0 |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
...
-AuditTicketLink <Uri>
Specifies a URL to a ticket system that keeps track of any interventions performed for JobScheduler.
This information is visible with the Audit Log view of JOC Cockpit.
It can be useful when integrated with a ticket system that logs interventions with JobScheduler.
Required? | false |
Position? | 89 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
WhatIf
-WhatIf <SwitchParameter>
Required? | false |
Position? | named |
Default value | |
Accept pipeline input? | false |
Accept wildcard characters? | false |
Confirm
-Confirm <SwitchParameter>
Required? | false |
Position? | named |
Default value | |
Accept pipeline input? | false |
Accept wildcard characters? | false |
RELATED LINKS
about_jobschedulerJobScheduler
EXAMPLES
-------------------------- EXAMPLE 1 --------------------------
...
-------------------------- EXAMPLE 2 --------------------------
PS > Start-JobSchedulerJob -Job /sos/dailyschedule/CheckDaysSchedule -At "2038-01-01 00:00:00" -Timezone "Europe/Berlin"
Starts the indicated job for a later date that is specified for the "Europe/Berlin" time zone.
-------------------------- EXAMPLE 3 --------------------------
...
-------------------------- EXAMPLE 3 4 --------------------------
PS > $params = $Start-JobSchedulerJob -Job /some_path/some_job -Parameters @{'par1' = 'val1'; 'par2' = 'val2'} Start-JobSchedulerJob -Job /some_path/some_job -Parameters $params
Starts the job with parameter 'par1' and 'par2' and respective values.