Copying Database Analyzer for Db2 procedures from one DB2 ssid to another receiving SQL-904 and 00D31057
search cancel

Copying Database Analyzer for Db2 procedures from one DB2 ssid to another receiving SQL-904 and 00D31057

book

Article ID: 53103

calendar_today

Updated On:

Products

Database Analyzer for DB2 for z/OS

Issue/Introduction

Using Database Analyzer for Db2 for z/OS (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.

Resolution

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.