My first thought on this topic was that it sounds like a can of reconstituted worms. We use REPLACEUNCONDITIONAL and RENAMEU to migrate (mainly zFS) files from the SMPE target environment to production, but we know where we're going, what we have already, and what the result should be, so we 'hard code' the new names via a dialog that generates the job(s). The idea of arming a DSS RESTORE job with wildcards and unstructured renames or replaces is pretty scary.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Elardus Engelbrecht Sent: Tuesday, May 24, 2016 9:24 AM To: [email protected] Subject: (External):Re: ADRDSSU renamunconditional Paul Gilmartin wrote: Paul, I must say, many thanks for your posts and your 1001 questions. It surely must stirred some lazy idle brain cells awake somewhere! ;-) >>You must renunc the same number of qualifiers as it is documented in the >>manual. >What's the rationale for this restriction? Is it a holdover from an era when >catalogs were structured according to the hierarchy of qualifiers? Feels like >RFE material. AFAIK, I think it is something about handling duplicate datasets before, during and after copy. Will there be a duplicate before or after copy+rename? What about this example, say A.B.C.INPUT is to be renamed according to RENUNC(A.B.**,A.B.C.**)? What will you do with this tricky part? Accept rename? Reject it? What if either the old and/or new dataset is/are already there and catalogued? If accept, will you handle the result as A.B.C.C.INPUT or simply reject that? Forget for a moment whether the new name is already catalogued or not. There must be a practical, but undocumented reason for that. Perhaps as you suggested it is a good RFE material. >I understand there's an ISV product that suffers no such restriction. How do they handle it? Just curious. Don't name them, just tell us if you can. >>Not easy but simpler than using ISPF Edit. >Even with Edit macros? Or use some parsing instructions in REXX. Or use CSV and send over to Excel, process it and send back for final processing by DFDSS. > Regular expressions are available nowadays. I get it for regular expressions. But, on native TSO/ISPF? Please educate me. I'm sure I must missed something while RTFM. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
