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
Categories USS
Created by Guest
Created on Feb 1, 2022

bpxwmigf working with ZFSs (VSAM) as name ends with .D (not .DATA)

Nós temos milhares de ZFSs para serem migrados/redefinidos porém este utilitário possui uma limitação no tratamento dos nomes dos ZFSs.
Ele obrigatoriamente espera que os nomes terminem com '.DATA' porém nossos ZFSs possuem nomes próximos de 44 caracteres.

Veja que na própria alocação via 'IDCAMS DEFINE CLUSTER' o componente DATA do VASM recebe automaticamente '.D' no final do nome.

Em resumo: o componente 'DATA' do VSAM (ZFS) pode ter o sufixo '.D' porém o utilitário bpxwmigf não está compatível:

BPXWMG022I <fsname> data name, <dataname>, is not standard.
Explanation: The name of the specified VSAM file system must have a data portion name that ends in ".DATA".
System action: The command ends.
User response: Ensure that the VSAM file system has a data portion name that ends in .DATA and then reissue thebpxwmigf command with the updated name.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 2, 2022

    Don't stop there with only bpxwmigf if other USS utilities use the same assumptions about there vsam clusters. Using .DATA is a good naming convention, but if that is not enforced by z/OS, then USS should not assume that it is.

1 MERGED

BPXWMIGF utility tolerate non standard name

Merged
HI we need to do a "hot" swap of a ZFS that has a "non-standard name in the data part"Clusters: omvs.name.z Data: omvs.name.z.D In this specific case we can also use a standard name. Even if we have filesystem with the data.d part because we reach...
7 months ago in z/OS / USS 1 Future consideration