We have just finished rebooting the computer
after editing ModParams.Dat and executing
the AutoGen utility to create a new set of
system boot files. I have got my
installation kits for PINet copied to the
disk of this computer. VMSInstal command
is you remember is, @sys$update
pinet024 is the name of our product and the location of our
install kits is pitape:[000000]
And that is what we need, and we hit the return key.
Again we need to be satisfied with the
backup of our disk-- I only have one disk in this computer.
If I had two disks and PINet was on one
and VMS was on the other, I would have to have a backup of
both disks in order to undo this installation.
Checking parameters and
accounts. New installation of PINet? Yes.
And I have got an informational
message here so it does not fail.
Alright, so we are going to continue with our
installation. You can choose where to install the PINet
software. Normally PINet and PINet
Build are the two directories that you need created in the root of the disk.
And that's what I am going to do in this case. I only have the
one disk on this computer, so I will just hit return and take the defaults.
And then I have some additional questions
dealing with networking and
PI architecture. We are going to connect to our PI
home node by TCPIP.
PI3 Server Managers
may want to consider this PINet to PINet option.
PINet to PINet allows a PINet node to
act as the Server for other PINet nodes.
You might want to do this to minimize the loading
on a PI3 Server for certain things
such as event and point configuration updates.
This option is normally not necessary
unless you have a large number of PINet
nodes-- 7, 8 or more.
In that case, then you would also want to have the PINet
node that is acting as the server for other PINets
to be the server for API nodes running
Windows or UNIX that are collecting
data with interface as well. In our case, we do not want to do PINet to
PINet because the server we
are working with is only going to have the one
PINet. Also modern servers do not have the kind of
loading problems that we have had in the past, so this is pretty much something
you do not need. So I am going to say no here.
And then I need to tell us the Operating System of
the PI Server and it's going to be Windows so I will say yes.
And now I am reminded that I need to make sure that I have got
TCPIP running and that we can connect to the PI Server. Because we are going to need to be able to reach out to
the PI Server during this install process.
And I have already confirmed that PI Server is
running so yes I want to continue with my installation.
And I need to give the name to my
PI Server, the name is going to be ChucksPC7.
And notice that it says
not an address, and I
think I am done with my questions. The VMSInstal kit
now is going out and editing a number of PI
files that are site specific. It then executes some of those
files and starts the installation.
There is pretty much nothing for us to do for the next
hour. So at the beginning of the next lesson, we will take a look
at the progress of the install and we will take a look
at to troubleshoot the errors, or at least identify if there are
errors. And then we will have post-installation steps
to check.