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 Delivered
Created by Guest
Created on Apr 22, 2012

Chainage "Libre" Pacbase non compatible avec RPP

Bonjour,

Les premiers tests de migration Pacbase vers RPP ont montr?s que les chainages "Libre" possibles dans Pacbase n'?taient pas repris dans RPP et provoquaient soit des erreurs soit une perte d'information lors de la migration.

Les chainages "Libre" sont de deux natures :

1) dans les appels de macro-structures, utilisation des pr?fixes E=, S=, D= pour ?tablir un chainage sur une entit? Rubrique, Segement ou Structure de Donn?es. Ces chainages n'imposent pas que l'entit? r?f?renc?e existe. Nous avons en particulier utilis? le pr?fixe E= pour ?tablir des relations sur des Rubriques non d?finies au Dictionnaire, mais pr?sentes sous forme "Cobol" dans des Macro-Structures. Ce chainage nous permet de retrouver les utilisations de ces Rubriques.
Sur ce type de chainage, si l'entit? cible n'existe pas, la migration supprime le pr?fixe E=, S=, D=. Ceci est une perte d'information.

2) dans des Relation Utilisateur de type "L". Ces relations permettent de d?finir un chainage sur une entit? qui n'est pas n?cessairement d?finie au Dictionnaire. Nous l'avons utilis?e sur des entit?s Rubriques (puisqu'il faut quand m?me d?finir un type d'entit? sur la Relation), mais non d?finies au Dictionnaire. Ce type de Relation nous permet de retrouver des Entit?s Utilisateur d?finies par ailleurs. Ce type de relation aurait aussi pu ?tre mis en oeuvre par exemple pour r?f?rencer un sous-programme d?finit dans un r?seau parall?le.
Ce type de relation provoque une erreur ? la migration.

Idea priority Medium
  • Guest
    Reply
    |
    Mar 6, 2017

    This feature was delivered in version 9.5.1.

  • Guest
    Reply
    |
    Mar 8, 2016

    The feature that is described in this request is a candidate for a future release.

  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Development Tooling
    Product - Programming Patterns

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Programming Patterns

  • Guest
    Reply
    |
    Jun 13, 2014

    This feature is fully taking into account in RPP 901