Richard, I'm familiar with all the codes and stuff, thanx. I'm just hoping that someone else has seen this. the only thing that changed were the names of the MQ datasets in the JCL for the IDMS jobs. It looks like some customization is missing for the VEGA piece or for IDMS. I have had to add pieces during various stages of the MQ rollout for V5R3, so I'm sort of expecting to have to do that again.
Thanx anyway for the feedback (and to Rick also) EARmerc ----- Original Message ----- From: "Richard Crook" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 11, 2003 04:53 P Subject: Re: Migrating MQSeries libraries in IDMS > Ernest, > 2058 is a Q_MGR_NAME_ERROR. Is your IDMS connection using the defaults > module CQSBDEFV to get the Qmgr name? If so, did you update this with the > 5.3 install? > > Just a thought. > > Richard. > > > > > > earMERC Roberts <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 12/09/2003 > 08:21:27 > > Please respond to MQSeries List <[EMAIL PROTECTED]> > > Sent by: MQSeries List <[EMAIL PROTECTED]> > > > To: [EMAIL PROTECTED] > cc: > Subject: Migrating MQSeries libraries in IDMS > > 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 > > > The contents of this e-mail are confidential. If you have received this > communication by mistake, please advise the sender immediately and delete > the message and any attachments. > Westpac Banking Corporation, ABN 33 007 457 141, is incorporated in > Australia > > > > --------------------------------------------------------------------- > The contents of this e-mail are confidential. If you have received this > communication by mistake, please advise the sender immediately and delete > the message and any attachments. > Nothing in this email designates an information system for the purposes of > Section 11(a) of the New Zealand Electronic Transactions Act 2002. > Westpac Banking Corporation, ABN 33 007 457 141, is incorporated in > Australia > --------------------------------------------------------------------- > > 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
