Middleware News

You have WebSphere MQ v5.3 CSD04 or MQ 6 or MQ 7.0 installed on AIX with 6 queue managers created. Two queue managers are sending queue managers and the remaining 4 are receiving queue managers. When the sender send data to the receiving queue manager, that queue manager reject the data and produce the following error and the FDC listed below. AMQ6119 with rc=27 meaning EFBIG "File too big" on both Sending and Receiving queue managers. Cause Probe AD020000 is caused by an attempt to increase the queue file size beyond the Operating System limit (ulimit). Resolving the problem Increase the /etc/security/limits to go beyond 1GB. Three things have to occur to over come the 1 GB limit: Enable large file support. Increase the ulimit values to match the MQ limit or to unlimited. Create the queue after you have enabled large file support. As stated from the System Administration Guide - "Enabling large queues WebSphere MQ Version 5.3 supports queues larg

Problem(Abstract) Your Queue manager fails to start due to an authorization problem, return code = 5 (ERROR_ACCESS_DENIED). Symptom AMQ7019: An error occurred while creating the directory structure for the new queue manager. Trace shows the failure occurs in zutCheckDirectory, with return code = 5 (ERROR_ACCESS_DENIED). Cause The domain User-ID under, which MQSeries services is running has not been authorized to access the shared disk. Resolving the problem Update the file permissions on the shared disk to authorize the MQ administrative User-ID to have "Full Control" to the shared disk. Verify the mqm group has "Full Control" to the shared disk. AMQ7019 when creating a queue manager (crtmqm)   Problem(Abstract) When trying to create a queue manager using "crtmqm", you receive the following error: AMQ7019: An error occurred while creating the directory structure for the new queue manager. The FDC shows Probe "ZT071000&qu