IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Change DSNTINST CLIST to allow temporary TSO/E EDIT datasets 'userid.editutil%' allocated on non-EVA volumes

Currently DSNTINST clist abends when using TSO/E EDIT macro that is unable to use temp datasets on EAV volumes.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 29 2020
  • Under Review
Who would benefit from this IDEA? As a customer, I would be able to run the DSNTINST clist without manually pre-allocating temp datasets.
How should it work?

I suggest to modify DSNTINST CLIST in such way that either on Panel DSNTIPA3 you may ask customer to fill in the non-SMS volser with or without nonsms storage group name, and then in similar fashion as DB2 does on panel DSNTIPT when it allocates **.NEW.SDSNSAMP etc datasets, allocate 'userid.EDITUTL1' and 'userid.EDITUTL2' on the volser provided by user/customer on Panel DSNTIPA3 for example.

The workaround is to either manually allocate temp datasets on non-SMS managed volume, or to modify ACS routine to force the allocation of temp datasets to a SG that allocates such datasets on non-EAV volume.

Idea Priority Medium
Customer Name Alexander Dashevsky
  • Attach files

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 "anonymous@euprivacy.out" 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