Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage 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
Created by Guest
Created on Jul 10, 2025

The logical volume is stuck mounting due to an interrupted operation (job abort, LPAR IPL, or other disruptive action taken on the host side for various reasons). In this case, ITAU would like to know WHICH volume was left mounted and requires operator intervention (either via host or MI) to unload it and prevent future job errors with CBR4196D-67 (Requested volume already in use). Regarding ITAU's request to be informed of which level is causing the CBR3750I G0032 message, since it is still mounted: This would be a new function request (nonexistent at current code levels). It is not a code defect.

Why are we seeing CBR3750I G0032_Informational_C_ TS7700_XX_ copies queued for more than 24 hours? The logical volume is stuck mounting due to an interrupted operation (job abort, LPAR IPL, or other disruptive action taken on the host side for various reasons). In the copy mechanism for volumes left MOUNTED due to unfinished operations, DEV explained that the copy-needed bit is set on the first write. When we perform the first write, the Grid is notified and sets the copy-needed bit. This is why, 24 hours later, G0032 will be reported (caused by the LVOL that was left mounted). The copy occurs at RUN (if in immediate mode) and after unmounting, if DEFERRED. If the host does not issue any of these messages, the copy will never be performed. The Grid doesn't know whether the mounted LVOL is in use or not, as there are cases where LVOLs remain mounted for consecutive days. This is EXACTLY the scenario seen at ITAU. All WAD. Request: In this case, ITAU would like to be informed of WHICH volume was left mounted and requires operator intervention (either via Host or IM) to unload it and avoid future task errors with CBR4196D-67 (Requested volume already in use). Regarding ITAU's request to be informed of which level is causing the CBR3750I G0032 message, since it is still mounted: This would be a new function request (nonexistent in current code levels). It is not a code defect.

Idea priority Low
  • Guest
    Aug 25, 2025

    Adding a customer request here:
    Two TPF lvols stuck in the copy queue since they are mounted. Delay reason (Exclusive Access).

     


    Unfortunately, these 2 volumes have been in the queue for 78 hours and 14 minutes. We trap on the message for when we have volumes in the copy queue for more than 24 hours. We do that because if something is in the copy queue over 24 hours, that means there is a problem somewhere in the grid that is preventing the copies from taking place. 

    I think a better solution would be to null or void the copy in the queue once a tape goes scratch and gets used again or if the tape gets mounted. So, is there anything that can be done to stop the timer of the 2 volumes in the copy queue or at least remove them from the queue? 

     

    With these 2 tapes being TPF, they could be mounted for up to a week or longer before they get written. That means we will continue to get these alerts until TPF uses or dismounts them.

  • Guest
    Aug 4, 2025

    Essas condições ocorre quando e realizado um system reset no mainframe e é gerado duas situações em que volumes ficam montados no VTS.

    Na leitura, quando uma nova montagem solicita o volume que já esta montado e sem gerenciamento do Z/OS, ocasiona a mensagem CBR4196D.

    Neste caso entramos na MI do VTS, em virtual, virtual tape drive, localizamos o volume, selecionamos e comandamos unmount.

    Na gravação, gerando fila de replicação e é sinalizado com a mensagem CBR3750 G0032 após 24horas, nesse caso conseguimos gerar uma lista de 'incoming copy queue' no VTS, onde identificamos o volume, conforme exemplo abaixo:

    X04476,Deferred,Queued,21:58:53,"Parallel copy is supported, but the volume was updated or had a scratch mount while the current copy was in progress",-,9.16,2025-07-03T13:32:32UTC,.

    Sendo necessário o unmount do volume.

    Favor verificar a possibilidade de gerar um alerta para esses volumes que ficam stand-alone.

  • Guest
    Jul 10, 2025

    The problem discussed involves messages CBR3750I - G0032O occurring in the TS7700 system. The G0032 message indicates that XX copies have been queued for over 24 hours. The issue arises when the system is stopped and then an IPL is performed without completing the tasks that are writing or reading the tapes. After the IPL, if the tape is requested by another job, the message CBR4196D will be issued.
    The client observed logical volumes left unmounted at clusters, causing CBR4196D messages. The problem occurs when the system is stopped abruptly, causing issues in the replica.

    Case Number: TS019676039