Before we install our PINet,
there are a couple of things that we need to check on.
First of all, we'd like to make sure that our
PINet machine, our VMS machine, has enough disk space.
So I am looking at command, show device, d
and it turns out all the device drivers for disks in
VMS that start with the letter d. And it shows that
I have got
6,472,000 blocks free.
And that's approximately 3.2GB.
That's more than enough space for the PINet
installation that we need to make. The next
thing that I have done is I have established a place for us to install our
PINet. We are going to be installing our PINet onto a disk called
DUA0. And I am going to
check to see that my PI3 Server,
which is a computer called ChuckPC7-- I am going to check to make sure our
PI3 Server is online. I am going to do that with a ping
command. You could also do this with FTP if your PI3 Server has
FTP installed. And I can see
that the ChuckPC7 machine is reachable.
So a couple of things that I also want to check on
the PI3 Server itself. So
I have opened up a command window to the PI3 Server and I have used the
net start command to show what services
are running over there. And what I am
looking to do is scroll through this list and
see that there are the usual
and expected PI something and PI- something
services running. So this looks like the core of my
PI Server. Also
I have continued and I have used the PI
AR tool-ss command to show
that the PI System is
online and how many tags I have and so on.
It turns out that I have built about 100 tags already, which we are
going to hope to collect data using our PINet
node to send it to the PI3 Server for archiving.
So it looks like we are just about ready to start
the installation.
We are ready to begin the installation of
PINet. I have logged into my VMS
machine and that's going to be our PINet interface
node as the system manager, the user called
system. And here I have shown the devices on my machine.
DKA300 is
my harddrive, my Winchester disk. And
DKA400 is my CD-ROM.
We are going to make our installation
from files on the CD-ROM. But it's
also possible to make the installation from files
that you have already copied to disk.
Here in my command list, I have an example of a
command used to mount the CD. I have abbreviated
some of the options here, and we are going to take another look at this command again.
But this is the command that is used
to mount the CD.
When the CD becomes mounted
VMS will show us the name of the
volume and it also shows you that it is write locked--
obviously because it's a CD-ROM. The label information
from the CD should match the
information for your system.
And this is normally also printed on the CD itself.
So you can confirm that you have the right system.
And this information right here is your PI Server
number, so this should be your PI Server number that you
use when installing PI, upgrading PI, contacting technical
support and attempting to attain
downloads. Now that the CD is mounted, we can
take a look at a directory.
So here is a list of the files that are
present on the CD right now.
This particular CD has files
for PINet version 2.3.
You will probably be working with a newer
version of PINet. Our distribution kits for
PI consist of an
A save set which has the product specific VMS install
instructions-- in other
words, the VMS install instructions that are specific to PINet.
V save set is actually the PINet product
itself and there may or may not be a
C save set. C save set
would include the encrypted source
code and other files called the PI Source Directory
Tree. These files may be useful for
examples or documentation, testing
utilities. Or they may be files
that technical support may ask you to restore to the
system that aid them in troubleshooting,
debugging the problem that you are having
or even running the debugger online and do development on your system.
I mentioned earlier a
file with a set of instructions in it
that is a brief description of the CD.
And that says readme.win file.
This readme.win file is actually a text file that was
created with Notepad in the Windows environment.
For some reason, this file does not read
very well in the VMS environment. So if you want to look at
this file, copy it to your PC and
look at it there. This is a copy of what the
readme.win looks like. So there
is some introductory information describing the CD which
I have already gone over with you a little bit. Finally
down here, I get to a set of instructions that help me deal with the
CD. These are an abbreviated set of
instructions for installing PINet. So here we can see
the mount command that I used. And
here the mount command has all the qualifiers and parameters spelled out full.
Mount override identification
[inaudible] format CD-ROM
[inaudible] [inaudible]
In some cases I mentioned that you
may want to install this CD from
files that you copied to your computer with
FTP. And if that's the case,
one of the things you need to know is FTP will damage the
files in the file transfer process, and you will need to
re-block the files. So here are instructions
for re-blocking the files.
So this set file /attribute
equals lrl 9216 will take care of undoing
the damage that FTP does to the files when you move them.
Scrolling back up here a
ways, this is an example of the command I might
use to start the installation of
PINet, or an upgrade of PINet on my computer.
In your case, you are probably going to be working with a
newer version of PINet than I am. We are working with
2.3, you are probably going to be working with
PINet 2.4 -- so your command will look something like
this where you will replace CD device
with the name of your CD drive. My
CD drive is DK400. I think we are ready
to continue with the installation.
We are using VMS install technology, you can think of
VMSInstal as being similar to the Windows setup program.
VMSInstal is an engine
that products like PI can use
to perform their installation or upgrade task.
VMSInstal is an [inaudible] update
directory.
It's called VMSInstal.
And this thing needs some
parameters passed to it. The first parameter will be the name of the product
I want to install-- in my case it is
OT3. And then we need to tell
it the location of the product-- in my case it is going to be
DKA400.
They ask you if you are satisfied with the backup of your system disk.
The backup of a system disk and the backup
of the disk where PINet is installed, because
PINet is on a separate disk. Those backups are the only
way to undo a failed installation-- that's
really important.
The next message here, PINet v2.3 actually
comes off of the CD.
So this indicates that I have successfully reached out to the CD and found the PINet
product. That's good news. We restore the
A save set and start executing commands from it.
Check to make sure this is the new installation of PINet
and we ask the question again, in case you
click your mouse or a different key accidentally
while the computer was running. Or had a pad
or something laying on the keyboard.
And then we check system parameters. You will see here that
I have some issues. Some of these issues are reported
to me. Some of
these are reported to me
with F in the message. The
F is a fatal problem that I definitely have to fix before I can go on.
The I messages are informational
and are optional to fix those. We can see here that a number of
my parameters needs some adjustment.
I am going to grab this
and copy it and stick it in
my clipboard so I can refer to this later.
You can probably get a log or some sort of a document
file open when you are working on your system-- that's good practice.
And that's what I am going to do
with this information.
Our VMSInstal kit can
allow you to automatically attempt to fix problems here.
So I am going to say yes for automatic
AutoGen and we will try to get the system to fix this.
When we come back in the next lesson, we will take a look at the
automatic AutoGen and we will see if it is OK to continue.