Skip to content

Error scenarios that are regressed by PR-442 #470

@davenice

Description

@davenice

Describe the bug

PR #442 begins to improve the error handling in the CICS extension, providing common code for processing errors and providing more user-readable results.

Enabling a bundle with errors works well, however a couple of scenarios work less well (and I think would be regressions).

Disabling DFHRPL - a library that can't be disabled.
Image
No error message is given and nothing useful is in the logs, even with FINEST trace:

2025-10-22 09:09:11.863 [debug] PUT - Resource [CICSLibrary], CICSPLEX [CICSEX61], REGIONNAME [IYCWENW2], CRITERIA [NAME='DFHRPL']
2025-10-22 09:09:11.880 [error] Something went wrong while disabling library DFHRPL

""
2025-10-22 09:09:11.887 [debug] GET - Resource [CICSLibrary], REGIONNAME [IYCWENW2], CICSPLEX [CICSEX61], CRITERIA [(NAME=*)], SUMMONLY [true], NODISCARD [true], OVERRIDEWARNINGCOUNT [true]
2025-10-22 09:09:11.899 [debug] GET - Resource [CICSResultCache], CACHETOKEN [E1ACB1DA426A8488], STARTINDEX [1], COUNT [250], NODISCARD [true]
2025-10-22 09:09:11.914 [debug] GET - Resource [CICSResultCache], CACHETOKEN [E1ACB1DA426A8488], SUMMONLY [true]

Disable + kill on a JVM server gives a different but also difficult to decode error message:

Image

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingpriority-mediumNot functioning - next quarter if capacity permitsseverity-mediumBug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex

Type

No type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions