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 following diagnostic items and contact the IBM support center.

Diagnostics

A description of the actions that led to the error or, if applicable, either a listing of the application program or the input string to a utility program that was being run at the time of the error.
The console output for the period leading up to the error.
The queue manager job log.
The system dump resulting from the error.
A printout of SYS1.LOGREC.
Appropriate WebSphere MQ, z/OS, Db2, CICS, and IMS service levels.

00F30003, 00F30004, 00F30005: 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 Diagnostics and contact the IBM support center.

00F30006: An internal error has occurred.
System action: The request is not processed.
System programmer response: Collect the items listed in Diagnostics and contact the IBM support center.

00F30007, 00F30008: 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 Diagnostics and contact the IBM support center.

00F30014: 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 Diagnostics and contact the IBM support center.

00F30027, 00F30030,00F30032, 00F30033, 00F30038: 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 Diagnostics and contact the IBM support center.

00F30042: 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 Diagnostics and contact the IBM support center.

00F30048: 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 Diagnostics and contact the IBM support center.

00F30052

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 might 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 might be additional CSQ3009E messages on the console log associated with the termination of RRS.

00F30053: 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 Diagnostics and contact the IBM support center.

00F30067: 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 Diagnostics and contact the IBM support center.

00F30070

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. We might find the items listed in Diagnostics useful in resolving the problem.

00F30071: 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 Diagnostics and contact the IBM support center.

00F30075: 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 Diagnostics and contact the IBM support center.

00F30078: 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 Diagnostics and contact the IBM support center.

00F30080: 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 Diagnostics and contact the IBM support center.

00F30091: The application program issued an RRSAF IDENTIFY function request, but RRS is not available.
System action: The IDENTIFY request is not processed.

00F30093: 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.

00F30095

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 Diagnostics and contact the IBM support center.

00F30096

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 Diagnostics and contact the IBM support center.

00F30101

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.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30102

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.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30103

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.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30104

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.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30105

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.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30106

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.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30107: 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, 00F30214: 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 Diagnostics and contact the IBM support center.

00F30216

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.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30217: 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 Diagnostics and contact the IBM support center.

00F30218: 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 Diagnostics and contact the IBM support center.

00F30219

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, it might be necessary to perform an IPL of our z/OS system.

Collect the items listed in Diagnostics and contact the IBM support center.

00F3021A

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 Diagnostics and contact the IBM support center.

00F3021C

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, it might be necessary to perform an IPL of our z/OS system.

Examine the LOGREC entries, and the console log for indications of a z/OS error, and try increasing the storage.

If we are unable to resolve the problem, collect the items listed in Diagnostics and contact the IBM support center.

00F3021D

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.

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 taking a system dump. The initialization stops, but termination proceeds.

System programmer response

Retry the command after the queue manager has terminated. If the problem persists, it might be necessary to perform an IPL of our z/OS system.

Examine the LOGREC entries, and the console log for indications of a z/OS error, and try increasing the storage.

If we are unable to resolve the problem, collect the items listed in Diagnostics and contact the IBM support center.

00F3021E

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.

We might find the items listed in Diagnostics useful in resolving the problem.

00F3021F, 00F30220: 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 Diagnostics and contact the IBM support center.

00F30230: 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 Diagnostics and contact the IBM support center.

00F30310: 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 Diagnostics and contact the IBM support center.

00F30311

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.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30312

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.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30313

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 we are running with the recommended region size, and if not, reset the system and retry. If we are unable to resolve the problem, collect the items listed in Diagnostics and contact the IBM support center.

00F30400, 00F30401, 00F30402: An internal error has occurred.
System action: The program which made the request might produce diagnostics to report the error.
System programmer response: Collect the diagnostics produced by the application program reporting the error, if any, and contact the IBM support center.

00F30406

The queue manager has gone to EOM (end-of-memory). This is probably because the z/OS command FORCE has been issued.

System action

The queue manager is terminated, and a dump is taken.

System programmer response

The queue manager can be restarted after termination completes.

Determine why the z/OS command FORCE was issued.

00F30409, 00F3040A

An internal error has occurred.

System action

The queue manager is terminated with an SVC dump.

System programmer response

The queue manager can be started again after it terminates.

Collect the items listed in Diagnostics and contact the IBM support center.

00F3040B

See message CSQ3001E.

System action

See message CSQ3001E.

System programmer response

See message CSQ3001E.

We might find the items listed in Diagnostics useful in resolving the problem.

00F3040C, 00F3040D

An internal error has occurred.

System action

The queue manager is terminated with an SVC dump.

System programmer response

The queue manager can be started again after it terminates.

Collect the items listed in Diagnostics and contact the IBM support center.

00F3040E

An internal error has occurred.

System action

The queue manager is terminated.

System programmer response

The queue manager should be restarted.

Collect the items listed in Diagnostics and contact the IBM support center.

00F3040F, 00F30410

