Nope.. my dsm.sys is: SErvername TSM COMMmethod TCPip TCPPort 1500 TCPServeraddress dev36 passwordaccess generate SCHEDMODe PROMPT maxcmdretries 10 Nodename DB2 schedlogname /opt/tivoli/tsm/client/ba/bin/dsmsched.log schedlogretention 3 errorlogname /opt/tivoli/tsm/client/ba/bin/dsmerror.log errorlogretention 3
I notice in TSM messages theres this which is similar to what you mentioned: 2032 E DSM_RC_NO_OWNER_REQD Explanation: PASSWORDACCESS=generate establishes a session with the current login user as the owner. System Action: The system returns to the calling procedure. User Response: When using PASSWORDACCESS=generate, set clientOwnerNameP to NULL. Question is, why is this happening? I don't have an owner specified anywhere.. Regards, Gerald Wichmann Senior Systems Development Engineer Zantaz, Inc. 925.598.3099 (w) -----Original Message----- From: Dave Canan [mailto:[EMAIL PROTECTED]] Sent: Friday, May 31, 2002 2:21 PM To: [EMAIL PROTECTED] Subject: Re: DB2 backup problem.. These return codes are documented in the dsmrc.h file, located in the tsm\api\include directory. The return code here means: #define DSM_RC_NO_OWNER_REQD 2032 /* owner not allowed. Allow default */ Do you have an "owner" specified in the dsm.sys file stanza? You need to remove it. At 01:27 PM 5/31/2002 -0700, you wrote: >I can't find this return code anywhere.. anyone know what this means? >DB2 7.1 EE, TSM 4.2.2 server/client.. both boxes are solaris 2.8 > > >db2 => backup db ds50 online use tsm >SQL2062N An error occurred while accessing media >"/opt/db2udb/sqllib/adsm/libadsm.a". Reason code: "2032". > >db2 => ? sql2062n > > SQL2062N An error occurred while accessing media "<media>". > Reason code: "<reason-code>" > >Explanation: An unexpected error occurred while accessing a >device, file, TSM or the vendor shared library during the >processing of a database utility. The following is a list of >reason codes: > > >1 An attempt to initialize a device, file, TSM or the vendor >shared library failed. > >2 An attempt to terminate a device, file, TSM or the vendor >shared library failed. > >other If you are using TSM, this is an error code returned by >TSM. > >The utility stops processing. > >User Response: Ensure the device, file, TSM or vendor shared >library used by the utility is available and resubmit the utility >command. If the command is still unsuccessful, contact your >technical service representative. > > > >$ ls -l /opt/db2udb/sqllib/adsm/libadsm.a >-r-r-r-1 bin bin 93664 Apr 17 2001 /opt/db2udb/sqllib/adsm/libadsm.a > > > >Regards, > >Gerald Wichmann >Senior Systems Development Engineer >Zantaz, Inc. >925.598.3099 (w) Money is not the root of all evil - full backups are.
