ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Generating & Sending MQRFH as a header

Post new topic  Reply to topic
 Generating & Sending MQRFH as a header « View previous topic :: View next topic » 
Author Message
pankajg
PostPosted: Fri May 17, 2002 10:43 am    Post subject: Generating & Sending MQRFH as a header Reply with quote

Acolyte

Joined: 11 Oct 2001
Posts: 53

Hi All

My following code in the request flow - compute node for generating the MQRFH & sending it as a header is working ,,,,,

-------start ---------------------------------------------------
DECLARE I INTEGER;
SET I = 1;
WHILE I < CARDINALITY(InputRoot.*[]) DO
SET OutputRoot.*[I] = InputRoot.*[I];
SET I=I+1;
END WHILE;
SET OutputRoot.Properties.MessageSet = 'DK7MFIS0GC001';
SET OutputRoot.Properties.MessageType = 'TRIUMPH_REQ';
-- Enter SQL below this line. SQL above this line might be regenerated, causing any modifications to be lost.
Set OutputRoot.Properties.MessageDomain = 'MRM';
Set OutputRoot.Properties.MessageFormat = 'CWF';
Set OutputRoot.MQMD.Format = 'MQHRF ';


-- Convert from ascii to ebcdic

Set OutputRoot.MQMD.CodedCharSetId = 500;
Set OutputRoot.MQMD.Encoding = 785;
Set OutputRoot.Properties.CodedCharSetId = 500;

-- Coding for RFH part

SET OutputRoot.MQRFH.StrucId = 'RFH ';
SET OutputRoot.MQRFH.Version = 1;

-- SET OutputRoot.MQRFH.StrucLength = 144;

SET OutputRoot.MQRFH.Encoding= 785;
SET OutputRoot.MQRFH.CodedCharSetId = 0;
SET OutputRoot.MQRFH.Format = 'MQSTR ';
SET OutputRoot.MQRFH.Flags = 0 ;

SET OutputRoot.MQRFH.OPT_APP_GRP = 'OPT_APP_GRP ';
SET OutputRoot.MQRFH.OPT_APP_GRP_VALUE = 'AAA ';
SET OutputRoot.MQRFH.OPT_MSG_TYPE = 'OPT_MSG_TYPE ';
SET OutputRoot.MQRFH.OPT_MSG_TYPE_VALUE = 'AAA_REQUEST _OF ';

-------ends ---------------------------------------------------


& the corresponding trace file print is ,,,

(0x1000000)MQRFH = (
(0x3000000)StrucId = 'RFH '
(0x3000000)Version = 1
(0x3000000)StrucLength = 146
(0x3000000)Encoding = 785
(0x3000000)CodedCharSetId = 500
(0x3000000)Format = 'MQSTR '
(0x3000000)Flags = 0
(0x3000000)OPT_APP_GRP = 'DK7MFIS0GC001'
(0x3000000)OPT_APP_GRP_VALUE = 'GNA '
(0x3000000)OPT_MSG_TYPE = 'TRIUMPH_REQ'
(0x3000000)OPT_MSG_TYPE_VALUE = 'AAA_REQUEST _OF '
)

I have the following questions...

1. If you notice carefully the StrucLength is commented, How come MQSI is setting it & that too to 146. ( How is this figure arrived at )

2. How are the fields MQRFH.OPT_APP_GRP & MQRFH.OPT_MSG_TYPE getting modified by MQSI.

3. Why was i getting errors while i tried to set the StrucLength .( hence i had to skip it & it worked.) can we set itr to some specific values only..

4. Shouldnt we be referring to the tag / value fields like OPT_APP_GRP using the parent field name "NeonOptionBuffer ".

5. What is exact IBM name of the parent field "NeonOptionBuffer ".

Thanking you in anticipation...
_________________
Regards
Pankaj
Back to top
View user's profile Send private message Send e-mail
CodeCraft
PostPosted: Sat May 18, 2002 12:52 am    Post subject: Reply with quote

Disciple

Joined: 05 Sep 2001
Posts: 195

When you're outputting a message, each portion of the message (MQMD, MQRFH, message body) has it's own parser (parser+writer) associated with it.

The header parsers (MQMD, MQRFH, etc) are intelligent and do fix ups of the headers so that the contents are valid according to what is defined in the Properties subtree. The application type and group fields are being fixed up with information corresponding to the MRM message set and type in use.

They will also calculate the lengths for the various portions of the message or message structures as they would be when serialised to an actual message bitstream.

If you output the message, and then check it by reading it with RFHUTIL or another tool, you should be able to work out where the headers are (using MQMD and MQRFH as eyecatchers) and consequently what the lengths are, proving the length of the RFH is indeed as calculated.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Generating & Sending MQRFH as a header
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.