At the end of our last lesson,
we were letting the VMSInstal
kit for PINet automatically edit and run
the configuration files to change
the system settings of VMS. And here we see the tail-end of that
processing. At the end of that processing,
we were returned to the prompt and we used this command
here to take a look at the output from the
AutoGen utility.
I made some notes here--
these are the messages here warning us
or reminding us that we need to change parameters
of the system. And
in order to correct these issues, we
let PINet to [inaudible] edit a file
called sys$systems ModParams.dat
This file is the
way users and system administrators can alter VMS system
settings. And then we later edited
the ModParams.dat file ourselves,
to make some minor changes.
So I have an example in the ModParams.dat file showed
here. This is the ModParams.dat file's
contents. What we did after the fact is we went in and
added these min_ qualifiers
to the key words that set the system settings in
VMS. The min_
qualifier is useful to allow
AutoGen in the future to increment
these parameters and at the same time it prevents AutoGen
from letting these parameters get less than what we specify here.
AutoGen is a rule-based
application and I think I described this earlier.
And what I mean by that is it does
have some rules about understanding that if you
change one parameter, it may affect another or it
may affect our system operation.
And based on statistics of requirement
needs, adjust things up or down in order to optimize the Operating
System. So what we are doing with these min_ qualifiers
is we are allowing the system to increment
these with optimized performance but we are not letting it make things smaller.
After editing and saving our changes,
we then executed AutoGen.com again.
And here is the command that we used to do this.
So we are telling it
the starting phase, SaveParams, the ending phase,
SetParams and then we are also telling it not to use
feedback information. Normally I would allow feedback
information. But in this particular case because it's a new installation of
PINet, the feedback or
statistics of the system that has been keeping on
resource needs do not apply.
Because after we install PINet, the environment is going to be very
different in VMS. After AutoGen was finished,
we wanted to take a look at the log file
for AutoGen and this is the name of that log
file. There is a message that pops up during
the AutoGen processing to remind
us that we should look at this log file. So let's go ahead
and do that now.
So what we can do is take a look at
this log file, and if I put the /p for
page qualifier, then we can look at it one screen at a time.
So here you
can see that these are mentioning parameters
loaded from ModParams.dat. And we have got some informational messages
here. Informational messages are significant
to us and then we know that we change some settings
and we want to make sure that the setting is what we asked for.
So in this case global parameters got set to what we asked for.
So did MaxBuff
and virtual page count.
MinimumGlobalSections got set to a parameter
that was more than we asked for which is also
OK. The process quota
limit default pagefile quota got set to the value
that we asked for which is cool. And we will just take a look
at some of the rest of these messages here. Again what
we are looking for are messages related to the parameters
we set and ensure that the parameter that got set is
what we asked for or better. We are also looking
for errors or warning messages.
GlobalSections is one of our parameters and it is set to an
OK value. Logical names
system hash table is one of our parameters
and it got set the way we want it. Logical name
process hash table again is one of our parameters.
It got set the way we wanted it to.
Process quota limit default page file quota
got set the way that we want it to.
So that is OK.
MaxBuff got set the way we want it to, so that's OK.
None of these are parameters that we
set. There are also no warning or error messages here
so this is OK.
Same thing here.
And the same thing here.
So it looks like we are OK. So the next
step is to reboot VMS and see if we can attempt
the PINet installation again.
And we will come back at the beginning of
the next lesson and see how we did.
Sometimes when working with the
tuning of the Operating System and setting system
parameters, not everything goes smooth. So the next couple of videos
are optional-- they
show what might be
a worse case example of trial and
error steps necessary to
get the system settings adjusted
so that we can install PI or PINet on an OpenVMS machine.
During these sessions, we are going to
run the AutoGen utility a number of times.
Edit ModParams.dat and also take a look at the
output file from
AutoGen. The AGen$report file and try and troubleshoot
problems. Again these are sort of
an example of a worst case, so you may want to
skip over these and move right into the next section.