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).
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.
I see you created https://github.com/ansible-collections/ibm_zos_core/issues/1164, which will be used to track this enhancement request. Closing this ticket out.
Please don't hesitate to open any new requests for Z Open Automation Utilities as needed.
Thanks for your submission. This does not look like a Z Open Automation Utilities request, however. Would it be possible for you to file it in the Ansible for IBM z/OS Core Collection repository?
You can find the repository here: https://github.com/ansible-collections/ibm_zos_core
By the looks of it the documentation metions that the restore will occur to the HLQ of the user invoking it if there is no hlq: parameter specified
"- name: Restore data sets from backup stored in the UNIX file /tmp/temp_backup.dzp.
Use z/OS username as new HLQ.
zos_backup_restore:
operation: restore
backup_name: /tmp/temp_backup.dzp"
I can understand that if you create some infrastructure datasets that are linked to a service via a specific HLQ upon restore you would like to restore them to the same HLQ when they were backed up.
Here you are looping through a list and you would have to track the HLQ (and probably also LLQ) specific to this service either in the backup dataset name or a separate file - which can be troublesome.
THere should be a parameter of some sorts that mentions that the restore should be done with the original HLQ.
Same as it's done natively by SMSDSS ADRDSSU program when doing backup and restore.