Issues with DBPROTOCOL(PRIVATE) to DRDA conversion

IBM's flagship relational database management system

Issues with DBPROTOCOL(PRIVATE) to DRDA conversion

Postby Abhi Shrivastava » Tue Jan 18, 2011 5:48 pm

Hi All

We have a requirement in our shop wherein we need to change, DBPROTOCOL parameter for plans and pacakages, from PRIVATE to DRDA.

Currently we are stuck with the below issue:

A) Given a scenario where, we have the same Collids across different DB2 subsystems :

CCM00001 DB2A DB00001 RACF1 RACF1
CCM00001 DB2B DB00002 RACF2 RACF2

and when we rebind the plans to a remote subsystem for expample: DB2C, we have statements like the following:


As we see, the PKLIST is a 3 part name, which has the SSID wildcarded and the Collection specified. While this may not be a problem, as it would be bound with a unique AUTHID, I think it is worthwhile to think about whether we should allow the same Collid for completely different testing environments/SSID/Authid. At the least it would provide clarity if unique names were used.

Could you please let me know if

it would cause a problem if left the way it is?
Determine what steps would be required to give the 2nd test environment with Authid of RACF2, a new Collection of CCM00002 and remove the packages and plans with CCM00001 (for RACF2)?

Abhi Shrivastava
Posts: 5
Joined: Fri Jan 07, 2011 3:09 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Issues with DBPROTOCOL(PRIVATE) to DRDA conversion


Return to DB2


  • Related topics
    Last post