The Bind customization task, ssid0002, issues a warning message stating that SETUP00 includes a duplicate definition for the local subsystem.

Document ID : KB000006471
Last Modified Date : 14/02/2018
Show Technical Document Details

When installing or upgrading the CA Database Management Solutions for DB2 for z/OS, the Bind Product Packages and Plans customization task, ssid0000, may issue warning message:

**** Parmlib member SETUP00 includes remote location DDF_location_name/ssid.
**** This is a duplicate definition for local subsystem DDF_location_name 
**** and will be omitted from remote DRDA package binds.                  




In the SETUP definition for this subsystem, ssid, check the settings for the following two parameters in the subsystem definition for this ssid:




It is most likely that the SSREMOTE parameter is set to (YES) and that the LOCATION parameter is not set to (LOCAL).


For the local subsystem definition, where you are executing the bind statements, I would normally expect to see the following:

SSID (ssid)
LOCATION (LOCAL)    <-- specify LOCAL not a location name               
LOCSSID (ssid)

If it is not your intention to generate remote bind statements then set SSREMOTE to (NO).

If however, your intention is to bind packages locally and remotely then specify SSREMOTE (YES). Please be aware though, that if you have several remote subsystems assigned to a given local subsystem, you may find that this job becomes too large, or one or more of the subsystems may not be active.

SSID (ssid)
LOCSSID (ssid)

LOCATION (DDF_location_name_1
LOCSSID (remote_ssid_1

LOCATION (DDF_location_name_2
LOCSSID (remote_ssid_2

If this occurs, change the SETUPxx member DRDA Remote Binds option (SSREMOTE) to NO for each subsystem and use bind task 0 to generate and execute the bind job separately on the local subsystem and then on each remote subsystem.  

Additional Information:

Please refer to the following documentation for further details on the 

Bind Product Packages and Plans customization task

Further details on the SETUP Parmlib member can be referenced at

Create a SETUP Global Parmlib member