By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,558 Members | 1,060 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,558 IT Pros & Developers. It's quick & easy.

Program querying DAS for isntances/databases

P: n/a
I have a tool that's trying to locate DB2 instances via the DAS, but
apparently is not finding them, even though the IBM tools say taht the
DAS is up and running and BTW, here's the list of instances on the
server.

I managed to monitor the network traffic to see what is going on, and
spotted something that looks odd in the data stream. The tool attempts
to connect to the DAS (ome message goes out and there's a response),
then the second message goes out and this comes back:

00000 00 a3 00 00 00 00 00 00 53 51 4c 44 42 32 52 41 ........SQLDB2RA
00010 07 00 02 00 00 00 40 01 00 00 00 53 51 4c 43 41 ......@....SQLCA
00020 20 20 20 88 00 00 00 7b fc ff ff 2b 00 43 6f 72 ....{...+.Cor
00030 72 75 70 74 69 6f 6e 20 64 65 74 65 63 74 65 64 ruption detected
00040 20 69 6e 20 70 61 72 73 69 6e 67 20 74 68 65 20 in parsing the
00050 72 65 71 75 65 73 74 ff 00 20 20 20 20 20 20 20 request..
00060 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
00070 20 20 20 53 51 4c 45 52 41 41 53 00 00 00 00 00 SQLERAAS.....
00080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00090 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 20 ...

Where can I go to find a detailed description of the messages that are
being sent and received?

At first glance, it really looks as though the second outgoing message
is not correct. Alternate is that the DAS may have been changed subtly
to be black-and-white on messages.

Thanks in advance!

Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
byrocat wrote:
I have a tool that's trying to locate DB2 instances via the DAS, but
apparently is not finding them, even though the IBM tools say taht the
DAS is up and running and BTW, here's the list of instances on the
server.

I managed to monitor the network traffic to see what is going on, and
spotted something that looks odd in the data stream. The tool attempts
to connect to the DAS (ome message goes out and there's a response),
then the second message goes out and this comes back:

00000 00 a3 00 00 00 00 00 00 53 51 4c 44 42 32 52 41 ........SQLDB2RA
00010 07 00 02 00 00 00 40 01 00 00 00 53 51 4c 43 41 ......@....SQLCA
00020 20 20 20 88 00 00 00 7b fc ff ff 2b 00 43 6f 72 ....{...+.Cor
00030 72 75 70 74 69 6f 6e 20 64 65 74 65 63 74 65 64 ruption detected
00040 20 69 6e 20 70 61 72 73 69 6e 67 20 74 68 65 20 in parsing the
00050 72 65 71 75 65 73 74 ff 00 20 20 20 20 20 20 20 request..
00060 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
00070 20 20 20 53 51 4c 45 52 41 41 53 00 00 00 00 00 SQLERAAS.....
00080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00090 00 00 00 20 20 20 20 20 20 20 20 20 20 20 20 20 ...

Where can I go to find a detailed description of the messages that are
being sent and received?

At first glance, it really looks as though the second outgoing message
is not correct. Alternate is that the DAS may have been changed subtly
to be black-and-white on messages.

Thanks in advance!


It appears that you are using V7. Is it correct?

What API you are trying to use?

Proper way to list DB2 instances is to execute as a priviledged user (root on
Unix, System administrator on Windows) db2ilist.

Jan M. Nelken

Nov 12 '05 #2

P: n/a
I need to do this remotely, via port 523 using TCP/IP.

Nov 12 '05 #3

P: n/a
byrocat wrote:
I need to do this remotely, via port 523 using TCP/IP.


As far as I know - DAS does not have externalised API - hence you have to rely
on GUI interface with DISCOVERY SEARCH.

Jan M. Nelken
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.