Filter
Top Products
ANR8281W (AIX)
Error binding dsmtli.drv for IPX/SPX or NetBIOS communications method.
Explanation: The server cannot loadbind dsmtli.drv to initialize the IPX/SPX or
NetBIOS communications driver after successfully loading dsmtli.drv.
System Action: Server operation continues. IPX/SPX or NetBIOS communications
is inoperative.
User Response: NetWare for AIX, IPX and NetBIOS Support/6000, or AIX
Connections must be installed on your system to use IPX/SPX communications. IPX
and NetBIOS Support/6000 or AIX Connections must be installed on your system to
use NetBIOS communications. File libtli.a is accessed as part of the load and
loadbind process through module dsmtli.drv. Both files must be available for the
load and loadbind system calls.
ANR8281E (AS/400)
Exit type EXIT exit name cannot be accessed.
Explanation: The *PGM object with the given exit name cannot be accessed by
the server. The attempt fails because the server does not have the authority
necessary to access the designated *PGM object.
System Action: The server does not process the command.
User Response: Reissue the command and specify a different exit name, or obtain
the required authority to access the designated *PGM object from the security
officer or the exit program owner before reissuing the command.
ANR8281W (Windows NT)
HTTP driver unable to initialize due to error in BINDing to Port port, reason
code reason code.
Explanation: While initializing HTTP communications, the server has failed to
connect to a master TCP/IP socket on which to listen for clients. The reason code is
the return code from the TCP/IP bind API.
System Action: Server operation continues, but the server cannot accept sessions
from administrative clients using HTTP protocol.
User Response: Ensure that no other application is using the port number
specified in the server options file with the PORT option. If TCP/IP is also in use
for client sessions, ensure that the same port number is not specified for both
TCP/IP and HTTP communications. This may be done by issuing the TCP/IP netstat
-s command. If the server is brought down and then started immediately, you may
be within the TCP/IP one minute timeout period for port reusage. Bring down the
sever, wait one minute, and then restart the server. If that does not work, it may be
necessary to restart Windows NT.
863
Tivoli Storage Manager Messages
3. Common and Platform
Specfic Messages