For automation we require the ability to generate MIG with DATA via a batch job with no foreground input. This is to enable the whole process to be automated via zosmf workflows.
So, for instance, there may be a requirement to generate unloads and loads for thousands of tables. We wish to be able to provide the list of tables via a file to a generate job which will then create the unload /load jobs.
Currently, you have to create an object selection list in Admin Tool. You can then generate a batch job which will then generate the unloads and loads. We want to effectively replace step one where instead the object selection is provided in a file.
Without this we have no way to provide a dev ops solution without writing our own rexxes to manipulate the Admin Tool ispf tables directly. This is, for obvious reasons, something that we want to avoid having to do.
Although important for dev ops, this is also important for other automation such as generating unloads and loads from production to test and creating 'backups' of test environments when image copies cannot be used due to table structure changes.
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions