Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace z/OS
Categories LE
Created by Guest
Created on Jul 13, 2021

LE should give an error for an attempt to start a new enclave in a single-enclave environment

An LE environment that is set up for a single enclave only will not support an attempt to start a
second enclave. Currently, if this is attempted in COBOL, the result is a S0C1 in CEEBPIRA.
An APAR is open that will change this to be a U4093-92 abend.

A U4093-92 from Language Environment just means “Anchor setup malfunctioned”.
It doesn't point to anything that would tell the developer what went wrong.

This RFE is for Language Environment to give a specific abend reason/return code to indicate
that the problem is due to an attempt to start a new enclave in a single-enclave environment.
(Or it could be an error for the specific situation given in the Use case below.)

Note that LE already does do some diagnostics for similar situations:

U4093-196: XPLINK application can't be started in a child enclave of a non-XPLINK environment
U4093-516: Request to create a nested (main-to-main) enclave in an AMODE 64 environment

Idea priority Low
  • Guest
    Reply
    |
    Jan 3, 2023
    This item is a valid requirement but unlikely to be given high enough priority to be placed into the product plan. If this requirement is high value, please re-open it, or open a new requirement.