|
Problem |
Cannot run bbolsrch or bborblog rexx execs
- load of module failed. |
|
Cause |
The failure is caused by an attempt to run bbolsrch or
bborblog while an automount managed path was also included in customer's
libpath. |
|
Solution |
This is a case of a path in the libpath including an
automount managed directory. If the libpath includes a '.' , then the
current working directory also will be searched
when looking for DLLs. If an automount managed directory is searched, a
HFS dataset name will be generated based on your automount configuration.
This will result in an attempt to mount a dataset that may not exist and
the resultant catalog error
when trying to locate the dataset. The rc 0000000153 (x'99') is listed in
USS messages and codes as a catalog error. The fix is to not include an
automount managed path in your
libpath.
There isn't a problem using automount managed directories in general. The
problem arises when you include an automount managed directory in your
libpath. Any time you access an automount managed pathname, you invoke
your automount policy for
that path. If you have generic entries in your policy, then the HFS
dataset name to be mounted will be generated from the path that you are
attempting to access.
|
|
|
|
|
|
|