Author |
Message
|
kwelch |
Posted: Wed Feb 20, 2002 1:25 pm Post subject: |
|
|
 Master
Joined: 16 May 2001 Posts: 255
|
Hi,
We just installed WMQI 2.1 in our sandbox environment. Today we attempted for the first time to create a messageset following some examples out of an exercise from the class we took.
The first step was to create a new messageset, which we did.
The second step was to add a Custom Wire Format Physical Layer to the new messageset. When we tried this we got the following:
BIP1813W: Message repository resource (Message Set, OrderApplication) not locked: Freezing Message Set operation not permitted.
The freezing Message Set operation is not permitted because the message repository resource (Message Set, OrderApplication) is not locked, or is locked by another user.
Check out Message Set, OrderApplication and retry operation.
The messageset was checked out, it was brand new!
Has anyone hit this with 2.1 and if so is there a work around or fix? Thanks!
Sincerely,
Karen
[ This Message was edited by: kwelch on 2002-02-20 14:12 ] |
|
Back to top |
|
 |
zpat |
Posted: Thu Feb 21, 2002 12:38 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
After creating the message set, check it in and out again before adding the physical format.
Have you applied CSDs to 2.1?
|
|
Back to top |
|
 |
kwelch |
Posted: Thu Feb 21, 2002 5:47 am Post subject: |
|
|
 Master
Joined: 16 May 2001 Posts: 255
|
Hi Zpat,
We tried checking it in and out. We even tried to unlock and unfreeze since based on the text of the message it seems to think that we are trying to freeze it and can't because someone has it locked. Nothing worked! I will check with the MQSI tech guy about the CSD's. Is there a way I can check myself?
Thanks for your suggestions.
Karen |
|
Back to top |
|
 |
Segs |
Posted: Tue May 28, 2002 2:14 am Post subject: |
|
|
Voyager
Joined: 04 Oct 2001 Posts: 78 Location: Zurich Financial Services
|
Did anyone ever get to the bottom of this, I getting exactly the same, but I use the Control Centre on the actual Config Mgr server it works. I can only think there must be a permission problem somewhere. Has anyone got any ideas?
Cheers
Segs |
|
Back to top |
|
 |
mapa |
Posted: Tue May 28, 2002 3:53 am Post subject: |
|
|
 Master
Joined: 09 Aug 2001 Posts: 257 Location: Malmö, Sweden
|
Don't know if any of this can help you...
From the "Working with messages" manual:
There are some restrictions you must be aware of:
v When you import a message set, it is initially in the frozen state. You can
unfreeze it if you want to make changes after import.
v When you freeze a message set, the freeze timestamp property of the message
set is set to the current date and time.
v If you unfreeze a message set, the message set must be checked out to you. The
freeze timestamp property of the message set is reset to blank.
v When you finalize a message set, the Finalized field in the properties of the
message set is set to True and the freeze timestamp property is set. Finalize
cannot be reversed. When a message set is finalized, it cannot be changed or
updated, although it can be deleted.
v You cannot freeze or finalize a message set if any of the elements it contains is
checked out.
Locked
The state of a message set while it is checked out (locked) by a Control Center
user. A message set must be locked to your user ID before you can change any of
its properties. A message set must also be locked to you before you can freeze it.
Frozen
This is the state of a message set that is not expected to change (for example, on
entry to a test phase). It is indicated by the existence of a Freeze date in the
message set properties. Neither the message set itself nor its contents can be
changed when it is in this state, nor can they be checked out. If you want to make
subsequent changes, you must unfreeze the message set by selecting Unfreeze.
You cannot freeze a message set if any component of the message set is checked
out, or if a component definition it contains is incomplete.
A message set must move to the frozen state from the locked state, and both state
changes must be requested by the same user.
Best regards Mapa |
|
Back to top |
|
 |
