From 5e41c52a56d78cf18da61622af91498e9a648bba Mon Sep 17 00:00:00 2001 From: Tushar Biswas Date: Sat, 18 Apr 2026 21:28:50 +0530 Subject: [PATCH] Add CeaTso request failed troubleshooting tip Closes #2665 Signed-off-by:- tusharnbiswas07@gmail.com Added troubleshooting information for CeaTso request failure with HTTP 500 error, including symptoms and solutions. Signed-off-by: Tushar Biswas --- ...Unable-to-generate-unique-CeaTso-APPTAG.md | 37 +++++++++++++++++++ 1 file changed, 37 insertions(+) diff --git a/docs/troubleshoot/zOS_services/Unable-to-generate-unique-CeaTso-APPTAG.md b/docs/troubleshoot/zOS_services/Unable-to-generate-unique-CeaTso-APPTAG.md index 9c28f09d54..a642baa0eb 100644 --- a/docs/troubleshoot/zOS_services/Unable-to-generate-unique-CeaTso-APPTAG.md +++ b/docs/troubleshoot/zOS_services/Unable-to-generate-unique-CeaTso-APPTAG.md @@ -12,6 +12,43 @@ Check the z/OSMF settings of REST API of file. You must define `RESTAPI_FILE` in `RESTAPI_FILE ACCT(IZUACCT) REGION(32768) PROC(IZUFPROC)` The default `IZUFPROC` can be found in `SYS1.PPROCLIB`. And the proper authorization is needed to get `IZUFPROC` to work successfully. +## ISSUE: CeaTso request failed with HTTP 500 error + +**Symptom** + +When you use Zowe CLI or Zowe Explorer to access USS files or data sets, you receive the following error: + +``` +Rest API failure with HTTP(S) status 500 +rc: 12 +reason: 2 +category: 3 +message: CeaTso request failed +``` + +**Solution** + +This error is caused by a buildup of IPC message queues on z/OS. + +1. Run the following command to check IPC resource usage: + +``` + ipcs -x +``` + + If a long list of entries is returned, the queues need to be cleared. + +2. **Immediate fix:** Recycle the Zowe `ZWESLSTC` started task. + +3. **Permanent fix:** Add the following to your `zowe.yaml` configuration: + +```yaml + zowe: + environments: + ZWE_PRIVATE_CLEANUP_IPC_MQ: true +``` + + This enables automatic IPC message queue cleanup on Zowe startup. ### ISSUE: z/OSMF JVM cache corruption