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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
HCD unattended export with replace leaves IODF in old disk, not the one specified in the panel.
Wait state obtained in IPL because IODF file was not in the intended
disk, the one in the LOADPARM.
IODF file was created by HCD export from other sysplex, with replace
option. So the current IODF was exported to the original disk
(pertaining to an old z/OS 1.11 set) where an old IODF with the very
same name existed, instead creating the new in the disk that was
specified in the export panel.
From our point of view, this does not make sense: the export process
should delete de old IODF from the old disk and create the new one in
the intended disk.
I attach export JCL output, where it can be seen that I specified
S12CD1 as the export target disk, and the new IODF file was created in
S12CB1, where the old IODF was residing.
I know that in the unattended export panel you can choose between two
options: specify the volser when "(If IODF does not exist at the target
node)" or "Replace target IODF" when the condition "(If IODF already
exists) " is met.
But I think that this is an opportunity to improve the process, and
make available a mixed third option: to send the file to an specific
disk, at the very same time the old IODF is deleted from the old disk.
Thanks a lot for your time to read this.
Best regards.
Julio Montalvo Moreno
Idea priority | Low |
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.
Hello Julio,
thanks for bringing this oddity in HCD to our attention.
We agree with you that HCD should not ignore a volser specification, if
(1) an IODF with the target name already exists and
(2) the REPLACE option has been specified
Instead of introducing a third option, we suggest this new behavior:
If an IODF with the same name exists on a target system then
- If no REPLACE option, then nothing happens, the EXPORT fails
- If REPLACE, no volser, then the IODF is replaced on the same volume
- If REPLACE, a new volser is specified, then the existing IODF is deleted and a new IODF is allocated on the specified volume ... of course, HCD has to check if this output volume exists.
Since the content of our next release is already defined, we will move your request into our long-term queue.
Kind regards,
Your HCD Team
Creating a new RFE based on Community RFE #84833 in product z/OS.