MVSFORUMS.com

[Bravo]

Hi All,

I'm exposing the web service using IBM Webspher Message Broker (WMB) 6.1.

.Net appl invokes WMB web services, converts HTTP SOAP to MQ and put the message in OTMA queue to trigger Primary IMS transaction.

Response status from Primary transaction sent to WMB and HTTP reply is sent to close the .Net appl.

In IMS, Primary IMS transaction calls series of child IMS transactions which are responsible to write to a printer.

Synchoronous process is working fine,

Web Service (.Net) --> WMB ---> Primary IMS transaction
Primary IMS transaction (Response) --> WMB --> Web Service (.Net)

But IMS programmers complaining that Child transactions which is responsible to write to a zebra printer is not printing fine when IMS primary transaction is triggered from Web Service(WMB).

When they trigger IMS primary transaction manually from Green screen, the Child IMS transactions work fine and print out is also fine.

We involved IMS admin to look at this issue, to compare data from Web Service & manually and try to put trace on zebra printer. So far I did not hear any complains or difference but still IMS admin is investigating.

The IMS programmers came to a conclusion that IMS transaction triggers from WMB at some point lose the transaction tread that creates problems with the PCBs of programs down stream from primary transaction that write to a zebra printer.

Now they are asking to rewrite the WMB interface using IMS connect instead MQ message to trigger IMS transaction.

I do not know does IMS connect make a difference.

Any one knows why the zebra printer have alignment problem when IMS transaction trigger from WMB using OTMA?

Do I need set any attribute in MQIIH header?.

Is mismatch CCSID could cause printing problem?

Any inputs?