It does, yes. Or so the documentation claims; I'm still debugging so I haven't confirmed it yet, but I believe it. When I wrote the below, I was depending on the note that says LMCOPY is for copying members; I hadn't yet gotten around to reading the details. Sorry for the trouble, folks.
--- Bob Bridges, [email protected], cell 336 382-7313 /* Helpdesk tip #2: When the support analyst says "Click...", wait for the rest of the sentence. */ -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Tuesday, April 13, 2021 21:34 According to: https://www.ibm.com/docs/en/zos/2.4.0?topic=lmds-parameters Doesn't LMCOPY operate on PS data sets ("flat files") simply by omitting the from-member-name and to-member-name parameters? The restriction of LM services I have encountered is the data-ids must refer to F1 DSCBs; they can't operate on tape, spool, or UNIX files. --- On Tue, 13 Apr 2021 19:56:49 -0400, Bob Bridges wrote: >I'm writing a REXX to copy a bunch of datasets. The input datasets are >catalogued; the output is to be >uncatalogued and written to a particular DASD volume. I figure to use LMCOPY >for PDS members, and for >flat files - since ISPF doesn't seem to have an analogous command for them - >SMCOPY. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
