dba-db2.com - db2 performance tuning, DB2 tuning,db2 performance,sql tuning db2, DBA in DB2, DBA Scripts,DB2,DB2 consulting,DB2 consultant,DB2 architecture,DB2 training

DB2 - SQL2033N and TSM reason code: 610

28 April,2011 by Tom Collins

The online definition is “An error occurred while accessing TSM during the processing of a database utility”

 The 610 code means the message catalog  aka  dscenu.txt can’t be
found.
I see this error usually when a DBA configures TSM at the DB2 instance level.

When you  configure DSMI_DIR, ensure it points to a directory
containing the correct dscxxx.txt file.

Usually,the administrator points to an incorrect DSMI_DIR or simply , the file is missing. I configure TSM and DB2 with a script – per instance , which assists in minimising the occurrences of these errors.

 Use dsmrc.h for a full list of TSM client API return codes

Read More

TSM backup client configuration for DB2 on Linux - DBA DB2

DB2 and TSM Cross-node recovery - DBA DB2

TSM losing connection with DB2 - DBA DB2

Author: Rambler(http://www.dba-db2.com)

Share:

Posted by Tom Collins at 12:44 PM in Backup & Restore | Permalink | Comments (0) | TrackBack (0)

Searches: , , ,

Verify your Comment

Previewing your Comment

Posted by: |

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment on DB2 - SQL2033N and TSM reason code: 610

Comments are moderated, and will not appear until the author has approved them.

dba-db2.com | DB2 Performance Tuning | DBA DB2:Everything | FAQ | Contact | Copyright