Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 Future consideration
Categories z/TPF
Created by Guest
Created on Mar 4, 2022

Update 3270 interrupt handling (CCP4) to close security loopholes

When using a 3270 subchannel that had previously been used with another application, and that session had not been logged-off (LOGO), the new session will still be logged-on to that application. When CCP4 (in CLOA) detects an unsolicited device end (DE), it should check the WGTA for that 3270 and force a LOGO (when it it not a permanently logged-in terminal). This way a new user is forced to always LOGI into a local application.

Also, when using Host-On-Demand (HOD), it does not attach to the OSA-C for all defined devices. When a device is reset with ZLSTP/ZLSTA, it is put in INTERVENTION REQUIRED state.

A check can be made in CLOG, asynchronous write interrupt routine, to check for a standalone ATTN. Then it can reset the status bits for the device and then load the ATTN BV to allow the user to hit ESC to clear the X SYSTEM and be able to access TPF without needing operator commands to clear the lock.

Idea priority Medium
  • Guest
    Reply
    |
    Mar 15, 2022

    IBM intends to implement this with user exits.