An internal error has occurred.

System action

The queue manager is terminated.

System programmer response

The queue manager can be started again after it terminates.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30411, 00F30412, 00F30413

An internal error has occurred.

System action

The queue manager is terminated.

System programmer response

The queue manager can be started again after it terminates.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30414

An internal error has occurred.

System action

The queue manager is terminated.

System programmer response

The queue manager can be started again after it terminates. If the problem persists, request a stand-alone dump, and perform an IPL of our z/OS system.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30415

An ESTAE could not be established during the processing of an EOM SSI broadcast. This is probably a z/OS problem, because these modules are executing in the z/OS master scheduler address space.

System action

The queue manager is terminated.

System programmer response

The queue manager can be started again after it terminates. If the problem persists, it might be necessary to perform an IPL of our z/OS system.

This can occur if the z/OS master scheduler address space has insufficient free storage. If such is the case, MQ is unable to write a SYS1.LOGREC record or request a dump. The z/OS master scheduler should have produced these diagnostic aids. Examine the dump to determine whether the problem is in z/OS or MQ. Other unrelated errors in the z/OS Master Scheduler address space would indicate a z/OS problem.

If the problem appears to be an MQ problem, collect the items listed in Diagnostics and contact the IBM support center.

00F30416

An ESTAE could not be established during the processing of an EOM for an allied address space.

System action

The queue manager is terminated.

System programmer response

The queue manager can be started again after it terminates. If the problem persists, it might be necessary to perform an IPL of our z/OS system.

If the problem appears to be an MQ problem, collect the items listed in Diagnostics and contact the IBM support center.

00F30417, 00F30418

An internal error has occurred.

System action

The queue manager is terminated.

System programmer response

The queue manager can be started again after it terminates.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30419

An internal error has occurred.

System action

The queue manager is terminated with an SVC dump.

System programmer response

The queue manager can be started again after it terminates.

Collect the items listed in Diagnostics and contact the IBM support center.

00F3041A

An ESTAE could not be established by the deferred end-of-task (EOT) processor. This error could occur only during queue manager startup. Probably, an ESTAE could not be established because of a shortage of LSQA space.

System action

The queue manager is terminated.

System programmer response

Restart the queue manager.

If the problem persists, increase the size of the queue manager address space private area.

We might find the items listed in Diagnostics useful in resolving the problem.

00F3041B, 00F30420

An internal error has occurred.

System action

The queue manager is terminated. A SYS1.LOGREC entry and associated SVC dump were requested.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30429

An internal error has occurred.

System action

The queue manager is terminated with an SVC dump.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30450

An ESTAE could not be established during the processing of an identify SSI call. This can occur if the current address space has insufficient storage.

System action

The allied address space is ended abnormally (without a dump). A dump should be produced by the allied task.

System programmer response

The user can retry the identify request. If a dump is available, review the storage manager's control blocks to determine if all of the private area has been allocated. If necessary, increase the private area size of the allied address space.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30451

An ESTAE could not be established during the processing of an identify SSI call. This can occur if the current address space has insufficient storage.

System action

The allied task is ended abnormally (without a dump). A dump should be produced by the allied task.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

00F30452

An ESTAE could not be established during the processing of an identify SSI call. This can occur if the current address space has insufficient storage.

System action

The allied task is ended abnormally (without a dump). A dump should be produced by the allied task.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

00F30453

ESTAEs could not be established during the processing of a n SSI call other than FEOT, EOM, HELP, COMMAND, and IDENTIFY. This can occur if the current address space has insufficient storage.

System action

The allied task is ended abnormally (without a dump). A dump should be produced by the allied task.

System programmer response

The user can retry the request. If a dump is available, review the storage manager's control blocks to determine if all of the private area has been allocated. If necessary, increase the private area size of the allied address space.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30454: An internal error has occurred.
System action: The allied task is ended abnormally.
System programmer response: Collect the items listed in Diagnostics and contact the IBM support center.

00F30455

An ESTAE could not be established during the processing of an identify termination request. This can occur if the current address space has insufficient storage.

System action

The allied task is ended abnormally (without a dump). A dump should be produced by the allied task.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

00F30456: An internal error has occurred.
System action: The calling task is ended abnormally.
System programmer response: Collect the items listed in Diagnostics and contact the IBM support center.

00F30457

An internal error has occurred.

System action

The caller is ended abnormally. The error might, in many cases, eventually terminate the queue manager.

System programmer response

Restart the queue manager if necessary.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30459

An internal error has occurred.

System action

The queue manager is terminated with a reason code of X'00F30420'.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30461

The queue manager was unable to successfully restart with RRS because of an internal error in either MQ or RRS.

System action

The queue manager is not connected to RRS and all services dependent on that connection are unavailable. This means that applications might not connect to the queue manager using RRSAF and that WLM-established address spaces might not be used for MQ stored procedures until the queue manager successfully restarts with RRS.

