| Author |
Message
|
| Sukideman |
 Posted: Wed Nov 01, 2006 5:30 pm Post subject: TSH Header - byte order settings |
 |
|
Newbie
Joined: 26 Sep 2006
Posts: 8
Location: Melbourne
|
Hi,
I got a question regarding TSH (transmission Segment Header). Noticed that the byte oder in TSH is stating Big Endian. We are currently running a TCP/IP trace using ethereal on solaris 10 machines. We got MQ version 6.0.1.0 installed on two machines (both solaris 10), and was wondering why would the byte order be big endian when we are on Unix machines, though I suppose its more internal to MQ the way it handles data. Would appreciate if anyone can shed some light on this.
regards
Sukideman |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Nov 01, 2006 5:58 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
"Network byte order" is big endian, so it makes sense for the TSH to be as well...
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 01, 2006 5:58 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
TSH is an undocumented internal header.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Sukideman |
| Posted: Wed Nov 01, 2006 6:20 pm Post subject: |
|
|
Newbie
Joined: 26 Sep 2006
Posts: 8
Location: Melbourne
|
I suppose i just wanted to know whether there was any configuration that I might i missed in terms on byte order settings.
Is there anyway we can get some info regarding the header?
regards
Sukideman |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 01, 2006 6:58 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I doubt it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Nov 02, 2006 1:31 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| Sukideman wrote: |
| Is there anyway we can get some info regarding the header? |
If you need these details, please talk to your account reps in the first instance. I expect a legal agreement would have to be made between you and IBM before such details can be disclosed.
Do you have any more specific questions? |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Nov 02, 2006 3:04 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| Quote: |
| We got MQ version 6.0.1.0 installed on two machines (both solaris 10), |
The byte order in the TSH is the machine native ordering, not the O/S. Solaris 10 runs on Intel as well as Sparc architecture, so your machines must have Intel processors.
I find the terminology big- and little-endian rather confusing, and I have found the terms used to mean the same thing by different people!
I think big-endian means the usual UNIX ordering, i.e. 1 is represented in four bytes by the hex word 00 00 00 01, i.e. the first byte represents the most significant digits, and is the biggest.
So, little-endian is Windows ordering, where 1 is 01 00 00 00.
A more intuitive way of describing it is that UNIX is byte-ORDERED, i.e. the bytes are the same order as the usual (decimal) written representation of a number with the most significant digits first, and that Windows is byte-REVERSED, i.e. the bytes are in reverse order compared to the usual written number.
The TSH structure is IBM Confidential, so IBM will not disclose its contents to you without some serious negotiations taking place. The exception is the 10th byte, where the meaning of some of its possible values are exposed in the Intercomms manual.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| Sukideman |
| Posted: Wed Nov 08, 2006 8:27 pm Post subject: |
|
|
Newbie
Joined: 26 Sep 2006
Posts: 8
Location: Melbourne
|
Thank you all for the info..It does help in what i am doing..
regards
Sukideman  |
|
| Back to top |
|
|
|
|
