Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

Figure 13 Relationship Among OSS Configuration Files, Processes, and Disk Volumes
HP strongly discourages changes in node (system) numbers. However, in a few situations, such as
during the first startup of a newly delivered system, you must change node numbers.
When an Enscribe alternate-key database file such as ZOSSFSET is created, the current node
number might be embedded in its ALTFILE attributes. If that happens, the attributes become invalid
after the node number is changed.
If your system was ordered with the OSS environment preconfigured, then the OSS Monitor was
started at least once before you received the system. That action created ZOSSFSET and might
have embedded the factory-default node number in the ALTFILE attributes.
After you change the node number, you must check that the OSS Monitor can open the OSS fileset
configuration database the next time the OSS Monitor is started. Enter the following command at
a TACL prompt after changing the node number:
FUP INFO ZOSSFSET,DETAIL
If output includes an ALTFILE name that looks something like:
\??.$SYSTEM.ZXOSSMON.ZOSSFS00
you need to correct the ALTFILE attributes. The question marks indicate that the Guardian filename
cannot be resolved because an unknown node number is embedded. Because the filename cannot
Configuration Files 105