Hi Vince,
Our QMGRs are the same (we run two on our test LPAR). All associations were
intact through the MQ migration/upgrade. When the libs were changed in the
IDMS CV JCL, the errors showed up. Of course our IDMS guy is off today, so
I cannot check with him about the Vegasoft configuration today. The 2058
did not arise from any disappearing MQ system information because we
haven't changed it. What I suspect is that some mismatch, possibly
release-related, is now occurring in the Vegasoft product between what it
expects to see (from a systems standpoint) and what it actually is seeing.
Thankfully, this is the test environment we're talking about. That's where
mysteries should begin and end. I'll post the follow-up when I get some
results.
Thanx much,
Ernest Roberts
IT - Sr Sys Prog
MBUSA, LLC
----- Forwarded by Ernest Roberts/171/DCAG/DCX on 09/12/2003 12:58 PM -----
Hi Ernest
We are under idms r15.0, os/390 v2.10. We just went from MQ v2.1 to
v5.31 without any problems. The MQSeries support staff had us changes
the loadlib's in the CV startup desk to point to MQ v5.31. After the
Jcl change we recycle the CV. We have not experience any problems.
The 2058 reason code means, Queue Manager Name error. Is there a
difference Queue Manager name between v2.1 and v5.31. If so, the
vegasoft software have to connect to this new queue manager name.
Vince Gibson
IDMS Systems Support
-----Original Message-----
From: ernest.roberts
Sent: Thursday, September 11, 2003 3:21 PM
To: MQSERIES
Cc: ernest.roberts
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
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
