IC99638: QTBACKUPACTIVE RETURNS 2061 ERROR CODE

IBM Tivoli Storage Manager (TSM) Client 7.1.1 Downloads and READMEs
IBM Tivoli Storage Manager (TSM) client 6.3.2.x interim fix downloads - EOL

APAR status

• Closed as program error.

Error description

• If an API application is written using the qtBackupActive flag
  on a backup query, the query will return a 2061 return code
  which is DSM_RC_FS_NOT_REGISTERED.
  .
  A service trace may look similar to
  .
  02/07/2014 09:25:17.555 : dsmnextq.cpp        (1045):
  dsmGetNextQObj EXIT: rc = >2061<.
  02/07/2014 09:25:17.555 : dsmmsg.cpp          ( 766): dsmRCMsg
  ENTRY: tsmHandle=1 rc: 2061 msg : 000000000019A020
  02/07/2014 09:25:17.555 : dsmmsg.cpp          (1170):
  tsmHandle=1 rc: 2061 msg : >ANS0241E (RC2061) On dsmSendObj,
  dsmDeleteObj, or dsmUpdateFS the filespace is not registered.<
  .
  Using the API sample program will also show the error as below
  .
  Choose one of the following items to query:
  
   0.  Access Query
   1.  Backup Query
   2.  Archive Query
   3.  Management Class Query
   4.  Filespace Query
   5.  Session Info Query
   6.  API Version Query
   7.  Option File Query
   8.  Session Options Query
   9.  Quit
  10.  Proxy Node Authority
  11.  Proxy Node Peers
  
  Enter selection ==>1
                         Filespace:\FILESPACE
                         Highlevel:\*
                          Lowlevel:\*
                Object Type(D/F/A):F
     Active(A),Inactive(I),Both(B):A
  If root, query all owners? (Y/N):y
                 Object Owner Name:
     point in time date (MMDDYYYY):
     point in time time     (hhmm):
       Show detailed output? (Y/N):y
  On Restore, Wait for mount?(Y/N):y
  Are the above responses correct (y/n/q)?
  y
  *** dsmGetNextQObj failed:
  ANS0241E (RC2061) On dsmSendObj, dsmDeleteObj, or dsmUpdateFS
  the filespace is not registered.
  
  Initial Impact:  low
  Additional Keywords: API sample APISMP
  

Local fix

• write the code with the normal BackupQuery and set the type to
  active
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All backup-archive client versions           *
  *                 starting with 6.1.0 for all platforms.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 6.4.2 and 7.1.1. Note              *
  *                 that until the fixing levels are             *
  *                 available, this information is subject to    *
  *                 change at the discretion of IBM.             *
  ****************************************************************
  *
  

Problem conclusion

• The problem has been fixed so that it no longer occurs.
  

Temporary fix

• 6.3.2.3 for UNIX/Linux and 6.3.2.4 for Windows
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• TSMAPI64
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63M PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP

• R64A PSY

     UP

• R64H PSY

     UP

• R64L PSY

     UP

• R64M PSY

     UP

• R64S PSY

     UP

• R64W PSY

     UP

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71M PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP