At this point we are ready to start our installation
of PINet. I have logged into our
VMS Machine. It's going to become our PINet Node
as the System Manager. There's a couple
of ways to install PINet. You could install PINet from
Safe-Set's Installation Media
that you have copied to the hard disk. This may be
the case if you have had to FTP the files
from a PC that happens to have a CD-ROM in it. This
particular machine we are working with has a CD Reader
so I will be able to use a VMS command
to mount the CD.
You can find instructions on how to mount the CD
and a brief set of notes on installing
the PINet
software in a file that we are going to show in a minute here.
So this command here,
Mount with Override Equals Identity,
Media Equals CD Rom, Undefined
fat is fixed: none, and a
block size. This is very important: 9216.
And the name of my CD Drive is dka400.
When my Drive gets mounted,
it tells me the name of the media that's on there
and this should match the information for
your site. This is OSI NWTraining.
My PIServer Serial Number is 3544,
and this is VAX Media.
And if I do a Show Device
d, I can now see that the status of my
dka400 drive has changed and now shows
Mounted Allocated Write Locked. Allocated means that
it's a private device so the users on the system
can access the CD while I am using it.
If I do a Show Device-Full
dka400,
I will get more information about the drive.
And here we can see that this is a Sony CD Drive
and
the format of it is ISO
9660. The ISO 9660 format is
why we use this
undefined fat,
fixed none, and 9216
set of qualifiers on the command.
We should be able to type dir to see what's on the root of my
disc. DKA
400.
[typing]
And this is typical of what you will see of an
installation disc for PINet.
The critical pieces we are working with here
are the A and B Safe-Sets for the PINet installation.
This happens to be PINet version 2.3 that we are
going to work with. You will probably have a newer version, 2.4.
And this is the C Safe-Set from the PINet
Installation Kit. On the CD is a file called
README.WIN. This is really a text file.
It was created with Notepad but for some reason or another
this file looks like gibberish when we try to edit it
on the VMS System. So, if you want to work with this
file, take your CD, put it in your PC,
copy it to your disc and then use Notepad or something to view it
as I have done here. So this
is what the README.WIN file looks like.
Basically, a description of what's on the CD.
A note about what versions of VMS we support.
I mentioned that there are System Management
Tools on the CD. I believe I mentioned earlier, though,
that the System Management Tools that ships with the PINet
and PI2 Server are not the
latest and greatest for your PI3 systems, so you would not want to use
those. And then we have got
Shortcut Instructions. This is very, very brief
on installing the PI or PINet
software. So, here's the Mount Command I used,
with all the commands spelled out fully, no abbreviations.
An alternate way to install this is to
take the CD, put it in a PC and
FTP to Files to your PINet
computer. If you FTP the files to your PINet computer,
FTP is going to damage the files
and will have to perform a, a re-block operation,
and the way to correct the blocking of the files,
or re-block it, will be with this SET FILE-ATTRIBUTE
command you see here. And you want to do this
for each of the Safe-Sets you have transferred from
your CD to the VMS System using FTP.
In this case, the command shows
the A and B Safe-Sets only for
the PINet Node and the version
that we were working with is PINet 2.2.
So again, you will probably be working with PINet 2.4
so your
Safe-Sets will probably be named something like this:
pinet024.a and
pinet024.b.
I am not going to save my
changes here because they are on the CD and that will not be fun.
To continue with the installation
OSIsoft uses a VMS Install Kit
Technology. VMS Install is the
setup or installation program that comes with the Operating System,
and you can invoke it like this.
[typing]
So the name of the Utility
is vmsinstal with one L. It's in the
systal or update directory.
You
need to pass some parameters to this. The first parameter will
be the name of the product you want to install.
In my case, I am
installing PINet version 2.3, so the product name is
going to be pinet023.
Next you need to tell me where the kit's located on disc.
And I am going to install
this from the CD, so the CD is dka400
[typing]
and the six zeros
in the square brackets here -- this specifies
the route of the CD which is
where these files happen to be located.
It's necessary usually to specify the route of the CD
Directory explicitly
rather than just specify the disc name. If I hit Return
here, this should start the installation process.
There'll be some questions for us to answer.
First of all, this comes from
vmsinstal itself. We have not executed any PI software yet.
Am I happy with the back of my System Disc?
And the answer here should be Yes. The disc
where PINet gets installed and the Operating System disc --
full backups of those are the only way that you will
be able to undo or recover from a failed installation.
So, the backup's pretty important. So, I am going to say yes here.
It then tells me which process --
products are going to be processed, and this information
comes directly from the Installation Kits, so
this is good news. I have actually been able to reach out and find the Installation Kit.
This causes the
A Kit to be re... installed, and the instruction's found in the A Kit Executed.
So you can see that we are checking the VMS Version, we are
checking VMS Accounts, we are creating a
user account for OSI Tech Support. This
account is initially disabled. We are also creating a
PI Server Account so you can use PI System Management Tools
to monitor your PI Server.
And, we are also listing the UIC Code that got created
for this PI Server User Account. Next we check
to see if this is a new installation of PINet. The same
kit that we use for upgrades can be used for new installs and vice versa.
We want to make sure this is a new install instead of an
upgrade. If this is not a new install,
the installation kit might accidentally
overwrite files that important to us.
In our case here, this is a new install, so we want to answer Yes here.
Again, I could save myself some typing just by
hitting the Return Key, because the item enclosed in square brackets
is the Default Choice. Now we ask
you again to make sure this is a new installation of PINet.
You might have had a pad laying on the keyboard or clicked on
the mouse or hit the Return Key a couple of times too many,
so we put this extra question up to that we do not accidentally proceed.
Then we check System
Quotas, and we see here that I have
got some issues. Let me scroll back up here
a moment. Some of
these infor... mess... information messages come out as
a -- I guess I will call them Warning or Status Information.
"I" items are not fatal. They are not required but they are
recommended. The, one -- the error messages that come out
here with "F" are required, and
so, this
will have to be fixed before we can continue.
If I hit
Yes here,
or actually hit any Return. I accidentally clicked and copied my
Clipboard into the buffer here.
This is going to verify
the System Account information and continue.
And then it bailed out because
the installation failed. So, I guess I have to fix these problems
by hand. Let me start this again
Now we will do it right this time. So, yes, I am happy with my backup.
So,
hopefully, you will see from this, errors are recoverable.
Yes, this is a new installation. Yes, I am sure.
Same messages I saw before. And this time
I am going to let the VMS
Socket do an automatic assistgen for -- or autogen for me, so I am
going to say Yes here.
Gonna enter the System File called Modparams.dat
that's in the Sys$System Directory.
And, after editing this file, then we are
going to execute autogen.
Autogen goes into about four places in VMS where
Operating System parameters are saved or
calculated from, and some of this information includes
feedback or experience based on
how the system's been operating. These
are used, then, to collate together a set of System Parameters
and create a new set of
boot files for the system. It's possible that
a System Parameter will be documented in more than one place.
So it's possible we will get some warning messages here saying
that there were duplicate entries. What we want to do is make sure
that the entries we find match
what we are expecting to get
for the setting we need for PI.
I should have kept a list of the warning
messages up above, or fatal error messages up above, so that I knew what
the settings needed to be.
When autogen completes, there'll be a log for us
to look at. And that's where we will begin with the next
part of our lesson.