Anonymous_User Absent Member.
Absent Member.
2222 views

TSA Errors with TSM v5.2

I've run into a few problems running a Tivoli system with both 6.5 and 5.1
boxes. So far, I've been unable to find a solution or even a decent lead
that might help me sole the issues. Anyone here had similar problems to the
following two scenarios ?

1. NW 6.5 sp3, TSM Client v 5.02.04, TSAFS.NLM v6.50 and I'm getting the
following:

(TSAFS.NLM 6.50.11 313) A file cannot be read

(TSAFS.NLM 6.50.11 269) No data sets can be found
---------------------------------------------------------------------------------
2. NW 5.1 sp8, TSM Client v 5.02.04, TSA500 v5.05i and I get:

(TSA500.NLM 5.5 259) This program cannot allocate a memory handle
---------------------------------------------------------------------------------

I'm guessing that the last three digits in the TSA message is an error code
of some kind, I can't seem to find a resource that gives me a solution.

cheers,

Tony


Labels (2)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: TSA Errors with TSM v5.2

Go to ftp://service.boulder.ibm.com/storage/tivoli-storage-management/
to download the latest patches for the client - they're under
maintenance.

Update to the latest version of TSA for NetWare 5.1 and 6.5.

As for documentation on error codes: Go to:
http://publib.boulder.ibm.com/tividd/td/IBMTivoliStorageManagerforWindows5.2.2.html

There is an error guide pdf available - the codes will tell you if
it's a client-side issue or server-side issue. Documentation on error
codes is very good.

Messages that begin with prefix ANR originate from the server.

Messages that begin with prefix ANS are from one of the following
clients: – Administrative clients – Application program interface
clients – Backup–archive clients – Space Manager (HSM) clients ©

– Data Protection for Lotus® Notes™v Messages that begin with prefix
ACD are from Data Protection for Lotus Domino™. v Messages that begin
with prefix ACN are from Data Protection for Microsoft® Exchange
Server. v Messages that begin with prefix ACO are from Data Protection
for Microsoft SQL Server. v Messages that begin with prefix ANU are
from Data Protection for Oracle. v Messages that begin with prefix BKI
are from Data Protection for mySAP.com for DB2® UDB and Data
Protection for mySAP.com for Oracle. v Messages that begin with prefix
DKP and are in range 0001–9999 are from Data Protection for WebSphere
Application Server. v Messages that begin with prefix EEO and are in
range 0000–9999 are from Data Protection for ESS for Oracle. v
Messages that begin with prefix EEP and are in range 0000–9999 are
from Data Protection for ESS for DB2 UDB. v Messages that begin with
prefix IDS and are in range 0000–0999 are from Data Protection for EMC
Symmetrix for R/3. v Messages that begin with prefix IDS and are in
range 1000–1999 are from Data Protection for IBM ESS for mySAP.com for
DB2 UDB and Data Protection for IBM ESS for mySAP.com for Oracle.

Message Format The following examples describe the Tivoli Storage
Manager message format: The callouts to the right identify each part
of the format.

The severity codes and their meanings are as follows:

E Error
Processing cannot continue.

W Warning
Processing can continue, but problems may occur later.

I Information
Processing continues. User response is not necessary.



Good Luck, Oksana


On Thu, 18 Aug 2005 09:53:08 GMT, "Tony Cummins"
<t.cummins@compserv.gla.ac.uk> wrote:

>I've run into a few problems running a Tivoli system with both 6.5 and 5.1
>boxes. So far, I've been unable to find a solution or even a decent lead
>that might help me sole the issues. Anyone here had similar problems to the
>following two scenarios ?
>
>1. NW 6.5 sp3, TSM Client v 5.02.04, TSAFS.NLM v6.50 and I'm getting the
>following:
>
>(TSAFS.NLM 6.50.11 313) A file cannot be read
>
>(TSAFS.NLM 6.50.11 269) No data sets can be found
>---------------------------------------------------------------------------------
>2. NW 5.1 sp8, TSM Client v 5.02.04, TSA500 v5.05i and I get:
>
>(TSA500.NLM 5.5 259) This program cannot allocate a memory handle
>---------------------------------------------------------------------------------
>
>I'm guessing that the last three digits in the TSA message is an error code
>of some kind, I can't seem to find a resource that gives me a solution.
>
>cheers,
>
>Tony
>

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.