Skip to content

Add CeaTso request failed troubleshooting tip for V3 docs #4989

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
TusharB-07 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add CeaTso request failed troubleshooting tip for V3 docs #4989

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 37 additions & 0 deletions docs/troubleshoot/zOS_services/Unable-to-generate-unique-CeaTso-APPTAG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Comment on lines +15 to +19

Copilot AI Apr 18, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This new section uses a different heading level/style than the rest of the page ("## ISSUE" vs existing "### ISSUE"), and the bold labels are missing the trailing colons ("Symptom"/"Solution" vs "Symptom:"/"Solution:"). For consistency (and to avoid TOC/structure oddities), align the heading level and label punctuation with the other ISSUE sections in this file.

Copilot uses AI. Check for mistakes.

```
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
```
Comment on lines +33 to +37

Copilot AI Apr 18, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fenced code block for ipcs -x is not indented under list item 1, so many Markdown renderers will break the numbered list (the code block becomes outside the list, and numbering/indentation can reset). Indent the opening/closing ``` fence (and its contents) so it is clearly part of item 1.

Copilot uses AI. Check for mistakes.

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
```
Comment on lines +45 to +49

Copilot AI Apr 18, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The zowe.yaml snippet is also fenced at column 0 while it’s introduced as part of list item 3, which can break list rendering. Additionally, the YAML example includes extra leading indentation before the top-level zowe: key, which makes copy/paste into a YAML file more error-prone. Indent the fence under the list item and format the YAML with zowe: starting at column 0 (with consistent 2-space indentation beneath).

Suggested change
```yaml
zowe:
environments:
ZWE_PRIVATE_CLEANUP_IPC_MQ: true
```
```yaml
zowe:
environments:
ZWE_PRIVATE_CLEANUP_IPC_MQ: true

Copilot uses AI. Check for mistakes.

This enables automatic IPC message queue cleanup on Zowe startup.

### ISSUE: z/OSMF JVM cache corruption

Expand Down
Loading