PK49837: MSG REMOTE SYSTEM'S SSID NOT FOUND

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In DB2 Object Compare Tool following apply of pk21021 OC jobs
  fail to find local DB2 ssid in Admin customization table,
  ADB2DB2D . Two major symptoms appear:
  .
  1. Error message appears stating:
  .
    Remote system's ssid not found in DB2 Admin's subsystem table
    (ADB2DB2D). Please check the customization
  .
  2. Jobstep DROP fails due to missing or  null value of &DB2SYS
     variable contents in jcl generated by skeleton GOCEDDL . The
     failing jcl shows no DB2 ssid, and appears as:
  .
     //SYSTSIN  DD *
     DSN SYSTEM()
  .
  Problem occurs on local DB2 ssid, where :locnam tag has not been
  provided in Admin customization table, ADB2DB2D. Using ADB2CUST
  to update the ADB2DB2D table to add a  :locnam.tag value has
  been demonstrated to bypass the problem, and should be used as a
  workaround until ptf availability. See chapter 2 step 7(b) for
  r710, or step 8(b) for r810, titled, 'Supplying information on
  the customization panels', for additional information on using
  ADB2CUST to perform this workaround.
  .
  Additional symptoms: UK22303 CM locnam location name CM db2sys
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  .
  

Local fix

• See above for directions on adding :locnam.tag value to table
  ADB2DB2D using ADB2CUST clist to perform customization update.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Object Compare with WSL.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Wrong target libs and  ssid used for    *
  *                      OC when two different location names    *
  *                      (:locnam) are used.                     *
  ****************************************************************
  * RECOMMENDATION: Apply The PTF.                               *
  ****************************************************************
  When two different location names (:locnam) are used, OC gets
  wrong target library and ssid.
  

Problem conclusion

• Incident is now resolved.  When WSL is used, APPLY points to the
  correct ssid and target libraries.
  

Temporary fix

Comments

•  PK53764 is the r720 solution.
  

APAR Information

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

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

Modules/Macros

•    GOCGCMP  GOC5
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R710 PSY UK36525

     UP08/05/28 P F805

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.