Subsystem support codes (X'F3')
Many of the following reason codes are returned in register 15 at the time of an abnormal termination with completion code X'0Cx', and not as the reason code for a completion code of X'5C6'. This is indicated in the descriptions that follow.
If a subsystem support reason code occurs that is not listed here, an internal error has occurred. Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30003, 00F30004, 00F30005Explanation:An internal error has occurred.
System Action:The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30006Explanation:An internal error has occurred.
System Action:The request is not processed.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30007, 00F30008Explanation:An internal error has occurred.
System Action:The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30014Explanation:An internal error has occurred.
System Action:The requester's task is ended abnormally with completion code X'5C6'. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30027, 00F30030 ,00F30032, 00F30033, 00F30038Explanation:An internal error has occurred.
System Action:The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30042Explanation:An internal error has occurred.
System Action:A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30048Explanation:An internal error has occurred.
System Action:The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30052Explanation:The recovery coordinator for the caller has already terminated, so the connection from the caller to MQ has been terminated.
System Action:The request is not processed. The connection from the caller to MQ is terminated.
The caller may reconnect to MQ when the recovery coordinator has been restarted.
System Programmer Response:Identify and restart the recovery coordinator.
This abnormal termination is most commonly associated with a termination of RRS. There may be additional CSQ3009E messages on the console log associated with the termination of RRS.
00F30053Explanation:An internal error has occurred.
System Action:The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30067Explanation:An internal error has occurred.
System Action:The connection request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30070Explanation:Functional recovery for the connection processing could not be established. The executing module could not establish its ESTAE. This can occur if the current address space has insufficient storage. This might lead to an abnormal termination of the queue manager.
System Action:The connection request is not processed. The caller is ended abnormally with completion code X'5C6' and this reason code.
System Programmer Response:Restart the queue manager if necessary. A dump should be taken for problem analysis.
Examine the usage and free areas in the LSQA portion of the current address space private area. If necessary, have the size of the private areas expanded.
The caller should produce a SYS1.LOGREC entry and an SVC dump, so that we can examine the LSQA area. You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F30071Explanation:An internal error has occurred.
System Action:The connection request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30075Explanation:An internal error has occurred.
System Action:A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30078Explanation:An internal error has occurred.
System Action:The request is not processed. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30080Explanation:An internal error has occurred.
System Action:The application program is ended abnormally with completion code X'5C6' and this reason code. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30091Explanation:The application program issued an RRSAF IDENTIFY function request, but RRS is not available.
System Action:The IDENTIFY request is not processed.
User Response:Retry the IDENTIFY request after RRS has been started.
00F30093Explanation:The application program issued an RRSAF TERMINATE THREAD or TERMINATE IDENTIFY function request, but the application has issued an MQ API request since the last invocation of SRRCMIT or SRRBACK and therefore is not at a point of consistency.
System Action:The function request is not processed.
User Response:We can continue processing with a corrected request.
00F30095Explanation:An internal error was detected in either MQ or RRS.
System Action:The application is ended abnormally. The error is recorded in the SYS1.LOGREC data set and an SVC dump is requested.
This error might, in many cases, eventually cause the queue manager to terminate abnormally.
System Programmer Response:This is probably either an error in MQ or in RRS.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30096Explanation:An internal error was detected in either MQ or RRS Context Services.
System Action:The application is ended abnormally. The error is recorded in the SYS1.LOGREC data set and an SVC dump is requested.
This error might, in many cases, eventually cause the queue manager to terminate abnormally.
System Programmer Response:This is probably either an error in MQ or in RRS.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30101Explanation:The parameter contained in the IEFSSNxx member used to initialize MQ (and other subsystems) is in error. See message CSQ3101E for details.
System Action:See message CSQ3101E.
System Programmer Response:See message CSQ3101E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F30102Explanation:The parameter contained in the IEFSSNxx member used to initialize MQ (and other subsystems) is in error. The MQ command prefix (CPF) must not be blank. For details, see message CSQ3102E.
System Action:See message CSQ3102E.
System Programmer Response:See message CSQ3102E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F30103Explanation:The parameter contained in the IEFSSNxx member used to initialize MQ (and other subsystems) is in error or the named module is not resident in a library available during IPL. See message CSQ3103E for details.
System Action:See message CSQ3103E.
System Programmer Response:See message CSQ3103E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F30104Explanation:Module CSQ3UR00 was unable to obtain the affinity table index for the named subsystem. z/OS did not recognize the named subsystem. See message CSQ3109E for details.
System Action:See message CSQ3109E.
System Programmer Response:See message CSQ3109E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F30105Explanation:Module CSQ3UR00 was unable to load Early module CSQ3EPX. Either there was an I/O error, or the named module is not resident in a library available during IPL. See message CSQ3105E for details.
System Action:See message CSQ3105E.
System Programmer Response:See message CSQ3105E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F30106Explanation:The parameter contained in the IEFSSNxx member used to initialize MQ (and other subsystems) is in error. The scope of the MQ command prefix (CPF) is not valid. For details, see message CSQ3112E.
System Action:See message CSQ3112E.
System Programmer Response:See message CSQ3112E.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F30107Explanation:An error occurred during command prefix registration.
System Action:The MQ subsystem ends abnormally.
System Programmer Response:See the accompanying CSQ3xxx messages for information about the cause of the problem.
00F30210, 00F30211, 00F30212, 00F30213, 00F30214Explanation:An internal error has occurred.
System Action:The caller is ended abnormally. An SVC dump and associated SYS1.LOGREC entries are produced.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30216Explanation:An attempt to create a queue manager address space failed. This is probably because the user who issued the START QMGR command has insufficient authority.
System Action:The current START command processing is terminated. An SVC dump and associated SYS1.LOGREC entries are produced.
System Programmer Response:Check the authority of users and consoles to issue commands. Retry the command.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F30217Explanation:The console ID for the z/OS console that entered the current command is not found in the z/OS unit control module (UCM) structure. An internal z/OS command might have been incorrectly issued by an application program that provided invalid input parameters.
System Action:The caller is ended abnormally.
System Programmer Response:Retry the START QMGR command. If the command was unsuccessful, collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30218Explanation:An internal error has occurred.
System Action:The current task is ended abnormally. The calling task might have requested an SVC dump or created associated SYS1.LOGREC entries.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30219Explanation:An internal error has occurred.
System Action:The calling task is ended abnormally. The calling task might have requested an SVC dump or created associated SYS1.LOGREC entries.
System Programmer Response:Cancel the queue manager. (End-of-task processing might still work, and it does a more complete clean-up than end-of-memory processing does.) If this does not work, issue the z/OS command FORCE for the queue manager. If the problem is still unresolved, re-IPL z/OS.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F3021AExplanation:An internal error has occurred.
System Action:The calling task is ended abnormally. An SVC dump and associated SYS1.LOGREC entries are produced.
System Programmer Response:Stop the queue manager and reissue the START QMGR command.
Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F3021CExplanation:An ESTAE could not be established. This can occur if the z/OS system address space that is broadcasting the command has insufficient storage.
System Action:The caller is ended abnormally (without a dump). The current START command processing is terminated.
System Programmer Response:Retry the command. If the error persists, re-IPL z/OS.
Examine the LOGREC entries, and the console log for indications of a z/OS error, and try increasing the storage.
If you are unable to resolve the problem, collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F3021DExplanation:An ESTAE could not be established during either the initialization or termination of the queue manager.
This can occur during initialization if the z/OS system address space that is broadcasting the first command (assumed to be the START command) has insufficient storage. e
This can occur during termination if the current address space (usually the queue manager, or in the case of EOM broadcast, a z/OS system address space) has insufficient storage.
System Action:The caller is ended abnormally (without a dump). The initialization stops, but termination proceeds.
System Programmer Response:Retry the command after the queue manager has terminated. If the problem persists, a re-IPL of z/OS might be necessary.
Examine the LOGREC entries, and the console log for indications of a z/OS error, and try increasing the storage.
If you are unable to resolve the problem, collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F3021EExplanation:An ESTAE could not be established while in the process of routing control to the actual ESTAE routine. The caller (RTM) is ended abnormally. This causes the original error to percolate to a higher-level recovery routine and causes this reason code to be shown in an RTM recovery environment.
This can occur if the current address space (usually an allied address space) has insufficient storage.
System Action:The caller is ended abnormally and a dump is produced.
System Programmer Response:Examine the usage and free areas in the LSQA portion of the current address space private area. If necessary, have the size of the private area expanded.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F3021F, 00F30220Explanation:An internal error has occurred.
System Action:The caller is not ended abnormally. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30230Explanation:An internal error has occurred.
System Action:The connection between the allied address space and the queue manager terminated. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30310Explanation:An internal error has occurred.
System Action:The invoker is ended abnormally. A dump is taken, and an entry is written in SYS1.LOGREC.
System Programmer Response:Collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30311Explanation:An ESTAE could not be established during the processing of a resolve-indoubt request. This can occur if the current address space has insufficient storage. This will probably cause an abnormal termination of the queue manager.
System Action:The caller is ended abnormally.
System Programmer Response:Restart the queue manager if necessary.
Examine the usage and free areas in the local system queue area (LSQA) portion of the current address space private area. If necessary, have the size of the private area expanded.
The caller should produce a SYS1.LOGREC entry and an SVC dump, so that we can examine the LSQA area.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F30312Explanation:An ESTAE could not be established during the processing of a resolve-indoubt-UR request. This can occur if the current address space has insufficient storage.
System Action:The caller is ended abnormally.
System Programmer Response:Examine the usage and free areas in the local system queue area (LSQA) portion of the current address space private area. If necessary, have the size of the private area expanded.
The caller should produce a SYS1.LOGREC entry and an SVC dump.
You might find the items listed in Subsystem support problem determination useful in resolving the problem.
00F30313Explanation:A control block could not be allocated. This could occur when the storage pool has no more free space available.
System Action:The request is not processed. The application program is ended abnormally with completion code X'5C6' and this reason code.
System Programmer Response:A dump should be taken for problem analysis.
Check that you are running with the recommended region size, and if not, reset your system and retry. If you are unable to resolve the problem, collect the items listed in Subsystem support problem determination and contact your IBM support center.
00F30400, 00F30401, 00F30402Explanation:An internal error has occurred.
System Action:The program which made the request might produce diagnostics to report the error.