What it means
2195 is a catch-all. The call failed for a reason MQ did not expect. Start by checking how the program builds its parameters; if that is fine, collect diagnostics for the MQ administrator.
Typical causes
- Wrong number of parameters, or bad pointers or storage keys in the call.
- On z/OS, MQCONN names a subsystem that is not an MQ queue manager, such as a Db2 subsystem.
- An internal MQ error, recorded in FDC or FFST files or in LOGREC.
How to fix it
- Check the call's parameter list against the MQI definition.
- On z/OS, check the job log, LOGREC and console messages, and check the subsystem name on connect.
- On distributed, look for FDC files and the queue manager error log; on IBM i check the FFST record.
- If it repeats, collect a dump (on z/OS add a CSQSNAP DD) and open a case with IBM.
Example
Illustrative only; names and values are invented.
MQCONN failed CompCode=2 Reason=2195 QMgrName=DB01