Re: Client conversion from Windows to OS/390
If the msg is string format, the channel should convert it. You do have to stop/start the channel if it is running when you change the conversion option. -Original Message- From: Dawson, John [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 05, 2002 10:41 AM To: [EMAIL PROTECTED] Subject: Re: Client conversion from Windows to OS/390 Peter, Thanks for your reply. The channel from the Windows client to the first OS/390 is a svrconn, so there is no conversion parameter to turn on. I have tried to turn on conversion for the channel between the first OS/390 and the second OS/390, but that does not help. Regards, John -Original Message- From: Peter Heggie [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 05, 2002 12:34 PM To: [EMAIL PROTECTED] Subject:Re: Client conversion from Windows to OS/390 You could dedicate a pair of channels for this application and perform the conversion on the channel.. From: "Dawson, John" <[EMAIL PROTECTED]> on 12/05/2002 01:14 PM Please respond to MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Client conversion from Windows to OS/390 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 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 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 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
Re: Client conversion from Windows to OS/390
John, Kevin is right. The data conversion is done on the get. The conversion on the get will not take place if the message descriptor format field on the put is set to MQFMT_NONE. Make sure it is set to MQFMT_STRING. The data conversion also does not automatically take place and must be requested on the get. Bob Kevin Ferguson To: [EMAIL PROTECTED] Subject: Re: Client conversion from Windows to OS/390 Sent by: MQSeries List 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 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
Re: Client conversion from Windows to OS/390
John, Make sure the message descriptor format field on your MQPUT is set to MQFMT_STRING and not MQFMT_NONE. I don't believe data conversion can take place with it set to MQFMT_NONE. We have the same set up client - os/390 and it works great. No problems. Thanks, Bob "Dawson, John"To: [EMAIL PROTECTED] Sent by: MQSeries List mailto:[EMAIL PROTECTED]] Sent: Thursday, December 05, 2002 12:34 PM To: [EMAIL PROTECTED] Subject: Re: Client conversion from Windows to OS/390 You could dedicate a pair of channels for this application and perform the conversion on the channel.. From: "Dawson, John" <[EMAIL PROTECTED]> on 12/05/2002 01:14 PM Please respond to MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Client conversion from Windows to OS/390 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 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 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 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
Re: Client conversion from Windows to OS/390
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
Re: Client conversion from Windows to OS/390
Check the Convert Option of the GMO... Nii-Boi Kotei "Dawson, John" <[EMAIL PROTECTED]>@AKH-WIEN.AC.AT> on 12/05/2002 01:14:35 PM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by:MQSeries List <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Client conversion from Windows to OS/390 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 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
Re: Client conversion from Windows to OS/390
Peter, Thanks for your reply. The channel from the Windows client to the first OS/390 is a svrconn, so there is no conversion parameter to turn on. I have tried to turn on conversion for the channel between the first OS/390 and the second OS/390, but that does not help. Regards, John -Original Message- From: Peter Heggie [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 05, 2002 12:34 PM To: [EMAIL PROTECTED] Subject:Re: Client conversion from Windows to OS/390 You could dedicate a pair of channels for this application and perform the conversion on the channel.. From: "Dawson, John" <[EMAIL PROTECTED]> on 12/05/2002 01:14 PM Please respond to MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Client conversion from Windows to OS/390 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 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 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
Re: Client conversion from Windows to OS/390
You could dedicate a pair of channels for this application and perform the conversion on the channel.. From: "Dawson, John" <[EMAIL PROTECTED]> on 12/05/2002 01:14 PM Please respond to MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Client conversion from Windows to OS/390 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 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
