The following prerequisites must be fulfilled, before you can use HIPLEX support for node files:
For each POSIX user, the POSIX information entered in the user catalog must be identical on all hosts.
A POSIX client file system for which the container is located on an SM pubset, must be mounted in the file system under the agreed directory “pubset”. For example, the file system for SM pubset A must be mounted under /SM-PUB/A. HSMS uses this convention to help it find where the POSIX data to be backed up is located and where the corresponding metadata is to be saved.
If a POSIX file system is to be mounted which has a path name containing /SM-PUB/A, then the POSIX installation program checks to see whether the file system container is really located on SM pubset A.
For this concept the mount points must be identical on all hosts.
The system administrator must avoid contradictory mount points within the file structure on the various hosts by making sure that all path names are identical.
Each individual environment must be taken into consideration when creating HSMS statements. Each environment requires its own HSMS statement.
The operand value *ALL is now limited to a single environment and can no longer cover all nodes if you are using several different environments.In the event of a system failure the system administrator must perform several actions to make sure that the activities can be continued on a substitute host.After the cause of the failure has been eliminated, the activities can again be taken up by the original host (see section "Usage models").
HIPLEX support requires local archiving of each individual SM pubset. Global archiving is not possible. The system administrator cannot, for example, carry out central archiving in a global archive on an SF pubset.