Thanx Javier, I was thinking along those lines, but I had no experience with the vegasoft product. What bothers me is that configuration info for the vegasoft product appears to have been kept in the old MQ lib. I'll take this back to out IDMS sysprog.
EARmerc ----- Original Message ----- From: "javier sotela" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 11, 2003 06:20 P Subject: Re: Migrating MQSeries libraries in IDMS > Ernest: > > We test idms 14.1 with MQ 5.3 without problems. The only difference is that > we are currently using OCA-MQ from Inneraccess, not the Vegasoft product, > but your erro 2058 means that there is a problem with te QMGR name. In our > Oca product we configure the QMGR in a module that idms use at start up. I > think that with Vega you have something like that. Check if you change the > QMGR name with the new release a proceed to configure in your Vega product. > I hope this help. > > Javier S. > > > >From: earMERC Roberts <[EMAIL PROTECTED]> > >Reply-To: MQSeries List <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Subject: Migrating MQSeries libraries in IDMS > >Date: Thu, 11 Sep 2003 16:21:27 -0400 > > > >We are under IDMS R14.1 VegaSoft Release V11101 V2R.7 and just went from > >MVS MQ Release V2.10 to V5.3 in our Test Environment. > >By that I mean we just updated the JCL to point to the new release (v5r3). > >I'm running on OS/390 V2.10 with MQS V5.3 > > > > I now see these errors: > > > >VG007899 V12 PROGRAM MQSERPL1 TASKID 24 LTE LD000006 > > MQCALL MQOPEN > > COMPLETION CODE 2 REASON CODE 2058 > > > >VG007853 V12 MQSERIES TRIGGER MONITOR ENCOUNTERED A FATAL MQSERIES ERROR > > COMPLETION CODE 2 REASON CODE 2058 > > IN MQOPEN, INITIATION QUEUE: VEGA.INIT > > > >VG007853 V12 MQSERIES TRIGGER MONITOR ENCOUNTERED A FATAL MQSERIES ERROR > > COMPLETION CODE 2 REASON CODE 2058 > > IN MQDISCEX, INITIATION QUEUE: VEGA.INIT > > > > > >VG007899 V12 PROGRAM MQSECHK1 TASKID 24 LTE LD000006 > > MQCALL MQBACK > > COMPLETION CODE 2 REASON CODE 2058 > > > >VG007899 V12 PROGRAM MQSECHK1 TASKID 24 LTE LD000006 > > MQCALL MQDISCEX > > COMPLETION CODE 2 REASON CODE 2058 > > > > > >Is there something that is not downward compatible with the new MQ Release? > >Has anyone else migrated the MQ from 2.1 to 5.3 in their IDMS environment? > >Is IDMS looking for a specific module that I should compile/assemble? that > >is the current direction I am looking. > > > > > > > >Ernest Roberts > >IT - Sr Sys Prog > >MBUSA, LLC > > > >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 > > _________________________________________________________________ > Protect your PC - get McAfee.com VirusScan Online > http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 > > 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
