A fix is available
APAR status
Closed as new function.
Error description
When SRCSSID=TRGSSID CAF connection is choosen instead of TCPIP and there is no way to force a TCPIP connection to the remote target DB2. When there are two DB2 subsystems with the same subsystem name and one is CAF connected and the other TCPIP connected, CT-TS assumes that the is only one subsystem. The CAF connection works and is used for the source and target subsystems. This enhancement allows the target to be connected using TCPIP when the subsystems names are the same. A new command SET REMOTE-CONNECT-TYPE(C|D|T) is available for this specification where C=CAF, D=DDF and T=TCPIP. Specifying T indicates that the same named subsystem for the source and target is two different subsystems. If no SET command is specified, the normal C, D, T connection progression is used. Note that this command is now the preferred way to specify all DDF and TCPIP connections, not just when the two subsystems have the same name. For example, if TCPIP is used and DDF fails, error messages are printed for the DDF failure. If SET REMOTE-CONNECT-TYPE(T) then DDF is not attempted and thus there are no error messages.
Local fix
Problem summary
**************************************************************** * PROBLEM DESCRIPTION: When SRCSSID=TRGSSID CAF connection * * is choosen instead of TCPIP and there * * is no way to force a TCPIP connection * * to the remote target DB2. * * * * When there are two DB2 subsystems with * * the same subsystem name and one is CAF * * connected and the other TCPIP connected,* * CT-TS assumes that the is only one * * subsystem. The CAF connection works and * * is used for the source and target * * subsystems. This enhancement allows * * the target to be connected using TCPIP * * when the subsystems names are the same. * * * * A new command * * SET REMOTE-CONNECT-TYPE(C|D|T) * * is available for this specification * * where C=CAF, D=DDF and T=TCPIP. * * Specifying T indicates that the same * * named subsystem for the source and * * target is two different subsystems. * * * * If no SET command is specified, the * * normal C, D, T connection progression * * is used. * * * * Note that this command is now the * * preferred way to specify all DDF and * * TCPIP connections, not just when the two* * subsystems have the same name. For * * example, if TCPIP is used and DDF fails,* * error messages are printed for the DDF * * failure. If SET REMOTE-CONNECT-TYPE(T) * * then DDF is not attempted and thus there* * are no error messages. * * MR1203082623 * **************************************************************** * RECOMMENDATION: APPLY the PTF. * **************************************************************** Code has been changed to correct this condition. When there are two DB2 subsystems with the same subsystem name and one is CAF connected and the other TCPIP connected, CT-TS assumes that the is only one subsystem. The CAF connection works and is used for the source and target subsystems. This enhancement allows the target to be connected using TCPIP when the subsystems names are the same.
Problem conclusion
Temporary fix
Comments
APPLY the PTF.
APAR Information
APAR number
PK77457
Reported component name
DB2 CLONING TOO
Reported component ID
5655N1000
Reported release
210
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-12
Closed date
2009-02-16
Last modified date
2009-03-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK44079
Modules/Macros
CKZ00501 CKZ00536 CKZ00545 CKZ00547 CKZ00600 CKZ00611 CKZ00616 CKZ00780
Fix information
Fixed component name
DB2 CLONING TOO
Fixed component ID
5655N1000
Applicable component levels
R210 PSY UK44079
UP09/02/18 P F902
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUUE","label":"IBM Db2 Cloning Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 February 2021