IC70580: BRARCHIVE TERMINATES WITH BKI9211E AND BKI2024E: ERROR IN CONNECTION TO PROLE

APAR status

• Closed as fixed if next.

Error description

• Using IBM Tivoli Storage Manager Data Protection for Enterprise
  Resource Planning with two SERVER sections with equal server
  names, each with different management class specifications for
  usage on different days, in the init<SID>.utl file the brarchive
  or brbackup will fail with messages:
  
  BKI9211E: Additional support information: An exception was
  thrown at position: prole_control_handler.cpp(1246). (State 1)
  
  ( adsmserver.cpp(482):  )
  ( esd-para.cpp(4058):  )
  ( esd-para.cpp(2067):  )
    prole_control_handler.cpp(1218):
    prole_control_handler.cpp(999):
    esd-portalcommunicator.cpp(297):
    esd-portalcommunicator.cpp(247):
    esd-thread.cpp(64):
  BKI2024E: Error in connection to ProLE.
  BKI9204E: Additional support information: An exception was
  thrown at position: esd-portalcommunicator.cpp(327)
  (text=BKI9217E: Additional support information: An exception was
  thrown at position: esd-socket.cpp(319).
  ).
  BKI9300E: Additional support information: Aborting 'send'
  operation. See previous error.
  ::::
  BKI0024I: Return code is: 2.
  
  Massage "BKI1017E The server <server> is already defined.Please
  use another name or specify TCP_ADDRESS!" is expected instead of
  the BKI9211E and BKI2024E
  
  We use TSM server name in string form in the TDP code to
  distinguish one server from another. So it isn't allowed to have
  two equal TSM server names in the init<SID>.utl file.
  The right way to use different management classes for certain
  days of week is to create two stanzas for the same server in the
  dsm.sys. These stanzas will be absolutely the same except names.
  
  Data Protection Versions Affected:
  IBM Tivoli Storage Manager Data Protection for Enterprise
  Resource Planning at all currently supported versions.
  
  Initial Impact: Low
  
  Additional Keywords:
  TSM TDP ERP SAP BKI9211E BKI2024E
  

Local fix

• Name the stanzas in the init<SID>.utl file differently and
  - on Unix duplicate the specified stanza in the dsm.sys file and
    name both accordingly.
  - on Windows duplicate the <servername>.opt file and name both
    accordingly to the stanza names in the init<SID>.utl file.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users running TSM for ERP v.5.3.2.0          *
  *                 through v5.5.0.2 on all supported            *
  *                 operation systems and using in the *.utl     *
  *                 file several SERVER stanzas with equal       *
  *                 names.                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: In the case a user wants to use         *
  *                      different management classes for        *
  *                      certain days of the week and for this   *
  *                      reason defines two SERVER stanzas       *
  *                      with the same server names but          *
  *                      different management classes TSM for    *
  *                      ERP will stop processing with an        *
  *                      error message that does not correctly   *
  *                      identify the wrong configuration.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The TSM for ERP does not correctly handle the situation when
  in the *.utl file there are two or more SERVER stanzas with
  the same server names. This configuration is not supported and
  should be checked at the very beginning when the *.utl file is
  parsed, but the server names duplication check is missing. The
  correct configuration is described in the documentation.
  

Problem conclusion

Temporary fix

Comments

• This problem is fixed as of version 6.1 and higher versions.
  Apply version 6.1 or higher to resolve this problem.
  

APAR Information

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

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

Modules/Macros

• PROLE
  

Fix information

Applicable component levels

• R610 PSY

     UP

• R620 PSY

     UP