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 Future consideration
Workspace z/OS
Created by Guest
Created on Aug 2, 2016

Better recovery from VTS and z/OS out of sync volume mount status

We have had numerous instances where z/OS and the VTS get 'out of sync' in regards to the mount status on a single VTS logical drive. We have had several instances of this situation with the most recent case documented in PMR 34469,122,000. In this case a mount pending status was documented within the VTS with the volser of the previously mounte LVOL but z/OS did not record any volume being mounted that drive. After that job was gone and out of the system another job attempted to mount a tape on the same drive. At that time the job failed with these error messages:
IEF116I JY1794## SORTD - MOUNT OF VOLUME 4XB191 ON DEVICE E507 FAILED
IEE763I NAME= CBRLLACS CODE= 14016A
CBR4000I LACS MOUNT permanent error for drive E507.
CBR4106I Invalid sequence of orders sent to library CVTS40C.

The business partner then attempted to rerun the job and got the same error again. It took a second level of support to bring that drive logically offline after which time the business partner could rerun the job and get a 'working' drive followed by successful completion.

We would like a more graceful reaction to this issue from the s/w side as we know that there will be times when these two components will get out of sync. An ideal solution would involve the identification of the drive and notification to the technical team but a bypassing of that drive for selection in future allocation attempts until the statuses are in sync.

Idea priority High
  • Guest
    Reply
    |
    Jun 1, 2017

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - DFSMS Tape Storage SW Support
    Operating system - IBM z/OS
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - DFSMS OAM
    Operating system - IBM z/OS
    Source - None

  • Guest
    Reply
    |
    Aug 16, 2016

    There are instances in the VTS (TS7700) where a volume can be left in the mounted state; however z/OS host software thinks that there is no longer a volume mounted on that device. IBM agrees that added recovery logic is needed to detect and handle this situation. Today there is already an attempt (by z/OS host software) to try and clear the volume from the device that does not always work, leaving the drive in a usable state for subsequent allocations.

  • Guest
    Reply
    |
    Aug 3, 2016

    Creating a new RFE based on Community RFE #92510 in product z/OS.