> Hi,
>
[quoted text clipped - 14 lines]
>
> Rahul
Hi,
I have found out the cause of it.
It seems we were accessing the application through some alias given to
the machine.
Further,
"db2 get snapshot for application applid <application_id>" was also
helpful in finding the actual ip address.
Rahul
> Hi,
>
[quoted text clipped - 6 lines]
>
> Can somebody explain what are these indifferent application ids?
The DRDA protocol does not allow application IDs to start with a digit
(0-9). Therefore, all digits in the first character are mapped to the
letters G thru P.
> Also, i want to find out the ip address of the machine is running
> these applications(because some of the locks are being caused because
> of that application id).
You may want to have a look here:
http://www.ibm.com/developerworks/db2/library/techarticle/dm-0402greenstein/inde
x.html

Signature
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany
Rahul B - 29 Aug 2007 07:10 GMT
> > Hi,
>
[quoted text clipped - 21 lines]
> DB2 z/OS Utilities Development
> IBM Germany
Knut,
It is the problem only with some application ids, rest all application
ids showed correct ip addresses.
Rahul
Knut Stolze - 29 Aug 2007 17:24 GMT
>> > Hi,
>>
[quoted text clipped - 13 lines]
> It is the problem only with some application ids, rest all application
> ids showed correct ip addresses.
If the first digit (first 4 bits) is 0 thru 9, it is mapped to G thru P. If
the first 4 bits already represent a letter A thru F, then no such mapping
is necessary. Therefore, some IP addresses are already correct while some
have to be mapped back - depending on the first letter.

Signature
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany