MQ

Hi Folks,
trying to convert a QM from circular to linear logging on distributed using migmqlog. It's managing to rename the log file to .bak but then fails.

There is an FFDC created:
probeid XC721030
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 1 |
| Probe Description :- AMQ6119S: An internal IBM MQ error has occurred (WinNT |
| error 2 from CreateFile.) |
| FDCSequenceNumber :- 0 |
| Comment1 :- WinNT error 2 from CreateFile. |
| Comment2 :- The system cannot find the file specified.

It is quite clearly (cough!) a permissions error. However, I'm in the same group that the QM was created in and this group has full read/write access to the shared drive.  My colleague created a test QM using the same shared drive etc. And I can convert their QM quite happily. I created a file permissions diff between their QM and the QM that's failing and could see nothing of consequence - I diffed all the data and log directories and even the local programdata directories. 

the command response screen tells me nothing:
AMQ7701I: migmqlog command is starting.
AMQ7736I: MIGMQLOG read 3196 bytes of log data and wrote 8192 bytes of log data. 0 log extents were migrated and 0 log extents were deleted. Log alignment is 4096 bytes.
AMQ7716I: migmqlog command has finished unsuccessfully.


So, anyone got any clues as to what I can do next to debug this?

many thanks for your help folks !

John.  

Hi John,

You are talking about an HA set up. Maybe you need to remove the qmgr from HA to change this setup.
Remember to also make sure no instance of the qmgr is running while you attempt this change (resource is offline),

qmgr is shutdown and not running elsewhere (dspmq -x -m QMGR ).

You are not telling us whether you are doing this with a UNC path (WinNT) or a mapped drive...
If you are using a UNC path or a mounted drive I suggest you do not trust the user id that is running the command.
Run it as the MQ Service user id. Make sure that USERID has full access to the log files (don't trust group access).
If using a UNC path you might want to map the path to a drive letter before executing the command.
Make sure the access is checked for all the files in the "active" directory, but also for the qm.ini file (careful with 9.2 and the conf directory) and for log control file.
If using a mapped drive you might want to reference that for the duration of the operation (migmqlog) in the qm.ini file.

My guess is you have the permissions on the *.log files but not to qm.ini or vice versa...

Hope it helps