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 USS
Created by Guest
Created on Nov 14, 2023

Uncontrolled environment after accessing OMVS

After accessing OMVS under TSO we are getting an uncontrolled environment and is necessary to logoff/logon in order tho have again a controlled environment.

We received the following message if we try to access any TSO application that requires a controlled environment:

BPXP015I HFS PROGRAM /bin/fomtlinp IS NOT MARKED PROGRAM CONTROLLED.

The reason is that if we use in OMVS a program without the Program Control attribute the dirty bit is set. The OMVS login program (/bin/fomtlinp) is not marked as Program Control. If we change the program Control attribute for this program, the dirty bit is also set in the following executed program, because most of the /bin programs do not have this attribute.

Our idea is to have a method to identify in RACF in wich OMVS paths or ZFS can trust, equivalent to PROGRAM ** for z/OS libraries.

We suggest some possible solutions:

- Add OMVS paths or ZFS in PROGRAM **
- Add a parameter to MOUNT command to instruct OMVS and RACF that the file system is controlled
 

Idea priority Medium
  • Guest
    Reply
    |
    Feb 16, 2024
    Invoking OMVS with the NOSHAREAS option creates a new address space which is isolated from TSO and will not cause it to become dirty. Note, the WLM classification of the new address space will not be associated with TSO and cannot be changed.