IBM Z Hardware and Operating Systems Ideas Portal
Hide about this 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.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM Z and LinuxONE Systems Hardware
Categories HMC/Support Element (SE)
Created by Guest
Created on Sep 3, 2024

RELATED IDEAS

Stand-alone IOCP should honour the POCID-ID field of the dynamic token even if IOCDS source has been edited.

In IOCDS source generated by z/OS HCD the 'processor ID' is included as the first field in the 'TOK' parameter of the ID statement. If an IOCDS is generated by HCD calling IOCP directly or by stand-alone IOCP using un-modified IOCDS source imported to the SE from an FTP server or a USB stick the TOK parameter is accepted and the generated dynamic token can be referenced by the z/OS opertaing system to determine the 'HWNAME'. However apparentyl if the IOCDS source is edited in any way on the HMC the source is marked 'modified' and stand-alone IOCP replaces the TOK value with an internally-generated value. Message ICP130I is produced. This means that the 'HWNAME' seen by z/OS is unpredictable possibly leading to IPL problems if the z/OS configuration is dependant on a specific HWNAME - for instance to set some system symbols based on HWNAME value. For instance if the hardware has been upgraded and the IOCDS created for the new hardware is found to require correction there is apparently no way to specify the required processor ID in the token if z/OS cannot be started.

Idea priority Low
  • Guest
    Reply
    |     Oct 14, 2024
    The work-around is to edit the IOCP source file elsewhere and reimport it onto the SE.  As the user discovered, IOCP invalidates the supplied token whenever a user modifies the source file because we cannot assume that the I/O configuration from the operating system that provided the IOCP source file still matches the I/O configuration in the IOCP source file.  Anything could have been changed.  The token is designed to identify an I/O configuration.  So when the software and hardware tokens match, the hardware and software I/O configurations should match.  IOCP cannot enforce anything prior to what we are given (i.e., the work-around) but once the IOCP source file is on the SE it cannot be modified and maintain the original token.
  • Guest
    Reply
    |     Sep 3, 2024

    (1). There is a typo in the title - should read 'PROC-ID'.

    (2) The scenario which gave rise to this idea was a Disaster Recovery test on a new machine in which the SE was accessed remotely via the HMC web server. It was not possible to import the IOCDS source for the new machine from a USB stick and an FTP server was not available. Therefore the IOCDS source generated by z/OS HCD was 'pasted' into the IOCDS editor window for a new empty IOCDS source. The standalone IOCDS build replaced the 'TOK' parameter and add commented "*ICP ICP130I **WARNING** DYNAMIC TOKEN ALTERED " - the new token is not shown. z/OS did not IPL in the way expected because the 'HWNAME' tested by z/OS had been changed. This was difficult to diagnose. Inclding the new token value in the ICP130I would have given a clue to dignsoe the problem Even so there was then no way to correct the token or alter the z/OS configuration parameters without a running z/OS system.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.