System programmer response

Stop and then start RRS. Stop and then start the queue manager. If the problem persists, perform an RRS cold start.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30501, 00F30502: An internal error has occurred.
System action: The requester is ended abnormally, and the request is not processed.
System programmer response: Collect the items listed in Diagnostics and contact the IBM support center.

00F30503: CSQ6SYSP is missing from the system parameter load module.
System action: Queue manager start-up is terminated.
System programmer response: Re-create the system parameter load module (if a customized version is being used) and restart the queue manager. For information about the system parameter modules, see Tailor the system parameter module.

00F30573, 00F30574: An internal error has occurred.
System action: The requester is ended abnormally, and 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 Diagnostics and contact the IBM support center.

00F30580: An internal error has occurred.
System action: The requester is ended abnormally.
System programmer response: Collect the items listed in Diagnostics and contact the IBM support center.

00F30581

An internal error has occurred.

System action

The queue manager ends abnormally. The startup/shutdown ESTAE creates a SYS1.LOGREC entry and takes an SVC dump.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30597, 00F30598: An internal error has occurred.
System action: The allied task is ended abnormally, and the request is not processed.
System programmer response: Collect the items listed in Diagnostics and contact the IBM support center.

00F30599

An internal error has occurred.

System action

The connection name associated with the error is probably unable to continue communication with MQ until the queue manager is terminated and restarted.

System programmer response

If necessary, stop and restart the queue manager.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30601

Asynchronous events occurred which caused the premature termination of the thread. The thread could not be recovered.

There might be other errors or messages concerning this allied user indicating what the asynchronous events were.

System action

The allied user is ended abnormally with completion code X'5C6' and this reason code.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

00F30610

An ESTAE could not be established during the processing of an 'end stop-work force' notification. This can occur if there is insufficient storage. This might lead to abnormal termination of the queue manager.

System action

The caller is ended abnormally. An SVC dump and related SYS1.LOGREC entry are requested.

System programmer response

If necessary, restart the queue manager.

If necessary, increase the private area size of the address space.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30801

An internal error has occurred.

System action

The queue manager is terminated. An SVC dump is requested.

System programmer response

Restart the queue manager.

Collect the items listed in Diagnostics and contact the IBM support center.

00F30802: An internal error has occurred.
System action: The task is not ended abnormally.
System programmer response: Collect the items listed in Diagnostics and contact the IBM support center.

00F30803

An ESTAE could not be established during the processing of an application program support call. This can occur if the current address space has insufficient storage.

System action

The allied task is ended abnormally. The allied task might have requested an SVC dump.

System programmer response

The user can retry the request. If necessary, increase the private area size of the application address space.

We might find the items listed in Diagnostics useful in resolving the problem.

00F30805: An internal error has occurred.
System action: The request might have been processed or rejected.
System programmer response: Collect the items listed in Diagnostics and contact the IBM support center.

00F30901: MQ has lost its cross-memory authority to an allied address space because the ally has released its authorization index.
System action: The allied address space is terminated.
System programmer response: We might find the items listed in Diagnostics useful in resolving the problem.

00F30902: MQ has detected a recursive error condition while processing End-of-Task for a task in an allied address space.
System action: The allied address space is terminated.
System programmer response: We might find the items listed in Diagnostics useful in resolving the problem.

00F30903: An error has occurred while processing End-of-Task for the queue manager address space.
System action: The address space is forced to 'end-of-memory' with this reason code.
System programmer response: We might find the items listed in Diagnostics useful in resolving the problem.

00F30904

End-of-Task occurred for the queue manager address space, and MQ could not establish an ESTAE to protect its processing. Insufficient storage might be the reason the ESTAE could not be established.

System action

The address space is forced to 'end-of-memory' with this reason code.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

Attempt to determine if one or more MQ address spaces is storage-constrained. Examination of the console output for the time period preceding this condition might reveal other messages or indications that the terminating address space was storage-constrained.

00F30905

End-of-Task occurred for the job step task in an allied address space. MQ would normally attempt to terminate the address space's connection to the queue manager but was unable to protect its processing by establishing an ESTAE. Insufficient storage might be the reason the ESTAE could not be established.

System action

The address space is forced to 'end-of-memory' with this reason code.

System programmer response

We might find the items listed in Diagnostics useful in resolving the problem.

Attempt to determine if one or more allied address spaces is storage-constrained. Examination of the console output for the time period preceding this condition might reveal other messages or indications that the terminating allied address space was storage-constrained.

00F33100: The MQ thread is read-only.
System action: A prepare issued by the application program was processed through Phase-1. MQ discovered there were no resources modified and no need for COMMIT or BACKOUT to be subsequently issued.
System programmer response: This might create a path length saving by not issuing the subsequent commit or backout which normally follows prepare. No further action is required to complete the unit of recovery; the unit of recovery is complete.

Parent topic: IBM MQ for z/OS codes