Thanks, this is encouraging. (We're still trying to figure out a non-disruptive non-chaotic way to test with SMS on for tape.) If we run this step for DASD
// EXEC PGM=IEFBR14 //SMSDSN DD DISP=(NEW,KEEP),DSN=any.SMS.name,UNIT=SYSALLDA,... the data set gets cataloged even though not requested. Then a second run of the same step then fails because of dup name in the catalog. If this step can be run multiple times with UNIT=TAPE, then I think we'll be fine. Again, we don't know how common this practice is, but we don't want any nasty surprise. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Erika Dawson Sent: Wednesday, July 17, 2019 10:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SMS for tape With system-managed (SMStape), we SMS-manage the tape libraries and tape volumes and we do not manage the datasets on the tape volume (we leave this up to the tape management system and the application that owns the data). And though we use an ICF catalog for our meta data (tape volume and tape library-related information) we do not require that the tape datasets on an SMS-managed volume be cataloged. This is where we differ from SMS-managed disk where the datasets are cataloged. And with SMS-managed tape, the ACS routines and constructs are then used to manage the tape volumes and tape libraries. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
