A moment ago,
we were taking a
look at editing and
setting up the ModParams.dat
file on our system. Let me scroll
back and catch you up on what happened there.
So I edited the ModParams.dat file and I
re-ran AutoGen using these commands here.
At the end then,
ModParams
finished successfully.
And as instructed here from the message from the AutoGen
utility, I took a look at the report that was generated using the
type command. So here is a report that was
generated. What I'm looking for is to see
if the changes I asked for occurred, and I'm also
looking for any warning or error messages. So we know that
we asked for ModParams to be 20,480
that happened. Virtual page count, we asked for it to be
70,000 and that happened.
The page file quota limit,
process quota limit, default page file
quota, we asked for it to be 35,000 and that happened.
We asked for
global pages to be set to something and that happened.
Global sections got larger and that was something that we
were concerned about. Logical name
system hash table, we asked for it to be 512.
Also logical main process hash table, we asked for it to be 512
so that happened.
So far so good.
We also asked for the default mailbox buffer
quota. This sets up
a buffer that can be used for watching programs quickly.
We asked for that to be set to 5120 and that happened.
So far so good. No warning or
error messages in this. It looks like we are ready to
continue. The next thing I did
is executed VMS's shutdown procedure
to reboot VMS. And you do that by typing this
command here, AddSys$SystemShutdown
You'll be prompted for some
answers. Since I was logged in over the
network, it wants me to confirm that I really
want to reboot the computer. If there is a problem,
the computer may not come up all the way and may not talk to the network.
So I'm confident here and I'd say yes. Minutes to shutdown,
so you can delay the shutdown and that will cause messages to
be broadcast to the user every minute telling them that the system
is going down. In this case, I want it to go down immediately.
The reason for shutdown, you can put in a comment
here and it will broadcast to the network.
Spin down disk volumes. For many of the smaller
machines that PINet runs on, this command doesn't really do anything.
But on the bigger systems, this spins down the
disks, powers them down and parks the heads. That may be
important especially if you are going to move the computer or turn the
power off. Site specific shutdown procedure.
You can skip that or run that, your choice.
I always let it run. Should I automatically reboot?
In this case I want to say yes. In some cases,
you want the system to go down and stay down. In this case,
I want to automatically reboot. And then you
get an option of tests to be made before the system starts back up.
So I'll usually invoke the reboot check and
the save feedback check. You can abbreviate these and provide
them as a comma separated list.
And then the system starts down.
Here is an example of the
message that gets broadcast to people on the network
to indicate the system is going down.
If other people were logged into this machine, they would've seen
that message.
The site specific shutdown procedure gets run, processes get stopped and
so on. And eventually what happens
then is usually within a minute or two or
maybe a little longer after this message comes out,
the machine is really and truly shut down. But at this point here when this message comes
out, the machine stops talking to
the operator console and stops talking to the network.
Eventually I got this message here telling me
my telnet connection was terminated. And I waited a few
minutes and hit the return key
to open a new session. Depending on your terminal or terminal
emulation software, you may need to do something beyond just
hitting the return key to reopen your session.
When I got the username prompt, I logged in
with my password and I got welcomed to VMS.
At this point, I'm ready to try and resume
the installation of PINet.
I'll do that by doing @sys$update
VMSInstall
And to show you a different
way to do this, I'm going to install PINet
this time from save sets that I copied to the disk of my computer. So this
[inaudible] I've created a directory
on my computer with a short-cut
called PITape.
And that's where the kits have been
installed. They are not installed, but copied.
So in this case, I can install them from my hard disk rather than
a CD. Is it worth copying the kits from the
CD to your hard disk? Maybe yes and maybe no.
If you don't have a CD reader in your computer,
definitely yes. If you have more than one of these things
to do, definitely yes. If you are just doing one of
them, the time it takes to copy the files over
and re-block them may not be worth it.
Except for the location of the kits,
the installation starts up just like before
and we should see the same kind of messages on the screen.
Am I happy with my backup? Yes.
Opps, it didn't find any of the products.
Alright,
Ahh, installing PINet 2.4
Much better.
Hopefully we'll hang in here
until we get to answer all the questions that we need to
answer. It'll make for a long part of this lesson
but then we'll continue on to the next step.
I'm seeing some of the same messages that we've seen
before. And we are confirming that yes, this is a new installation of
PINet. We're still hoping for
success. It looks like the default pagefile
quota isn't big enough yet. This sometimes
happens, you change this or you change that and it causes
some interactions and that may mean that the system needs more
resources when you get done. So we are going to
have to run AutoGen again. I'm going to say
yes to this question here.
And we'll repeat the steps we've already gone through once or twice before.
So I'm going to skip those and when we come back, we're
going to try the installation PINet one more time.