Bryan,
<Unless anyone else is in the same boat, I would like to go ahead and
politely request that any replies be sent off-list.>
No, no, no! Private replies don't get on the archives so the next
guy can look up and read the answers. Bryan, similar problems have
come up before on this list. Have you searched the archives?
Cortlandt Wilson
Cortlandt Software
Mountain View, CA
(650) 966-8555
http://www.cortsoft.com (MANMAN Resources Guide)
"bcole" <[log in to unmask]> wrote in message
news:39bced0c$1_1@skycache-news.fidnet.com...
> Greetings to one and all,
>
> Having loaded MPE 6.5 this weekend, we are now taking this new
release out of the gate for general use and abuse. Unfortunately, we
have noticed a problem when we attempt to call the new Support Tools
Manager utility through either "cstm" or "mstm" at the command prompt.
What follows is the (verbatim) message we are receiving:
>
> [DATA/CU1 9/11/0] cstm
> UNRESOLVED EXTERNALS: umask (LDRERR 512)
> UNRESOLVED EXTERNALS: putenv (LDRERR 512)
> UNRESOLVED EXTERNALS: sigemptyset (LDRERR 512)
> UNRESOLVED EXTERNALS: sigaction (LDRERR 512)
> UNRESOLVED EXTERNALS: getlogin (LDRERR 512)
> UNRESOLVED EXTERNALS: getuid (LDRERR 512)
> UNRESOLVED EXTERNALS: getpwuid (LDRERR 512)
> UNRESOLVED EXTERNALS: symlink (LDRERR 512)
> UNRESOLVED EXTERNALS: waitpid (LDRERR 512)
> UNRESOLVED EXTERNALS: sigaddset (LDRERR 512)
> UNRESOLVED EXTERNALS: sigprocmask (LDRERR 512)
> UNRESOLVED EXTERNALS: geteuid (LDRERR 512)
> UNRESOLVED EXTERNALS: uname (LDRERR 512)
> UNRESOLVED EXTERNALS: ttyname (LDRERR 512)
> UNRESOLVED EXTERNALS: fork (LDRERR 512)
> UNRESOLVED EXTERNALS: execl (LDRERR 512)
> UNRESOLVED EXTERNALS: kill (LDRERR 512)
> UNRESOLVED EXTERNALS: fstat (LDRERR 512)
> UNRESOLVED EXTERNALS: stat (LDRERR 512)
> UNRESOLVED EXTERNALS: sigismember (LDRERR 512)
> UNRESOLVED EXTERNALS: rmdir (LDRERR 512)
> UNRESOLVED EXTERNALS: fcntl (LDRERR 512)
> UNRESOLVED EXTERNALS: getcwd (LDRERR 512)
> UNRESOLVED EXTERNALS: mkdir (LDRERR 512)
> UNRESOLVED EXTERNALS: opendir (LDRERR 512)
> UNRESOLVED EXTERNALS: readdir (LDRERR 512)
> UNRESOLVED EXTERNALS: closedir (LDRERR 512)
> UNRESOLVED EXTERNALS: execve (LDRERR 512)
> UNRESOLVED EXTERNALS: fnmatch (LDRERR 512)
> UNRESOLVED EXTERNALS: ioctl (LDRERR 512)
> UNRESOLVED EXTERNALS: utime (LDRERR 512)
> UNRESOLVED EXTERNALS: readlink (LDRERR 512)
> UNRESOLVED EXTERNALS: popen (LDRERR 512)
> UNRESOLVED EXTERNALS: pclose (LDRERR 512)
> UNRESOLVED EXTERNALS: getpwnam (LDRERR 512)
> UNRESOLVED EXTERNALS: regcomp (LDRERR 512)
> UNRESOLVED EXTERNALS: regexec (LDRERR 512)
> UNRESOLVED EXTERNALS: regfree (LDRERR 512)
> Failed to locate the exported code symbol(s) for the imported code
symbol(s)
> listed above. (LDRERR 522)
> Native mode loader message 522
> /usr/sbin/stm/ui/bin/stmc -c
> Unable to load program to be run. (CIERR 625)
>
> -----
> The general feeling amongst our back office staff is that this
error condition relates to a linking or library issue in Posix, but in
lieu of our lack of experience with the Posix shell, we are polling to
see if anyone has a more knowledgeable approach to resolving this
issue other than calling, waiting, and praying.
>
> In particular, we concentrated on one job from the install that
dealt with libc.sl (all of the calls from CSTM appear to be located in
libc.sl) that had originally abended, and this in particular we re-ran
in an attempt to fix the situation, unfortunately it failed.
>
> Just to provide additional reference, we have loaded the F1 patch
for 6.5, have verified that we can access the shell, and have tried
re-running the varied "installation" jobs that deal with the libraries
in Posix. In addition, we increased the maximum number of TCP
connections to 2000 (thru NMMGR) and have verified that the Predictive
Support job is up and running (and by proxy the diagmond daemon).
Unless anyone else is in the same boat, I would like to go ahead and
politely request that any replies be sent off-list.
>
> It's beginning to look a lot like Christmas,
>
> -Bryan Cole
> KTVAECU
>
|
