This is a good time to think about your approach to PowerShell's functions.
Are they a tool to be used occasionally for recurring blocks of code?
Alternatively,
will functions become the central methodology for every script you create.
To elaborate what I mean, let us consider three statements from people with
different scripting knowledge:
For beginners - Functions are mysterious even mythical.
For intermediates - Functions are a method of saving time when tackling repetitive tasks.
For experts - Functions are a way of life. They consider
a functions as a building block in their master plan to build scripts.
I have an aversion to using 'Hello World' examples. Instead, Guy
has invented a basic function to calculate batting averages. I
realise that my hybrid example may please neither cricket lovers nor baseball
aficionados. Casting aside sporting loyalties, these two scripts
will get you started with PowerShell's functions.
By using keyboard input, we are going to take two numbers and divide the
first number by the second, and thus calculate the average in
traditional math fashion.
Before we get down to using my BatAvg Function, here are a few
considerations.
PowerShell dictates a format consisting of three parts, the keyword 'Function',
followed by a name of your choice, finally, the payload containing the script block,
which is enclosed by curly, or parenthesis style brackets. What you place inside the
script block is the same code that you could execute normally outside the
scope of the function. The whole point is that you can execute
this block of PowerShell code simply by typing the name of the function.
When you invest time in creating PowerShell
functions, the benefits are as follows: firstly, you can repeat the block of code easily
and reliably by
calling the Function's name again and again. Secondly, you can introduce parameters
which modify the code, for example, to change a name
or a numeric value within the code block.
In PowerShell, learning about the 'function' command is easy; to get started
type these two words at the command line:
help about_function. Note
that's an underscore not a dash, also appreciate that 'function' is singular.
The point of this script is to create a function called BatAvg which calculates
your batting average. You need to supply three parameters, a name,
the number of runs, and the number of outs. My default settings are
for the English game of cricket, however, for baseball, you could modify
the Param $outs to $AtBats, and $runs to $Hits.
# Microsoft PowerShell script to create a simple function
# Author: Guy Thomas
# Version 2.2 June 2008 tested on PowerShell v 1.0
function BatAvg
{param ($Name, $Runs, $Outs)
$Avg = [int]($Runs / $Outs*100)/100
Write-Output "$Name's Average = $Avg, $Runs, $Outs "
}
BatAvg Bradman 6996 70
Note 1: The last line calls for the function BatAvg
and inputs the three parameters. It would make my day if you altered the name
'Bradman' and then used two different numbers instead of 6996 and 70.
Note 2: Each param is separated by a comma.
Note 3: When you explicitly declare with param, it
must be the very first word inside the curly bracket.
Guy Recommends: SolarWinds Engineer's Toolset v10
The Engineer's Toolset v10 provides a
comprehensive console of utilities for troubleshooting computer problems. Guy says
it helps me monitor what's occurring on the network, and the tools
teaches me more about how the system literally operates.
There are so many good gadgets, it's like having free rein of a
sweetshop. Thankfully the utilities are displayed logically: monitoring, discovery, diagnostic, and Cisco tools.
Download your copy of the Engineer's Toolset v 10
A classic example for dissecting, fiddling, changing stuff to see
what happens and thus learn about functions. I re-jigged the first script to make it more suitable for baseball. Often, looking at
two slightly different scripts gives you 'binocular vision', as a result you get
extra insights
into the techniques.
It's good scripting technique to scope the parameters with the [String] or
[Int]. Incidentally, square brackets mean optional information.
$Avg = [int]($Runs / $Outs *100)/100 simply applies some maths to display the
average to two decimal places.
I wanted to introduce logic to help Americans who are thinking baseball 'outs',
and Englishmen who are thinking cricket 'dismissals'. Observe how inside
the main curly brackets are {if... } and {Else... } blocks. My hidden agenda is to make you aware
that you can put all sorts of scripting 'stuff' inside those curly brackets.
# Microsoft PowerShell script to create a baseball batting average
function
# Author: Guy Thomas
# Version 2.5 June 2008 tested on PowerShell v 1.0
function BatAvg
Note 1: Observe the relationship between declaring the param
$name, and employing the parameter -name.
Note 2: Another advantage of Param is that you can try
different sequences, for example:
BatAvg -AtBats 70 -hits 6999 -name Babe. (Default order -Name -Hits
-AtBats)
Note 3: The If... Else logic assumes that cricket
averages are greater than one, but baseball averages are less than one.
Note 4:
Please pay close attention to the type of bracket. Also 'Single' or "double"
quotes are highly significant.
Scripting functions are like macros, they replay your commands. In the case
of PowerShell, you could also make functions the rational, framework or
building-block for creating your scripts. When you get down to creating
functions it reinforces knowledge of parameters. My subsidiary reason for
explaining functions in this ezine is to reinforce the importance of employing
the correct type of bracket, and paying attention to single and double quotes.
Please write in if you see errors of any kind. Please report any factual mistakes, grammatical errors or broken links, I will be happy to not only to correct the fault, but also to give you credit.
Guy
Recommends: Orion's NPM - Network Performance Monitor
Orion's performance monitor is designed for detecting network outages.
A network-centric
view make it easy to see what's working, and what needs your attention.
This utility guides you through troubleshooting by indicating whether the
root cause is faulty equipment or resource overload.