Currently DSNTINST clist abends when using TSO/E EDIT macro that is unable to use temp datasets on EAV volumes.
|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.
|Customer Name||Alexander Dashevsky|
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