Mark, Well, well, great minds think alike and all that. As you may have seen from an append a week or two ago I am in the middle of adding this type of support to my MO72 SupportPac.
As you know I'm sure, we can't publish the format of this file nor are we supposed to encourage reverse engineering. It's not that we're trying to be unhelpful it's the concern that you might expend considerable effort getting your code working and then in the following release we go and change the file format on you, causing your application to abend. However, just between you and me, as I'm sure you've discovered the file consists of a number of 'records'. Each of these records has a header which is the length of the record and the length of data within that record. In some cases the length of the data is 0 - indicating that although there is space in the file at this point there is no actual data. This can happen when a records length increases. For example, suppose you defined a channel X and then did an alter channel to add some channel exits or whatever. The definition of channel X is now longer and will no longer fit in the file at the point where it was. So, a new record is written and the old one is marked as length 0. We don't set the whole record to NULLs or whatever just because there's no real point. So, if you just look a the file with an editor it can look like the record is in there multiple times. Anyway, as I said, I am planning to put this kind of support into MO72, hopefully in the next couple of weeks. If you decide to continue with your own application then feel free to contact me if you get stuck. Cheers, P. Paul G Clarke WebSphere Messaging Clients IBM Hursley MQSeries List <[email protected]> wrote on 12/07/2006 23:30:10: > > I have a small Java utility that reads an AMQCLCHL.TAB file and > dumps the contents out in RUNMQSC format. It doesn't handle the > SSLPEER, Send Exit and Receive Exit information yet--I'm still > trying to figure out how they are referenced in the channel table > file. Don't suppose IBM would like the save me some time and share > the internal structure :-) > > I'll make it available for download off the web in due course, but > until then if anyone wants a copy, feel free to email me. > > PS. While using it internally I came across something odd. While > testing on a Linux MQ V6 system I added several client channels > through MQ Explorer, then updated one of them twice, saving changes > each time. I found I had three entries in the channel table with the > same name, one for each of the changes I made. IBM--possible bug? > > Mark Durman > MQ Solutions LLC Instructions for managing your mailing list > subscription are provided in the Listserv General Users Guide available at > http://www.lsoft.com > > Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
