If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Setting Up of Aliases from converting from DB2 Private Protocol to DRDA

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-29-09, 14:52
Shamik Shamik is offline
Registered User
 
Join Date: Sep 2009
Posts: 1
Setting Up of Aliases from converting from DB2 Private Protocol to DRDA

Hi,

Let me first state that we have successfully implemented a project that involved conversion from DB2 Private Protocol to DRDA access.

We followed the concept given in http://publib.boulder.ibm.com/infoce...bjnqmstr04.htm

But, then the DBA of our concern asked us not to define the alias in the LOCAL location. He stressed on just defining the alias in the REMOTE location. This is violating point # 4 in the above given website.

And, much to our surprise the BIND job ended with a Return Code of 4 and the COBOL+DB2 program ran successfully. That is very puzzling following the fundamentals of DRDA.

If there is no LOCAL ALIAS then how is the program able to find out
the exact LOCATION of the remote table. There are other related questions as well.

Could you please throw some light on this issue so that we may resolve this problem? We still believe that the LOCAL aliases are must.

Thanks & Regards,
Shamik
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On