John I believe that there is no such thing as a PMO of Convert. The 'getting' application should do the convert. Havign the 'getting' application do the conversion makes much more sense as the 'putting' application has no idea where the message will end up (platform wise)
If the final destination application isn't behaving and converting then a channel between the 2 OS/390 Qmgrs could do it.....but it may be easier to change the applicaton so that it behaves itself. :) Failing that, maybe you could write an application that sat in the middle that did the conversion for it? Kevin Ferguson
From: "Dawson, John" <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Client conversion from Windows to OS/390 Date: Thu, 5 Dec 2002 12:14:35 -0600 Hello, I have a client on a Windows NT platform that is putting a message onto a remote queue defined on a OS/390 platform, which in turn sends the message to a second OS/390 platform. The application on the second OS/390 platform does not do a 'get' with convert and thus the message is still in ascii code. What do I need to do to convert the message to EBCIDC before the message is 'put' from the client. Thanks, John Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
_________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
