Resolving problems with MQSC commands
If we cannot get MQSC commands to run, use the information in this topic to see if any of these common problems apply to you. It is not always obvious what the problem is when you read the error that a command generates.
When we use the runmqsc command, remember the following:- Use the < operator to redirect input from a file. If you omit this operator, the queue manager interprets the file name as a queue manager name, and issues the following error message:
AMQ8118: IBM MQ queue manager does not exist.
- If you redirect output to a file, use the > redirection operator. By default, the file is put in the current working directory at the time runmqsc is invoked. Specify a fully-qualified file name to send your output to a specific file and directory.
- Check that we have created the queue manager that is going to run the commands, by using the following command to display all queue managers:
dspmq
- The queue manager must be running. If it is not, start it; (see Starting a queue manager ). You get an error message if you try to start a queue manager that is already running.
- Specify a queue manager name on the runmqsc command if we have not defined a default queue manager, or you get this error:
AMQ8146: IBM MQ queue manager not available.
- We cannot specify an MQSC command as a parameter of the runmqsc command. For example, this is not valid:
runmqsc DEFINE QLOCAL(FRED)
- We cannot enter MQSC commands before you issue the runmqsc command.
- We cannot run control commands from runmqsc. For example, we cannot issue the strmqm command to start a queue manager while you are running MQSC commands interactively. If we do this, you receive error messages similar to the following:
runmqsc . . Starting MQSC for queue manager jupiter.queue.manager. 1 : strmqm saturn.queue.manager AMQ8405: Syntax error detected at or near end of cmd segment below:-s AMQ8426: Valid MQSC commands are: ALTER CLEAR DEFINE DELETE DISPLAY END PING REFRESH RESET RESOLVE RESUME START STOP SUSPEND 2 : end