When I try copying procedures from one DB2 ssid to another I get -904 and 00D31057. Why?

Products

• RC Compare for DB2 for z/OS
• Database Analyzer for DB2 for z/OS
• Fast Unload for DB2 for z/OS
• Fast Check for DB2 for z/OS
• Fast Index for DB2 for z/OS
• Rapid Reorg for DB2 for z/OS
• CA Distributed Database Management
• CA Database Analyzer for DB2 for Oracle
• Database Analyzer (IMS Tools)
• Mainframe Configuration Manager for IMS for z/OS
• IMS TOOLS - MISC
• Compress Data Compression (IMS Tools)
• Database Analyzer for IMS for z/OS
• Database Copier for IMS for z/OS
• Database Organizer for IMS for z/OS
• Mainframe Extended Terminal Manager (IMS Tools)
• High Performance Recovery for IMS for z/OS
• Database Organizer (IMS Tools)
• Mainframe Program Restart Manager for IMS for z/OS
• Secondary Index Builder for IMS for z/OS
• Secondary Index for IMS for z/OS

Issue/Introduction

Description:

I am trying to use PDA to copy procedures from one DB2 ssid to another using DRDA but this is not working. The tables of the Communications DB seem to be fine and these links are used elsewhere with no problems.

Solution:

DRDA is used via the definitions held in SYSIBM.LOCATIONS and corresponding entries in SYSIBM.LUNAMES and/or SYSIBM.IPNAMES.

If the LINKNAME in LOCATIONS is matched with an entry in IPNAMES then TCP/IP is used for the DRDA connection.

If the LINKNAME is LOCATIONS is matched with an entry in LUNAMES then SNA is used for the DRDA connection.

IF the LINKNAME in LOCATIONS is matched with an entry in both IPNAMES and LUNAMES then TCP/IP is used.

TCP/IP can only be used for Plans/Packages bound with DBPROTOCOL(DRDA).

SNA can only be used for Plans/Packages bound with DBPROTOCOL(PRIVATE).

Up to and including R11 of PDA, plans should be bound with DBPROTOCOL(PRIVATE) - this requires SNA. As of R11.5 release and later there is now support for DBPROTOCOL(DRDA)

So please check to see what DBPROTOCOL value has been used in the binds for your plans/packages for PDA. (Plan names are listed in your highlvl.PARMLIB(PLANS00) member)

Then check to see that you have IPNAMES or LUNAMES correctly defined based on the DBPROTOCOL value used.

Environment

Release:
Component: DBA