| Author |
Message
|
| bobbee |
 Posted: Tue Jun 27, 2006 9:59 am Post subject: z/OS TSO generating a 531 message for v6 installation |
 |
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
I have a new z/OS MQ install. While going into the MQ ops control panel in TSO I receive the following message imed.
ISPD014 - "CSQ531.SCSQMSGE' was not in catalog.
This is a true statement and I cannot argue. All the HLQ's are CSQ600. So where is this 531 message comming from???
bobbee |
|
| Back to top |
|
 |
| tleichen |
| Posted: Wed Jul 05, 2006 11:30 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
Somewhere in your logon profile, you are executing a CLIST or REXX program that is setting up your ISPF library assignments. You need to find this exec. At some time this was obviously set up this way, but this is very poor practice.
When you do an installation, do not put the version number on the HLQ, such as CSQ531, CSQ600, etc. By doing so, you have created your own problem every time you do a new installation, because anything that references the MQSeries libraries would need to be changed! 
Your logon proc should reference libraries that have a generic HLQ that will always contain the current version, such as MQPROD, MQTEST, etc. 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| bobbee |
| Posted: Wed Jul 05, 2006 3:08 pm Post subject: |
|
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
I had found it by turning on the panelid switch. I found the panel and searched the concat libs for it. In the panel there was a call to REXXO and it was passing the 531 parameter instead of 600. I corrected the pannel and it now works Ok.
bobbee |
|
| Back to top |
|
|
| tleichen |
| Posted: Wed Jul 05, 2006 3:49 pm Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
Okay, you can do it that way. But like I said, it is really poor practice that you force applications to change things just because you upgrade to a new release. 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Wed Jul 05, 2006 9:40 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
@tleichen - what do you do to run multiple versions of mq at the same time on the same machine?
i just dont like the "poor practice". your mileage may vary, but i prefer to have a version in the filename, because i am in the need to run multiple versions at the same time.
i aggree with you that there should not be the need to change the application, this can be archived by using various technics, but "poor practice"? no!
_________________
Regards, Butcher |
|
| Back to top |
|
|
| tleichen |
| Posted: Thu Jul 06, 2006 6:02 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
I was not really considering running multiple versions of MQ on the same machine, particularly on z/OS. I just never really have had the need. I can see how this might be a temporary need in a test environment and you might want to adjust procs, etc. in such a situation. But I don't feel that production systems should need to be touched just to go to the next release. That's just the approach we've always taken. Just my two cents on it.
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
|
|
