DB2 manager codes (X'F5')

 

If a DB2 manager reason code occurs that is not listed here, an internal error has occurred. Collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50000
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Ensure that the QSGDATA system parameter is specified correctly and restart the queue manager.

If the problem persists, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50001
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Restart the queue manager.

If the problem persists, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50002
Explanation:

An internal error has occurred.

System Action:

The task ends abnormally. Queue manager processing continues but the queue manager may not terminate normally and may not register DB2 termination.

System Programmer Response:

Refer to DB2 for z/OS Messages and Codes for information about the completion and reason code in the accompanying message and collect the diagnostic data requested in the manual. In addition, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50003
Explanation:

An internal error has occurred.

System Action:

The task ends abnormally. Queue manager processing continues.

System Programmer Response:

Collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50004
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Ensure that the following modules are available through the linklist or the steplib concatenation: DSNRLI, DSNHLIR, DSNWLIR, ATRCMIT and ATRBACK. Restart the queue manager.

If the problem persists, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50006
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

All queue managers that are members of the same queue-sharing group must connect to the same DB2 data-sharing group. Check that all queue managers in the queue-sharing group have the same DB2 data-sharing group specified in the QSGDATA system parameter. Restart the queue manager.

Collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50007
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Ensure that the DB2 subsystem(s) specified on the QSGDATA system parameter are members of the DB2 data-sharing group that is also specified on the QSGDATA system parameter. Restart the queue manager.

If the problem persists, refer to DB2 for z/OS Messages and Codes for information about the completion and reason code in the accompanying message and collect the diagnostic data requested in the manual. In addition, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50008
Explanation:

An internal error has occurred.

System Action:

The task ends abnormally and processing continues.

System Programmer Response:

Collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50009
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Restart the queue manager.

Refer to DB2 for z/OS Messages and Codes for information about the completion and reason code in the accompanying message and collect the diagnostic data requested in the manual. In addition, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50010
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Restart the queue manager.

Refer to z/OS MVS Programming: Sysplex Services Reference for an explanation of the error and the diagnostic information, if any, that collect. In addition, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50013
Explanation:

No queue manager entry was found in the CSQ.ADMIN_B_QMGR table for this combination of queue manager and queue-sharing group, or the entry was incorrect.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Check the CSQ.ADMIN_B_QMGR table in the DB2 data-sharing group and ensure that an entry has been defined for the queue manager and it relates to the correct queue-sharing group.

If you are migrating from a previous release of MQ, check also that you have updated the DB2 tables to the format for the current release. See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about migration and compatibility between releases.

Restart the queue manager. If the problem persists, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50014
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Check that the DB2 related installation and customization tasks have all completed successfully. Restart the queue manager.

If the problem persists, refer to DB2 for z/OS Messages and Codes for information about the completion and reason code in the accompanying message and collect the diagnostic data requested in the manual. In addition, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50015
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Restart the queue manager.

If the problem persists, refer to DB2 for z/OS Messages and Codes for information about the completion and reason code in the accompanying message and collect the diagnostic data requested in the manual. In addition, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50016
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Restart the queue manager.

If the problem persists, refer to DB2 for z/OS Messages and Codes for information about the completion and reason code in the accompanying message and collect the diagnostic data requested in the manual. In addition, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50017
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

See z/OS MVS Programming: Sysplex Services Reference for information about the completion and reason code in the accompanying message.

Restart the queue manager. If the problem persists, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50018
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

See z/OS MVS Programming: Sysplex Services Reference for information about the completion and reason code in the accompanying message.

Restart the queue manager. If the problem persists, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50019
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

See z/OS MVS Programming: Sysplex Services Reference for information about the completion and reason code in the accompanying message.

Restart the queue manager. If the problem persists, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50021
Explanation:

An internal error has occurred.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

See z/OS MVS Programming: Sysplex Services Reference for information about the completion and reason code in the accompanying message.

Restart the queue manager. If the problem persists, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50024
Explanation:

An internal error has occurred.

System Action:

The task ends abnormally and a dump is taken.

System Programmer Response:

If the problem persists, collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50025
Explanation:

An internal error has occurred.

System Action:

The task ends abnormally and a dump is taken.

System Programmer Response:

Collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50026
Explanation:

An internal error has occurred.

System Action:

The task ends abnormally and a dump is taken.

System Programmer Response:

Collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50027
Explanation:

An internal error has occurred.

System Action:

The task ends abnormally and a dump is taken.

System Programmer Response:

Collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F50028
Explanation:

An internal error has occurred.

System Action:

The task ends abnormally and a dump is taken.

System Programmer Response:

This may be a temporary condition if DB2 or RRS has just failed. If the problem persists, collect the items listed in DB2 manager problem determination, together with output from DB2 command DISPLAY THREAD(*), and contact your IBM support center.

00F50029
Explanation:

The queue manager has detected a mismatch between its supported versions of MQ and those of other members of the queue-sharing group.

System Action:

The queue manager terminates, a record is written to SYS1.LOGREC and a dump is taken.

System Programmer Response:

Verify the started task JCL procedure for the queue manager (xxxxMSTR) is executing the correct version of MQ. Restart the queue manager. If the correct version is being executed, collect the items listed in DB2 manager problem determination, together with a printout of the CSQ.ADMIN_B_QMGR table from the DB2 data-sharing group to which the queue manager connected, and contact your IBM support center.

00F50901
Explanation:

An internal error has occurred.

System Action:

The job ends abnormally with a X'5C6' completion code and a dump is taken.

System Programmer Response:

Collect the items listed in DB2 manager problem determination and contact your IBM support center.

00F51030
Explanation:

An internal error has occurred.

System Action:

The task ends abnormally and a dump is taken.

System Programmer Response:

Restart RRS if it has terminated. If RRS has not terminated, collect the items listed in DB2 manager problem determination and contact your IBM support center.

 

DB2 manager problem determination

Collect the following diagnostic items:

  • A description of the action(s) that led to the error, or if applicable, a listing of the application program, or the input string to a utility program, being run at the time of the error

  • Console output for the period leading up to the error

  • Queue manager job log

  • System dump resulting from the error, if any

  • Printout of SYS1.LOGREC

  • The WebSphere MQ, z/OS, DB2, CICS, and IMS service levels