|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| crtmqm on Windows 2016 fails for users on code page 65001 | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | gbaddeley | 
			  
				|  Posted: Tue May 19, 2020 3:47 pm    Post subject: crtmqm on Windows 2016 fails for users on code page 65001 |   |  |  
		  |  Jedi Knight
 
 
 Joined: 25 Mar 2003Posts: 2538
 Location: Melbourne, Australia
 
 | 
			  
				| Hi MQ friends, 
 Has anyone tried creating a v9.0.0.6 qmgr on a Windows server from a user that is code page 65001 (Microsoft UTF-
  ?  The user is a local Administrator. 
 It seems that crtmqm.exe does not like it:
 crtmqm MQ01
 IBM MQ queue manager created.
 Directory 'C:\\MQdata\\qmgrs\\MQ01' created.
 The queue manager is associated with installation 'Installation1'.
 AMQ8101: IBM MQ error (893) has occurred
 
 FDC files contain:
 --{ xcsQueryCCSIDType
 ---{ xxxFindNode
 ---} xxxFindNode rc=Unknown(FFFF)
 --} xcsQueryCCSIDType rc=xecX_E_INVALID_CCSID
 
 -{ kpiCreateQM
 --{ xcsGetQMCCSID
 ---{ xxxFindNode
 ---} xxxFindNode rc=Unknown(FFFF)
 ---{ xcsFFST
 
 ----} xcsGetConsoleOutputCP rc=Unknown(FDE9)
 ----{ xcsConvertString
 -----{ xcsQueryCCSIDType
 ------{ xxxFindNode
 ------} xxxFindNode rc=Unknown(4E4)
 
 message information
 0000006939AFDB50   43617420  43435349  44203132  35322C20    Cat CCSID 1252,
 0000006939AFDB60   75736572  20434353  49442036  35303031    user CCSID 65001
 0000006939AFDB70   2C206D65  73736167  65204944  20273230    , message ID '20
 0000006939AFDB80   30303831  30312758                        008101'X
 
 
 The user's code page can be displayed using the 'chcp' command.
 
 It can also be changed, eg. chcp 850
 but crtmqm still fails, with a different error
 AMQ6109: An internal IBM MQ error has occurred.
 Looks like the qmgr was created, and it tried to start up, but 3 of the qmgr processes failed with various FDC ProbeIds.
 
 Tried it from a user that is code page 850 (Latin 1), and crtmqm works OK.
 
 Any thoughts?  Time for an IBM Service Request?
 _________________
 Glenn
 |  |  
		  | Back to top |  |  
		  |  |  
		  | fjb_saper | 
			  
				|  Posted: Tue May 19, 2020 7:00 pm    Post subject: |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| This is what I got when trying to use cp 65001 (my default is 437) MQ Version is 9.1.0.4
 
 
   
	| Code: |  
	| d:\>chcp 65001 Active code page: 65001
 
 d:\>crtmqm qm65001
 Unknown attribute in ini file.
 Unknown attribute in ini file.
 Unknown attribute in ini file.
 The details supplied for service 'ErrorsToFile' conflict with the details for
 service 'ErrorsToFile'.
 AMQ7059E: An error occurred when reading the configuration data.
 |  
 However creating the qmgr under cp 437, starting it, switching the ccsid to 1208  (alter qmgr) and ending went fine.
 Then starting it from cp 65001 gave me no problems...
 Enjoy
  _________________
 MQ & Broker admin
 |  |  
		  | Back to top |  |  
		  |  |  
		  | gbaddeley | 
			  
				|  Posted: Wed May 20, 2020 4:06 pm    Post subject: |   |  |  
		  |  Jedi Knight
 
 
 Joined: 25 Mar 2003Posts: 2538
 Location: Melbourne, Australia
 
 | 
			  
				| Actually I found that other MQ programs (dspmq, dspmqver) also generated the above FDCs when run from a user that is set to code page 65001. It appears to be an issue with the MQ program converting a message to display for the users "Console Output Code Page". MQ doesn't support 65001. 
 However, the output from dspmq & dspmqver actually appeared.
 
 I tried changing to code page 850, and the FDCs were no longer generated.
   
 Regarding the issue with crtmqm failing with
 AMQ6109: An internal IBM MQ error has occurred.
 The user is an AD domain user that a member of AD domain groups that resolve through to being in the local mqm group. Apparently this is not good enough for high privilege MQ commands like crtmqm, as directly adding the domain user to the local mqm group eliminated the error, and the qmgr was created OK.  The qmgr error logs show qmgr processes running ok under the domain user, for when it creates the default objects etc.
  _________________
 Glenn
 |  |  
		  | Back to top |  |  
		  |  |  
		  |  |  |  
  
	|    |  | Page 1 of 1 |  
 
 
  
  	| 
		
		  | 
 
 | You cannot post new topics in this forum You cannot reply to topics in this forum
 You cannot edit your posts in this forum
 You cannot delete your posts in this forum
 You cannot vote in polls in this forum
 
 |  |  |  |