Segs |
Posted: Tue May 28, 2002 4:31 am Post subject: |
|
|
Voyager
Joined: 04 Oct 2001 Posts: 78 Location: Zurich Financial Services
|
Not really, but thanks anyway. It seems that when I logon to the Control Centre with the same userid as the one used to start the configmgr I'm able to add the physical format, but when I'm not I can't. I've checked all the security on the config mgr and everything appears in place, never mind I'll crack it soon. |
|
Back to top |
|
 |
kwelch |
Posted: Tue May 28, 2002 9:15 am Post subject: |
|
|
 Master
Joined: 16 May 2001 Posts: 255
|
Hi Segs,
We did eventually get around this but my memory is failing me. I know we made some adjustments to JVM settings and bumped a setting in the mqsilcc.bat file from -mx200M to -mx900M on the control center machines and the broker machines.
I hope one of these helps. I will keep looking and if I run across it will post it here.
In our case we were not importing a messagest but creating it brand new when we hit this problem. I am not sure about Segs.
Good luck!
Karen |
|
Back to top |
|
 |
Segs |
Posted: Tue May 28, 2002 10:04 am Post subject: |
|
|
Voyager
Joined: 04 Oct 2001 Posts: 78 Location: Zurich Financial Services
|
Thanks Karen, I'll try that in the morning. I was creating a new message when I got the problem.
What I don't understand is why the userid that started the control centre can add the format from the same control centre with the same settings.
Any ideas? |
|
Back to top |
|
 |
kwelch |
Posted: Tue May 28, 2002 12:38 pm Post subject: |
|
|
 Master
Joined: 16 May 2001 Posts: 255
|
Hi Segs,
No, I will check around some more tomorrow myself. Are you saying that the control center on the machine where the broker lives can do it but no other control centers can?
I will post if I find anything.
Karen |
|
Back to top |
|
 |
Segs |
Posted: Wed May 29, 2002 5:57 am Post subject: |
|
|
Voyager
Joined: 04 Oct 2001 Posts: 78 Location: Zurich Financial Services
|
Karen
The config manager has been started by mqsiadm. If you connect to the config manger from a control centre not on the same NT box you can only add the physical format if you are logged on the the control centre as mqsiadm.
Regards |
|
Back to top |
|
 |
kwelch |
Posted: Wed May 29, 2002 6:34 am Post subject: |
|
|
 Master
Joined: 16 May 2001 Posts: 255
|
Hi Segs,
I am sorry I am not being much help here. I was asking some of the support folks about this issue and they couldn't recall either.
One person thought it might have been an issue when we did an upgrade vs. a clean install. It certainly sounds like it's an autorization issue though huh? I wonder? In the past we have had problems when the MCA User ID on the channel has not been set correctly. You could check that but I am just guessing here. My problem is I usually see the problems but I am not the person who does the resolution of the problems, we have another level of MQsupport staff that does that.
Good luck
Karen |
|
Back to top |
|
 |
Segs |
Posted: Thu May 30, 2002 10:55 pm Post subject: |
|
|
Voyager
Joined: 04 Oct 2001 Posts: 78 Location: Zurich Financial Services
|
Karen
At last it's sorted, some little bunny had set the MCA user for the SYSTEM.BKR.CONFIG channel on the config manager queue manager.
Thanks for your help, I've now got to sort out all the other problems this has highlighted. It seems the install for a control centre only is noy quite 100% |
|
Back to top |
|
 |
garyweik |
Posted: Mon Jul 22, 2002 11:10 am Post subject: |
|
|
 Apprentice
Joined: 28 Jun 2002 Posts: 30 Location: Miamisburg, Ohio
|
What did you change the MCA User to be in order to get this to work? |
|
Back to top |
|
 |
Segs |
Posted: Mon Jul 22, 2002 10:46 pm Post subject: |
|
|
Voyager
Joined: 04 Oct 2001 Posts: 78 Location: Zurich Financial Services
|
It should be set to blank, however there are a number of other problems if you install the control centre only.
Hope this helps.
Segs... |
|
Back to top |
|
 |
|