Subject: | |
From: | |
Reply To: | |
Date: | Thu, 19 Nov 1998 10:20:40 +1100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
When you make changes dynamically the logdcc.pub.sys file is the file that
will contain the messages As far a I remember the log4onln.pub.sys file only
relates to online changes made through sysgen by running doionow or by using
ioconfig.
When you save and validate the changes in nmmgr the changes are saved to the
nmconfig.pub.sys file (by default). When you create an SLT tape from sysgen
this will take a copy of nmconfig and put it on the SLT. So if you make
changes in nmmgr and do not cut a new SLT then if you have a crash and have to
recover from SLT, then your recent changes will not be available.
Also be aware that there could be a problem with making dynamic changes. I
have come across a problem where dynamic changes were made, and then the
system had to be recovered using a 'start recovery'. This gave a DCCERR when
booting. Therefore it is advisable to do a 'start norecovery' soon after doing
the dynamic changes to ensure that no errors occur. This does look like it
goes against the idea of dynamic changes, but dynamic changes, in my thoughts,
are more for urgent changes where the system can not be rebooted, or changed
with dtccntrl.
Regards
Richard Bayly
Hewlett-Packard Response Centre Australia
Paul H. Christidis wrote:
> Recently I added some additional 'device classes' and used the 'activate
> now' option that is currently presented after validating. Just after
> making the selection I also remembered that someone had posted a warning
> about this new feature and (memory not very clear) that if an SLT was
> created it would NOT contain these changes.
>
> I also noticed that file 'log4onln.pub.sys' was modified, but its contents
> were more related to events that took place months ago (4 new drives were
> added) than the creation of these 'device classes'. In addition it seems
> that statements relating to the creation of the new device classes were
> appended to the file 'logdcc.pub'.
>
> Can anyone elaborate on the above and on what procedural changes should be
> included when 'nmmgr' changes are activated immediately?
>
> Regards
> Paul H. Christidis
|
|
|