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 Delivered
Workspace z/OS
Created by Guest
Created on Mar 1, 2022

zERT - unneccessary Migration trouble 2.3 to 2.4 to 2.5

We were on z/OS 2.3 and have zERT Table Version 1.3.0 in use.
After Migration to z/OS 2.4 the zERT-Plugin in z/OSMF tells wrong schema version.
So i tried to run Migration Script IZUZNADG, which creates the new statements for getting correct DDL.
But Script gives only this:
*** WARNING *** Template contains no commands for versions newer than 1.3.0
*** WARNING *** No DDL commands written to output data set
This Script should be enhanced for a second parameter like ZOSVER, giving the "old version" and creating INSERT/UPDATE-Statements for the current version.


And Performance: With this index the import of SMF-Records speeds up.
CREATE INDEX SYSIBM_EZB_ZNADB.SESSION_INSERT_IX
ON SYSIBM_EZB_ZNADB.SESSION_STATISTICS
(STATS_SESSOID ASC,
STATS_SMFXTME ASC,
STATS_SMFXDTE ASC,
STATS_OID ASC)

Idea priority Medium
  • Guest
    Reply
    |
    Oct 5, 2023
    This was delivered in z/OS 3.1 with "zERT Network Analyzer Enhanced Upgrade Support"
  • Guest
    Reply
    |
    Apr 5, 2022

    We did some further investigation:

    Empty the APPL-Table, do the one insert from IZUZNDDL, so
    INSERT INTO APPL
    (APPL_TYPE, CREATED_TIME, LAST_UPDATED_TIME,
    APPL_CURR_SCHEMA_VERSION, APPL_CURR_SCHEMA_RELEASE,
    APPL_CURR_QRTSPARTITIONSNUM, APPL_PREV_QRTSPARTITIONSNUM)
    VALUES (2, CURRENT TIMESTAMP, CURRENT TIMESTAMP, '1.3.0',
    'HSMA24E', 5, 0)
    ;

    And then the same table version for different program version runs nearly fine. Only a different number of columns is disturbing:

    Table TLSSPACE, Fields
    ,"TLS_CLNTHSSIGMETH" SMALLINT WITH DEFAULT 0
    ,"TLS_RAWPUBLICKEYAUTH" INT WITH DEFAULT 0
    ,"TLS_PRESHAREDKEYAUTH" INT WITH DEFAULT 0
    ,"DTYPE" VARCHAR(255)

    So: Why is the table schema the same version but has different column numbers for the tables?

    There is a logic error in the (human) version number assignment! What Columns are also new, but not mentioned by increasing APPL_CURR_SCHEMA_RELEASE?

    I think this is an Error (but they told me i should open an RFE for it!