| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem triggering MQ apps on Tandem |
« View previous topic :: View next topic » |
| Author |
Message
|
| Nige Roberts |
 Posted: Wed Jan 16, 2002 4:07 am Post subject: |
 |
|
Newbie
Joined: 15 Jan 2002
Posts: 2
Location: Chester, UK
|
Can anyone help with a problem we have.
We're sending messages from NT to Tandem, with the Tandem application being triggered on receipt of the first message. Sequence is
1. Message arrives on init Q okay
2. trigger monitor invoked OK
3. Application started OK
4. Application unable to retrieve QM & Q details from the trigger monitor (can't inspect it either) |
|
| Back to top |
|
 |
| donthomas |
| Posted: Wed Jan 16, 2002 9:41 am Post subject: |
|
|
Novice
Joined: 28 Nov 2001
Posts: 23
Location: EDS, Pittsburgh, PA
|
You didn't say what RC you were getting from the application but I suspect that it's 2035. The problem sounds very much like an authority issue. Make sure your app is running under an ID that is recognized by the qmgr and has the necessary authority to access that queue. Tandem is very different from the other OS's that I've worked with and particularly in regards to the OAM.
_________________
Don Thomas
412-203-3539 |
|
| Back to top |
|
|
| Nige Roberts |
| Posted: Wed Jan 16, 2002 10:00 am Post subject: |
|
|
Newbie
Joined: 15 Jan 2002
Posts: 2
Location: Chester, UK
|
Problem is that we don't get an RC. The app works when the QM and Q are hard coded, so is looks like a problem accessing the data sent to the app from the trigger monitor.
We've tried "READ REQUEST-IN" ($RECEIVE) and ACCEPT, which both just hang (ACCEPT was used in desperation!) |
|
| Back to top |
|
|
| Tibor |
| Posted: Mon Jan 21, 2002 5:36 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| Quote: |
On 2002-01-16 10:00, Nige Roberts wrote:
Problem is that we don't get an RC. The app works when the QM and Q are hard coded, so is looks like a problem accessing the data sent to the app from the trigger monitor.
We've tried "READ REQUEST-IN" ($RECEIVE) and ACCEPT, which both just hang (ACCEPT was used in desperation!)
|
I developed apps on Tandem in C and its worked fine. I think so you have a COBOL problem because the trigger info (MQTMC[2] structure) arriving at command line. If you are working with COBOL85 try 'GETSTARTUPTEXT' (a Guardian call), for example:
<pre>
01 start-up.
02 type pic x(6).
88 stdin value "IN ".
88 stdout value "OUT ".
88 volume value "VOLUME".
88 commandline value "STRING".
02 info pic x(60).
02 result pic s9(4) comp. initialize start-up
...
set commandline of start-up to true
enter "GETSTARTUPTEXT" of cobollib
using type of start-up,
info of start-up
giving result of start-up
</pre>
I don't know which compiler are you using, but you can find the description of native function calls in Cobol manual.
|
|
| Back to top |
|
|
| Tibor |
| Posted: Mon Jan 21, 2002 5:41 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
Try again... HTML is off...
| Code: |
01 start-up.
02 type pic x(6).
88 stdin value "IN ".
88 stdout value "OUT ".
88 volume value "VOLUME".
88 commandline value "STRING".
02 info pic x(60).
02 result pic s9(4) comp. initialize start-up
...
set commandline of start-up to true
enter "GETSTARTUPTEXT" of cobollib
using type of start-up,
info of start-up
giving result of start-up
|
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
