Skip to content

Commit 1dc0b2f

Browse files
authored
Set-DbaAgentJobOutputFile: Made it more clear that the Job and Step parameters expect names. (#9675)
1 parent 4e8aebf commit 1dc0b2f

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

public/Set-DbaAgentJobOutputFile.ps1

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,13 +17,19 @@ function Set-DbaAgentJobOutputFile {
1717
For MFA support, please use Connect-DbaInstance. be it Windows or SQL Server. Windows users are determined by the existence of a backslash, so if you are intending to use an alternative Windows connection instead of a SQL login, ensure it contains a backslash.
1818
1919
.PARAMETER Job
20-
The job to process - this list is auto-populated from the server.
20+
The name of the job to process.
21+
22+
This parameter is not officially mandatory, but you will always be asked to provide a job if you have not.
2123
2224
.PARAMETER Step
23-
The Agent Job Step to provide Output File Path for. Also available dynamically
25+
The name of the Agent Job Step to provide Output File Path for.
26+
27+
Within a job, step names are unique so this is a safe way to select steps.
28+
29+
Also available dynamically. If you do not specify this parameter and the target job has only one step, then we use that step. If it has more than one, then a GUI will be used to make you pick steps. If that GUI does not work, then we use all steps.
2430
2531
.PARAMETER OutputFile
26-
The Full Path to the New Output file
32+
The Full Path to the New Output file.
2733
2834
.PARAMETER WhatIf
2935
Shows what would happen if the command were to run. No actions are actually performed.

0 commit comments

Comments
 (0)