| Author |
Message
|
| sri_csee1983 |
 Posted: Wed Apr 02, 2008 3:55 am Post subject: |
 |
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Dear Vitor,
01 CMD_FEE_INQ.
02 HD_CMD_FEE_INQ.
03 HD_CICS_TRAN_ID PIC X(04) VALUE SPACES.
03 HD_MEG_DELIM PIC X(03) VALUE SPACES.
03 HD_EXTRNL_TRAN_CODE PIC 9(04) VALUE ZEROES.
03 HD_TELLER_ID PIC 9(06) VALUE ZEROES.
03 HD_OVER_TELLER_ID PIC 9(06) VALUE ZEROES.
03 HD_TRANS_SEQ_NUM PIC 9(04) VALUE ZEROES.
03 HD_TRANS_STAT_BYTE PIC X(03) VALUE SPACES.
03 HD_TRANS_TIME PIC X(06) VALUE SPACES.
03 FILLER PIC X(04) VALUE SPACES.
02 CMD_FEE_INQ_FIELDS.
03 CMD_FS_REF_NO PIC X(16) VALUE SPACES.
03 CMD_FS_IDENTIFIER PIC X(0 VALUE SPACES.
03 CMD_FS_OPERT_ID PIC X(12) VALUE SPACES.
03 CMD_FS_COUNT_ID PIC X(0 VALUE SPACES.
03 CMD_PRINC_AMT PIC 9(10) VALUE ZEROES.
03 CMD_EXPT_ACTU_PAYOUT PIC 9(10) VALUE ZEROES.
03 CMD_MONEY_TRANS_TYPE PIC X(03) VALUE SPACES.
03 CMD_DEST_CUNTRY PIC X(02) VALUE SPACES.
03 CMD_ORIG_CUNTRY PIC X(02) VALUE SPACES.
03 CMD_DEST_CURR_CODE PIC X(03) VALUE SPACES.
03 CMD_ORIG_CURR_CODE PIC X(03) VALUE SPACES.
03 CMD_MSG1 PIC X(69) VALUE SPACES.
03 CMD_MSG2 PIC X(69) VALUE SPACES.
03 CMD_MSG3 PIC X(69) VALUE SPACES.
03 CMD_MSG4 PIC X(69) VALUE SPACES.
03 CMD_MSG5 PIC X(69) VALUE SPACES.
03 CMD_MSG6 PIC X(69) VALUE SPACES.
03 CMD_MSG7 PIC X(69) VALUE SPACES.
03 CMD_PREFE_CUST_NUM PIC 9(09) VALUE ZEROES.
03 CMD_DELIVERY_SERV_CODE PIC 9(03) VALUE ZEROES.
03 CMD_SENDER_PROMO_CODE PIC X(20) VALUE SPACES.
03 CMD_PROMT_SEQ_NUM PIC X(10) VALUE SPACES.
above is the copy book from which I created the message definition file. As soon as created the message definition file I am having msg_CMD_FEE_INQ under messages in the mxsd file. (This I see in the MB Toolkit Message Definition Editor) In the MQInput Node what should I give in Message Type. Whether msg_CMD_FEE_INQ? Now I have given it as CMD_FEE_INQ. Reason for that is while creating the msg definition file from COBOL CPY bk we get a log and in that log the type is specified as CMD_FEE_INQ. And also whether the Message Set ID (in my scenario APCELAS002001) should be sent in with the incoming msg? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Apr 02, 2008 4:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sri_csee1983 wrote: |
| As soon as created the message definition file I am having msg_CMD_FEE_INQ under messages in the mxsd file. (This I see in the MB Toolkit Message Definition Editor) In the MQInput Node what should I give in Message Type. Whether msg_CMD_FEE_INQ? Now I have given it as CMD_FEE_INQ. Reason for that is while creating the msg definition file from COBOL CPY bk we get a log and in that log the type is specified as CMD_FEE_INQ. And also whether the Message Set ID (in my scenario APCELAS002001) should be sent in with the incoming msg? |
You have a number of options here. Firstly (and my recommended path) is try some of the differing values to see what happens! Another alternative is to spend some time reading the broker documentation which explains how message type is set and obtained.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Wed Apr 02, 2008 10:28 pm Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Dear Vitor,
One great thing is atlast I am able to populate the Message Set in my default properties of the MQInput Node. This I have uninstalled and reinstalled the Toolkit. After that I am able to do it. Now type of the message is not getting populated. What may be the reason.  |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Apr 02, 2008 11:56 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| Now type of the message is not getting populated. What may be the reason. |
Your toolkit needs to be updated to the latest fixpack?
Earlier you posted this:
| Quote: |
| In the MQInputNode properties, I have set MRM as the default Message Domain, Message Set to the name the of Message set ( Actually it didnt come in the drop down) , Message Type as Message Definition File(EBCDIC mxsd) and Message Format as CWF1 |
'Message Type' identifies a message definition. It does not identify a message definition file. It should be set to one of the messages listed under 'Messages' in the Outline view of the Message Set Editor. 'EBCDIC mxsd' sounds like the wrong value. |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Thu Apr 03, 2008 3:41 am Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Thanx a lot Kimbert and Vitor,
Atlast my message flow is parsing the values  . Now I am able to see the incoming message. It is going out of the compute node finishing all set statements in that. But it again comes back to the MQInput node with the exception RM Discriptor Not Avaiable with the number 5313. I have gone through the other postings for this error and cannot find the solution. Can u people give a solution for the same. |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Thu Apr 03, 2008 7:07 pm Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Dear Friends,
I am now able to cinvert the messages without any errors  . Now only problem is my MQOutput Node is configured to Remote Queue. So my broker fails to open the queue with the reason code 2184. Please let me know How shud I configure my MQOutput Node to a Remote Queue?  If it is a local queue, The messages are coming without any issues. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Apr 04, 2008 12:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sri_csee1983 wrote: |
| Please let me know How shud I configure my MQOutput Node to a Remote Queue? |
The same way you configure it for a local queue. What you should do here is configure the Remote queue correctly; Mr Google points this out:
| Quote: |
2184 MQRC_REMOTE_Q_NAME_ERROR
Explanation:
On an MQOPEN or MQPUT1 call, one of the following occurred:
A local definition of a remote queue (or an alias to one) was specified, but the RemoteQName attribute in the remote queue definition is entirely blank. Note that this error occurs even if the XmitQName in the definition is not blank.
The ObjectQMgrName field in the object descriptor is not blank and not the name of the local queue manager, but the ObjectName field is blank.
Completion Code:
MQCC_FAILED
Programmer Response:
Alter the local definition of the remote queue and supply a valid remote queue name, or supply a nonblank ObjectName in the object descriptor, as appropriate.
|
 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Fri Apr 04, 2008 6:08 am Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Dear Victor,
Have done with it. Thanx a lot. I have made it. It clearly shows even a person with 0 knowledge in message broker, but he knows that ther is a forum called www.mqseries.net he will be able to implement any project in MQ and MB. hats off to this forum and all members. I may post again for the conversion from XML to CWF and also will ans if I know the answer for any post. Once again thanx a lot  |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Apr 04, 2008 6:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sri_csee1983 wrote: |
| It clearly shows even a person with 0 knowledge in message broker, but he knows that ther is a forum called www.mqseries.net he will be able to implement any project in MQ and MB. |
Well obviously  for getting it sorted, though I do feel your claim is a little optimistic! Obtaining a little knowledge first, and perhaps a smear of training, will smooth the process.
| rjlfc wrote: |
| I may post again for the conversion from XML to CWF |
Having achieved this, you should find future developments will go a lot smoother for you.
| rjlfc wrote: |
| also will ans if I know the answer for any post. |
It's this sort of thing which keeps the board going. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
